Академический Документы
Профессиональный Документы
Культура Документы
1 of 5
http://answers.microsoft.com/en-us/windows/forum/windows_vista-sy...
By using this site you agree to the use of cookies for analytics, personalized content and ads.
Learn More
Sign in
Community
Home
Categories
Participate
Additional Support
Announcements: 1
Windows
Applies to: Windows | Windows Vista | Repair and Recovery
Related Content
Question
| 93497 views
PC was working fine until today. Upon boot-up, it goes in startup repair but says it cannot repair this
computer automatically.
Looked in diagnostic and repair details, find at the bottom
Reply |
Answer
Report abuse
Subscribe to updates
08/11/2014 18:09
2 of 5
http://answers.microsoft.com/en-us/windows/forum/windows_vista-sy...
run. It will scan and try to fix some of your system files. Hopefully it will complete with no corruption it
could not repair (if there is such corruption post back here or try to analyze it to find the problem file(s)
using http://support.microsoft.com/kb/928228. Try to post any corrupted files here so we can see if
they can be repaired with good copies from the installation disk (unless there are too many).
While in Command Prompt, type chkdsk /f /r and enter and let it run. You may need to reboot if it
schedules itself to run at the next startup. It will scan and try to fix any corruption or bad sectors on your
hard drive and mostly remove that as a potential cause.
If that doesn't work, then please post any repeating error messages from the Event Viewer concerning
startup (Start / Control Panel / Administrative Tools / Event Viewer or typing eventvwr from the
command prompt). Here's how to use Event Viewer: http://www.petri.co.il/vista-event-viewer.htm.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------It may be that your boot information is missing or corrupt on the hard drive (or there is another
problem with your hard drive). That's what the error message suggests. We'll have to try to repair that
if we can. You will need a Vista Installation Disk to do this process (see below if you don't have one and
can't borrow one from ANYONE):
To run the Bootrec.exe tool, you must start Windows RE. To do this, follow these steps:
1.
Put the Windows Vista installation disc in the disc drive, and then start the computer.
2.
Press a key when you are prompted.
3.
Select a language, a time, a currency, a keyboard or an input method, and then click Next.
4.
Click Repair your computer.
5.
Click the operating system that you want to repair, and then click Next.
6.
In the System Recovery Options dialog box, click Command Prompt.
7.
Type Bootrec.exe, and then press ENTER.
Note If rebuilding the BCD does not resolve the startup issue, you can export and delete the BCD, and
then run this option again. By doing this, you make sure that the BCD is completely rebuilt. To do this,
type the following commands at the Windows RE command prompt:
c:
cd boot
attrib bcd -s -h -r
bootrec /RebuildBcd
If that doesn't work or if you can't get your hands on the disk, you can try the free EasyBCD at:
http://neosmart.net/dl.php?id=1 and see if that program is able to help.
I hope this helps.
Good luck!
Lorien - MCSE/MCSA/Network+/A+ --- If this post helps to resolve your issue, please click the "Mark as
Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you
help others find the answer faster.
Reply |
Report abuse
08/11/2014 18:09
3 of 5
http://answers.microsoft.com/en-us/windows/forum/windows_vista-sy...
I have created a recovery disk as per instructions, changed the BIOS to boot from CD. I then choose the
repair computer option and go into System recovery options. Startup Repair comes up with the same error
as described initially. System Restore cannot find any restore points so I then tried the Command Prompt.
Find myself in X:\Sources> directory (window title says "Administrator: X:\windows\system32/cmd.exe")
I cd to c:\windows\system32 and try the sfc /scannow and get
Beginning system scan. This process with take some time.
Windows Resource Protection could not perform the requested operation.
Then try the chkdsk /f /r and get
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another process. Chkdsk may run if this volume is
dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to
force a dismount on this volume? (Y/N)
I choose N and get
Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume
to be checked the next time the system restarts? ( Y/N)
I choose Y and reboot but it doesn't seem to do any check and I am back at the beginning again.
Reply |
Report abuse
Tried the sfc and chkdisk on the D: drive as I noticed that I have "Operating system: Miscrosoft Windows
Vista on (D:) SW_Preload" but get the same messages as per C: drive in previous post.
Reply |
Report abuse
If you answer yes to the chkdsk question to start at the next startup and then reboot, it will run when it
restarts. You need to do that because it can't run the chkdsk while the system is operating normally.
I'm not sure why you're having troubles with SFC. It seems like it started correctly then stopped for some
reason - perhaps SFC itself is corrupted (or maybe there's some problem running it from the disk). It could
also be caused by the partition table problem that's the reason for this post. I guess we'll just have to skip
that step.
Good luck with the others and keep me posted.
Lorien - MCSE/MCSA/Network+/A+ --- If this post helps to resolve your issue, please click the "Mark as
Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help
others find the answer faster.
Reply |
Report abuse
All I can say is THANK GOODNESS I'm not the only one!! Unfortunately, I'm in the process of repairing a WIN
7 with this exact same issue. Worked fine when I left work, came back in the next morning (yesterday) and
have been trying to bypass a complete format as would rather not. Received different error codes regarding
I/O issues. CHKDSK passed every time. Haven't lost any other files, but as stated previously, it can't find the
OS. I'm going to try the fixes that have been given here, and hopefully they will work. Otherwise, will be back
with more error codes.
08/11/2014 18:09
4 of 5
http://answers.microsoft.com/en-us/windows/forum/windows_vista-sy...
Report abuse
Hi Willoweagle,
These are Vista Forums. For Windows7 questions (even if they are the same as those posted here), you need
to post in the Windows7 Forums at: http://social.answers.microsoft.com/Forums/en-US/category
/windows7 where experts in Windows7 will be more than happy to assist you.
I'm sorry we can't be of more help, but there are a LOT of differences between the two systems and using
Vista procedures could cause more harm instead of resolving the problem.
Good luck!
Lorien - MCSE/MCSA/Network+/A+ --- If this post helps to resolve your issue, please click the "Mark as
Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help
others find the answer faster.
Reply |
Report abuse
08/11/2014 18:09
5 of 5
http://answers.microsoft.com/en-us/windows/forum/windows_vista-sy...
I had this problem and tried EVERYTHING including the detailed advice in this thread.
I came to the conclusion that a combination of a windows update and a dodgy system restore when this
update crashed were responsible for the error.
However, I have since managed to fix the issue, doing the following:
I installed a new instance of Windows 7 on the recovery partition of my hard-drive.
This installed without any problems.
I then checked for windows updates - it found several, so i installed and restarted the laptop.
The new update booted fine, so i tried the other instance of Windows 7 (i.e. the original one that was
providing problems) - and this worked fine too!
I then removed the second instance of Windows 7 from my recovery and removed its boot from msconfig
and the system is running perfectly.
I hope this can help anyone with the issue - I know what it feels like....trust me!
Cheers,
Rob
Reply |
Report abuse
English
Report abuse
08/11/2014 18:09