My Window 7's files got corrupted after a blue screen interrupted the update process, and I don't have a recovery or installation disc at the moment.
This nuisance occurred during an apparently bugged update process. Although I gave up on the never-ending process and unchecked all important and optional updates two months ago (which had only been happening for two weeks after a fresh install of Windows 7 64-bit SP1), Windows still shows the "install updates" icon next to the shutdown button in the start menu (a yellow shield icon) and spends a while preparing and installing updates on about a third of the restarts. And in this last one, on a restart, Windows spent too long in the "shutting down" screen and then displayed a blue screen!
Windows now gives me the option to launch Startup Repair on startup. Opting to start Windows normally will get it stuck at the Windows logo.
The Startup Repair initially asks if I wanna go to the System Recovery Options menu or to use a restore point. However, the list of installed OS's is empty, and opting to use a restore point will display the following error: "An internal error occurred. The following information might help you resolve the error: The system cannot find the file specified. (0x80070002)"
As for the more elaborate Recovery Options menu:
Startup Repair quickly says "Startup Repair cannot repair this computer automatically."
System Restore doesn't work because no Windows installation has been specified.
System Image Recovery returns the same error mentioned above (0x80070002).
And finally, in the Command Prompt, I tried to manually fix the boot record by inputting the following commands:
bootrec /fixMBR
bootrec /fixBoot
bootrec /rebuildBCD
The three of them completed successfully. However, the last one displays this message: "Total identified Windows installations: 0"
What? Failure to detect Windows installations contradicts the fact that the Srartup Repair is kicking in in the first place!
Having gotten here, it's almost clear I have already used up all of my options, and none work.
I can't remember my exact specs, but they include a 3.3 GHz Ivy Bridge Core i5 with a GeForce 760 and 16 GB HyperX RAM on some H/Q77 Gigabyte motherboard. No overclocking, but Intel's SSD caching is at work for the system's 500-GB WD Green drive using a 120-GB Samsung SSD.
The disk acceleration mode might have been set to maximized before the problem occurred, which is similar to 0 RAID if I remember correctly and thus has risk. Might this fact complicate matters?
What would you do if you were me? Is there anything that can be done without using a recovery disc? And is one supposed to be able to solve the problem?
This nuisance occurred during an apparently bugged update process. Although I gave up on the never-ending process and unchecked all important and optional updates two months ago (which had only been happening for two weeks after a fresh install of Windows 7 64-bit SP1), Windows still shows the "install updates" icon next to the shutdown button in the start menu (a yellow shield icon) and spends a while preparing and installing updates on about a third of the restarts. And in this last one, on a restart, Windows spent too long in the "shutting down" screen and then displayed a blue screen!
Windows now gives me the option to launch Startup Repair on startup. Opting to start Windows normally will get it stuck at the Windows logo.
The Startup Repair initially asks if I wanna go to the System Recovery Options menu or to use a restore point. However, the list of installed OS's is empty, and opting to use a restore point will display the following error: "An internal error occurred. The following information might help you resolve the error: The system cannot find the file specified. (0x80070002)"
As for the more elaborate Recovery Options menu:
Startup Repair quickly says "Startup Repair cannot repair this computer automatically."
System Restore doesn't work because no Windows installation has been specified.
System Image Recovery returns the same error mentioned above (0x80070002).
And finally, in the Command Prompt, I tried to manually fix the boot record by inputting the following commands:
bootrec /fixMBR
bootrec /fixBoot
bootrec /rebuildBCD
The three of them completed successfully. However, the last one displays this message: "Total identified Windows installations: 0"
What? Failure to detect Windows installations contradicts the fact that the Srartup Repair is kicking in in the first place!
Having gotten here, it's almost clear I have already used up all of my options, and none work.
I can't remember my exact specs, but they include a 3.3 GHz Ivy Bridge Core i5 with a GeForce 760 and 16 GB HyperX RAM on some H/Q77 Gigabyte motherboard. No overclocking, but Intel's SSD caching is at work for the system's 500-GB WD Green drive using a 120-GB Samsung SSD.
The disk acceleration mode might have been set to maximized before the problem occurred, which is similar to 0 RAID if I remember correctly and thus has risk. Might this fact complicate matters?
What would you do if you were me? Is there anything that can be done without using a recovery disc? And is one supposed to be able to solve the problem?
Facebook
Twitter
Instagram