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

Windows Server 2012 and Windows Server 2012 R2 will end on October 10, 2023.

After this date, these products will no longer receive security updates, non-security updates, bug fixes, technical support, or online technical content updates.

I doubt whether any operating system released by Microsoft in/before October 2013, such as this Windows Server, would use any separate "Recovery" partition.

The output on the host from the REAGENTC command shows that the "C:\Recovery" (hidden) folder contains the "System Recovery" support.

the guest, update runs and then after some period of time closes itself. .... neither of these install

The first update is to the Windows Defender anti-virus software.

If Windows Update is running correctly, the failure of the other update to install should NOT cause the update to Defender to fail.

Can you double-click the green-coloured "shield" icon for Defender (in the System Tray at the bottom of the screen) and manually force it to try to update. Is this successful?

Then, go back to Windows Update, and click on "Update History", to see the newest date on which KB2267602 was successfully installed, and the list of dates on which it was installed.

Then, do a "check for updates", to see if ONE (or TWO) updates are offered.

This might be corruption within the Windows Update app.

There is a Microsoft "troubleshooter" for issues with Windows Update. Run it, and see if it makes any changes.

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

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,

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