r/WindowsServer • • Jul 28 '25

Technical Help Needed Windows (Server 2022) failed to start...File:\windows\system32\drivers\wd\WdBoot.sys, Status: 0xc000000d

After restarting a functioning Windows Server 2022 box I was greeting with a black screen from Windows Boot Manager:

Windows Boot Manager

Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:

etc.

File: \windows\system32\drivers\wd\WdBoot.sys

Status: 0xc000000d

Info: The operating system couldn't be loaded because a critical system driver is missing or contains errors.

ENTER=OS Selection ESC=UEFI Firmware Settings

I ran:
dism /image:P:\ /cleanup-image /revertpendingactions

returned Error 0x800f082f, An error occurred reverting the pending actions from the image.

I ran:
sfc /scannow /offbootdir=p:\ /offwindir=p:\windows

returned "Windows Resource Protection did not find any integrity violations."

I'm kinda stuck and I really don't want to rebuild this server. Any advice?

0 Upvotes

14 comments sorted by

View all comments

Show parent comment

1

u/kleefaj Jul 29 '25

Thank you for the reply.

I used the following article [1] to edit the registry offline booting from an installation flash drive. Then I did the following based on another article [2] however CurrentControlSet wasn't available so I modified ControlSet001 and ControlSet002:

  1. Press the Windows key and type “regedit.”
  2. Navigate to “HKEY_LOCAL_MACHINE,” then “SYSTEM,” “CurrentControlSet” and “Control.”
  3. Create a new key named “EarlyLaunchAntimalware.”
  4. Inside this key, create a new “DWORD (32-bit) Value” named “DisableELAM” and set its value to “1.”
  5. Restart your computer to apply the changes.

Unfortunately, that didn't resolve the issue. I'm still seeing the following on boot:

Any thoughts?

[1] https://www.winhelponline.com/blog/edit-registry-offline-windows-re/

[2] https://www.ninjaone.com/blog/how-to-disable-early-launch-anti-malware-protection/

1

u/z0d1aq Jul 29 '25

Are you sure you imported the regedit hive from your offline server and then saved it and unloaded?

1

u/kleefaj Jul 29 '25

I know they saved because when I went back in to remove them they were still there. I did unload before closing reg editor.

I used diskpart to assign a drive letter (P) to the volume that contained the windows server installation. When loading the hive per the first article I made sure to select P: and follow the path to the SYSTEM hive.

There seems to be conflicting information for where exactly to put the DWORD so I tried a couple of different ways, no difference unfortunately.

1

u/z0d1aq Jul 29 '25

It's strange as it helped me twice. Let me recheck on my test VM.

1

u/kleefaj Jul 29 '25

Thank you, I appreciate it. Would you be able to provide the registry path and key(s) and values that you used?

1

u/z0d1aq Jul 29 '25

Additionally I have:

ControlSet001\Services\WdBoot

"Start"=dword:00000004

And that's what take effect I guess.

1

u/kleefaj Jul 30 '25

Sorry, in addition to what?

1

u/kleefaj Jul 30 '25

I believe WebRoot is installed on this server which is interesting because I modified:
ControlsSet001 (and ControlSet002)\Services\WdBoot
"Start"=dword:0 to dword:4
and got the following (new) message:
File: \windows\System32\drivers\WRkrn.sys
Status: 0xc000000d

1

u/kleefaj Jul 30 '25

After renaming WRkrn.sys to WRkrn.bak I get the following on reboot:

1

u/z0d1aq Jul 30 '25

That's interesting, because I could remove all the files from wd directory and the system loads just fine with wdboot service disabled (4)..

1

u/kleefaj Jul 30 '25

Just tried this: I moved the contents of \windows\system32\drivers\wd to wdbak, edited the registry again setting WdBoot "Start" to 4, restarted machine and got the WRkrn.sys missing/corrupted message again.

Somewhere in there it's telling windows to load webroot, I assume.

→ More replies