[Solved] eGPU error 12 fail after update to Windows 10 1903 or newer (OS Build 18362.329 or newer) inc downgrade pci.sys version solution
Is anyone else having issues with updates being forced to run even after being disabled in Group Policy?
I disabled updates using the exact steps in the original post, but after one or two restarts, the system will automatically install an update the next time I go to reboot. it breaks my eGPU functionality and I have to manually uninstall it every few days. What am I missing?
(sorry if this has been covered in the previous 79 pages, I just couldn't read through them all)
It is discussed I am pretty sure in the pages.
You can only disable the updates for a fixed period, when they tend to re-enable themselves. I have just make sure I have a restore point after every round of patch updates. Have not had much issue with the bootcamp eGPU combo after patch updates. I tend to not install the big feature update incase it decides to replace the PCI.SYS file as part of the feature update.
@daniele_pugliese, There is is a typo in the post, I spent a lot of time trying to get the official windows ISO from the windows servers,
Under the "Uninstall Windows 10 Updates" heading you mention that the Build version is 18382.30 for Windows 10 ISO 1903 V1.
Uninstall Windows 10 Updates:
The May 2019 update is OS Build 18382.30, ISO file is called Windows 10 1903 V1.
But under the following heading , you see the OS Build version is 18362.30
Download Any Windows ISOs:
Also, a better way of downloading the ISO's would be using the FIDO tool - https://github.com/pbatard/Fido
This way you can be sure that the ISO is coming from the official windows servers and not a third party webpage.
I replaced my pci.sys with the one provided here, from then the system is stuck in a bootloop just after passing the loading screen, so I restored the original pci.sys but the system is now damaged with these symptoms: unable to load the control panel, settings or any of its modules. I tried with chkdsk / f / r at boot, which resulted in 5 phases, with final BSOD (black screen, no pointer), it is also impossible to complete a sfc / scannow or DISM.
eGPU is not always recognized as before and there are new screen glitches that force me to turn off the MacBook.
Update: I was able to run a surface test using third party software and after several attempts with chkdsk on reboot without success, I was finally able to run it to completion from the advanced boot menu. Still can't finish sfc / scannow or DISM, I need to re-download my Windows build and specify the source for restoring the corrupted files. Currently when I restart Windows or in other situations, the screen glitches no matter what GPU it is.
Update 2: by adding the / Source option to DISM, I was able to complete the recovery of damaged components from the original disk image from which I had installed Windows. Currently the system works fine but the external GPU is not recognized every time it is detected at boot.
I'm still trying to get my setup going, but in reading I ran across this and just wanted to comment.
I've noticed (over the dozens of attempts!) that while maybe the bootcampdrivers don't make an end difference for the Mac mini (with no dGPU), they often actually install, whereas the AMD ones fail. I think this might be because the AMD ones do more checking on the hardware. Mat's seem to just install.
So, I've gotten farther by using bootcampdrivers, even on the Mac mini. (Still can't get rid of error 12... going to try once more on 1903 with pci.sys swap, and then maybe go back to 1809 and just deal with not having some of the newer stuff for now.)
I replaced my pci.sys with the one provided here, from then the system is stuck in a bootloop just after passing the loading screen, so I restored the original pci.sys but the system is now damaged with these symptoms ...
I don't think the pci.sys swap works beyond a certain Windows version. I hosed my 20H2 install attempting this as well. It is important (I *finally* noticed!) to keep in mind the post dates as you read through this thread. People are talking about 'the latest version of' and such, but that's back a couple years ago.
@cgwerks, This is stupid and typical of Windows. The GPU is connected, it is ALWAYS recognised and loaded into apple_set_os.efi. Then the system proceeds to boot up and with a bit of luck, estimated at 50% of the time, Windows recognises the connected video card. I say almost because if I put the system to sleep or hibernate the eGPU is ejected without the possibility to reconnect it as it happens in macOS, however solvable by leaving the eGPU always on.
@francesco_ripa, Unfortunately, I haven't even gotten that far yet. And, yes, it is absolutely crazy of Windows to get hung up or not properly recognize hardware like this in 2021. I'm taken back to my IT days of changing jumpers on Ethernet cards and having conflicting addressing, etc. It is kind of crazy. (It's good though in a way, because every time I get ticked off at Apple, I have to use Windows for something and re-learn how the grass isn't greener...)