This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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:
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:
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.
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.
And when I tried KB4073291-x86 it said 'The update is not applicable to your computer'.
It works. Thank you @MaBow. I renamed the pcmcia.sys driver file and reboot the laptop. No longer see conflict on the network adapters.
I'm not going to use PCMCIA card. So this work around is good for me.
I've googled it and all results indicate your renaming fix is for Vista kit being upgraded to Win7.
Although my machine was originally Vista, then 7, now 10 - are you sure this fix is appropriate for the issues we are experiencing with shot-gunned device managers?
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.
