Forum Discussion
After upgrade to build 17035 BAD POOL CALLER
Thanks for the info on 17040. I have the same problem with 17035. I installed it twice, once after reverting to 17025 with no issues. I still have the Bad Pool Call on the second install and am in the Recovery option go back to previous version (again) right now. Once its stable back on 17025 I will try to install 17040 and cross my fingers.
Dennis
HP Touchsmart 610f 8 GB, 1TB
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?
- Just happened to me after upgrading last night. I went the route of going settings>recovery>roll back to prev version but it crashed during the rollback and so I am no longer able to rollback.
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?
