Forum Discussion
After upgrade to build 17035 BAD POOL CALLER
How many people had this happened to? Am I just desperately unlucky to get it on 2 machines or is it very common? Do MS have any clue how ******* incompetent this is?
More practically... So how am I supposed to fix either machine when any attempt to do anything crashes it?
Feels good.
Curious if anyone from Microsoft monitors this and can provide help to NOT upgrade (again) to 17035. There are now two new releases out 17040 and 17046 but I still have 17035 in queue to install. How can we "skip" to 17040 or 17046 and avoid GSOD before the next version can be downloaded and installed? Anyone, anyone? Ferris Bueller maybe? ;-)
Don't know, I'm afraid.
What I can tell you is that I've managed to get windows reinstalled from media, but it was a real pain - e.g. full clean reinstall is the only option when you boot from media, and booting from media requires starting windows then doing shift-restart before GSOD, finally managed it on about the 10th go....
... back to your query - it can't be as simple as "check for updates", can it? If you're on fast ring that will bring up 17046 and surely they haven't put 17035 to slow ring have they?
Thanks for the reply Andy. Unfortunately there's no option to check for updates when there is a queued install pending. I surely hope 17035 is not going to ANY ring given the serious problem and many complaints about Bad Pool Caller and GSOD. I'm going to try 17035 and quickly try to get to 17046 via Windows Update before I GSOD. Failing that I'll be stuck on 17025 until Microsoft or someone had an idea on how to skip or reject the 17035 before it installs.
