Skip to content

Konstantinos Tsoukalas

Konstantinos is the founder and administrator of Wintips.org. Since 1995 he works and provides IT support as a computer and network expert to individuals and large companies. He is specialized in solving problems related to Windows or other Microsoft products (Windows Server, Office, Microsoft 365, etc.).

20 Comments

  1. Luca Benedetti
    March 27, 2024 @ 5:00 pm

    I'm here because my old PC is no longer bootable. At startup I get "Preparing Automatic Repair", then "Diagnosing your PC" and finally an error message that it wasn't repaired.

    It's def Windows 10, 64 though it started as Windows 7×64. I have attempted to repair the SFC as noted above from a bootable hard drive and always get "Windows Resource Protection could not perform the requested operation". I've used the Windows MTC and tried booting from Win10 64, Win10 32, Win11 64 and also from the original disc that has Win7x64. No luck. Any other ideas? Thank you!

    Reply

  2. Bocephus
    October 2, 2023 @ 6:15 am

    windows resource protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file located at windir\logs\cbs\cbs.log. For example c:\windows\logs\cbs\cns.log. For offline repairs, details are included in the log file provided by the /offlogfile flag. I can't get the mouse to work or the keypad to work when I do manage to get it to boot up to the desktop. Any and all help is appreciated!

    Reply

  3. majed
    August 29, 2023 @ 2:42 pm

    this post was very helpfull to fix boot in windows 22h2 version

    Reply

  4. Robert Willemsen
    September 8, 2021 @ 10:45 am

    After starting the sfc command, I got the message:

    Windows Resource Protection could not perform the requested operation.

    What can I do now ??

    Reply

    • lakonst
      September 9, 2021 @ 3:26 pm

      Ensure that you 're using a Windows Installation Media according to the Windows Version and Edition you try to repair.

      Reply

  5. Francesco
    December 18, 2020 @ 12:01 pm

    Thanks, thanks, thanks….
    You saved my day, month, year and life!

    Reply

  6. Noah
    September 19, 2019 @ 9:46 am

    Great tutorial but everything I've tried when I input any other SFC command except for SFC /scannow just replies back with all the possible options almost like if I typed /?. Any ideas?

    Reply

    • lakonst
      September 19, 2019 @ 6:05 pm

      Something in the command you are writing is wrong or missing

      Reply

      • Jessiah
        September 20, 2019 @ 4:18 pm

        Happened to me, i used backslash instead of forward slash. Misspell Any command and you will get that.

        Reply

  7. Cemil Iskender
    August 13, 2019 @ 1:12 pm

    Thanks, it is great, worked flawless. I recommend to everyone. Just follow instructions carefully.

    Reply

  8. Kazem
    April 3, 2019 @ 7:30 am

    I LOVE YOU.

    YOU SAVED MY LIFE AND TIME. THANKS A LOT

    With this method you wont need to reinstall the windows. It will just fix corrupted files

    Reply

  9. volker01
    February 14, 2019 @ 6:48 pm

    WHY?
    your example:
    sfc /SCANNOW /OFFBOOTDIR=D:\ /OFFWINDIR=D:\windows
    But in your example, the Windows Bootmanager is on C:
    for that, isn't it correct?:
    sfc /SCANNOW /OFFBOOTDIR=C:\ /OFFWINDIR=D:\windows

    Reply

    • lakonst
      February 14, 2019 @ 7:20 pm

      @volker01: Yes, the Windows Boot Manager is on drive C: but the Windows FOLDER is at drive D:, so the command "sfc /SCANNOW /OFFBOOTDIR=D:\ /OFFWINDIR=D:\windows" is correct.

      Reply

  10. Mitch Turner
    January 24, 2019 @ 5:05 pm

    Helpful if SFC works. But when it says there are corrupt files, but logging doesn't work for offline scenarios, how do I find which files are corrupt?

    Reply

    • lakonst
      January 25, 2019 @ 3:16 pm

      @Mitch Turner: Before running the sfc command, give the following commands in order (replace the drive letter "D:" with the Windows drive letter)
      mkdir D:\Temp
      set WINDOWS_TRACING_LOGFILE=D:\TEMP\CBS.log

      After running the SFC command you 'll find the CBS.LOG file at D:\TEMP\ folder.

      Reply

  11. Scott Simpson
    August 30, 2018 @ 8:51 pm

    Windows resource protection could not start the repair service?

    This is what I got

    Reply

    • lakonst
      September 5, 2018 @ 10:12 am

      @Scott Simpson: Make sure that you 're using a Windows Installation Media according to the Windows Version and Edition you try to repair. This means that if you want to repair a Windows 10 64Bit installation, then you have to boot your system from a Windows 10 64bit installation media

      Reply

  12. Sergio from Brazil
    February 3, 2017 @ 7:01 pm

    Great! Very useful.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *