The issues with bad updates started before Windows 10 was released. You can easily fix the long search for updates and make it quick again, have a look at this thread.
I'm aware of it, I posted the original fix for it. Then there were the next 2 times they broke it... then I didn't care anymore.
Updates are overrated, used fully unpatched XP SP2 for 8 years until 2014 without any problemos. And lucky, I'm not. With those forced updates you are going to have problems, maybe not today or tomorrow, but you'll see ... soooooooon very soooon. And clairvoyant, I'm not.
There were many already, especially the one, which crippled Windows Update and in order to fix it, users had to download the fix manually. Luckily it was caught in the beginning, so MS pulled it down before too many users downloaded it. They should at least test it before releasing.
some are getting success with the media creation tool. I tried it today but could not check save all personal files and apps and did not feel like reinstalling all them so canceled the install. anybody tried an older image?
Windows Update failure rates are a significant percentage - as high as 30 % for some specific W10 updates. Even offline W10 updates will fail. For Enterprise or business user, the problems with W10 updates is a real headache. Logistically it is unreasonable to expect any user to perform a clean install of the OS to ensure that every single cumulative W10 update is installed without problems. This is why Enterprise versions of Windows allow for up to an 18 month delay when installing updates. Microsoft acknowledges that updates are often problematic and need bugfixes. That acknowledgement by Microsoft just doesn't apply to Windows home consumers any longer. Whereas before the user had the option to delay or not install updates, this is no longer true... as it is apparent that W10 home users are Microsoft's guinea pigs... so that Microsoft has a large test bed of systems to work out problems - at the home users expense - and then apply those fixes later and forewarn Enterprise users not to install certain updates until such time that the fixes are pushed...
the quality of updates have definitely taken a hit with windows 10 since the anniversary update. hyper v doesn't even allow me to start virtual machines rendering it useless. I kinda expected the pro version to be better in terms of updates but terms out i was wrong. some issues were detected during the insider previews for the current cumulative update of failing to install and causing other issues but Microsoft ignored this and pushed it anyway... the insider previews are meant to be the guinea pigs not the people running what should be a stable operating system.
It is discouraging, I know... I solved the slow update checking issue by doing a clean install of Win 7 SP1, then installing all of the Update Rollups thru August, including the August IE Cum Update, then I turned automatic updates on again, and did one last check, installed everything there, including all optional and recommended updates, and it's been great and working fine ever since in 7. I think it was the July Update Rollup and a subsequent re-release via Win Updates of the 605 July update fix that finally corrected the issue. In 10, everything has worked fine updating the AU edition, but I have seen bugs and issues which gives me the impression that I can't rely on 10 for daily use, even though I do like it overall. I have been using linux off and on, and could make do with that if I had to, but I still prefer Win 7, as long as it works well.
Later that day when I have posted my comment about the update I have noticed a sudden processor peak caused by Windows update installation service running in the background. It lasted a couple of minutes but without apparent disk activity. So I rebooted what triggered "updating machine, don't power off it" but nothing happened then. So I made the forced switch off. After that I have booted my machine without any problems and since than I have rebooted more than 4 times free of this weird behaviour. Everything's alright now. Yeah, Microsoft ...
@mantra ...sorry for the late reply. I am not worried, so much, that it updated....It is still version 1511, and not 1607. So, that is good to my way of seeing it.
A potential workaround for KB3194496... but I can't test it for about 7 hours: http://www.windowscentral.com/how-successfully-install-windows-10-build-14393222-workaround
jack I looked at your link and yes that will work. on my machine the update started, wanted to restart and I didn't restart. Instead I followed this link which worked and is a bit simpler. http://techdows.com/2016/10/fix-kb3194496-windows-10-fails-to-install.html
What in the name of ..., does a xbox task have to do with Windows Update and even preventing it from working? MS has gone mad, I am telling you. Ok, seriously, I guess it has something to do with Microsoft login, so I would guess, that people using Microsoft account had a problem installing the update?
Not likely a Microsoft account issue, as I am using the same account on two machines and one worked and the other failed. In any case I just got around to trying the workaround and it does work. It's nice to be done with the reboots and failed attempts, but I'm still mad at Microsoft.
Good guess I think. I'm not using Microsoft account for login and I have installed the update almost trouble free (OK some issue happened, described a few posts above, but nothing serious comparing to others).
in the page I posted I did not have to disable any services first. just deleted the XblGameSave folder and deleted the reg key.
Microsoft needs to stop running Windows 10 as a rolling distro. Give users the option of having an LTS version, like its business customers get with Windows Enterprise 10 LTS.
Yes, that, and also they need to rehire all the internal quality control and testing people that they laid off a few years ago, so they can start putting out a clean and polished product, instead of all this buggy stuff that isn't working....
Sweeping it all aside.. I simply want a system that doesn't nag me, doesn't get in the way, and is reliable. Not daily updates. I'm not a tester or developer.