Windows 10 Version 22H2 (KB5022834) will not update

Anonymous
2023-02-15T16:34:29+00:00

2023-02 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5022834) will not update for the past month.

The message "We couldn't complete the updates. Undoing changes" keeps appearing.

I am on

Edition: Windows 10 Home

Version: 22H2

Installed on: 25/12/2020

OS Build: 19045.2251

Experience: Windows Feature Experience Pack 120.2212.4180.0

I have tried running the Windows Update troubleshooter.

I am unsure what else to do as I am a newbie at this.

I would appreciate any assistance with this.

Thanks in advance.

Windows for home | Windows 10 | 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

100 answers

Sort by: Most helpful
  1. Anonymous
    2023-02-18T22:30:29+00:00

    Hello,

    I also don't understand why I need to completely download and reinstall Windows 10 as well. There is an issue with the update itself. Will the Microsoft team be taking a closer look at the release? I can advise when the update fails it does rollback the update altogether. I just went ahead and paused my updates for the time being.

    Also, I have seen the tips on restarting / resetting the Windows Update via an elevated Command prompt. That did not work as well.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Ramesh 181.4K Reputation points Volunteer Moderator
    2023-04-10T05:55:10+00:00

    The problem lies in the mofcomp procedure, one of the steps performed by the KB5022834 installer. The EventTrace WMI class is missing, which indicates the WMI repository is damaged. See if the following repair method helps.

    • sc config winmgmt start= disabled
    • net stop winmgmt
    • CD %WINDIR%\System32\Wbem\Repository
    • DEL /F /Q /S %WINDIR%\System32\Wbem\Repository\*.*
    • CD %WINDIR%\System32\Wbem
    • for /f %s in ('dir /b *.dll') do regsvr32 /s %s
    • wmiprvse /regserver
    • sc config winmgmt start= auto
    • net start winmgmt
    • for /f %s in ('dir /b *.mof') do mofcomp %s
    • for /f %s in ('dir /b *.mfl') do mofcomp %s
    • dism /online /cleanup-image /restorehealth
    • sfc /scannow

    And then test by running the following command:

    • mofcomp "C:\windows\system32\wbem\netprofm.mof"

    If you still get the error 0x80041002, try one of the following:

    Copy the %WINDIR%\System32\Wbem\Repository folder from another computer. You may need to stop the WMI service first.

    or

    Repair install Windows 10. See How to perform an In-place Upgrade with Windows 10 Step-by-Step Guide - Microsoft Community: https://answers.microsoft.com/en-us/windows/forum/all/how-to-perform-an-in-place-upgrade-with-windows-10/7f0b236e-3c6c-4913-9691-c4baa2a6190a

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-03-01T12:11:07+00:00

    There would appear to be a number of issues that might occur and no one thing will fix this for everyone. I had a lot of good help from Ramesh by opening a new thread and a fix was tailored for my machine.

    Trying to talk to many people in this thread is going to get very messy very quickly, so breaking it out into separate threads helps focus the issue. Once enough issues have been solved then patterns might emerge that help a great many more people.

    Please help the support professionals help you by starting a new thread, where requested, and providing the logs that make remote diagnosis possible.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-02-24T12:40:38+00:00

    I'm also experiencing this failure issue from Windows update.

    Having looked through the CBS logs I can see that the x64 version of the update is using the amd64 architecture to perform the installation. I have an Intel i5-13600K CPU.

    I have taken the x64 installer from the Microsoft Update Catalog and found that it also tries to install for the amd64 architecture.

    Hope this helps identify the issue and root cause in the update.

    Download link for CBS logs, systeminfo, and analysis: https://www.dropbox.com/s/mo78yaawt8lup99/KB5022834%20install%20failure%20analysis.zip?dl=0

    2023-02-24 12:05:22, Info CBS Adding an owner for inf: usbxhci.inf, arch: amd64, hash: +3JV2xdRoUCYkbcF1afHH36eEAtqpcClJzqHg/NMi8s=, owner: Microsoft-Windows-Client-Desktop-Required-Package05110~31bf3856ad364e35~amd64~~10.0.19041.2604~7D10AD543E96E47608426F3F459B84DB8C827BFF59C3C319CE3A26695A8552C6
    ...
    2023-02-24 12:05:22, Info CBS Perf: Doqe: Install started.
    2023-02-24 12:05:22, Info CBS Doqe: [Forward] Installing driver updates, Count 365
    2023-02-24 12:05:22, Info CBS Startup: Changing logon timeout to a sliding window timeout: 900000
    2023-02-24 12:05:22, Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Percent progress: 7.
    2023-02-24 12:05:23, Info CBS INSTALL index: 67, phase: 1, result 0, inf: multiprt.inf
    ...
    2023-02-24 12:05:23, Info CBS INSTALL index: 707, phase: 2, result 0, inf: usbstor.inf
    2023-02-24 12:05:23, Info CBS INSTALL index: 708, phase: 2, result 13, inf: usbxhci.inf
    2023-02-24 12:05:23, Info CBS Doqe: Recording result: 0x8007000d, for Inf: usbxhci.inf
    2023-02-24 12:05:23, Info CBS DriverUpdateInstallUpdates failed [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    2023-02-24 12:05:23, Info CBS Doqe: Failed installing driver updates [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    2023-02-24 12:05:23, Info CBS Perf: Doqe: Install ended.
    2023-02-24 12:05:23, Info CBS Failed installing driver updates [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    2023-02-24 12:05:23, Error CBS Startup: Failed while processing non-critical driver operations queue. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    2023-02-24 12:05:23, Info CBS Startup: Rolling back KTM, because drivers failed.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-02-21T13:08:45+00:00

    Hi,

    I have the same issue. 2 months ago I had the same problem therefor I have re-installed windows from scratch and today we have to go again.

    This is not acceptable.

    Please come back to us with a proper solution.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments