New
#250
I hope when mS release this fix it will be a new KB number and fixes the AppReadiness issue as well.
I hope when mS release this fix it will be a new KB number and fixes the AppReadiness issue as well.
Yes I removed the XblGameSave folder and the registry key.
I don't understand what anything relating to XBox is doing on a release of Windows labeled "Pro" in the first place.
This update has failed multiple times on my system, is there any validity to the fix suggested here Getting s the Fix
This has failed on my homebuilt Asus F2 A85-M PRO (AMD) multiple times. I finally did the XblGameSave removal process and the KB ran OK, a little crazy that MS has not addressed this issue.
Last edited by GaryCN; 05 Oct 2016 at 00:27.
I took your advice and ran Wushowhide to hide the update. But this evening my wife got the "Required updates need to be installed" (or however it's worded) popup is it's high-powered incarnation - the one when Esc doesn't get rid of it. We force powered off and rebooted, and sure enough the update to be downloaded was KB3194496. I ran Wushowhide again, thinking I might have messed up the first time, but KB3194496 was no longer listed. So I guess it's hidden, but that doesn't seem to keep Windows Update from trying to download it. Any Idea what is going on? BTW, I realize that this is pretty tangential to news about KB3194496. And as an outsider, I don't belong in an insider thread. Should I move this posting to a different thread on a different sub-forum?
Damned if you do... Insider or wet behind the ears vanilla user, this CU is aimed at you!
If your PC is not able to complete the CU installation and it tries to rollback to the previous state time after time, you can waste hours at every restart.
I am guessing that telemetry is at the root of this b@stard of a problem, and when released to the small numbers of "Release Preview" Insiders, they realised there was a problem, that they just had not enough data to fix it, so they pushed it to the "Slow Ring" Insiders as well.
Now, Insiders are generally savvy folk, and they probably have the nous to avoid getting stung twice, or at least an alternative Windows installation to use in the event of an Insider cock-up, so the telemetry gathered by Windows Error Reporting (WER) possibly still did not present any common features to distinguish the Failures from the Successes.
This was partly because WER does not look at Successes - "nothing to report, move along there!"
So the development team broadcast the CU to all and sundry running 14393 in order to broaden their baseline of failures, to isolate the cause(s), and thereby to gain the knowledge to produce a fix.
So it may go to show that we are all Lab Rats or Guinea Pigs in the race to improve the push to get Windows (formerly known as ...10) on all PCs - you don't just have to be an Insider, and anyway you got it for free, didn't you?
I got this Update last Friday automatically.
But, I did not Subscribed any "Insider Build" what ever.
Do I am a Insider Group without knowing? How to disable this, my PC is production and I can not, nor I do not want, to go all that Beta“s Releases.
Build 187 had also problems installing, now 222 is also Broken.