@XweAponX
to have the boot-partition (EFI) on a separate disk is quite normal. That is not a problem at all.
998 MB is big enough. If you now how to extrakt a "fresh" WinRE.wim from a new ISO, you should do that. 7z is a nice tool for that if you run it as administrator.
EDIT
C:\WINDOWS\system32>reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /t REG_SZ /v WinREVersion
The answer should be:
WinREVersion REG_SZ 10.0.19041.3920
And a screenshot looks different.
In this case it's a huge problem cos it's on a larger partition than my C drive... Is there a tutorial in here for migratring a system drive that;s set up this way? I've tried about 3 different programs and they either failed or in the case of Paragon, it could not allow me to choose my target drive.@XweAponX
to have the boot-partition (EFI) on a separate disk is quite normal. That is not a problem at all.
998 MB is big enough. If you now how to extrakt a "fresh" WinRE.wim from a new ISO, you should do that. 7z is a nice tool for that if you run it as administrator.
EDIT
C:\WINDOWS\system32>reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /t REG_SZ /v WinREVersion
The answer should be:
WinREVersion REG_SZ 10.0.19041.3920
And a screenshot looks different.
I had a Windows 8 system that was like that, eventualy, I copied the efi partition to a new drive, then the system partition, then the other partitions. It booted.
I tried the same thing, and it just doesnt work for windows 10 for some reason
Sorry, I could not take a screenshot at the time. But I'm glad I got this issue fixed finally
KB5034441 seems to be offered to LTSC 2021 (21H2) systems as well - immediately hid/blocked the update using wushowhide.diagcab when it was offered thru a windows update scan several days ago
@gibran
You run a system that is more or less ruined and you should be happy that just the KB5034441 failed.
I also guess that you don't have a verified backup of your (C:) partition. What do you do when the next February update crashes because of a space problem?
You are not aware of the problem you have! In a professional environment I never saw a (C:)-Partition bigger than 150 GB. Such systems can be recovered within 2 min.
Do you have any idea how long it takes to recover 930 GB from an external USB-Disk. It can take days!
Sitting in front of your PC would make it easy. But this forum is not the place where you can get all the problems solved!
I'm sorry to tell you that.
Last edited by Pentagon; 29 Jan 2024 at 04:43.
I wonder if Microsoft will ever issue a fix for this broken update.
I lost patience with Microsoft to fix it, so I extended the recovery partition.
I'm just curious as to whether Microsoft ever implemented a fix.
MS is aware of this and is said to be working on a revised update. For now, if still problems, hide the update (can be done neatly using WUmgr, free) and wait for the next updates.
From what I see I have no Recovery Partition and AFAIK KB5034441 addresses a Bitlocker vulnerability that makes use of the Recovery Partition, but if the partition does not exist I would assume that there is no need to install KB5034441, right? In which case the update can be hidden.
In case I do need to install KB5034441, what steps should I follow to create the recovery partition with the right size? Screenshot below of my current Windows install, thanks.
Quote
