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

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

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

Sebastian,

In case you were wondering, 

Overwriting the pcmcia.sys caused a page fault and the system wouldn't boot. Now to restore the system (from the restore point I created before I overwrote the pcmcia.sys), rename the pcmcia.sys back to old and call it fixed. 

Thanks 

Jodi

Just updated My Sony Viao VGN-240E to Winows 10 1803 and had this problem.

This thread was spot on, the registry fix didn't work but re-naming the file did. I didn't name it back and deiced to just leave it as a .old file

Thank you MaBow, MikeMiCal, SamuelLazarin and Rainer Germany. 

The walk-through on taking permission of the file to rename it was especially helpful. 

After a reboot everything started working except for just 2 unknown devices and a quick google search of

VEN_104C&DEV_803B

Took me to this thread,  Link

IDCam replied on

I know this is an old thread however I've put Win10 on a Sony Vaio VGN-FZ11M and came across this missing driver.

After a search I came across this link:

ftp://ftp.vaio-link.com/PUB/VAIO/ORI...R\_2.0.0.19.ZIP

Download extract and then run the setup.exe

Driver now installed although I've not tested yet.

a Second search of

ACPI\SNY5001

Lead to me downloading the Sony Firmware Extension Parser Driver right from the Sony support website.

There are no windows 10 drivers available for these but so far so good with installation of the windows 7 drivers.

Cheers and thank you!