Bork Tuesday, Any Problems Yet?

Of note is this comment;

Similar comments on Microsoft TechNet thread of this subject.

 

Hi @ProTruckDriver

An Apple a day keeps the doctor away, or should that be Microsoft?

 

But of course! Always try, otherwise you don't get.

I've been reading others' experiences and some have taken the plunge and others like me don't wanna. I think I'll wait and see for a few days, in case Microsoft does the right thing and releases a script or something to expand the partition instead of our having to do it. So, we'll see. The update isn't even going to the "install" stage anymore, it just shows the error at the d/l stage now. If it silently updates, that would be lovely.

Do the right thing, Microsoft.

 

When I had a problem back in October with this type off error https://www.wilderssecurity.com/threads/bork-tuesday-any-problems-yet.370217/page-315#post-3167222, I managed to solve it, but I have forgotten how:

 

Thank you @Tarnak I might use that catchy phrase in my signature.

 

I found a link going back to that time period, https://www.computerworld.com/article/3080839/repair-windows-10-and-11-step-by-step-guide.html, and I kind of followed the advice for the following:

Step 1: Using DISM and SFC for system repair

 

You might have done this?

https://answers.microsoft.com/en-us...-updates/d30d1e1e-bac9-4d9d-9607-070c0ee57852

This will allow you to download the update again. Did it and still a no-go with it crapping out on installation.

 

You're welcome.

 

No, I didn't do that.

But, I did follow this advice: "best to run DISM before running the System File Checker, a.k.a. SFC.", and followed on from there.

 

I had the same failure as described in the article. This kb5034441 update was offered today, and was not part of the January CU I downloaded from Windows Catalog and installed without problem.

I ran the batch script from here to remove the error from view: https://www.askvg.com/fix-0x80070643-error-code-from-kb5034441-update-in-windows-10/

 

OK, this is something I was interested in as I didn't want a constant reminder about this failure. I ran it but I have a habit of forcing updates so the error message came back the next time I checked. Darnsville! Also: no integrity violations via sfc as Tarnak suggested so that's good. I know I can re-do the WinRE partition and solve the problem. But I would rather Microsoft do it.

 

Got the failed update on one of two laptops.



Noticed this in Temp folder, earlier:

 

I had to manually redo the partitions on this SSD once after installation, so I don't particularly want to do it again, especially for an update that doesn't really apply to Windows Home. Also, a user on G Hacks says the "fix" doesn't work on a 256 GB SSD like mine: https://www.ghacks.net/2024/01/10/f...ng-to-install-windows-update/#comment-4578977

 

I haven't seen that file anywhere on my system using "Everything."

 

For me, this update is a waste of time:
Checking for updates...
1 update(s) left to hide.
1> 2024-01 Security Update for Windows 10 Version 21H2 for x64-based Systems (KB5034441)
Hiding update: 2024-01 Security Update for Windows 10 Version 21H2 for x64-based Systems (KB5034441)

 

But, but, it has to be important it is from Microsoft.

 

I just checked Windows Update and the error isn't there anymore, without any input from me. Yay!

Strange thing is that I cannot find the update having successfully installed, just several attempts and fails.

Edit: I should note that I have not manually checked for updates since the day this fiasco began. Doing so may see the return of the update attempt and error.

 

Sarcastic I hope.

 

just an idea - how old is your windows installation? maybe older then the recovery partition may be smaller than current installations. that update concerns winre and its partition, nothing else. winre is vulnerable at least you have no reliable recovery environment and your windows get infected by using it. useless update? think again.

 

Just back at work today, which I do from home on a work supplied desktop. Noted this failed update was sent through via Intune this morning. Which means our IT dept will have over >1000 machines affected., most of them remote to office. None of us staff have adminstrator priveleges (in fact we have very reduced standard user priveleges), so that's going to be a real headache for work places if MS don't address this with a proper automated fix. So far there is no indication that they will, given the update is till being sent out & they don't describe the fix as a temporary workaround or state a fix will be issued in futiure (unlike with previous screwed up updates they've released).

 

Here's my MCF story on Win 10 22H2 when applying Microsoft's recommended fix to the KB5034441 update failing issue.

Performed Microsoft's instructions exactly as stated. After completion, rebooted as instructed and retried the failed KB5034441 update. It now installed w/o issue. Now for the MCF part.

Lucky for me, I happened to open Win Explorer and noticed a new drive letter showing with an id of Windows RE tools? Next, opened Win 10 Disk Management and sure enough, there was the drive and partition with nothing showing a Recover Partition. Worse, this new partition was 100% accessible including write access. WTF?

Luckily, someone on the Win 10 forum had encountered the same exact situation: https://www.tenforums.com/windows-1...1h2-22h2-jan-9-a-post2598936.html#post2598936 . The fix is given in the following posting there. However, that had a problem. I had to change;

set ID=0x27 to set ID=27
​

to get the command to run. At this point, I now had a hidden unnamed partition identified as Recovery Partition as existed previously. Note that the fix given applies to the OP's hardware setup; you will have to change disk and partition id accordingly

What is wrong with the Microsoft instructions? Not sure, but suspect it's this command, create partition primary id=27.

Finally, I rebooted into Win 10 RE to make sure it worked as previously.

Bottom line - applying this fix is not for "the faint at heart."

 

I don't know what all this means:

 

I've run the Windows Update Troubleshooter a few times since Wednesday our time, but it never finds any problems.

 

I am getting more confused with this update. Seeing is believing?