|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
ISSUE 21.02.1 • 2024-01-10 By Susan Bradley KB5034441 fails to install with error code 0x80070643. This failure is very unusual, so much so that I fee
[See the full post at: MS-DEFCON 1: Partition size blocks update]
Susan Bradley Patch Lady/Prudent patcher
Only for those that use Bitlocker. I’m still hoping that Microsoft can make the detection of this patch better. I have two home pcs that have NO TPM chip and thus no way to ever have bitlocker. There is ZERO reason for them to have this update.
Susan Bradley Patch Lady/Prudent patcher
I have two home pcs that have NO TPM chip and thus no way to ever have bitlocker.
It’s possible to use Bitlocker without a TPM:
I do NOT recommend you do ANYTHING about this error at this time. Do NOT attempt to resize your Recovery Partition. Just wait until Microsoft fixes the issue (probably next month). There have been reports of it failing EVEN with a large recovery partition. You should not be installing January updates now anyway…
Our standard policy is not to install Monthly Quality Updates for 19 days. This policy is based on Microsoft’s proven incompetence over the last couple of years. An update that causes business disruption and loss of revenue is unacceptable. We’ve found that Microsoft will address serious bugs within that 19 day period (3 work weeks).
So, how large is “large enough”?
Is the only way to find out to try the update and see if it fails? If so, what is the impact of the update failing — just that the vulnerability remains unpatched, or is system operation impaired?
I assembled my machine myself and installed Windows 10 Pro on an SSD. The recovery partition appears to be first, not last, and it’s 529MB. I do have Bitlocker active on the system and data partitions, as a precaution should the machine ever be stolen.
@SB my Recovery shows 1GB but also shows 100% free? Is that possible? And if so, should I just install this?
I DO have Reflect set to recover I belive. Thought it woul duse this, but perhaps I am confused here.
Thanks!
@SB my Recovery shows 1GB but also shows 100% free? Is that possible?
The Recovery partition is a “hidden” partition, and hidden partitions are always shown as 100% free.
You are correct about not being affected if BitLocker is not enabled. I do not have BitLocker enabled and KB5034122, KB5034275, and KB5034441 all successfully installed this date. I use Win 10 22H2. I cannot upgrade to Win 11, even if I wanted to.
grumble grumble grumble grumble – I would like a smarter patch. Many of us do not need this installed.
Susan Bradley Patch Lady/Prudent patcher
The first time I forget to set my no-update date to the 26th, and we get a DEFCON 1 level!
That being said, the patch did fail for me even though I don’t have BitLocker running. Now what is the fallout, other than the failure message? As a longtime programmer, I would expect (hope?) that the first thing the patch does is check the size of the partition and immediately terminate if it’s too small, in other words, no harm, no foul. It would be naive, amateurish and incompetent to start writing to the partition without that step and detect the problem only after the partition has been trashed … but then, expecting the average user to be able to expand the partition and move on is also naive, amateurish and incompetent in addition to being a cure possibly worse than the disease due to how many users it would affect.
Do we know of any ill effects if the patch fails, or is the DEFCON-1 intended to protect against any unknown problems?
So, how large is “large enough”?
See Microsoft’s Learn page UEFI/GPT-based hard drive partitions. It does not precisely answer the question but says that the minimum size of the recovery partition must be 300MB and that an additional 100MB to 250MB is required for the Windows Recovery Environment (WinRE).
That would imply 550MB just to be on the safe side. But scroll down to the “Recovery tools partition” section of that page and you’ll become further confused, as am I.
I just checked both the recently installed 1TB NVME system drive as well as the older 500GB SSD that I cloned the NVME from and both have 529MB recovery partitions on them. I’ll still hold tight doing any update on my workstation though I will test the HTPC maching that I only use for streaming to my TV set. I let that one update as normal every month as it doesn’t do anything other than content streaming.
See Microsoft’s Learn page UEFI/GPT-based hard drive partitions. It does not precisely answer the question but says that the minimum size of the recovery partition must be 300MB and that an additional 100MB to 250MB is required for the Windows Recovery Environment (WinRE).
That page date shows that it’s been updated, but not all of the information is up-to-date. That 300MB is leftover from Windows 7 early days.
I had a thought that since Windows 10 Home does not have Bitlocker, those users do not have to install this update.
I have read where OEM supplied WinRE partitions will require an additional 100MB because of the additional utilities contained in the partition.
Also, I have read that Microsoft has developed a Powershell script to do the partition massaging. I don’t have a link for it.
Easus has a free Partition Master utility that apparently is user-friendly for partition massaging. It also has a paid business version with a free trial. I don’t use it myself.
https://www.easeus.com/download/partition-manager.html
Mark
BIOS / MBR installation also don’t have UEFI and Secure Boot, yet they used to get their updates
Microsoft logic
From what I’ve read here on AskWoody it seems that when the patch fails the computer still functions normally and that it simply has a failed patch. So it seems that for those with limited computer skills, just let Windows Update do it’s thing. If the patch fails, it fails, and so what?
Disclaimer – I’m not recommending this, just throwing it out so the experts here can say yay or nay (and if it’s a dumb idea, please say so)
Edit – I’m assuming this is for folks NOT running Bitlocker.
Update: the recovery folder does contain the correct items.
It must contain a WindowsRE folder with a winre.wim file within that folder in order for the Windows Recovery Environment to function properly. You can find out by opening an elevated Command Prompt and type
reagentc /info
The results should look similar (the location will be different) to this:
If you get “Disabled”, then the correct items aren’t where they should be.
The updates link for “forensic reference”
Why isn’t KB5034441 in the catalog?
Note that consumers who have complete physical access to, and control over, their computers and who have not enabled BitLocker are unlikely to be affected by this update. But check anyway.
I have a question about “check anyway”. In this case (i.e., if you do not have BitLocker enabled), what does “check anyway” mean? I don’t think it means “go ahead and try to install KB5304441 and see if you get one of the two failure messages, and if you do, you know that there is a problem with the WINRE partition size.” This because in the preceding paragraph, it says “I don’t want you to attempt to install it until you are confident it will have no effect on your system.”
Maybe it means 1) ‘check on your partition sizes’ or 2) ‘check to see if you have a WINRE partition’ or 3) ‘check on the size of the WINRE partition’ or 4) ‘check to see where the WINRE partition is’. Or any combination of these. If these are the “checks”, when how do we do that? Or if these are not the “checks”, what are they?
One post says that you can run the command prompt reagentc /info to find out where the WINRE partition is. But, once you find that out, then what? I’ve done that and it says that WINRE is in partition 4. So, where do I go from there with this info?
Additionally, I know very little about the info I find in the diskmanagement snap-in and what it means for KB5304441, when BitLocker is not enabled. See the diskmanagement snap-in below and my questions about that.
And if I should want to enable BitLocker in the future, I know even less about what to do now in order to have things prepared for that!
Post-Script: Curiously, System Properties>System Protection still calls these partitions ‘Image’ and ‘DELLSUPPORT’. See ‘System Protection.jpg’ So, if these partitions are protected, what does that mean for KB5034441, BitLocker ‘OFF’ or BitLocker on ‘ON’?
You would really have to feel sorry for the people that have no computer skills, and Microsoft release a windows update that causes this problem for them.
Shame on you Microsoft it’s not acceptable!
Indeed. It definitely isn’t acceptable.
Actually, I’m expecting to see something like “To resolve this issue Microsoft recommends upgrading to Windows 11” any day now.
I don’t believe I’ve ever come across a large company so “tuned out” to their customers’ needs and requests as MS is these days.
For example – we were told no more features will be added to Window 10 and then we get things like Windows Backup and Start Menu cluttering “System” labels added… with no easy way (for the average user, at least) to remove them. And I suspect that’s only the beginning for what will probably happen with Windows 10 between now and October next year.
I don’t know whether all this is due to arrogance or incompetence (probably both) but it has definitely been getting worse lately. Especially since the release of Windows 10 in 2015.
As for my own situation – I hid the KB5034441 update with Windows Update Manager (wumgr) and just installed the monthly cumulative update. No problems with that so far.
Edit: I don’t have a recovery partition by the way – that’s always one of the first things I remove (with diskpart) after a Windows 10 clean install. I use Macrium Reflect for all of my backup needs.
Hi Carl D
Yes in the past i have done the same at times.
“I don’t have a recovery partition by the way – that’s always one of the first things I remove (with diskpart) after a Windows 10 clean install. I use Macrium Reflect for all of my backup needs.”
The only problem i faced with removing the recovery partition was Windows Security-Defender. You could not use “Microsoft Defender Offline scan” It needs the recovery partition to boot into.
If i remember correctly when Win 10 had a new version release, it would install, and also put back the recovery partition.
Makes me wonder if one did not have a recovery partition would the update create a new one with the correct size etc… Probably not.
You should have your laptop Bitlocker setup so that you must type in a PIN before it will boot. This is the best and safest way to use Bitlocker. This vulnerability does not apply if you are setup with a Pre-Boot PIN. In other words, it will prevent this exploit.
If TPM+PIN BitLocker protectors are being used, can the vulnerability be exploited if the attacker does not know the TPM PIN?
No. To exploit the vulnerability the attacker needs to know the TPM PIN if the user is protected by the BitLocker TPM+PIN.
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-20666
Here is how to add a Pre-boot PIN:
https://www.howtogeek.com/262720/how-to-enable-a-pre-boot-bitlocker-pin-on-windows/
Critical: You must keep a copy of your Recovery Key. This is mandatory!! if you don’t, you risk losing everything on your drive permanently.
https://support.microsoft.com/en-us/windows/back-up-your-bitlocker-recovery-key-e63607b4-77fb-4ad3-8022-d6dc428fbd0d
The intent of the troubleshooter is to help you hide an update. You can now let the computer alone for the month if you’ve already installed the OTHER updates.
Susan Bradley Patch Lady/Prudent patcher
I have WIN 10 v 22H2 home edition and a program called Bit Locker to GO?
How is that possible and do I need it???
Win 10 Home 22H2
If I use wushowhide and hide this patch now it will never come back until unhidden right?
Yes, mostly correct. The one thing that will make it reappear once hidden is, I believe, if it is superseded in the Microsoft system. Then, it might reappear.
Case in point is KB4023057. That particular update has been around for a few years now and it keeps reappearing every time it is modified by Microsoft, even though folks have hidden it. The only thing that changes is the month and year of it’s issue in the title of the update from, for example, 2023-08 to 2023-10. That small change is enough to make it reappear to be hidden again.
So for KB5034441, the current title of KB5034441 is actually “2024-01 Security Update for Windows 10 Version 22H2 for x64 based Systems (KB5034441)”. If Microsoft makes a change to the patch and re-releases it in May of this year (for example), the new name might start with 2024-05 and the rest of the title will be the same. This seemingly little change would make it reappear in wushowhide, and you’d have to re-hide it if you still didn’t want to install it.
This will prevent it from installing?
Yes, it definitely will.
I hope this information helps answer your questions.
The problem here is that the cumulative update next month will probably have the same fix
As @WCHS pointed out, KB5034441 was a Security Update, the January Cumulative Update for Windows 10 22H2 x64 is KB5034122.
Microsoft doesn’t normally include standalone Security updates as part of a Cumulative update. If they need to reissue it, it’ll be issued as either a completely new KB# or using the same KB# but with a newer issue date.
Well, I just confirmed that this “famous” partition on my computer:
I have BitLocker, but it is not used anyway.
So I really don’t understand why this patch has been failing at least 3 times until I blocked it…
I have not tried to install KB5034441 or any other Jan 2024 Patch Tuesday update so I don’t know yet if my Win 10 Pro v22H2 machine is affected by this bug. Control Panel | System and Security | BitLocker Drive Encryption shows that BitLocker is OFF.
Can anyone explain the discrepancy in the size of my WinRE recovery partition when I check in an elevated command prompt vs Windows Disk Management?
The ReagentC and Dism /get-ImageInfo commands described in the MS Learn article Validate the Windows RE Version in an Online Windows OS show that my WinRE recovery partition is Partition4 and is 3.791 GB in size (see attached image), but Windows Disk Management shows Partition4 has a capacity of 990 MB and is 100% free.
I enabled the System Restore feature (disabled by default) years ago as instructed in the WindowsCentral article How to Use System Restore on Windows 10 so my system creates the occasional system restore point [max usage = 22.34 GB (10% of C: drive); current usage 12.77 GB].
I have no idea what my Partition6 is used for, but note that I have added my Macrium Reflect Free recovery environment to my Windows boot menu options and used to have the Dell SupportAssist OS Recovery utility (now uninstalled) installed on my Inspiron laptop.
—————
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3803 * Firefox v121.0.1 * Microsoft Defender v4.18.23110.3-1.1.23110.2 * Malwarebytes Premium v4.6.8.311-1.0.2235 * Macrium Reflect Free v8.0.7783
Hi @lmacri,
FWIIW, when my Dell Inspiron 5482 was almost new, Disk Management showed the name WINRETOOLS for partition 4 (990 MB), Image for partition 5 (12.31 GB), and DELLSUPPORT for partition 6 (1.23 GB). At the end of the partition map, there was 13 MB of unallocated space. At that time, Disk Management showed a specific % of free space for partitions 4, 5, and 6.
In 2020, I opted for Dell’s SupportAssist System Repair, and Disk Management showed something different. Partitions 4, 5, and 6 were no longer named, but the capacity of each had not changed. It showed 100% free for each of those 3 partitions.
I still have System Repair ON and Disk Management looks the same now. (BTW, System Repair has come to the rescue several times.)
Personally, I think SupportAssist System Repair has something to do with Disk Management’s 100% free space for partitions 4, 5, and 5 and no names for them, whether this feature was once-ON-but-no-longer / or still-ON.
I called Dell once about the ‘100% free’ designation and an agent told me that this was because the data was hidden. I know that when System Repair is turned on, the backup/repair points are hidden at C:\ProgramData\Dell\SARemediation\SystemRepair (I learned that from you), so I have thought that’s why Disk Management says 100% free, maybe because there is a pointer in those partitions to the hidden folder in OS (C:).
But, since you have System Repair OFF now, it looks like the info in Disk Management superficially remains the same as it was when System Repair was once ON.
P.S: The 1st and 2nd files are .png files and their images get posted. The 3rd file is a .jpg file and it gets rendered as a link. I don’t know the reason for the difference in how the screenshots are posted – it must be due to the extension of the file.
P.S.S: the 3rd file (a .jpg file) is now an incomplete image in the post. But, if you click on it, you will see it all.
P.S.S.S: now all three files are posted as full images!!
The ReagentC and Dism /get-ImageInfo commands described in the MS Learn article Validate the Windows RE Version in an Online Windows OS show that my WinRE recovery partition is Partition4 and is 3.791 GB in size (see attached image), but Windows Disk Management shows Partition4 has a capacity of 990 MB and is 100% free.
Bear in mind that winre.wim is an image file, and image files don’t do anything until they are mounted. That combination of commands you used gives you the mounted size of your recovery environment (in actual use, WindowsRE is a mounted VHD in RAM, not on your physical drive).
There is no discrepancy, it’s just the difference between virtual drive and physical drive. As for the 100% free, hidden partitions are always 100% free; the contents are hidden.
700MB should be more than enough. You must have another issue.
cheers, Paul
I do not believe that I have BitLocker on my Win 10 Home PC. But should I be safe in installing the update if offered? If I need to hide the patch, how do I do so. Is it by using the BlockAPatch method? And if so, how exactly does that work. *Note* I do not know the size of my recovery partition. How do I find that out?
It seems the patch will install on all PCs, BitLocker or no.
I would run WUmgr, search for updates, then hide 34441.
This will give MS time to fix it so you don’t have to worry.
cheers, Paul
Recovery Partitions exist on all commercial machines. Home built, maybe.
Run Disk Management to view your partitions, but don’t modify any.
Win R, diskmgmt.msc, Enter
cheers, Paul
@self: I answered your second question in the post above yours. As to how you can see if you have recovery partitions, and if so, what size your recovery partitions are and how much space is available on them, one way in Win 10 Pro is to open Control Panel and then Administrative Tools. Right-click on Computer Management and select “Run as administrator.” Enter your administrator password if needed, and on the left, under Storage, select Disk Management.
After a brief pause you’ll see your connected storage devices listed in the upper center. Some of them will be marked “Healthy (Recovery Partition).” Scroll to the right if needed and the Capacity and Free Space is indicated for each Recovery Partition. You can also see the Capacity for each partition displayed in the corresponding boxes in the diagram below, but to see Free Space or % Free, you have to look in the upper center window where devices are listed and scroll to the right if needed.
I do NOT recommend using this because you shouldn’t even be installing Windows Quality Updates Yet as AskWoody is at MS-DEFCON 1 – Do not Install. This will be worked out by Microsoft by next month without user intervention. Let it be. Anyway, here is info for those interested:
Microsoft shares script to update Windows 10 WinRE with BitLocker fixes
https://www.bleepingcomputer.com/news/microsoft/microsoft-shares-script-to-update-windows-10-winre-with-bitlocker-fixes/
MSFT need to simplify this, as there are differing conotations of partition layouts where expanding/ shrinking the WinRE is just TOO FAR for most!
My experience:
W11 Pro monthly’s updated without any fuss this month.
However, 2 x W10 Pro x64 and 1 x W10 Pro x86 were each in need of individual attention after CU and .NET patches. Grrr!
All W10’s required increase adjustments to WinRE size before kb5034441 would inject. (yup, two attempts on the test device, clearing distributionstore between each)
Rather than the MS method of the 250mb increase, I used bootable Minitool Partition Wizard 9.1 USB media (UEFI & MBR versions respectively) to adjust the WinRE size to 750mb from ~500mb, as they were next to the OS partition, then re-aligned partitions.
Upon restart within cmd (as admin) ran:
Reagentc /enable
Revisted WU and installed kb5034441 without error on each.
Checked and analysed DISM, no corruptions. SFC /scannow reported no violations. Phew!
Feeling your pain enterprise admins..
However, 2 x W10 Pro x64 and 1 x W10 Pro x86 were each in need of individual attention after CU and .NET patches. Grrr!
You’re lucky that you know what you are doing and can do this. What about us poor souls that will be hanging out to dry for lack of this kind of expertise?
No. The new PatchWinREScript_2004plus.ps1 script appears to patch the WinRE image to mitigate the vulnerability in the existing partition without resizing it just fine… I’m sure MS will find a way to fix the issue automatically by next month.
I do NOT recommend using this because you shouldn’t even be installing Windows Quality Updates Yet as AskWoody is at MS-DEFCON 1 – Do not Install. This will be worked out by Microsoft by next month without user intervention. Let it be. Anyway, here is info for those interested:
Microsoft shares script to update Windows 10 WinRE with BitLocker fixes
https://www.bleepingcomputer.com/news/microsoft/microsoft-shares-script-to-update-windows-10-winre-with-bitlocker-fixes/
I think you are naive if you think Microsoft can just fix this. If the problem is that a partition is too big for a new winre.wim file (which seems to be the problem,) they very likely can’t just make the file smaller again. Their only other choice is to start re-sizing partitions (not just the recovery one) while installing a replacement update. I, for one, do not trust Microsoft not to screw this up while doing it silently behind the scenes during another update!
This is just horrible for the home user, and one should not undertake the stress of doing this.
I do not patch until the week before the next patch Tuesday and not in a rush to be a guinea pig. I also value my equipment and need my laptop for important personal use. I am sure that most home users feel the same way.
Several years ago Microsoft failed to release a .cab that rendered the windows update manager useless. They fixed it and then everyone could download the updates. It was not immediate, but timely.
I will sit tight and wait out the month. Not a happy camper! Trying to stay positive!
Win 10 Home 22H2
What’s the difference in the terms WindowsRE and Recovery Environment?
WindowsRE = Windows Recovery Environment.
On 19 Nov 2023, I had to run a “Repair Install Windows OS” <see Options # 2604213>
Today, 12 Jan 2024, I ran MiniTool Partition Wizard Free 12.8, which shows my Recovery Partion is almost at full capacity <529 MB capacity, 481.57 MB used>
The Minitool “Space Analyzer” tool shows my Recovery Partion has two folders as follows:
(1) System Volume Information; this folder has one sub folder and one log
EfaSIDat <folder with one file>
SYMEFA.DB <40 KB >
tracking log < 20 KB >
(2) Recovery; this folder has one sub folder
WindowsRE < folder has three files >
boot.sdi <3.02 MB>
Reagent.xml <1.08 KB>
Winre.wim <467.99 MB> “the image file containing the bootable repair tools for Windows”
I ran across this file << https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment–windows-re–technical-reference?view=windows-10 >>
It says: “Add the baseline WinRE tools image (winre.wim) to a separate partition from the Windows and data partitions. This enables your users to use WinRE even if the Windows partition is encrypted with Windows BitLocker Drive Encryption. It also prevents your users from accidentally modifying or removing the WinRE tools.
“Store the recovery tools in a dedicated partition, directly after the Windows partition. This way, if future updates require a larger recovery partition, Windows will be able to handle it more efficiently by adjusting the Windows and recovery partition sizes, rather than having to create a new recovery partition size while the old one remains in place.
“The Windows RE update process makes every effort to reuse the existing Windows RE partition without any modification. However, in some rare situations where the new Windows RE image (along with the migrated/injected contents) does not fit in the existing Windows RE partition, the update process will behave as follows:
Does this mean Windows will, someday, somehow, automatically shrink the old partition and create a new one ?
Does this mean Windows will, someday, somehow, automatically shrink the old partition and create a new one
More likely MS will work out how to do the update without using so much space. A partition resize is not something you do unattended or without prior backup.
cheers, Paul
Does this mean Windows will, someday, somehow, automatically shrink the old partition and create a new one ?
Indeed. That happened to me with the update to 22H1 or 22H2, don’t recall which. My WindowsRE partition on a separate drive was orphaned, and a new WindowsRE created by shrinking my Windows partition and creating WindowsRE behind Windows.
I updated my orphaned WindowsRE in my preferred location, deleted the Windows-created WindowsRE, and everything worked the way I wanted it to work once again.
On the other hand, with this most recent update, my WindowsRE winre.wim was updated in my partition of preference, and the update did not create a new WindowsRE after the Windows partition.
The January 2024 Windows RE update might fail to install
Status
Confirmed
Affected platforms
Client VersionsMessage IDOriginating KBResolved KB
Windows 10, version 22H2 WI706429 KB5034441 –
Windows 10, version 21H2 WI706430 KB5034441 –
Devices attempting to install the January 2024 Windows Recovery Environment update (the Originating KBs listed above) might display an error related to the size of the Recovery Environment’s partition. The Windows Recovery Environment (WinRE) is used to repair or recover from issues affecting Windows.
Resulting from this error, the following message might be displayed.
“0x80070643 – ERROR_INSTALL_FAILURE”
Workaround: It might be necessary to increase the size of the WinRE partition in order to avoid this issue and complete the installation. Note that 250 megabytes of free space is required in the recovery partition. Guidance to change the WinRE partition size can be found in KB5028997: Instructions to manually resize your partition to install the WinRE update.
Next steps: We are working on a resolution and will provide an update in an upcoming release.
Susan Bradley Patch Lady/Prudent patcher
You actually want Windows to use lots of RAM, otherwise it’s sitting around wasted.
Having apps loaded and ready to go is a good thing in my book.
cheers, Paul
Hello all
Thanks for posting this information. I was troubleshooting this yesterday and found a site that showed how to resize the Recovery Partition in order to get the patch to install… I found that the Recovery had to be resized to 1GB or greater. I wrote a blog about it here: jvhconsulting.com – https://jvhconsulting.com/2024/01/13/windows-10-kb5034441-security-update-fails-with-0x80070643-errors;
it uses Diskpart to remove, recreate recovery partition based on MBR or GPT disk types after shrinking space off OS drive (550mb). After doing this the patch installs okay.
Today after reading your article and also trying the WUHowHide.diagcab tool to block /hide the KB5034441 article I figured there must be a way to do this via powershell – especially since in my RMM I had about 35 Machines needing this fix.
While I haven’t gotten the RMM script to work successfully (yet), the commands do work from a remote command prompt-powershell.
Here are the commands for Win10/11 machines to Hide this KB5034441 patch from the system and remove the error
Set-ExecutionPolicy Unrestricted -Force
install-module -name PSWindowsUpdate -Force
Hide-WindowsUpdate -KBArticleID KB5034441 -AcceptAll
After running above the output below shows, indicating the KB is Hidden by the H in Status Column:
ComputerName Status KB Size Title
———— —— — —- —–
<PCNAME> D–H– KB5034441 23MB 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems
Hope this helps! I plan to update my blog with this info. (jvhconsulting.com).
Regards
Joost van Haaren
JVH Consulting, LLC
MS have a PowerShell script to perform the update.
https://www.askwoody.com/forums/topic/0x80070643-error_install_failure-with-kb5034441/#post-2623194
cheers, Paul
Stay tuned for part 2 in next week’s Patch Watch.
Susan Bradley Patch Lady/Prudent patcher
Tackled the first Win10 Pro today. Hardware install on an old Dell Studio XPS 1340 with 6GB RAM and a 512GB spinner HDD, originally Win7 Ultimate upgraded to Win10 Pro. The disk: partition 1 is 39MB OEM, partition 2 is 14.65GB Recovery, and partition 3 OS the rest of the drive.
First, I tried to shrink the OS partition by 1GB with Mini Tool Partition Wizard, thinking perhaps the install would abandon the existing WinRE and install it on an NTFS formatted partition 4. Didn’t work – Mini Tool reported not enough memory.
Next tried Windows Update including KB5034441. There was an error on download (not install) on KB5034441. I hid it before rebooting and the installation (KB5034122 CU 22H2 Build 19045.3930, .NET Framework, Defender, and MSRT) completed without error.
After the update, wondering what would happen, I unhid KB5034441 and allowed it to download/install. It did without error and the Partition 2 WinRE was updated to Build 3930, modified date 1/16/24. So the WinRE does not have to be in Part4 to be updated, as long as it is big enough.
On to the other two Win10 in Parallels VMs tomorrow
Update: see #2629983 for results on the other two installs.
PKCano wrote: partition 2 is 14.65GB Recovery
That size indicates an OEM Recovery partition used to restore the PC/laptop to OOBE condition, not just the Windows Recovery Environment, although it may also contain the Windows RE.
I have posted here to complete my experience with the Win10 update installs. See #2628205 for what occurred with the first update. Note: Bitlocker is not installed on any of the three installs.
The two remaining Win10 Pro are in Parallels VMs, one on an Intel Ivy Bridge MacBook Pro and one on an Intel Kaby Lake iMac.
On the MacBook Pro, the Win10 installation had a close to 900MB Recovery partition that I did not resize. The Windows update queue contained KB5034441, KB5034122 CU 22H2 Build 19045.3930, .NET Framework, Defender, and MSRT as with the previous one. All installed without error, including KB5034441.
On the iMac, I used Mini Tool Partition Wizard to shrink the OS partition by 1GB and extended the Recovery partition to 1.54GB. The Windows Update queue offered all the updates including KB5034441. All updates installed without error EXCEPT, there was again the error on download (not install) on KB5034441. This time I did not hide it before the reboot.
After the reboot (no other errors), I let the computer stew for a half hour or so to complete the install, then revisited the Update queue. KB5034441 was again offered, and it installed successfully, this time with no error.
Who knows! It’s Microsoft…
Is there a way to do it in Windows 10 Professional without using WuMgr?
Yes, there is using GPEdit.
Computer Configuration – Administrative Templets – Windows Components – Windows Update – Windows Update for Business – Select when quality Updates are Received (open and enter pause number of days / date.
You should also set ‘Notify = 2’ (notify, don’t download / Install)
https://www.askwoody.com/forums/topic/2000016-guide-for-windows-update-settings-for-windows-10/
My apologies if this solution has already been posted, but I inadvertently found a solution to this problem. After reading Susan Bradley’s posts and possible workarounds to this problem, I checked my partition size and found it inadequate for the KB5034441 installation. But, while working on another issue, I took Susan’s advice and did an “over the top” installation of Win 10. My issue was resolved. I also found that my Recovery partition size had increased from 465MB to 680MB.
This month, KB5034441 installed with no problems! I didn’t have to run any scripts, no manual resizing of partitions and their inherent problems. Just a simple “over the top” installation of Win 10 did the trick! Easy breezy!
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
