Security Update KB5034441 for Windows 10 Ver. 22H2 will not install.

Anonymous
2024-01-09T18:42:21+00:00

Thank you so much Microsoft as you have started the New Year off with bang with this update failure below on the first patch Tuesday of the year:

Installation Failure: Windows failed to install the following update with error 0x8024200B: 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441).

Tried multiple times to install this brick but no luck on my OMEN desktop and my wife's Envy laptop. So now what Microsoft?

Don

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

170 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-01-21T17:26:02+00:00

    Agree with you. I have win 10 22H2 home also! Wish they would fix this too.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2024-01-21T16:38:03+00:00

    Could not get a live person to chat with!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-01-21T11:48:28+00:00

    Have you tried to Chat online with them and could you get any further clarification??

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2024-01-21T00:05:27+00:00

    Too technical for me too!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2024-01-20T23:34:13+00:00

    Especially for Marv6's question:

    Before performing the partition fix and the patch, I ran a Windows Defender quick scan followed by a checkdsk, sfc and dism. I repeated these tests after the install and these tests reported no problems. Today sfc found bad files that it could fix itself. Now I have to go look at the details of errors reported by sfc. I was also able to run a hardware diagnostic that tests the CPU, memory and circuit board features. It also didn't find any problems.

    Here's only the diagnostics from running these 3 Windows tests.

    C:\WINDOWS\system32>chkdsk /scan

    The type of the file system is NTFS.

    Volume label is Bubbles_W10.

    Windows has scanned the file system and found no problems.

    No further action is required.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan.  This process will take some time.

    Beginning verification phase of system scan.

    Verification 100% complete.

    Windows Resource Protection found corrupt files and successfully repaired them.

    For online repairs, details are included in the CBS log file located at

    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline

    repairs, details are included in the log file provided by the /OFFLOGFILE flag.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool

    Version: 10.0.19041.3636

    Image Version: 10.0.19045.3930

    [==========================100.0%==========================]
    The restore operation completed successfully.

    Going back to the earliest days of ENIAC and more recent computers, people routinely tested a computer with known tests before running any user apps, and they re-ran the tests afterwards. If the tests failed at the start, you get to fix the computer before doing anything else. If the tests fail after the run, the results of the run are considered unreliable. While the tests I used here are often recommended by Microsoft support, they do not attempt to diagnose partition problems. It's just useful to know whether other problems exist that might interfere with installing new stuff. I run these tests on my systems several times a week.

    art

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments