Windows 10 updates errors and no window update extension error

If you are experiencing Windows 10 update errors, there are several common error codes and their mitigations you can try:

1. 0x80072EE2: This error indicates a timeout due to connectivity issues with Windows Update. Ensure your device can reach the update servers by checking your network connection and firewall settings.
2. 0x800F0920: This error suggests a hang detected during the operation. You can extend the timeout or increase resources on your device, especially if it's a virtual machine.
3. 0x800f081f: This error indicates that the source for a package or file is missing, which may be due to component store corruption. You can repair the component store using the Dism.exe /Online /Cleanup-Image /Restorehealth command.
4. 0x800f0831: This error means there is corruption in the Windows Component Store. Similar to the previous error, you can use the Dism command to repair it.

To extend Windows 10 updates, you may want to check your Windows Update settings and ensure that your system is configured to receive updates properly. Additionally, you can use the Windows Update Troubleshooter to reset any components that need it.

Regarding the issue with the "learn Profile" and adding a login under Login Account Management, it seems to be a separate issue not covered in the available context. You may need to consult specific support for that feature.

References:

• Windows Update common errors and mitigation
• Windows 10 upgrade error codes

Hi KDEPC,

It sounds like you are hitting a wall on two fronts: the technical requirement to keep Windows 10 secure after its End of Support (which occurred in October 2025) and an account management issue preventing you from fixing it.

Based on the errors "every way you try" and your intent to "extend" updates, you are likely trying to activate the Windows 10 Extended Security Updates (ESU) program. Since we are now past the official support cutoff, standard Windows Update channels will throw errors (often 0x80240030 or similar "license check failed" errors) if the device isn't properly "tagged" with an ESU license.

I'll show you how to resolve:

Part 1: "Extending" Updates (Fixing the ESU Error)

The generic error codes provided by the AI (0x800F0920, etc.) are for corrupted files, but your issue is likely Licensing. Windows Update will reject your request for new patches if it cannot find the ESU "ticket" on your system.

1. Install the Mandatory "Key" You cannot simply "extend" updates via a setting. You must install the Licensing Preparation Package. Without this specific update, your computer does not know how to process the ESU subscription, and Windows Update will fail repeatedly.

Go to the Microsoft Update Catalog or your update history and ensure KB5001716 (or its 2025 successor) is installed.

If you are an Enterprise user, ensure your ESU MAK Key is installed via slmgr /ipk <your-key>.

If you are a Consumer/Pro user, ensure your Microsoft Account (MSA) has the valid ESU subscription active.

2. Verify the License State Before trying to run Windows Update again, verify if the OS actually thinks it is allowed to update.

Open Command Prompt as Administrator.

Run: slmgr /dlv

Look for a line mentioning "Windows 10 ESU-Year1" (or similar).

If it says "Licensed": The extension is active. Your update error is likely a corruption issue (see step 3).

If it says "Unlicensed" or is missing: Windows Update will never work. You must resolve the purchase/activation first.

3. Reset the Update Components If slmgr says you are licensed but updates still fail, the update agent is likely stuck trying to download old, non-ESU content. Force a clean slate:

Open Command Prompt as Administrator.

Run the following strictly in order:

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 catroot2.old

net start wuauserv

net start cryptSvc

net start bits

net start msiserver

Restart the PC and check for updates again.

Part 2: The Microsoft Learn Profile Issue

The inability to add a login under "Login Account Management" usually stems from a session conflict between a "Work/School" (Azure AD) identity and a "Personal" (MSA) identity stored in your browser's cookies.

1. The "InPrivate" Workaround This is the fastest fix.

Open your browser and launch an Incognito/InPrivate window (Ctrl+Shift+N or Ctrl+Shift+P).

Navigate to the Microsoft Learn profile page.

Log in with your primary account first.

Attempt to add the secondary login.

Why this works: It bypasses the cached credentials that are likely confusing the identity portal.

2. Check for Account Alias Conflict If you are trying to link an email address that is already associated with another Microsoft Learn profile, it will fail silently or throw a generic error. You can only link an email to one Learn profile at a time. You may need to log in with the secondary email separately and "delete" that profile (or unlink the email) before you can attach it to your main profile.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to ACCEPT ANSWER. Should you have more questions, feel free to leave a message. Have a nice day!

VP