Security Update for Windows 10, 2024-11, KB5048239 getting error 0x80070643 when installing

I have a PC and this is the message that appears when I click Check for Updates.

2024-11 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5048239) STATUS Installing - 0% After an hour or so the screen goes back to Check For Updates. When I click it. the same message a[[ears.still says

Have you read all the older posts within this discussion thread?

Try this:

1. right-mouse-button click on the Windows "Start" button.
2. choose "Disk Management" to see output like the below.
3. Double-click on the vertical-bar just before "Capacity" to increase the width of the "Status" window.
4. How large (Megabytes) is that "System Reserved" partition?
5. Is that partition at the "start" or the "end" of the disk-drive?
6. Previous messages on this thread suggest several ways to "shrink" or "enlarge" the partitions, to increase the size of that "System Reserved" partition.
7. After the "resizing", try again to apply the update.

Hi melvin,

I was able to expand the 768 to over 1gb see below. I still get the same issue as the other guy where it not attempts the upgrade and eventually quits.

partition3 is right

regarding cloning drives. This is a guest on a VM. the server has multiple 2tb drives in raid configs. there is a 2tb raid for the host boot and vm guests

and there are 8tbs about for the plex drive which I'm trying to recover. the host is configured as such

The R: drive is a scsi raid and is basically not being used right now

any other suggestions?

thanks leon

I see your image:

It is unfortunate that you did not "widen" that "Status" column, to show more information, especially to show the text below "350 MB NTFS" and to show more of the "Healthy (S..." field.

Are you running Windows Update on the "(C:)" partition? If so, then if "partition0" really is the "WinRe" partition, then that partition probably is too small (only 88 MB free) for the update to be successfully applied. Use that REAGENTC command on this system, to show which "partition[N]" really is the "WinRE" partition.

Inside the "guest" VM, can you use the command-line DISKPART utility to assign a drive-letter to that "partition3", and then to see how much disk-space is occupied, and how much space is free? Note that many files on "partition3" are tagged as "hidden" files.

After assigning a "drive-letter", use the command-line "DIR [drive-letter]: \ /A /S /P" to show All the files & Sub-folders, and to Pause when the terminal-window gets full.

Or, just ignore the fact that the update will not apply.

Windows 10 will achieve its "sunset" on October 13 this yearf,

forcing you to install Windows 11, with a completely-new "WinRE" partition.

Finally, if you never need to do a "Wndows Restore", then you will never use the "WinRe" partition. All the future monthly updates will successfully be applied, to keep your system secure. When your system is otherwise secure, there is no way for a hacker to exploit the vulnerability in the "unpatched" WinRe partition.

If you keep firearms inside your home, but no burglars cannot enter your home to take the firearms. Similarly, if Windows is secured against hackers, then the "vulnerable" WinRe cannot be exploited.

Hi melvin....here's a new screenshot of the GUEST

here is a screenshot of the HOST

The host is W2012 R2 Server not W10 or W11. The guest is W10. The 350MB NTFFS partition says Healthy(System, Active, Primary Partition).

the guest is what I am concerned about. The host, I believe is EOL (?) or close to it I think.

here is the reagenctc on the Host:

C:>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status:         Enabled  
Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE  
Boot Configuration Data (BCD) identifier: 155b846b-16e2-11e9-9098-a939de75f708  
Recovery image location:  
Recovery image index:      0  
Custom image location:  
Custom image index:        0  

REAGENTC.EXE: Operation Successful.

C:>

but remember this is the Hyper-V Host

so back to the guest, update runs and then after some period of time closes itself.

neither of these install

thanks leon