Run sfc in vista




















Show 3 more comments. Active Oldest Votes. I have this code in a non-elevated WinForms app Start startInfo ; From a 32 bit WOW64 process this fails with this message in the console window: Windows Resource Protection could not start the repair service.

From a 64 bit process, the above code succeeds. From a 64 bit process, running without elevation, the following succeeds Start startInfo ; So I guess the solution to your problem will involve either switching your main program to 64 bit probably a little drastic , or splicing a 64 bit process into the chain so that the 64 bit sfc can be run. David Heffernan David Heffernan k 40 40 gold badges silver badges bronze badges. Ian I answered the question you originally asked.

I also answered the second question that you asked in your question edit. Fire up a 64 bit executable dedicated to running sfc. But only do that if you are on 64 but OS. You cannot use cmd. But your 64 bit exe that is outside system dir is fine. So start the 64 bit cmd then. Anyway, I think that is your problem. I believe I answered the question that you asked. Or forget about cmd and go straight to the 64 bit sfc.

It's a shame you are getting confused between the solution to your problem, and the answer to the question that you asked. Show 7 more comments. Hidden; a. ReadToEnd ; a. Show "DONE! AGnoob AGnoob 11 1 1 bronze badge. Add a comment. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Replace c: with the letter of the drive where Windows 7 is installed.

Method 2. Run sfc in Windows 8 or 8. You can also run the utility from the Windows installation disc. This error usually appears if the hard disk has corruptions or bad sectors. To fix this error, you can try any of the following tips:. To boot into Safe Mode, follow these steps:.

To get the full instructions on how to boot into Safe Mode, read our guide on Safe Mode with instructions for each Windows version:. To run chkdsk related guide: chkdsk , follow these steps:. Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow. To do this, click Start , type Command Prompt or cmd in the Search box, right-click Command Prompt , and then click Run as administrator.

To view the details that included in the CBS. Log file, you can copy the information to the Sfcdetails. To do this, follow these steps:. Note The Sfcdetails. The file includes information about files that were not repaired by the System File Checker tool.

Verify the date and time entries to determine the problem files that were found the last time that you ran the System File Checker tool. How to manually replace a corrupted system file with a known good copy of the file. After you determine which system file was corrupted and could not be repaired through the detail information in the Sfcdetails. To do this, follow these steps: Note You may be able to get a known good copy of the system file from another computer that is running the same version of Windows with your computer.

You may perform a System File Checker process on that computer to make sure the system file that you intend to copy is a good copy. Take administrative ownership of the corrupted system file. To do this, at an elevated command prompt, copy and then paste or type the following command, and then press ENTER:. Grant administrators full access to the corrupted system file.

Replace the corrupted system file with a known good copy of the file. If the steps above don't work, you may need to reinstall Windows.



0コメント

  • 1000 / 1000