Multiple device failure (Code 12) after Windows 10 Creators Update

Hi Jodi,

quote: "I renamed  Renamed pcmcia.sys to pcmcia.sys.old - Rebooted windows."

After you rebooted and the network adapter and other devices work again, have you renamed the pcmcia.sys.old back to pcmcia.sys? In my case, renaming the pcmcia.sys.old to the original name made my pcmica card functional again and windows (funnily) did not run into the previous device manager issue. For the moment, my system is running winversion 1803, the pcmcia.sys is present (re-renamed), everything runs well and I am now waiting 6 months, how it works with a new major update.

If you go through the update process and installing several major updates in a row, you could check whether the re-renaming after the first update runs fine with the next update you do. Presumed you do such kind of update process.

However, it seems clear that renaming pcmcia.sys to pcmcia.sys.old without re-renaming just presents a temporary workaround - which actually I personally can live with.

Best Regards,

Sebastian

For the record I renamed  Renamed pcmcia.sys.old  back to pcmcia.sys - Rebooted windows."

and I'm back to Multiple device failure (Code 12).

I'm going to take it a step further and copy the pcmcia.sys from my other system which does not have this issue and overwrite the pcmcia.sys on the failing system.  

If all else fails I will Rename pcmcia.sys back to pcmcia.sys.old and call it done. 

Thanks again.

Jodi

Hi Jodi,

quote: "I renamed  Renamed pcmcia.sys to pcmcia.sys.old - Rebooted windows."

After you rebooted and the network adapter and other devices work again, have you renamed the pcmcia.sys.old back to pcmcia.sys? In my case, renaming the pcmcia.sys.old to the original name made my pcmica card functional again and windows (funnily) did not run into the previous device manager issue. For the moment, my system is running winversion 1803, the pcmcia.sys is present (re-renamed), everything runs well and I am now waiting 6 months, how it works with a new major update.

If you go through the update process and installing several major updates in a row, you could check whether the re-renaming after the first update runs fine with the next update you do. Presumed you do such kind of update process.

However, it seems clear that renaming pcmcia.sys to pcmcia.sys.old without re-renaming just presents a temporary workaround - which actually I personally can live with.

Best Regards,

Sebastian

quote: "I renamed  Renamed pcmcia.sys to pcmcia.sys.old - Rebooted windows.

I did not rename it back. The PCMCIA is of no use to me anyhow.

Renaming pcmcia.sys to pcmcia.sys.old and rebooting did do the trick for the majority of the drivers and after updating its still working. 

I have installed a pile of updates without renaming it back and so far so good. 

 I think I can live without the pcmica card.

Although I agree there is no reason MS hasn't addressed this bug.

Thanks again,

Jodi

Hi Jodi,

quote: "I renamed  Renamed pcmcia.sys to pcmcia.sys.old - Rebooted windows."

After you rebooted and the network adapter and other devices work again, have you renamed the pcmcia.sys.old back to pcmcia.sys? In my case, renaming the pcmcia.sys.old to the original name made my pcmica card functional again and windows (funnily) did not run into the previous device manager issue. For the moment, my system is running winversion 1803, the pcmcia.sys is present (re-renamed), everything runs well and I am now waiting 6 months, how it works with a new major update.

If you go through the update process and installing several major updates in a row, you could check whether the re-renaming after the first update runs fine with the next update you do. Presumed you do such kind of update process.

However, it seems clear that renaming pcmcia.sys to pcmcia.sys.old without re-renaming just presents a temporary workaround - which actually I personally can live with.

Best Regards,

Sebastian

I see this hack having to be applied with every major update.

Since my last reply the system became unusable and would not boot past the Windows startup ring... 

I wiped the drive and re-installed the original Windows 10 pro. No issues! I spent a couple of hours gathering and reinstalling all my programs. I spent the better part of the night and completely  re-configured the system.  Overnight Windows auto update updated this system 1709  OS Build 16299.125 and I'm back to Multiple device failure (Code 12) after Windows 10 Creators Update.

This is so frustrating.

I renamed  Renamed pcmcia.sys to pcmcia.sys.old - Rebooted windows.

Devices restored, windows is updating again. We'll see what happens after the updates.

I see this hack having to be applied with every major update.