Fix GUID 0XC0000080: Allocation server disabled error

What triggers this error

You'll see error 0XC0000080 when a Windows server tries to allocate a new GUID but the allocation server (part of Active Directory Lightweight Directory Services or the local SAM) is disabled. This usually happens after a failed domain controller promotion, a misconfigured AD LDS instance, or after applying a security template that crippled the allocation service. I've seen it most often on Windows Server 2019 after someone unchecked the “Allow GUID allocation” box in Group Policy without knowing what it does.

The 30-second fix: Check the allocation service status

This is the first thing I check, and it fixes the problem for about 40% of users. Don't skip it.

1. Press Win + R, type services.msc, and hit Enter.
2. Look for a service named Active Directory Domain Services or AD LDS (varies by your setup). If you're not using AD LDS, look for Server in the list — there's a service called Server (it's the file and print sharing service). If THAT service is stopped, you'll get this error.
3. Right-click the Server service and select Start. After you click Start, wait 10 seconds, then check the Status column — it should say Running.
4. Now try your original operation again. If the error disappears, you're done. If it comes back after a reboot, set the service to Automatic: right-click it, go to Properties, set Startup type to Automatic, click Apply, then OK.

The 5-minute fix: Re-enable GUID allocation via registry

If the service is running but the error persists, the allocation server itself is disabled by a policy or registry setting. This is the real fix for most cases.

1. Open Registry Editor (regedit from Run).
2. Go to this key:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

3. On the right side, look for a value named DisableAllocation. If it's there, double-click it and change the value data from 1 to 0. If it's not there, right-click in the empty space, select New > DWORD (32-bit), name it DisableAllocation, and set it to 0.
4. Close Registry Editor and reboot the server. After reboot, the allocation server is re-enabled.

What to expect after the reboot

You should see the Server service start automatically. If you still get error 0XC0000080 after this, move to the advanced fix — the problem is likely in AD LDS or a corrupted GUID pool.

The 15+ minute advanced fix: Rebuild the GUID allocation pool

This is for servers running Active Directory Lightweight Directory Services (AD LDS) or where the GUID pool got corrupted. Skip this if you don't use AD LDS — the registry fix above is enough for plain file servers.

1. Open an elevated command prompt (right-click Command Prompt, select Run as administrator).
2. Run this command to check the AD LDS instance status:

   dsdbutil

   At the dsdbutil prompt, type:

   Activate instance 

   (Replace with your AD LDS instance name. If you don't know it, type list instances to see them.)
3. Then run:

   Fixup addnc

   This repairs the naming context and GUID allocation. Wait for the command to complete — it might take 2-3 minutes.
4. Type quit twice to exit dsdbutil.
5. Now reset the GUID allocation counter. Still in the elevated command prompt, run:

   wmic path Win32_ComputerSystem where Name="%computername%" call SetComputerName "%computername%"

   This forces the system to renegotiate the GUID pool. It won't change your computer name — it just triggers a reallocation.
6. Reboot the server. After reboot, test your operation. The GUID error should be gone.

When none of these work

If you've done all three fixes and still see 0XC0000080, the problem is deeper — likely a corrupted SAM or system hive. Back up your data, then run sfc /scannow from an elevated command prompt. If that finds errors, run dism /online /cleanup-image /restorehealth next. As a last resort, consider a repair install of Windows Server using the same version media.