Share via

Windows 11 version 23H2 download error 0x80246019

Anonymous
2024-06-14T19:15:15+00:00

Windows11 version 23H2 shows up in my Windows Update, but it will not install or download. The error code is 0x80246019.

I ran the "Windows Update Troubleshooter" but that did not fix the problem

The event log shows "MoUpdateOrchestrator Success Content Download Download started", then 2 minutes later "MoUpdateOrchestrator Failure Content Download Error: Download failed."

Any help would be appreciated, thank you

Windows for home | Windows 11 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

15 answers

Sort by: Most helpful
  1. Anonymous
    2024-06-14T20:48:27+00:00

    Hi, I'm Robinson, and I’m happy to help you today.

    Usually, this problem is caused by corrupted files on Windows or a corruption of the Windows Update cache. You can use these commands to repair the corrupted files on Windows and reset the Windows Update cache.

    Step 1: Check if there are any corrupted files on Windows.

    1-Right-Click on Start then click on Windows Terminal (admin)

    2- Type these commands.

    sfc /scannow (and press Enter)

    Dism /Online /Cleanup-Image /ScanHealth (and press Enter)

    Dism /Online /Cleanup-Image /CheckHealth (and press Enter)

    3- The DISM tool will report whether the image is healthy, repairable, or non-repairable. If the image is repairable, you can use the /RestoreHealth argument to repair the image.

    4-Type this command and press Enter:

    Dism /Online /Cleanup-Image /RestoreHealth

    Step 2: Reset Windows Update components

    1-Right-Click on Start then click on Windows Terminal(admin)

    2-Type these commands:

    net stop wuauserv (and press Enter)

    net stop cryptSvc (and press Enter)

    net stop bits (and press Enter)

    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old (and press Enter)

    ren C:\Windows\System32\catroot2 Catroot2.old (and press Enter)

    net start wuauserv (and press Enter)

    net start cryptSvc (and press Enter)

    net start bits (and press Enter)

    netsh winsock reset (and press Enter)

    3-Reboot your PC and try to install the update again

    I hope this information helps. If you have any questions or the problem persists, please let me know and I'll be glad to assist you further.

    20+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-01-02T11:39:46+00:00

    If anyone is having this issue, I got 0x80246019 because my computer's date and time was wrong, since it was not turned on for a while and automatic date update didn't work properly.

    Might be something you miss if you had a similar case.

    6 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-07-13T05:58:57+00:00

    I am having the same error code and tried the steps you gave and when enter the

    C:\Windows\System32>ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

    A duplicate file name exists, or the file

    cannot be found.

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

    A duplicate file name exists, or the file

    cannot be found.

    Any assistance would be greatly appreaciated!

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2025-01-29T20:07:54+00:00

    Hey, Robinson.

    I have an issue that i am stuck into,

    My laptop i did the steps till step 4 and to restore image health but the repair is stuck in 63 percent for almost 20 minutes, i am in need for a solution ASAP, even if the solution is to abort the repair and end mid process safely

    Thank you for understanding.

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-06-15T15:21:11+00:00

    Thanks for the reply! It looks like 23H2 was successfully installed overnight

    1 person found this answer helpful.
    0 comments No comments