Win 11 OEM Activation problems on Laptop w/ Win 10 S Mode

• Same laptop
• Same Windows 11 Home media
• Normal manual install activates
• Unattended install does not

Most likely cause​

• Microsoft-Windows-Setup\UserData\ProductKey\Key = which image/edition to install
• Microsoft-Windows-Shell-Setup\ProductKey = what key to use for activation

1. reads the embedded OEM marker/key from firmware,
2. installs the matching edition,
3. and activates online afterward if the edition matches the device’s entitlement.

Why your errors fit that theory​

• 0xC004C003 commonly appears when the key/channel being used is not accepted for activation.
• 0x8004FE94 is also consistent with a licensing/activation path going sideways rather than the device lacking entitlement.
• The broken “activate by phone” country list is likely a side-effect of the licensing state/setup path, not the root cause.

Things in autounattend.xml to inspect first​

1. Any ProductKey entry at all
   • Microsoft-Windows-Setup\UserData\ProductKey
   • Microsoft-Windows-Shell-Setup\ProductKey
2. Edition forcing
   • InstallFrom
   • MetaData
   • /IMAGE/NAME
   • /IMAGE/INDEX
3. Anything that injects generic/default keys
   • especially common in “skip setup questions” templates downloaded from forums or generators
4. Anything copied from Pro/Enterprise examples
   • even if the install ends up showing Home

My practical recommendation​

• Do not specify any product key in the answer file unless you truly need one.
• Do not force edition by key unless you are certain the edition mapping is correct.
• If you must force image selection, do it by image name/index only, not by activation key.
• Let Setup use the machine’s existing entitlement and firmware/OEM data.

Best next test​

Test A​

• Microsoft-Windows-Setup\UserData\ProductKey
• Microsoft-Windows-Shell-Setup\ProductKey

Test B​

Test C​

• Settings > System > Activation
• Installed edition = Windows 11 Home
• Activation status text

Commands worth running on a failed unattended install​

slmgr /dlv
slmgr /xpr
wmic path softwarelicensingservice get OA3xOriginalProductKey

• whether Windows sees an OA3 OEM key in firmware,
• whether the installed channel/edition looks wrong,
• whether the machine is trying to activate with some other key instead.

Important nuance about S Mode​

For your nonprofit rollout​

• Never include product keys in unattended files for OEM-refurb/redeployment scenarios unless there is a licensing reason you fully control.

• partitioning
• locale
• OOBE suppression
• local account creation
• privacy defaults

My likely diagnosis in one sentence​

ChatGPT said:

What you’re describing strongly suggests the autounattend.xml is overriding or interfering with the OEM/digital-license path, not that the laptop suddenly lost its entitlement.
The biggest clue is this:

• Same laptop
• Same Windows 11 Home media
• Normal manual install activates
• Unattended install does not

That almost always points to the answer file, not the license itself.

Most likely cause​

In unattend, Microsoft separates:

• Microsoft-Windows-Setup\UserData\ProductKey\Key = which image/edition to install
• Microsoft-Windows-Shell-Setup\ProductKey = what key to use for activation

Microsoft explicitly documents that the Setup\ProductKey setting selects the Windows image, while the Shell-Setup\ProductKey setting is for activation, and the two can be different. An invalid or inappropriate key in the answer file can therefore break activation even if the machine would have activated normally using its embedded OEM key/digital license. Microsoft also notes that invalid product-key values in the answer file can cause setup/licensing problems. citeturn0search17
On OEM laptops like your HP, a standard interactive install usually does the right thing automatically:

1. reads the embedded OEM marker/key from firmware,
2. installs the matching edition,
3. and activates online afterward if the edition matches the device’s entitlement.

Microsoft’s activation guidance says that on reinstall, if the device already has a digital license, you should reinstall the same edition and, if prompted, use “I don’t have a product key” so Windows can reactivate automatically after setup. It also stresses that the installed edition must match the license. citeturn0search17

Why your errors fit that theory​

• 0xC004C003 commonly appears when the key/channel being used is not accepted for activation.
• 0x8004FE94 is also consistent with a licensing/activation path going sideways rather than the device lacking entitlement.
• The broken “activate by phone” country list is likely a side-effect of the licensing state/setup path, not the root cause.

Things in autounattend.xml to inspect first​

Look very closely for any of these:

1. Any ProductKey entry at all
   • Microsoft-Windows-Setup\UserData\ProductKey
   • Microsoft-Windows-Shell-Setup\ProductKey
2. Edition forcing
   • InstallFrom
   • MetaData
   • /IMAGE/NAME
   • /IMAGE/INDEX
3. Anything that injects generic/default keys
   • especially common in “skip setup questions” templates downloaded from forums or generators
4. Anything copied from Pro/Enterprise examples
   • even if the install ends up showing Home

My practical recommendation​

For OEM Home devices like this, the safest unattended approach is:

• Do not specify any product key in the answer file unless you truly need one.
• Do not force edition by key unless you are certain the edition mapping is correct.
• If you must force image selection, do it by image name/index only, not by activation key.
• Let Setup use the machine’s existing entitlement and firmware/OEM data.

Best next test​

Do a binary-isolation test:

Test A​

Use your autounattend.xml exactly as-is, but remove both of these if present:

• Microsoft-Windows-Setup\UserData\ProductKey
• Microsoft-Windows-Shell-Setup\ProductKey

If activation starts working, you’ve found the culprit.

Test B​

If still broken, remove any explicit image-selection block too, and keep only your local-account/OOBE automation.

Test C​

After install, check:

• Settings > System > Activation
• Installed edition = Windows 11 Home
• Activation status text

Commands worth running on a failed unattended install​

Open elevated Command Prompt:

Code:

slmgr /dlv
slmgr /xpr
wmic path softwarelicensingservice get OA3xOriginalProductKey

What to look for:

• whether Windows sees an OA3 OEM key in firmware,
• whether the installed channel/edition looks wrong,
• whether the machine is trying to activate with some other key instead.

If OA3xOriginalProductKey returns a key, that’s even more evidence the unattended file is bypassing what Setup would normally use.

Important nuance about S Mode​

Since the machine originally shipped with Windows 10 Home in S mode, your prior switch out of S mode should not by itself prevent later activation of the underlying licensed Home edition. The fact that normal Windows 11 Home installs activate supports that the entitlement is fine; the unattended process is what’s changing behavior.

For your nonprofit rollout​

Before using the same XML on similar devices, I would standardize on this rule:

• Never include product keys in unattended files for OEM-refurb/redeployment scenarios unless there is a licensing reason you fully control.

For mixed donated/OEM laptops, unattended files should ideally handle:

• partitioning
• locale
• OOBE suppression
• local account creation
• privacy defaults

…but not licensing.

My likely diagnosis in one sentence​

Your autounattend.xml is probably supplying or implying a key/edition selection that overrides the HP’s normal OEM/digital-license activation path.
If you want, paste the autounattend.xml here and I’ll go through it line by line and tell you exactly which entries are likely breaking activation.

Click to expand...

ChatGPT said:

What you’re describing strongly suggests the autounattend.xml is overriding or interfering with the OEM/digital-license path, not that the laptop suddenly lost its entitlement.
The biggest clue is this:

• Same laptop
• Same Windows 11 Home media
• Normal manual install activates
• Unattended install does not

That almost always points to the answer file, not the license itself.

Most likely cause​

In unattend, Microsoft separates:

• Microsoft-Windows-Setup\UserData\ProductKey\Key = which image/edition to install
• Microsoft-Windows-Shell-Setup\ProductKey = what key to use for activation

Microsoft explicitly documents that the Setup\ProductKey setting selects the Windows image, while the Shell-Setup\ProductKey setting is for activation, and the two can be different. An invalid or inappropriate key in the answer file can therefore break activation even if the machine would have activated normally using its embedded OEM key/digital license. Microsoft also notes that invalid product-key values in the answer file can cause setup/licensing problems. citeturn0search17
On OEM laptops like your HP, a standard interactive install usually does the right thing automatically:

1. reads the embedded OEM marker/key from firmware,
2. installs the matching edition,
3. and activates online afterward if the edition matches the device’s entitlement.

Microsoft’s activation guidance says that on reinstall, if the device already has a digital license, you should reinstall the same edition and, if prompted, use “I don’t have a product key” so Windows can reactivate automatically after setup. It also stresses that the installed edition must match the license. citeturn0search17

Why your errors fit that theory​

• 0xC004C003 commonly appears when the key/channel being used is not accepted for activation.
• 0x8004FE94 is also consistent with a licensing/activation path going sideways rather than the device lacking entitlement.
• The broken “activate by phone” country list is likely a side-effect of the licensing state/setup path, not the root cause.

Things in autounattend.xml to inspect first​

Look very closely for any of these:

1. Any ProductKey entry at all
   • Microsoft-Windows-Setup\UserData\ProductKey
   • Microsoft-Windows-Shell-Setup\ProductKey
2. Edition forcing
   • InstallFrom
   • MetaData
   • /IMAGE/NAME
   • /IMAGE/INDEX
3. Anything that injects generic/default keys
   • especially common in “skip setup questions” templates downloaded from forums or generators
4. Anything copied from Pro/Enterprise examples
   • even if the install ends up showing Home

My practical recommendation​

For OEM Home devices like this, the safest unattended approach is:

• Do not specify any product key in the answer file unless you truly need one.
• Do not force edition by key unless you are certain the edition mapping is correct.
• If you must force image selection, do it by image name/index only, not by activation key.
• Let Setup use the machine’s existing entitlement and firmware/OEM data.

Best next test​

Do a binary-isolation test:

Test A​

Use your autounattend.xml exactly as-is, but remove both of these if present:

• Microsoft-Windows-Setup\UserData\ProductKey
• Microsoft-Windows-Shell-Setup\ProductKey

If activation starts working, you’ve found the culprit.

Test B​

If still broken, remove any explicit image-selection block too, and keep only your local-account/OOBE automation.

Test C​

After install, check:

• Settings > System > Activation
• Installed edition = Windows 11 Home
• Activation status text

Commands worth running on a failed unattended install​

Open elevated Command Prompt:

Code:

slmgr /dlv
slmgr /xpr
wmic path softwarelicensingservice get OA3xOriginalProductKey

What to look for:

• whether Windows sees an OA3 OEM key in firmware,
• whether the installed channel/edition looks wrong,
• whether the machine is trying to activate with some other key instead.

If OA3xOriginalProductKey returns a key, that’s even more evidence the unattended file is bypassing what Setup would normally use.

Important nuance about S Mode​

Since the machine originally shipped with Windows 10 Home in S mode, your prior switch out of S mode should not by itself prevent later activation of the underlying licensed Home edition. The fact that normal Windows 11 Home installs activate supports that the entitlement is fine; the unattended process is what’s changing behavior.

For your nonprofit rollout​

Before using the same XML on similar devices, I would standardize on this rule:

• Never include product keys in unattended files for OEM-refurb/redeployment scenarios unless there is a licensing reason you fully control.

For mixed donated/OEM laptops, unattended files should ideally handle:

• partitioning
• locale
• OOBE suppression
• local account creation
• privacy defaults

…but not licensing.

My likely diagnosis in one sentence​

Your autounattend.xml is probably supplying or implying a key/edition selection that overrides the HP’s normal OEM/digital-license activation path.
If you want, paste the autounattend.xml here and I’ll go through it line by line and tell you exactly which entries are likely breaking activation.

Click to expand...

Glad that solved it​

Good rule for your nonprofit rollout​

1. Do not include any ProductKey entry in autounattend.xml.
2. Do not force activation-related settings unless you truly need them.
3. Keep the XML focused on:
   • partitioning
   • locale
   • OOBE options
   • local account creation
   • privacy/setup defaults
4. Test the XML on one known-good machine before using it broadly.

Practical takeaway​

That’s a very good observation​

• it’s probably not S mode by itself
• it’s more likely the combination of an OEM Home/S-mode licensing path plus the dummy ProductKey entry that caused Setup to take the wrong activation route.

Why this laptop was more likely to expose the problem​

1. Windows 11 in S mode is only available on Home edition.
2. If a device starts as Windows 10 Home in S mode, upgrading targets Windows 11 Home in S mode.
3. Windows activation/reactivation depends on the same edition remaining in place, and digital licensing is tied to the device’s hardware.

In practical terms​

1. Never use placeholder keys in unattended files, even all-zero values.
2. On OEM redeployments, let Windows use the device’s embedded/OEM entitlement.
3. Make sure the reinstall stays on the same edition the device is licensed for.

For your rollout template​

1. Remove all ProductKey entries from the generic nonprofit deployment XML.
2. Only force edition if you absolutely must, and then only when you’re certain it matches the licensed edition.
3. Keep one XML for OEM redeployments and a separate one for any scenario where you truly need license-driven setup behavior.