New
#1
Windows 7 Startup Repair Superbug
Let's get straight to the point:
The Windows 7 Startup Repair Utility included on the Windows installation disk is there to help us repair problems which may arise during the use of our computer and which may prevent the OS from starting, loading, booting (call it whatever you like). Throughout my experience of the past 2 days, I have learned to undoubtedly deny it. Why, you may ask? Well here is the story.
Throughout the last few months my Toshiba laptop (kinda figured it is not the best out there by now) has grown to hate me. At times, the OS would simply refuse to load, presenting me with the classic blinking cursor in the top corner of the screen.
Well, I have decided to fix the situation (which was clearly broken, not only by the above, but even when Windows did manage to load, it would immediately get slowed down to a halt thanks to all of the Toshiba crapware loaded on it! ). Now, let's get this straight: I know my stuff. I have done stuff like this countless times before. This is the first time something this (excuse me) shitty happened to me. I literally felt like pulling my hair out. So, 2 days ago I decided to reinstall Windows fresh on the 500GB HDD sitting in there.
Like any smart man should do, I first backed up all of my stuff to an external hard drive. Great, no hell beyond this point. Just like with any other OS re-installation, I booted the computer of the Windows 7 Ultimate 64-bit Setup Disc. Immediately proceeding to the partition selection screen, I encountered a friendly message:
"Windows cannot be installed to this drive because this computer's BIOS may not support starting from it."
Obviously, I proceeded to the BIOS setup to switch the SATA controller mode from "AHCI" to "Compatibility", as clearly I could not have installed it otherwise. Back to the setup disc, I no longer saw the alerting yellow icon. Great. Here's what I did next.
I had 3 partitions on my drive:
- System Reserved - The current OS's boot manager. (Should be obvious)
- No label - Largest partition on the drive, held all of my system and private files.
- HDDRECOVERY - 11.5 GB partition holding Toshiba's greatest invention; the "Recovery" partition. I should also mention that when attempting to recover later from this partition AFTER removing the previous 2, I got quite disappointed to know that I couldn't for similar reasons as stated above.
At first, I left the HDDRECOVERY partition intact. Just in case. Installation finished, the computer restarted, Windows loaded up saying "Updating Registry settings" and "Configuring Services" and finally the moment we have all been waiting for: "Completing installation...". Ah...... not so fast. It took it approximately half an hour to complete that last step before restarting another time. Sitting there all filled with tension, I waited.... and waited.... and waited.... and ... .. Ok, it started to seem ridiculous. All I saw in front of me was a blank, black, screen. And nothing else. Not even a blinking cursor in the top corner of the screen. Nothing. By this time I figured I need to start the Windows Startup Repair program. After I entered the "Repair my computer" section, Windows told me it found problems with my startup configuration and offered to fix it. I thought; "Great, it even figured it out by itself." After restarting yet another time, I was sadly exposed to the same blank screen. After rebooting into the Startup Repair option a few more times, it told me Windows Startup Repair was unable to fix the problem because of a corrupted MBR, which IT WAS SUPPOSED TO FIX!!!! Clearly, at this point, it got so pointless to try to use it to automagically repair shit, and I had to do the rest myself.
Since then I have tried countless procedures (including reloading the Win7 bootloader using the ms-sys program from a linux live cd, and also checking the MBR using the linux disk editor), all to no avail. But all was not lost, as I got to the point where I removed all of the partitions from the drive (including HDDRECOVERY, which I have found to be useless and unable to recover anything) and reinstalled Windows 7 on the drive (that is the state of my HDD right now, as a matter of fact).
On with the story, I was able to boot into Windows (somehow magically) by performing the following sequence of commands:
- Start Windows Repair from the installation DVD.
- Skip through the dialogs, until you get to the list of available options for recovery.
- Open the Command Prompt and change the current bootloader from BOOTMGR to NTLDR by issuing the following command:
Code:bootsect.exe /nt52 ALL- Restart the computer, and let Windows issue the following error:
Code:NTLDR is missing. Press Ctrl-Alt-Del- Start Windows Repair again, open the command prompt (again) and repair the boot sector on all drives using the following command:
Code:bootrec.exe /fixboot- Repair the BCD store (partition table, I believe) by issuing:
Code:bootrec.exe /rebuildbcd- Change the bootloader back to BOOTMGR by entering:
Code:bootsect.exe /nt60 ALL- Repair the MBR (although I believe this step is not necessary) by issuing:
Code:bootrec.exe /fixmbr- Restart the computer and admire your hard work (if in case it has succeeded)
- After enjoying your new Windows installation, shut down the computer.
- Restart and see all of your hard work go to waste.
- Go to step 1!
Clearly, upon shutting down the computer, Windows seemed to have overwritten the partition table or boot sector. I would like to add that I have not changed the SATA controller mode back to AHCI yet.
Finally, I want to ask:
How would I go about fixing this damn, ****ing, problem???
Thanks in advance,
superbug
PS: I signed up to this forum just to post this, and I think that this may be a Windows bug or a driver problem.