chrishoffman at January 11th, 2014 06:40 — #1
Originally published at: http://www.howtogeek.com/179629/is-windows-update-broken-5-broken-updates-microsoft-released-in-2013/
What happened to Windows Update in 2013? Quality control seems to be suffering as Microsoft scrambles to update their software faster than ever. They’ve released quite a few buggy and broken Windows Updates this year.
straspey at January 11th, 2014 11:36 — #2
If you've ever taken a trip down to the depths of "Update Hell" - as I once did -- you know it's a place to which you never want to return.
In my case, as a result of my trip to Update Hell, the only place I could buy a return-trip ticket was at the computer-repair shop.
Since then, I now wait at least a full two weeks after the Patch Tuesday to see if there's problems arising from the updates. And I can also tell you that the list of my my "Hidden Updates" is somewhat lengthy, without having experienced any negative reprecussions.
I would like to also be very quick to add, that some of the BEST guidance and advice I have received over the past two years regarding my questions and anxieties over Microsoft Updates -- have been provided right here on the HTG forums, from some of our very knowledgeable and experienced friends.
ringhalg at January 13th, 2014 02:45 — #3
I always used to disable Windows Update and only wait for Service Packs to be released. Only then would I update my Windows. I enabled it because I experienced system slow down and for security reasons.
Any updates that affect the system (BSOD, as above), system files (System File Checker), or the device itself (firmware update), should be tested and retested before being released to the public.
belladea at January 15th, 2014 16:17 — #4
I wait about a month before applying updates to my company's servers, then I wait about a week before I release those same updates to customer servers. Yesterday I installed Exchange 2010 rollup 8 from December's patch Tuesday....it completely broke our exchange services - disabled all services, exchange related or no, then stopped IIS server and all sites (such as our OWA) and corrupted a base themes folders for the OWA site. Luckily we had a backup quickly available. All told it took us about 2 hours to undo what this patch did in less than 10 minutes.
system at January 21st, 2014 06:40 — #5
This topic was automatically closed after 10 days. New replies are no longer allowed.