It doesn't smell like a rat - it smells and behaves like a virus and the response from MS has been as if it were a virus ("it's the fault of someone else" and so "roll your system back to a known good state"). For me, so as to continue with my same hardware it's not Apple as the alternative but Linux... The risk of Windows dropping hardware off a system (and the associated time and resources to go back to "the last known good state") is not acceptable & I've begun setting several critical machines as dual boot as a contingency...
Multiple device failure (Code 12) after Windows 10 Creators Update
Hi all,
I was given a computer to fix that showed multiple 'This device cannot find enough free resources that it can use (Code 12)' errors in the Device Manager. It is a quite old Sony VAIO VGN-N29VN.
I reinstalled Windows from scratch but the problem reappeared after applying the Creators update. As of now, multiple devices show the Code 12 error and are unusable. In some cases, there are multiple errored entries and one good entry for a given device (e.g. Intel 945 integrated GPU). In other cases, there is only one errored device and the device isn't working (e.g. WiFi or wired network adapters.)
The peripherals showing the errors are the following:
- Mobile Intel 945 GPU
- Intel 82801G ATA controller
- Texas Instruments 1394 OHCI controller
- LAN-Express AS 802.11g PCI-E adapter
- Marvell Yukon 88E8036 PCI-E Fast Eth controller
- HD audio controller
- various PCI to PCI bridges
- three Inter 82801G USB controllers
Some of them are usable (as they appear twice or three times in the Device Manager, others are not.) It looks like the update broke something, as this happened twice and I haven't added or removed any internal or external peripherals. What can I do to fix the problem?
Thank you.
Moved From:
Windows for home | Windows 10 | Devices and drivers
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
107 answers
Sort by: Oldest
-
Anonymous
2018-01-13T20:16:57+00:00 -
Anonymous
2018-01-13T20:21:49+00:00 Mr. Bar
Why is the update causing so many instances of "Corrupted system files..."? If I could understand why, then perhaps I can deal with the issue... Is this update still being pushed out to us? If so, how do I turn it off / prevent it from installing on the other machines on my system?
-
Anonymous
2018-01-14T12:30:04+00:00 Same issue for my ACER 9410.
- Mobile Intel 945 GPU
- Intel 82801G ATA controller
- Texas Instruments 1394 OHCI controller
- LAN-Express AS 802.11g PCI-E adapter
- Marvell Yukon 88E8036 PCI-E Fast Eth controller
- HD audio controller
- various PCI to PCI bridges
- three Inter 82801G USB controllers
They do not solve and this is very suspicious. They simply reveal their purpose:
FORCE PEOPLE TO REPLACE OLD DEVICES so new devices will be sold, more Windows will be sold etc etc etc.
A problematic software THAT HAS BECOME WORST THAN SILLY ANDROID. And the worst is that Microsoft is paid for this and paid too much. New programmers hired by Microsoft know nothing in comparison to their predecessors.
The only possible solution is to temporarily ?? stop Update v1703 by using:
http://download.microsoft.com/download/f/2/2/f22d5fdb-59cd-4275-8c95-1be17bf70b21/wushowhide.diagcab
and uncheck the box "Apply Repairs Automatically" then Next, then wait for a while and from list uncheck "Feature update to Windows 10, version 1703 or 1709"
-
Anonymous
2018-01-17T09:47:41+00:00 Before my old Toshiba applied the Creators Update, Windows Update said it could not install security patches until an update was applied. I suspect the Code 12 error means curtains for the 11 year old machine or a migration to Linux.
-
Anonymous
2018-01-18T11:25:40+00:00 Same problem with my 9-year old Toshiba Laptop. 1607 OK 1703 and 1709, no go. This is a 32bit machine. Could it be that the automatic update installes a 64-bit version for some reason thereby affecting the devices drivers?
I did not get a warning that 1703 or 1709 would cause problems. Might the solution be to install manually the 1709 32 bit version from USB stick?
I'll try this sometime next week.
Regards, Teunis