November 10, 2015

Windows Update hates me

I run Windows Update on my HP tablet first before I let it get anywhere near any of my computers that I care about. That's because I want to make sure that each new batch of patches doesn't brick my real computers.

It may have happened today. I just finished running the update, and the tablet was doing the restart, and now the screen is flashing, alternating between black and the Windows login backdrop.

I'm going to let it run like that for a couple of hours before I try shutting it down and starting it again, but I have a feeling it's toast.

And I won't be updating any of my other computers for a few days.

UPDATE: Well, I gave it one hour, and then tried to reboot it, and when it came back up it did the same thing. It appears to have been something trying to run during the reboot.

I plugged in my USB keyboard and managed to get it into safe mode, and now I'm doing a system restore to a save point from a week ago. Here's hoping...

UPDATE: And it's back! (Whew!)

Posted by: Steven Den Beste in Computers at 12:00 PM | Comments (4) | Add Comment
Post contains 194 words, total size 1 kb.

1 I used to have auto update turned off and manually review updates for installation myself at some later date.  Only once in many, many, years did I decide that no, I wouldn't install an update, so I went ahead and turned it on.  That would have been back in the days of Windows XP.  I've been letting windows update at will since, and I've only once had a significant error, where a patch was failing to install, and kept popping up notices about needing to reboot and refusing to shut down, but that machine was still entirely functional until I had the time to google the patch number and how to clean it up.  Once, a security patch did valid things that a bunch of games took offense to, but that was the fault of those games that were relying on a security hole, not Microsoft or Windows Update.  A couple of times reviewing the literature revealed that a security patch, wasn't, and I recall once that the advice was to remove that patch as you were better off with the original unpatched flaw, but my normal manually supervised process would have produced the exact same result.

Posted by: David at November 10, 2015 07:37 PM (+TPAa)

2

My Acer NAS runs Windows Home Server 2003. Or I should say "ran". Now it doesn't run at all.

Last spring it got bricked by Windows Update. After installing patches, it hung during reboot. And it has never booted since. I eventually gave up and unplugged it.

That was where I kept my anime, and it all vanished into the bit bucket. I've redownloaded all the important stuff onto my other NAS, and I'm hoping that it doesn't die on me too.

Posted by: Steven Den Beste at November 10, 2015 07:43 PM (+rSRq)

3 That sounds like the NAS was just a ticking time bomb waiting to die on the next reboot.  I've lost a few "leave it in the closet and don't touch it for a year" machines that way, including an Acer WHS NAS like yours.  That one died to the point where I couldn't even get it to rebuild itself from the installation media.  My torrent ratio took a major hit rebuilding my collection after that, since of course the NAS was my main storage repository and I didn't happen to have backups for all 5tb of the data that was on it.  That said, servers and automatic updates don't mix, you're right. 

Posted by: David at November 10, 2015 10:53 PM (+TPAa)

4 I wasn't using automatic update on that server. It died after I did a manual update.

Posted by: Steven Den Beste at November 11, 2015 12:06 AM (+rSRq)

Hide Comments | Add Comment

Enclose all spoilers in spoiler tags:
      [spoiler]your spoiler here[/spoiler]
Spoilers which are not properly tagged will be ruthlessly deleted on sight.
Also, I hate unsolicited suggestions and advice. (Even when you think you're being funny.)

At Chizumatic, we take pride in being incomplete, incorrect, inconsistent, and unfair. We do all of them deliberately.

How to put links in your comment




What colour is a green orange?




10kb generated in CPU 0.0, elapsed 0.0096 seconds.
22 queries taking 0.0059 seconds, 23 records returned.
Powered by Minx 1.1.6c-pink.