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

These hacks work:

(Original 04.04.2018) Thank you MaBow and MikeMiCal - I worked with your suggestions.

(Updated 07.04.2018) Thank you SamuelLazarin for having confirmed that it's working.

Solution by registry hack*:*

(Update 07.04.2018 from a reply by Le Hobo Bob:

"A much simpler way that won't get undone by sfc or corruption repair and doesn't require complicated steps to take permissions on files would be to disable the driver service in the registry, I've tested this on Toshiba Satellite A135 and it works (well, other than my SD card reader which uses pcmcia not working anymore, everything else was fixed):

* hit start

* type regedit, hit enter

* accept prompt

* navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\pcmcia on the left

* Double click "Start" on the right and change the value to 4 (the default is 0)

* Reboot"

//End Update)

COMMENT: By resetting the registry value back to default and rebooting, the pcmcia service might work again without causing the failure. Should be tried.

Aparently it also should help to shove in any PCMCIA card, though in my case that solution didn't help. However, renaming files did the job and the update from Windows 10 version 15xx/16xx to the creatore's update versions 1703, 1709 and 1803 is operating well. After your Windows 10 got updated and your network hardware gave up while the device manager went to apocalypse by showing multiple device failure / errors (code 12) try this hack:

Solution by renaming pcmcia.sys*:*

Before starting, make sure you are logged in with an account having administrator permissions ascribed. Also, you need to enabled 'all files visible' and 'file extensions visible' in the file explorer. If you don't know what this is or how to do it, ask a technican to guide you through and rather don't continue alone.

1.) Open the folder: c:\windows\system32\drivers and find the file pcmcia.sys

2.) Change the file access permission to 'full control' as follows:

2a.) Right mouse click on pcmcia.sys - choose 'properties' - choose the tab 'Security' - click button 'Advanced' for special permissions - a new window opens called 'Advanced Security Settings for pcmcia.sys'

2b.) In the new window you see 'Name' in the first line and 'Owner' in the second*.*In the owner line Click 'Change' - a new window opens called 'Select User or Group' - click button 'Advanced...' - a new window opens also called 'Select User or Group'- click 'Find Now' - in the lower part of the window you see 'Search results' - Scroll to the 'Name' that equals your user name and that shows your PC name under 'In Folder' - click (highlight) your name and click 'OK' - the current window closes -you returend to the first 'Select User or Group' window - click 'OK' - window closes and you are back to 'Advanced Security Settings for pcmcia.sys' - check whether the owner now is your user name and click 'OK' - you might get ask for confirmations and get system info pop-ups which all need to be acccepted or confirmed.

2c.) You are back in window 'pcmcia.sys properties' - in the list 'Group or user names:' choose your 'Users (PC-Name\Users)' - in the lower part of the window change the 'Permissions for Users' by ticking the check- boxesto 'Full control' and 'Modify' - then click 'OK' - confirm the corresponding security warnings.

3.) Rename pcmcia.sys to pcmcia.sys.old - Reboot windows

Either problem solved or continue with 4:

4.) Open folder *c:\windows\system32\driverstore\filerepository* and find the folder *\pcmcia.inf_amd64_(hashtag)* - Right click and change permissions for the user 'Everyone' to enabled 'Full control' and 'Modify' - you might have to go through the process of step 2a-c.

5.) Open folder c:\windows\system32\driverstore\filerepository\pcmcia.inf_amd64_(hashtag) - rename pcmcia.sys to pcmcia.sys.old- rename pcmcia.inf to pcmcia.inf.old - Reboot windows

The multipe device failures (Code 12) should have disappeared. The WLAN/LAN should be functional and connect again.

After all this completed, I have renamed all three files to their original name, then rebooted and it STILL WORKS including the PCMCIA card**.** I also recommend to change all permissions of files and folders back to the original setting.

Further help: The following website explains how to get the required rights: https://www.drivereasy.com/knowledge/you-require-permission-from-trustedinstaller-error-fixing-guide/

Please let us know whether it has helped.

Best regards and good luck,

Rainer & Sebastian

Have a look at the stream I had replied to:

.

.

Solution by registry hack*:*

(Update 07.04.2018 from a reply by Le Hobo Bob:

"A much simpler way that won't get undone by sfc or corruption repair and doesn't require complicated steps to take permissions on files would be to disable the driver service in the registry, I've tested this on Toshiba Satellite A135 and it works (well, other than my SD card reader which uses pcmcia not working anymore, everything else was fixed):

* hit start

* type regedit, hit enter

* accept prompt

* navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\pcmcia on the left

* Double click "Start" on the right and change the value to 4 (the default is 0)

* Reboot"

//End Update)

.

.

.

Good day.

The responses for Drivers continue to be baffling on here when people come on with older hardware.

The users has an Intel 945 Express based system probably built around 2005-2007 or so when that chipset was used a ton in devices around the end of XP and beginning of the Vista and 7 Era. 

Anyway, this chipset has worked fine in Windows 10 up until the 1703 update. Once 1703 or 1709 is installed, The device manager looks like a bomb went off and a bunch of devices have the yellow exclamation point on them with most all having the Error Code 12. Another weird bit is there are multiple of the same device showing (so normally 1 945GM Graphics device, now shows 3 with 1 working, and 2 that should not be there, with the errors as described showing). 

So far I have yet to find a working fix and while restoring to a previous 1600 based build is a temporary solution, it really isn't an optimal one as the devices may be old, but are in no way incapable of running Windows 10 all this time before this update came along and shotgunned the device manager and made the device run immensely worse because of it.

I will keep this thread updated if I find a fix. If Windows 10 intentionally breaks all the hardware running on the 945 chipset, that is going to be a huge number of older but still capable devices completely abandoned for no other reason than "Just Because" at this point.

Inserting an old PCMCIA card or renaming the pcmcia.sys driver file to pcmcia.old fixed this for me as it has done on many laptops using this chipset.  Google is your friend.

Hallelujah. Finally. I renamed the C:\Windows\System32\drivers file pcmcia.sys to pcmcia.old, as suggested, and my device manager is happy again (apart from the Mass Storage Controller). No duplicated entries, network adapters all good, PCI bridges all happy, USB universal host controllers working fine.

The hardest bit is configuring the access permission in the properties of the file.

Many thanks.