Fix UUID (0X000006A9) error in Windows Server 2019/2022

Getting the UUID error 0X000006A9 is frustrating — it usually pops up during Windows Update or when trying to activate a license. But don't panic. The fix is quick and doesn't require a reinstall.

What causes the 0X000006A9 error?

This error message — "The string is invalid" — means Windows is trying to read a UUID from the registry or a file, but the string it finds isn't formatted correctly. The most common trigger is a corrupted SusClientId value in the Windows Update registry key. I see this a lot after a failed update or a botched system restore. It can also happen when a third-party tool (like a server optimizer) accidentally chops part of a GUID.

Step-by-step fix: Repair the Windows Update UUID

This fix works on Windows Server 2019, 2022, and even Windows 10/11 (if you're unlucky enough to see this on a desktop).

1. Open Registry Editor. Press Win + R, type regedit, and hit Enter. If a UAC prompt appears, click Yes.
2. Navigate to the Windows Update key. In the left pane, go to:
   

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

   If you're on a 64-bit system running a 32-bit app that's throwing the error, also check:
   

   HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\WindowsUpdate

3. Look for a value named SusClientId. It should be a string (REG_SZ) with a GUID format like {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}. If the value is empty, missing the braces, or has extra characters, that's your problem.
4. Delete the corrupted SusClientId. Right-click it and choose Delete. Confirm when asked. Important: Deleting this forces Windows to generate a fresh UUID the next time it checks for updates. That's exactly what we want.
5. Reboot the server. This step matters — Windows needs a clean start to recreate the key properly.
6. Run Windows Update. After reboot, go to Settings > Update & Security > Windows Update and click "Check for updates". Watch for the error to disappear. If it works, you'll see a normal update check with no 0X000006A9.

What if the error persists?

Sometimes the UUID isn't in the Windows Update key. The error can come from other places. Here are two less common variations I've fixed on client servers:

Variation 1: License activation UUID (Windows Server)

If you see the error when activating Windows or after a license key change, the UUID might be in the licensing registry. Go to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SL

Look for a value called ActivationToken or any value with a malformed GUID. Delete it (Windows will regenerate it on next activation attempt). Then run slmgr /ato from an admin command prompt to re-activate.

Variation 2: Third-party software UUID

Some backup tools or server monitoring software store UUIDs in their own registry keys. The error message usually shows a path in the details. Search the registry for that path using Ctrl + F in Regedit. Look for any string that looks like a broken GUID — missing hyphens, too short, or contains special characters. Delete or fix that string. For example, if it says ABC12345-6789-0 instead of {ABC12345-6789-0DEF-B123-456789ABCDEF}, that's your culprit.

Why does deleting the UUID key work?

Windows generates UUIDs automatically when they're missing or invalid. The SusClientId value is a unique identifier that the Windows Update client uses to talk to Microsoft's servers. If that identifier gets corrupted (say, from a partial registry write during a failed update), the client can't parse it, and throws 0X000006A9. By deleting the key, you let Windows start fresh — it creates a new, well-formed UUID on the next update check. It's like clearing a jammed paper from a printer: you're removing the bad input so the system can try again cleanly.

Preventing this error from coming back

I've seen this error repeat on servers that have bad RAM or failing hard drives. If the UUID gets corrupted more than once, run a memory test (use Windows Memory Diagnostic) and check your system drive with chkdsk /f. Also, avoid using third-party registry cleaners — they've caused this exact issue on two of my client's Domain Controllers. Stick to manual registry edits only when you know exactly what you're changing.

If you're still seeing 0X000006A9 after trying these steps, check the Application event log in Event Viewer. Look for an event ID 1000 or 1001 that points to the exact source. That log entry usually includes the registry path or file path with the bad UUID. Nine times out of ten, it's the Windows Update key. The other time, it's a backup agent or license manager that needs a fresh install.