Hipster Librarian v. Windows Boot Error


Imagine this: after a long day of typing/shopping/dowloading/whatever, you decide it’s time for bed. You get a little notification on your computer that says the machine will have to be restarted in order to install automatically downloaded updates. You dutifully shut it down and go to sleep. When you wake up the next morning and stumble bleary-eyed to your computer so that you can check the weather and avoid flinging your hand out the window in an effort to ascertain the temperature, the thing won’t turn on. All you get is a black screen with “Windows Error Recovery” at the top. If you choose “Launch Startup Repair (Recommended),” you go into a boot loop. If you choose “Start Windows Normally,” you go to a blank black screen.

When this happened to a friend, I was eager to try my hand at fixing it. So I picked up his laptop, did some research on the issue, and dove in. Here’s what I found:

This type of error is not uncommon. It can hit any computer that comes pre-installed with Windows. So, in all likelihood, it applies to you, whoever you are. Windows pushes out a ton of updates all the time ranging from security patches to software updates. Any one of these updates has the potential to seriously mess up your machine. Every time these system updates are pushed out (which happens monthly), a bunch of computers crash. This is because the OEM Windows installs have specs that are tied to the machines they inhabit, and Windows isn’t going to test their updates on every machine that has ever come stock with Windows. Unfortunate, eh?

The first thing I did before mucking about with the system was make a full backup of my friend’s data. Luckily, I was able to boot into safe mode by holding down F8 at startup. If that doesn’t work for you, I recommend doing a live install of a lightweight Linux distribution, such as Knoppix. That will give you access to the filesystem. From there, it’s as simple as dragging and dropping the files to portable storage. I recommend you do the same. I’ll wait.

After that, I downloaded a fresh copy of Windows and burned it to a disc. You can download official copies of the Windows ISO files here. Once you have the right one (check your documentation to see if you need the 32 or 64 bit version), burn it to a DVD or USB drive. I recommend using the official Windows 7 USB/DVD tool. It just makes things easier. I’ll tell you why in a moment.

A full system disc has a host of repair options on it. I ran all of them. None of them worked. The hardware was fully functional and the memory was good. The problem had to be with Windows itself. I booted back into Safe Mode and attempted to restore the system to a time when it was fully functional. And here’s where I go off about how bad Windows is.

I hate Windows. Automatic updates are recommended and enabled by default. These things have the potential to break your computer, as happened in this case. What’s worse? Each of those updates creates a new restore point. I had six restore points available to me, all stemming back to November 13, 2012 when the update was first rolled out. The problem? The boot error evidently resulted from the earliest update. So I could only restore the machine to an earlier broken version!

So that meant that I had to do a fresh install of the operating system. Luckily, I already had the data backed up and had a system DVD for recovery purposes. I was ready to go, if a bit annoyed that I had to wipe all the installed programs from the machine. I popped my fresh Windows 7 disc in the drive and clicked “Install.” Very quickly, I was warned that I was missing a driver for the CD/DVD drive. Without that driver, I couldn’t continue. And here’s where I go off about how awful Microsoft is.

To make a long story short, I wasn’t missing any driver. The official ISO I downloaded was corrupt. I discovered this by doing a hash check and comparing the file I downloaded with the hashes of ISOs known to be functional. That sounds complicated, yes, but it was fairly easy to ascertain. For one, the ISO I had was .48GB smaller in size than the one I had selected to download. That’s a lot of missing data. The USB/DVD tool mentioned above won’t work with a corrupted ISO, so if it won’t copy the files to your USB or DVD, your file is probably corrupted. Simple, but frustrating. It takes a couple hours to download one of those ISOs. I did it twice (both corrupted) before giving up and just torrenting the file. But I have successfully gotten good ISOs from the official site before. Your mileage may vary. I wish Microsoft would take more care in this aspect of their service. If their product worked correctly, these files wouldn’t even be necessary. But since it doesn’t, they are and they should make them more accessible.

Okay, so I created a good bootable ISO and went through the install process. Everything went nice and smooth. I transferred the data back onto the machine and everything is fully operational. It was just a pain to get there.

So, if this happens to you:

***Update: Please see the comments for an alternative approach to this problem that may allow you to skip a full reinstall.

1. Back up your data.
2. Download and burn an ISO of Windows 7 and try the repair tools.
3. If that doesn’t work, boot into Safe Mode and try to do a system restore.
4. If that doesn’t work, do a clean install.

Lastly, if your computer came with Windows pre-installed (which is most of them), consider turning off automatic updates. That way you can do research ahead of time to determine whether or not the update would be disasterous to your specific computer model. The security patches come out the second Tuesday of every month. Just wait until Wednesday and google your computer model and “update crash.”

If you have read to this point, you probably happened across this post through a Google search. I hope it helps. Understand, though, that I am not responsible if your attempt to duplicate my efforts results in things not working. đŸ™‚


6 thoughts on “Hipster Librarian v. Windows Boot Error

  1. You’re right. There are so many variations of PC hardware out there that Microsoft can’t test them all. Actually, I’m suprised this doesn’t happen more often. I’ve only run into this a handful of times where I’ve had to reinstall Windows. I recommend setting Windows Updates to download automatically but not install until you want to so you can manually create a restore point before installing or upgrading any software.

  2. Your post is only partially accurate. MS does not create the hardware so of course they cannot test. Linux and I love Linux, has the same issues but at the same time they also update applications often. Mac has a distinct advantage here since they do control the hardware.

    Not knowing the hardware in the article or the actual error makes this seem a bit vague. Personally I have never had to do a clean install after an update. I have had issues but most are solvable sooner or later. This could have been something easily preventable, select only security updates as automatic. Issues like this are almost always some driver and auto updates can be configured to download those too. The OS has very little interaction with the hardware and as such is not the reason for failures like this. An updated driver that is incorrectly identified will for sure. My last point is to run Linux. đŸ™‚ Pear OS looks and acts just like a Mac but for free.

    The real issues are usually drivers which Windows will download for you in the ‘Other Updates’ category. Be really careful with those.

    1. Thanks for the comment, Johnny.

      How would one go about discovering what the actual error might be? Is there a utility for figuring out an error code? As it was, the machine was stuck in a continual boot loop and didn’t display any error codes that I could find.

      Any help would be great, as the official Microsoft assistance (discussion boards, etc.) was useless. It’ll all have to be theoretical, though, since I already did the reinstall and that did fix the problem.

      1. I use BlueScreeView by Nirsoft. (http://www.nirsoft.net/) It is a small utility that helps identify what is in the memory dump file. Makes it human readable and gives you a better Google target in the error. I can pinpoint what is wrong much easier with this detail.

        Second you need to turn off the auto reboot on the Advanced Properties of the system. I also like to check the box for pausing on recovery options.

        One last thought, I have found in the past that many of these loops are caused by an update that just has not installed correctly and never will this go around. So once again the Linux CD comes in handy to go in and find the update logs. At the end will most likely be an answer to the loop and the offending update. Removing the update and any temp files, usually in some directory named like this: andoaoifinfoiehhucuubfjenvonebebjsnjsnncjsoch0w or some other gibberish, note the date in the details and remove the Windows Update folder from the Windows directory, it recreated itself and the system should start up again. If it doesn’t then the reinstall is an option worth taking.

      2. Great suggestions, Johnny. I had no idea the Blue Screen utility could be used for any other purposes. Guess I was fooled by the name. I’ll certainly try this route before a reinstall the next time I encounter a problem like this.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s