Quizzes & Puzzles25 mins ago
Unmountable_boot_volume
9 Answers
Had this error message come up yesterday when booting up my computer. Running Win XP Home SP2. Any ideas what the problem is?
Problem occurred after Google Earth update failed to install and I had to turn m/c off via the on switch. Would not let me close down windows.
Problem occurred after Google Earth update failed to install and I had to turn m/c off via the on switch. Would not let me close down windows.
Answers
Best Answer
No best answer has yet been selected by djprescott. Once a best answer has been selected, it will be shown here.
For more on marking an answer as the "Best Answer", please visit our FAQ.When a PC first starts up it has no idea which devices contain an operating system such as Windows, and which device to "boot " from.
There could be an operating system on diskette (honestly), hard disk or CD or DVD.
So the PC looks on each of these devices, one at a time, trying to find a file that identifies itself as a "boot" volume.
If the PC cannot find any device with the "boot" file then you will get a message like you have got.
This may be for a number of reasons.
One reason may be that the "bios" in the PC has "lost" the device (so the PC does not even know the device, say hard drive, is even there).
Another reason may be that although the device, such as hard disk, is there, maybe the "boot" file has become corrupt or deleted so the PC is not able to boot from it.
More....
There could be an operating system on diskette (honestly), hard disk or CD or DVD.
So the PC looks on each of these devices, one at a time, trying to find a file that identifies itself as a "boot" volume.
If the PC cannot find any device with the "boot" file then you will get a message like you have got.
This may be for a number of reasons.
One reason may be that the "bios" in the PC has "lost" the device (so the PC does not even know the device, say hard drive, is even there).
Another reason may be that although the device, such as hard disk, is there, maybe the "boot" file has become corrupt or deleted so the PC is not able to boot from it.
More....
As you can see, it all gets rather technical and dificult to fix.
You could try to go into the BIOS and verify if the hard disk on the PC is listed as a being available.
(Watch as your PC starts up and you get a brief message saying something like "press xxx to go into the BIOS". Read the documentation if you are not sure).
When you are in the BIOS find a list of the devices and see if the hard disk is listed.
I had a similar problem to this a few weeks ago after doing a Microsoft update, my PC would not boot afterwards. I tried everything but in the end gave up and had to reinstall Windows.
Luckily I had a complete backup of my hard drive and was able to recover in about 10 minutes.
In your case you may not be as lucky and it may mean a new hard drive, or a reinstall of Windows on this hard drive, which means you will lose everything.
Let us know if you need more help.
You could try to go into the BIOS and verify if the hard disk on the PC is listed as a being available.
(Watch as your PC starts up and you get a brief message saying something like "press xxx to go into the BIOS". Read the documentation if you are not sure).
When you are in the BIOS find a list of the devices and see if the hard disk is listed.
I had a similar problem to this a few weeks ago after doing a Microsoft update, my PC would not boot afterwards. I tried everything but in the end gave up and had to reinstall Windows.
Luckily I had a complete backup of my hard drive and was able to recover in about 10 minutes.
In your case you may not be as lucky and it may mean a new hard drive, or a reinstall of Windows on this hard drive, which means you will lose everything.
Let us know if you need more help.
I can't follow your reasoning as far as the cause of corruption is concerned. There is no reason for any of the boot info to be modified during an application update or install, so no reason for it to become corrupted if you interrupt the process.
You can attempt a repair by following the instructions here:
http://support.microsoft.com/kb/555302
If you get the machine working, I strongly suggest that your next task is to ensure that you have a full backup
You can attempt a repair by following the instructions here:
http://support.microsoft.com/kb/555302
If you get the machine working, I strongly suggest that your next task is to ensure that you have a full backup
It's impossible to say without further investigation. However, in my experience the symptoms you describe will 99 times out of 100 indicate a failing hard drive. The fact that it blue screens could indicate a corrupt driver file, and once again the corruption could be caused by a fault in the hard drive.