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

Question

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.

Answer 1

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

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

Answer 2

Hi theo,

I don't see any code integrity violations regarding drivers or boot files. And that sfvfs02.sys file is not loading.

We can try rebuilding the boot files and BCD via WinRE.

Also, there is a 2025 BIOS update for your system, which you may apply.

• ASRock > B650M Pro RS WiFi: https://www.asrock.com/MB/AMD/B650M%20Pro%20RS%20WiFi/index.asp#BIOS

Please boot into WinRE and open Command Prompt in WinRE. In WinRE Command Prompt, run these commands:

mountvol y: /s

---

diskpart

---

list disk

---

select disk 0

---

list part

---

list vol

---

exit

Using your mobile phone or camera, take photos of the output screen and share the images here. Don't quit WinRE yet. Two more commands need to be run.

Answer 3

In winRE I cannot find the command prompt. I know where it should be located as it's how I managed to boot into test mode in the first place earlier today.

Answer 4

In winRE I cannot find the command prompt. I know where it should be located as it's how I managed to boot into test mode in the first place earlier today.

You must use a Windows 11 USB setup disk to get into WinRE because the native WinRE is disabled, according to the Farbar logs..

Maybe you can try enabling WinRE by running "reagentc /enable" in admin Command Prompt. If that doesn't work, you need the USB setup disk.

(or)

If you want to upgrade to 24H2, run the compatibility assessment test below.

Open an admin Command Prompt window and run:

CompatTelRunner.exe -m:appraiser.dll -f:DoScheduledTelemetryRun

It should complete within two minutes. After it completes, run the following command:

REG QUERY "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators" /s

Post the output here.

The output indicates whether a 24H2 safeguard hold is in place for your system.

Answer 5

I ended up using the boot drive, this is what it came up with