After the May 2026 cumulative, previously activated Windows 10 and 11 devices throw 0x8007007B with the message "The filename, directory name, or volume label syntax is incorrect." Settings shows Windows is not activated. The KMS or product key reference looks fine. The desktop watermark comes back.

Root cause is a channel mismatch the update exposes. A device that shipped retail but later got a volume license (or vice versa) had the mismatch papered over until this CU tightened key validation. Same thing happens after motherboard or TPM replacements that fell back to a stale key.

Identify Your License Channel

Run elevated:

slmgr /dlv

Note the Description line. RETAIL channel or VOLUME_KMSCLIENT channel tells you what the current key expects. If your environment uses KMS or AD-based activation, the device needs a VOLUME key. If it is a one-off retail purchase, it needs a retail key.

Volume Environment (KMS or AD-Based Activation)

Install the correct KMS client setup key for the SKU. Microsoft publishes the full list in the KMS client setup keys article. Common Windows 11 Pro example:

slmgr /ipk W269N-WFGWX-YVC9B-4J6C9-T83GX
slmgr /skms kms.yourdomain.local:1688
slmgr /ato

Replace the key with the one matching your SKU (Pro, Enterprise, Education).

Retail Device After Hardware Change

Sign in with the Microsoft account previously linked to the device. Settings, System, Activation, Troubleshoot. Pick "I changed hardware on this device recently" and select the right entry.

Device Flipped from Retail to Volume by MDM

Run the activation troubleshooter first (Settings, Activation, Troubleshoot). If it fails, clear the stale key and reapply.

slmgr /upk
slmgr /cpky
slmgr /ipk <YOUR-CORRECT-KEY>
slmgr /ato

Verify

After reactivation:

slmgr /xpr

You should see The machine is permanently activated (retail or digital) or a 180-day KMS window. If slmgr /ato still throws 0x8007007B, the key you applied does not match the SKU edition. Pull the edition with Get-ComputerInfo | Select-Object WindowsProductName, OsName, then re-pick the key.

Why This Hit Now

The May 2026 servicing change validates the key channel against the running SKU on every activation refresh, not just at install. Devices that drifted (hardware swap, MDM key push, OEM-to-volume reimage without a clean wipe) now fail audit immediately. Same machine, same key, stricter check.

Need help auditing license channels across your fleet before more devices fail? Rain City Techworks handles managed IT and security for businesses in the Seattle and Tacoma area.