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

[mfi10011]

I purchased an HP laptop model 15-dw3033dx from Best Buy a few years ago. These had Windows 10 in S-Mode preinstalled.

First thing I did after OOBE and initial activation was to go to the Windows Store and switch the laptop out of S-Mode, then I did a clean install of Windows 10 Home. I run it with a local account only.

When I did a clean install from a fresh Win 11 Home 25H2 download with a local account, the system activated as expected.

However, when I did a Win 11 Home 25H2 install with a customized autounattend.xml file and local account, I get an activation error with code 0xC004C003. I installed from the SAME media to the SAME laptop, the only difference being having the custom autounattend.xml file or not.

I then did a clean install of Win11 Home 25H2 WITHOUT the custom autounattend.xml file and logged in with a Microsoft account. The Activation was normal.

On the same laptop and same media, I reinstalled Win 11 25H2 Home using the custom autounattend.xml file and logged in with a Microsoft Account. This time, I get an activation error with code 0x8004FE94. I am also given an option to activate by phone, but the countries listed goes from Afghanistan to Palau, and NOTHING past Palau.

There was an option to say I changed hardware on the device so I gave that a try. I get a "Unable to activate Windows" message.

Bottom Line - on the same laptop (sold w/ Win10 S Mode and switched out) and same install media, clean install of Windows 11 Home activates normally, customized autounattend.xml install gives activation error.

I have some other similar devices at a local nonprofit to migrate to Win11 so all suggestions and insights are welcome!

 

[ChatGPT]

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:

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.

 

[mfi10011]

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:

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.

(edit: contents of the autoattend.xml file deleted, see next reply)

 

[mfi10011]

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:

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.

That was it, the autounattend.xml generator I used added a ProductKey entry with all zeroes, and normally Windows would stop and ask for a Product Key. Once the entry was removed, the screen was skipped and the reinstall was complete, and it activated normally as expected. Impressed with ChatGPT!

Thank You!

 

[ChatGPT]

Glad that solved it​

That makes perfect sense — the all-zero ProductKey entry was the culprit.
Windows Setup was treating that as an explicit key value instead of falling back to the laptop’s normal OEM/digital license path. Once you removed it, Setup could proceed normally and activation worked the way it should.

Good rule for your nonprofit rollout​

For OEM laptops that already have a valid Home license:

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​

If an unattended install behaves differently from a manual install on the same hardware and same media, the answer file is usually the first place to look.
Thanks for reporting back with the fix — that’ll definitely help the next person who runs into the same issue.
And thank you for the kind words. Glad you got it activated normally.

 

[mfi10011]

Note that I had used the "bad" autounattend.xml with the ProductKey entry on many installations without activation issues, but I believe this is the first laptop I used it with that was originally shipped with Windows 10 S Mode which triggered these activation issues - the rest were shipped with Home or Pro.

 

[ChatGPT]

That’s a very good observation​

I think your hunch is reasonable, with one important nuance:

• 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​

Microsoft says:

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.

So this HP was almost certainly a very “strictly Home” OEM case. My read is that the all-zero key interfered with the normal Home OEM/digital-license fallback, while some of your other Home/Pro machines likely still found a workable activation path despite the bad XML. That part is an inference, but it fits the behavior you saw across devices.

In practical terms​

The lesson is probably:

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​

I’d treat this as your safe policy:

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.

So yes — your S-mode note is probably a real clue, but the root cause still looks like the bad key entry, with the S-mode/Home OEM licensing path simply being the first environment where it failed visibly.