Share via

Recently serviced boot binary is corrupt, can only boot into test mode, please help

Anonymous
2025-05-05T15:42:07+00:00

Startup Repair diagnosis and repair log

Last successful boot time: ‎02/‎05/‎2025 16:14:19 (GMT)

Number of repair attempts: 3

Session details

System Disk = \Device\Harddisk0

Windows directory = C:\Windows

AutoChk Run = 0

Number of root causes = 1

Test Performed:

Name: Check for updates

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: System disk test

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Disk failure diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Disk metadata test

Result: Completed successfully. Error code = 0x0

Time taken = 94 ms

Test Performed:

Name: Disk metadata test

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Target OS test

Result: Completed successfully. Error code = 0x0

Time taken = 16 ms

Test Performed:

Name: Volume content check

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Boot manager diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: System boot log diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Event log diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Internal state check

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Check for installed LCU

Result: Completed successfully. Error code = 0x0

Time taken = 1265 ms

Root cause found:

A recently serviced boot binary is corrupt.

Session details

System Disk = \Device\Harddisk0

Windows directory = C:\Windows

AutoChk Run = 0

Number of root causes = 1

Test Performed:

Name: Check for updates

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: System disk test

Result: Completed successfully. Error code = 0x0

Time taken = 16 ms

Test Performed:

Name: Disk failure diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Disk metadata test

Result: Completed successfully. Error code = 0x0

Time taken = 62 ms

Test Performed:

Name: Disk metadata test

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Target OS test

Result: Completed successfully. Error code = 0x0

Time taken = 16 ms

Test Performed:

Name: Volume content check

Result: Completed successfully. Error code = 0x0

Time taken = 47 ms

Test Performed:

Name: Boot manager diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: System boot log diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Event log diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 15 ms

Test Performed:

Name: Internal state check

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Check for installed LCU

Result: Completed successfully. Error code = 0x0

Time taken = 1750 ms

Root cause found:

A recently serviced boot binary is corrupt.

Repair action: Uninstall latest LCU

Result: Failed. Error code = 0x905

Time taken = 3109 ms

Session details

System Disk = \Device\Harddisk0

Windows directory = C:\Windows

AutoChk Run = 0

Number of root causes = 1

Test Performed:

Name: Check for updates

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: System disk test

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Disk failure diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Disk metadata test

Result: Completed successfully. Error code = 0x0

Time taken = 63 ms

Test Performed:

Name: Disk metadata test

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Target OS test

Result: Completed successfully. Error code = 0x0

Time taken = 15 ms

Test Performed:

Name: Volume content check

Result: Completed successfully. Error code = 0x0

Time taken = 63 ms

Test Performed:

Name: Boot manager diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: System boot log diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Event log diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 31 ms

Test Performed:

Name: Internal state check

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Check for installed LCU

Result: Completed successfully. Error code = 0x0

Time taken = 2297 ms

Test Performed:

Name: Check for installed driver updates

Result: Completed successfully. Error code = 0x0

Time taken = 515 ms

Test Performed:

Name: Check for pending package install

Result: Completed successfully. Error code = 0x0

Time taken = 1172 ms

Test Performed:

Name: Boot status test

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

Name: Setup state check

Result: Completed successfully. Error code = 0x0

Time taken = 32 ms

Test Performed:

Name: Registry hives test

Result: Completed successfully. Error code = 0x0

Time taken = 296 ms

Test Performed:

Name: Windows boot log diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Root cause found:

Boot critical file c:\windows\system32\drivers\sfvfs02.sys is corrupt.

Repair action: File repair

Result: Failed. Error code = 0x57

Time taken = 766 ms

Repair action: System files integrity check and repair

Result: Failed. Error code = 0x57

Time taken = 500 ms

I have been battling with my pc to get to this point, but it can only launch with diver signature enforcement disabled, not allowing me to do many things.

Another thing to note is that c:\windows\system32\drivers\sfvfs02.sys does not exist anymore as I found another post which said that simply removing all files relating to StarForce would help, therefore I ran their uninstaller and removed all related files. The main issue to me seems to be:

A recently serviced boot binary is corrupt.

Repair action: Uninstall latest LCU

Result: Failed. Error code = 0x905

Time taken = 3109 ms

I assume that uninstalling the latest LCU would work? But I am unsure of how to do this.

Also how can I come out of test mode? I have tried bcdedit /set testsigning off.

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
  1. Ramesh Srinivasan 173.3K Reputation points Volunteer Moderator
    2025-05-06T15:07:44+00:00

    The commands ran correctly. The old BCD has been backed up.

    Please restart the system. Test signing is now turned off (default setting).

    1 person found this answer helpful.
    0 comments

14 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ramesh Srinivasan 173.3K Reputation points Volunteer Moderator
    2025-05-05T15:47:44+00:00

    Please boot into Windows with signature enforcement disabled and run a Farbar scan. Share your Farbar scan logs for analysis.

    1. Download Farbar Recovery Scan Tool 64-bit (FRST64.exe)

    https://www.bleepingcomputer.com/download/farbar-recovery-scan-tool/

    (or)

    https://downloads.malwarebytes.com/file/mbst-frst64

    Note: If Microsoft Edge or Chrome mislabels the Farbar Scanner executable as PUA/malware, choose to keep it by tapping … in the bottom bar, choosing Keep, and then choosing Keep anyway in the dialog that appears.

    See this screenshot: https://learn.microsoft.com/en-us/deployedge/media/microsoft-edge-security-download-interruptions/dowload-was-blocked.png. It's a safe tool used in most antimalware forums.

    1. If the OS language is not English, rename FRST64.exe to FRST64English.exe.
    2. Run the program. Don't check or uncheck any options. Click "Scan".
    3. Add the two logs, FRST.txt and Addition.txt, to a Zip archive, share them on OneDrive or GoFile.io and post the link here.
    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2025-05-05T16:11:53+00:00

    Hi Ramesh thank you for responding so quickly,

    I have followed the instructions of which you have provided, here is the gofile link:

    https://gofile.io/d/zvOlZ1

    0 comments
  3. Ramesh Srinivasan 173.3K Reputation points Volunteer Moderator
    2025-05-05T16:24:06+00:00

    Hi theo,

    1. Please run this fix list.
    • Download fixlist.txt
    • Save Fixlist.txt to the same folder as FRST64English.exe.
    • Close all programs.
    • Launch the Farbar Scanner tool and click "Fix".
    • Restart Windows when prompted.
    • Upload the output log file (FixLog.txt) to your OneDrive.

    NOTE: Don't run the same fixlist.txt more than once. Also, the fixlist.txt script was written specifically for this user and for use on that particular machine. It is not recommended to run it on another machine.

    1. If Windows RE is not enabled on the system, create a Windows 11 USB setup disk and have it ready. Will post further steps.
    0 comments
  4. Anonymous
    2025-05-05T16:48:14+00:00

    I have again done this. Fixlog_05-05-2025 17.37.30.txt there is the log.

    0 comments