Based on the ESU requirements and known enrollment issues, the following checks and steps are relevant for resolving repeated “Something went wrong. We can't enroll you in ESU right now” during Windows 10 Consumer ESU enrollment:
- Confirm all ESU prerequisites
- Windows 10 edition must be one of:
- Home, Pro, Pro Education, or Workstation
- Version must be 22H2.
- The device must have the latest Windows 10 updates installed.
- The Microsoft account used to sign in must:
- Be an administrator account on the device.
- Not be a child account.
- Windows 10 edition must be one of:
- Verify Microsoft account vs local account
- ESU licensing is tied to a Microsoft account, not a local account.
- If signed in with a local account, enrollment will prompt for a Microsoft account sign-in.
- If enrollment keeps failing, explicitly sign in with a Microsoft account that meets the requirements:
- Go to Settings → Accounts → Your info and ensure the account shown is a Microsoft account and an administrator.
- If necessary, switch to a local account and then back to the correct Microsoft account to refresh the link between the device and the account, as other users have reported this resolved ESU enrollment failures.
- Ensure the account is not managed by an organization
- If the device or account was previously allowed to be managed by an organization (for example, by accepting a prompt like “Allow my organization to manage this device”), this can interfere with consumer ESU enrollment.
- Removing such management or using a clean, non-managed Microsoft account profile on the device has resolved similar account-related issues in other scenarios.
- Check rollout and device state
- ESU is rolling out gradually to eligible Windows 10 22H2 devices.
- Some users have resolved missing or failing enrollment flows by:
- Ensuring only one primary user account is present and is an administrator.
- In more extreme cases, performing a clean install of Windows 10 22H2, then checking Windows Update again, where the ESU enrollment option appeared and worked.
- If ESU key activation is used (enterprise/volume scenarios)
- For environments using ESU keys and
slmgr/VAMT instead of the consumer in-place enrollment flow, typical activation failures are caused by:- Missing prerequisite updates (resulting in errors like 0xC004F050).
- Lack of elevated privileges (0xC004F025).
- Connectivity issues to Microsoft Activation services (0x80072EE7, 0x80072EE2).
- In those cases, verifying all prerequisite updates, running activation from an elevated Command Prompt, and ensuring internet connectivity or correct VAMT/TLS configuration is required.
- For environments using ESU keys and
Given that the device already meets version and admin requirements and that Rewards points have been redeemed, the most impactful next steps are:
- Confirm the signed-in account is a Microsoft account, not a child account, and is an administrator.
- If enrollment still fails, sign out and:
- Switch to a local account, then
- Sign back in with the intended Microsoft account and retry ESU enrollment from Settings → Update & Security → Windows Update → Enroll now.
- If the device has been joined to or managed by an organization, use a non-managed profile or, if feasible, a clean Windows 10 22H2 installation with only a single administrator Microsoft account, then attempt enrollment again.
References:
- Windows 10 Consumer Extended Security Updates (ESU) program
- Troubleshoot issues in ESU
- Extended Security Updates (ESU) Slovenia Win10 - Microsoft Q&A
- Audio garbled after new Windows 10 installation - do I need different drivers? - Microsoft Q&A
- ESU Enrol not yet showing on one device - Microsoft Q&A
- Cannot perform Win10 ESU Offline Activation using Proxy Scenario 2 activation - Microsoft Q&A
- Device management could not be enabled - Microsoft Q&A