Fix SCCM OSD Error code 0xc0000098

One of the most common error seen while performing SCCM operating system deployment is error code 0xc0000098. Usually the error code 0xc0000098 is seen when you PXE boot a client machine.

This is also one of the frequently asked question in my community forums. There is no one fixed solution to this issue because there could be lot of reasons behind this error.

I will list out all the steps that should help you in fixing the SCCM OSD Error code 0xc0000098. Except the error code, this looks very much similar to issue where you see 0xc000000f boot configuration data missing error. Before that let’s look at a scenario that is explained by an IT guy experiencing this issue.

Scenario – The IT guy says, I enabled PXE and multicast on the distribution point. The other DP options are configured and the task sequence is protected with a password.

On both the boot images, I enabled “Deploy this boot image from the PXE-enabled distribution point”. I then distributed the x86 and x64 boot images.

I then created the SCCM task sequence and deployed it (made available to media and PXE). When I PXE booted the client and pressed F12, I got error code 0xc0000098.

I also tried to set my DHCP option 66 to the IP address of SCCM server and option 67 to smsboot\x64\ but again I see same error.

You PC/Device needs to be repaired
The Windows Boot Configuration Data (BCD) file from the PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture.
File: \Tmp\x86x64{file}.bcd
Error code: 0xc0000098
You’ll need to use recovery tools. If you don’t have any installation media (like a disc or USB device), contact your PC administrator or PC/Device manufacturer.

SCCM OSD Error code 0xc0000098

Steps to Fix SCCM OSD Error code 0xc0000098

In order to fix the error code 0xc0000098, you might have to try all the below given steps.I assume you have redistributed the boot images to distribution points.

Whenever you make any changes to boot images, ensure it is updated to all the distribution points in your setup.

  1. First of all, start with removing the PXE on distribution point. Right click SCCM distribution point > PXE > uncheck Enable PXE support for clients.
  2. In the next step, uninstall the WDS role. You can either do that via remove roles and features wizard or using PowerShell. Refer this guide to know how to uninstall WDS. Restart the distribution point server after uninstalling WDS role.
  3. Login to the distribution point server, make sure the WDS completes any other uninstall actions it has to do.
  4. Go to distribution point properties and under PXE tab, re-enable the PXE option.
  5. Now click General tab and ensure the DP certificate is valid. If an expired or wrong Distribution Point certificate is assigned to DP, you may see error code 0xc0000098.
  6. If you have made any other changes to boot images, always remember to redistribute them to DP’s.
  7. PXE boot the client machine and you shouldn’t see the error 0xc0000098.

Note – If something else worked for you and if it’s not described here, do write in comments section. That will help others in fixing the issue.

7 thoughts on “Fix SCCM OSD Error code 0xc0000098”

  1. Does this also apply to 0xc0000098 error \Tmp\x64uefi{random characters}.bcd?
    The Windows Boot Configuration Data (BCD) file from the PXE server does not contain a valid operating system entry. Ensure that the server…..

  2. For those of you with working servers that unexpectedly ran into this situation…simply try rebooting the server, if you haven’t already. I ran into this message 5 minutes ago with a setup that has been running fine for over 2 years. I did not want to mess with anything, so I gave it the old “Turn it off and back on again”, and boom.

  3. For anyone like me who bashed their head against the wall when nothing else worked:

    Upgrading to MECM version 2006 I had this error on both networks I manage. Both times it ended up being the “Default Web Site” in IIS on the SCCM server was not started and would not start. The bindings had been broken. It was listening for HTTPS on 80 and 443. Once I changed 80 to HTTP again the site started and PXE started working.

Comments are closed.