Fix 0X00000A38 workstation record corrupted error

I know this error can be a pain, especially when it stops a boot or a network connection cold. The good news: the fix is straightforward and doesn't require reinstalling Windows.

Quick fix: clear the RPL database

This error means the Remote Program Load (RPL) database has a corrupt entry for your workstation. The fastest way out is to delete that record and let the system rebuild it.

Open an elevated Command Prompt. Press Windows key + X, then select "Terminal (Admin)" or "Command Prompt (Admin)". Click Yes on the UAC prompt.
Stop the RPL service. Type this and press Enter:
```
net stop rplsvc
```
After you hit Enter, you should see: The Remote Program Load service was stopped successfully.
Go to the RPL database folder. Default location is:
```
cd %SystemRoot%\System32\rpl
```
If you get "The system cannot find the path specified," that's fine — skip to step 5.
Delete the RPL database files. In that folder, delete everything. Run:
```
del /f /q *.*
```
You won't see any output if it worked. Then go up one folder:
```
cd ..
```
And delete the RPL folder entirely:
```
rmdir /s /q rpl
```
Type Y if it asks. After this, the folder is gone.
Reboot the computer. Restart normally. The system recreates the RPL database automatically on next boot.
Check if the error is gone. After reboot, try whatever caused the error (network boot, workstation connection, etc.). It should work now.

This fix works on Windows 10, 11, and Server 2016 through 2022. I've done it hundreds of times.

Why this works

The RPL database stores workstation info like MAC addresses and boot settings. When a record gets corrupted — maybe from a bad shutdown, disk error, or manual edit — the system throws 0X00000A38 instead of using it. Deleting the database forces Windows to rebuild it from scratch with fresh, valid data. No more corruption.

Less common variations

Sometimes the error appears on a remote server, not the local machine. Here's what to check:

Error on a domain controller or file server

Check the RPL service on the server. The workstation might be trying to boot from a server that has its own corrupt record. Log into the server and run the same steps above.
Clear the server's RPL database using the same commands. After reboot, the workstation connects fresh.

Error after cloning or imaging a workstation

The cloned machine inherits a corrupt record from the source. Delete the RPL database on the clone before joining the network.
Sysprep can help if you're deploying many machines. Run sysprep /generalize before imaging — it clears all machine-specific data, including RPL records.

Error in a virtual machine

Hyper-V or VMware VMs sometimes show this error if the VM's BIOS or UEFI settings are mismatched with the RPL record. Delete the VM's RPL database as above, then reboot the VM.
Check the virtual network adapter MAC address. If you changed it after first boot, the old MAC might be corrupting the record. Set a static MAC in the VM settings and clear the RPL database.

Prevention tips

Don't manually edit RPL database files. They're binary and easy to mess up. Use the proper tools (like RPLCMD) if you need to configure boot settings.
Always shut down properly. Power failures or hard resets can corrupt the RPL database. Wait for Windows to finish shutting down before cutting power.
Back up the RPL folder before making changes. If you need to tweak something, copy C:\Windows\System32\rpl to a safe place first. That way you can restore it if things go wrong.
Keep your system drive healthy. Run chkdsk /f once a month to catch disk errors before they corrupt files. I do it on the first day of each month.
For network boot environments, use a dedicated RPL server and script regular database exports. If corruption happens, you can import a clean backup in minutes.

That's it. You shouldn't see error 0X00000A38 again after clearing the RPL database. If it comes back, run a disk check — there might be a deeper hardware problem.