Fix 0X00000A48: incompatible profile error

Quick answer

Rebuild the workstation's Remote Program Load (RPL) profile in the Remote Boot Manager to match the adapter ID and OS version. Then restart both the workstation and the RPL service.

Why you're seeing this

This error comes from the ancient but still-used Remote Boot service in Windows NT 4.0 and some legacy corporate networks. The error code 0X00000A48 maps to NERR_RplIncompatibleProfile — it means the profile you've assigned to that workstation doesn't fit the hardware or software it's trying to boot from. I tripped on this one when migrating old thin clients to a newer server. The real trigger is almost always a mismatch between the profile's adapter type (like NE2000 or 3C509) and what's actually in the machine, or a profile tied to Windows 95 when the workstation runs DOS.

Fix steps

Open Remote Boot Manager on the server running the Remote Boot service. It's under Administrative Tools in Windows NT 4.0 or Windows 2000 Server.
Find the problem workstation in the list. Right-click it and choose Properties.
Check the profile name listed under Profile Name. If it says something like WIN95_NE2000 but the machine has a 3C509 card, that's your problem.
Create a new profile if the existing one is wrong. Go to File > New > Profile. Name it something descriptive, like WIN95_3C509.
Select the correct adapter type and OS in the profile wizard. For this error, pick the adapter that matches the physical NIC in the workstation. Common options are NE2000, 3C509, AMD PCNet.
Assign the new profile to the workstation. Right-click the workstation in Remote Boot Manager, go to Properties, and set the profile to the one you just created.
Push the configuration by stopping and restarting the Remote Boot service. Open a command prompt on the server and run:
```
net stop remoteaccess
et start remoteaccess
```
Reboot the workstation. It should now pull the correct profile and boot without error.

Alternative fixes

If the main fix doesn't work, try these in order:

Delete and re-create the workstation entry. Right-click the workstation in Remote Boot Manager, choose Delete, then add it fresh. This clears any corrupted settings.
Update the RPL database. Sometimes the database file Rpl.mdb gets stale. Stop the service, delete the file from %SystemRoot%\System32\Rpl, and it rebuilds automatically when the service restarts. Back up first.
Check for duplicate adapter addresses. Two workstations with the same MAC can cause this error. Run rplcmd at the command line and use the adapter menu to list all registered adapters.

Prevention tip

Always name profiles by the OS and adapter type — like DOS_NE2000 or WINNT40_PCNET — and keep a master list of what each workstation actually has. When you swap a NIC, update the profile the same day. I've seen this bug linger for months because nobody remembered to update the profile after a hardware refresh.