Extended Security Updates error message"Something went wrong"

Question

I need technical assistance as to why I continue to get the error message"Something went wrong" when trying to enroll in the extended security updates. I have all of the prerequisite downloads. I am not an IT professional. When I call the support numbers, I am hung up on. Please HELP.

Answer 1

Hello Sherila Jones-Tuggle,

The error message “Something went wrong” when trying to enroll in Extended Security Updates (ESU) usually indicates either a licensing mismatch or a prerequisite configuration that hasn’t been fully applied. Even if the downloads are installed, the activation process requires that the ESU licensing key is properly added and activated through the Volume Activation tools.

A few things to check: make sure your system has the latest cumulative updates installed, confirm that the ESU preparation package is applied, and then use the slmgr /ipk command to install the ESU key followed by slmgr /ato to activate it. If the activation fails, it often points to either a missing prerequisite update or a connectivity issue with the activation servers. Running Windows Update manually after applying the ESU key can also help finalize the enrollment.

Since you mentioned you are not an IT professional, I recommend carefully following Microsoft’s official ESU enrollment guide step by step. If the support line disconnects, you can also open a support ticket directly through the Microsoft Support website, which avoids phone queues.

I hope the response provided some helpful insight. If you find this answer useful, please hit “accept answer” so I know it addressed your concern.

Jason.

Answer 2

The generic “Something went wrong” message during Extended Security Updates (ESU) enrollment usually indicates one of three issues: prerequisites not fully met, region/eligibility problems, or activation/licensing problems.

Follow these checks step by step:

1. Confirm Windows version and edition
   • ESU for Windows 10 requires the device to be running Windows 10, version 22H2 and a supported edition (Home, Pro, Pro Education, or Workstation for consumer ESU; other editions for commercial ESU scenarios).
   • If the device is not on 22H2, install the latest Windows 10 cumulative update first. Devices must have the latest update installed.
2. Make sure all ESU prerequisites are actually installed and the device is restarted
   • For ESU scenarios, missing prerequisite updates commonly cause failures or “not applicable”/generic errors.
   • Verify in Control Panel → Programs → Programs and Features → View installed updates that the required Servicing Stack Update (SSU) and any ESU-enabling updates are present.
   • If an ESU-related update shows “The update is not applicable to your computer,” it usually means the package does not match the edition/architecture or the OS is not at the required level. In that case:
     1. Confirm the update package matches the device’s edition (Home/Pro/etc.) and architecture (x64 vs ARM).
     2. Restart the device and try installing the package again.
     3. If it still fails, follow the guidance under “The update is not applicable to your computer” in Troubleshoot issues in ESU.
3. Check for ESU-specific installation/activation errors
   • If using ESU product keys (commercial ESU, Windows 7/Server, or volume scenarios) and running slmgr.vbs /ipk, the error 0xC004F050 (“product key is invalid”) indicates either:
     • The ESU licensing rollup/security-only/standalone package is not installed, or
     • The device was not restarted after installing prerequisites.
   • In that case:
     1. Confirm all ESU prerequisite updates are installed successfully in update history.
     2. Confirm the ESU key matches the correct product and edition.
     3. Restart the device and run the key installation again.
4. If the message appears when installing ESU updates themselves
   • If an ESU security update installs, reboots, and then shows “Failure to configure Windows updates. Reverting changes” and appears as Failed in Update History, this is expected when:
     • The edition is not supported for ESU, or
     • No ESU MAK add-on key is installed and activated.
   • Verify:
     1. The Windows edition is in the supported ESU list.
     2. The ESU key is installed and activated (for MAK-based ESU).
     3. All prerequisites from the “How to get this update” section of the specific KB are installed.
5. Region and account issues (consumer Windows 10 ESU)
   • For consumer Windows 10 ESU enrollment (through Settings → Update & Security), ESU availability can depend on region and Microsoft account configuration.
   • If ESU is reported as not available in the region or enrollment fails with a generic error, users have resolved it by:
     1. Signing in with a Microsoft account instead of a local account when enabling ESU.
     2. Ensuring that account is an administrator and not a child account.
     3. Turning on location services and restarting the PC, then trying enrollment again.
6. When all prerequisites are met but errors persist
   • For Windows client ESU issues that persist after confirming prerequisites, edition, and activation:
     1. Copy the CBS log file from C:\Windows\Logs\CBS\CBS.log.
     2. Contact Microsoft Support and provide this log file. ESU support covers installation, key activation, and regressions caused by ESU when there is an active support plan.

If the device is Windows 10 and the goal is to stay on Windows 10 past October 14, 2025, ensure it is on 22H2, meets the ESU device prerequisites, and is properly enrolled in the Windows 10 ESU program as described in the ESU documentation.

---

References:

• Troubleshoot issues in ESU
• September 13, 2022—KB5017373 (Security-only update)
• Windows 10 Consumer Extended Security Updates (ESU) program
• Extended Security Updates (ESU) program for Windows 10
• Extended Security Updates (ESU) Slovenia Win10 - Microsoft Q&A
• Lifecycle FAQ - Extended Security Updates