Can't recover from crash caused by sfc /scannow


  1. Posts : 6
    Version 10.0.19042 Build 19042
       #1

    Can't recover from crash caused by sfc /scannow


    Have not been able to recover my pc after running sfc /scannow utility. I have tried rolling back to previous working restored point. Have also tried usb recovery with no success and at a loss for next step to try recovery choice.
    My winver is 2017090 16299-1004 And as a note have been able to upgrade past 16299-1004.
      My Computer


  2. Posts : 4,554
    Windows 11 Pro 64-bit
       #2

    The SFC command repairs corrupted system files i never heard of it cause a boot problem.

    What kind of error message Windows shows you?
      My Computer


  3. Posts : 6
    Version 10.0.19042 Build 19042
    Thread Starter
       #3

    Rebooted, thanks for replying.
    The error codes are 0xc00000e9 and 0xc000000f
      My Computer


  4. Posts : 4,554
    Windows 11 Pro 64-bit
       #4

    Have you installed any driver or Windows update?




    Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

    Please type below command into Command Prompt and press Enter key.

    The following command scans integrity of all protected Windows system files and repairs files with problems when possible.

    Code:
    Sfc  /Scannow   /OFFBOOTDIR=D:\   /OFFWINDIR=D:\Windows


    Please replace partition letter D: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.




    Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

    Please type below command into Command Prompt and press Enter key.

    Following command will fixes errors on the disk and locates bad sectors and recovers readable information.


    Code:
    Chkdsk D: /r


    Please replace partition letter D: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.
      My Computer


  5. Posts : 39,996
    windows 10 professional version 1607 build 14393.969 64 bit
       #5

    FreeBooter,
    Like you I've not seen scannow crashes.
    In this link the OP reported an automatic reset following restorehealth.
    Various intermittent BSODs Win 10 (1903)
    Another unexpected finding.
      My Computer


  6. Posts : 56,116
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #6

    bob3677 said:
    Have not been able to recover my pc after running sfc /scannow utility. I have tried rolling back to previous working restored point. Have also tried usb recovery with no success and at a loss for next step to try recovery choice.
    My winver is 2017090 16299-1004 And as a note have been able to upgrade past 16299-1004.
    16299 (Version 1709) is a 2 year old version of Windows that is no longer supported. That, alone, can cause issues that are very difficult or impossible to rectify.

    Strongly suggest you update to 1903, or at the very minimum, 1809.

    https://docs.microsoft.com/en-us/win...e-information/

    Windows 10 version history - Wikipedia

    Can't recover from crash caused by sfc /scannow-2019-10-20_05h50_26.png
      My Computers


  7. Posts : 39,996
    windows 10 professional version 1607 build 14393.969 64 bit
       #7

    f14tomcat,

    The opening post was unclear:

    "My winver is 2017090 16299-1004 And as a note have been able to upgrade past 16299-1004. "

    How has it been able to upgrade?
    Was "not" missing?

    If not was missing then options are:
    reset save files
    custom install
    reset remove files
    clean install
    troubleshoot
      My Computer


  8. Posts : 936
    xp
       #8

    9 year old AIO. Have you checked the HDD for errors ?
      My Computer


  9. Posts : 56,116
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #9

    zbook said:
    f14tomcat,

    The opening post was unclear:

    "My winver is 2017090 16299-1004 And as a note have been able to upgrade past 16299-1004. "

    How has it been able to upgrade?
    Was "not" missing?

    If not was missing then options are:
    reset save files
    custom install
    reset remove files
    clean install
    troubleshoot
    Yep, it's contradictory. Dead-end service level for 16299 was .1481. So, those would be options. Bat 1 noted the age of the machine, 9 yrs. It may be on the "Sorry, no can do" list from MS. Lots of unknowns here.

    A run with MCT and it's up front Compatibility Checker would catch that right off. By some quirk of good luck, it might upgrade.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 15:52.
Find Us




Windows 10 Forums