Share via

Win 11 Pro to Enterprise step-up license not triggering

Felduv Garnat 0 Reputation points
2026-04-30T01:47:50.12+00:00

All our users have Microsoft 365 E3 licenses, which should automatically step up their Windows 11 Pro machines to Enterprise when they log in. For some reason, about 20% of our fleet is stuck on Pro. They show as active in Entra, but the OS refuses to upgrade. Rebooting doesn't help. Any quick fixes to force the license check?

Windows for business | Windows Client for IT Pros | Devices and deployment | Licensing and activation
0 comments No comments

2 answers

Sort by: Most helpful
  1. Tracy Le 8,070 Reputation points Independent Advisor
    2026-04-30T02:35:12.1966667+00:00

    Hi Felduv Garnat,

    The AI gives good theory, but telling an IT admin to wait up to four days for a cache to clear is not practical.

    Here is the exact way to force the Enterprise step-up immediately without waiting:

    1. Force a PRT Refresh: Open Command Prompt as the affected logged-in user (do not run as admin for this specific step) and run: dsregcmd /refreshprt This forces Entra ID to issue a fresh Primary Refresh Token containing the updated E3 license claim.

    2. Trigger the Hidden Acquisition Task: Now, open Command Prompt as Administrator and force the scheduled task that actually checks the license: schtasks.exe /Run /TN "\Microsoft\Windows\Subscription\LicenseAcquisition"

    3. The Base Key Trap (Most Common Cause for the 20%): If steps 1 and 2 do not step it up instantly, those specific machines are likely using a MAK or weird OEM key. Subscription activation only triggers over a standard Pro retail/OEM base. To fix this, go to Settings > System > Activation, click Change Product Key, and enter the Microsoft generic Windows 11 Pro key: VK7JG-NPHTM-C97JM-9MPGT-3V66T

    Sign out, sign back in, and those stubborn machines will step up to Enterprise instantly. If this fixes your fleet, please click "Accept Answer".

    Tracy.

    Was this answer helpful?

    0 comments No comments

  2. Q&A Assist
    2026-04-30T01:48:19.2533333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Use subscription-activation troubleshooting steps to force the step-up and identify why those devices stay on Pro.

    1. Verify the device meets all requirements
      1. On each affected device, confirm it runs a supported Windows Pro build:
        • Run winver.exe and compare with the Windows 10/11 release information to ensure it is in support.
      2. Confirm it is Microsoft Entra joined or hybrid joined:
        • Run in a command prompt:
                  dsregcmd.exe /status
          
        • Under Device State, AzureAdJoined must be YES (or hybrid-joined via Microsoft Entra Connect).
      3. Confirm the underlying Pro license is activated:
        • Open Settings > System > Activation (or run ms-settings:activation).
        • Under Activation state, it must show Windows is activated with a digital license.
        • If it shows Windows is not activated or error 0xC004F034, Pro must be activated first (for devices without a firmware-embedded key, manually enter a valid Pro key).
    2. Confirm the user’s Enterprise subscription is applied
      • In Settings > System > Activation, expand Subscription.
        • It should show Windows 11 Enterprise subscription is active.
        • If the Subscription section is missing or shows Windows Enterprise subscription isn't valid, verify in Microsoft Entra ID / Microsoft 365 admin center that the user has an active Windows Enterprise E3/E5 (via Microsoft 365 E3) license assigned and that it has not lapsed or been removed.
    3. Force a fresh activation/step-up check
      1. Make sure the device is online and can reach Windows Update / activation endpoints.
      2. Ensure the policy Do not connect to any Windows Update Internet locations is Disabled or Not Configured so the activation-related registry value is not forced back to 1.
      3. Sign out and sign back in with the licensed Microsoft Entra user on the affected device.
      4. Allow for the built-in cache delay: subscription activation can take up to four days after a qualifying purchase or license change before upgrade eligibility is re-evaluated.
    4. Validate via slmgr
      • Run in an elevated command prompt:
             slmgr /dli
        
        or
             slmgr /dlv
        
      • Confirm the underlying edition is Pro and that the License Status is Licensed. If Pro is not properly licensed, fix that first; subscription activation does not remove the requirement to have the base OS activated.
    5. Typical quick-fix pattern for stuck devices
      • For each affected machine:
        1. Confirm: supported Pro build, AzureAdJoined = YES, Pro activated.
        2. Confirm: user has Windows Enterprise E3/E5 via Microsoft 365 E3.
        3. Ensure the Windows Update Internet locations policy is not blocking.
        4. Sign out/in with the licensed user while connected to the internet and wait for the cache to refresh (may take some time, up to several days in worst case).
      • Once all conditions are met, the device should step up from Pro to Enterprise and show the Enterprise subscription as active.

    References:

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.