Bork Tuesday, Any Problems Yet?

calm down, nothing is hot baked like this. but maybe you really have cracked up your windows.

 

Well one thing has been confirmed in regards to this repeated 10-2023 KB5001716 update bork.

I was going through my Win 10 Event log which showed a bunch of the following MsInstaller errors;



Clearly, this a Microsoft Update Server processing error. The update should never be offered if 03-2024 KB5001716 update is installed.

 

borked for you and some other, but i would bet not for the majority of other users. it will hard to find voices "yes, it can" where those udpate was performed. and meanwhile - which took some time and trial&error - my other win10 os could accomplish the kb5034441 update.
well, after wiping both partitions after backup i reverted those steps. then i resized smaller one of it the with 2gb (minitool), to have 2gb for the winre partition, i have to work on with DISKPART.

essentially DISKPART

list disk
select disk # (operating disk with windows)
list partition
select partition # (where winre is created)
set id=27 (for mbr)
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac" (for efi)
assign letter=# (a-z possible, do not have impact for the position later)
exit

reagentc /info (to see whats on)
reagentc /disable
reagentc /enable (to get new partition)
reagentc /info (to see if success)

back in diskpart if winre ist on drive C) do not perform if NOT drive C
list partition
select partiton # (where winre is created)
set id=27 (for mbr)
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac" (for efi)
remove letter=# (which was set, does not matter to have a letter)

let windows update try again. dont worry if you have to repeat those steps (like me).

additional tools
bcdedit /enum all > c:\bcd#.txt (# for increasing number to see differences later)

you need to compare the UID in recoverysequence, resumeobject,
and in section where is "description Windows Recovery Environment"
---> ramdisk=[\Device\HarddiskVolume3]\Recovery\WindowsRE\Winre.wim,{long_uid_numer}

that long_uid is found at the most bottom
Bezeichner {long_uid_numer}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume3

it has to match 4 times with 2 numbers in total.
this is really important, check with care!

next tool ist VisualBCD from boyans
https://www.boyans.net/DownloadVisualBCD.html
its a bit tricky to use, bcdedit has advantage
visualbcd helped me out in the past where i cloned my win8 partition and had buzz with the hibernate and pagefile - the new and older had access to same file and mixed up the booting. see above again with the long_uid_number which need to be unique for each os.

EasyBCD is not really helpful here.

at least i have to fix two windows on a triple boot system which makes the bcdedit result even longer and i have to work on all not to mess up windows again.

i forgot, i work with the boot media from stick with "MiniTool Partition Wizard" to work on my partitions.

at least no magic at all, but a lot to read and trial, i had a second and third try. if i wont had success, the os would have gone finally and the pro installed from scratch, i dont care.

after reading several articles in englisch and german, yes, we know this right now.
but articles say, that you have to remove an older update with this number, then let WU install the newer build. stapp mentioned where to find it to uninstall.

if no KB5001716 is found, even not earlier, as i said, you cracked it up.

edit:
today i received the latest build of KB5001716, and it installed flawlessly.

 

Well, a few minutes ago an automatic update check took place and guess what ... everything is up to date with a green check mark. I'm glad I left it alone to heal.

 

and all records of failed updates have mysteriously disappeared from the update history. There was only one left and that was about a successful update of this patch. It seems MS has finally done their homework and sorted this out on their end.

 

Problem seems resolved for me also.

 

Yes, that's what I meant.

It's understandable that we don't get any errors anymore if the error was on the MS servers and they fixed it there. What surprises me though is that they can remotely delete the update history. I thought the update history is stored locally.

 

It is stored indeed locally => C:\ProgramData\USOPrivate\UpdateStore\store.db
Mine Windows Update history still shows that KB5034763 is installed successfully, but I uninstalled it and the update was suppressed by KB5034843 (or at least it contains the fixes from KB5034763 too).
But I don't want to delete the history, as it contains all the history from when Windows was installed on my PC.

 

Did test afterwards, as I said in the article. Didn't get the error or another attempt to install.

Windows Update showed a clean "You're up to date!"

 

FYI - There's a lot more to this KB5001716 update bork than meets the eye: https://www.wilderssecurity.com/thr...ased-29-jul-2015.368734/page-278#post-3186942.

Now my device is not eligible for Win 11 upgrade.

 

@itman - may I ask what you mean by your device not being eligible to upgrade to win 11 after installing KB5001716? Did you try to upgrade & that was the message you got? Or has the green tick with "This PC can run Windows 11" in the Windows Update changed to the red cross & stating it is ineligible? I ask because the same machines that were eligible remain eligible for me after installing the update (according to the green tick etc in Windows Update).

Good to see that the update has stopped being repeatedly offered once already installed.

 

if the machine meets win11 requirements, than a hint will coming. my 2 working machines have win10 (no upgrade possible due older hardware) and win11 (with tweak), the other two machines are win11 capable and already have win11 installed.
from another thread here:
https://www.tenforums.com/tutorials...rget-feature-update-version-windows-10-a.html
disabling is so easy.
and honestly, i wont upgrade from 10 to 11 with a fresh install, too much remnants.

 

offtopic. same here. first view i was nosy again, then i liked it. nevertheless i still do work of any type on win 10, currently, but i have now some spare space to install win11 here also. but - this will also limit my work concerning win10, the downward compatibility is no longer perfect. and my further support help might also limited, not only here. my living room has a HP SFF machine for tv and streams, and its fully win11 comaptible. therefor i finally have left windows 8 behind me but this required a new scanner and printer (ok, laser printer got broken inside). my epson gt is not 64-bit compatible due scsi card. historical view my win10 experience started in 2015, first view in pro, but i decided to use the LTSC 1503 because a very old machine, but win10 was not compatible to that one so the first upgrade came in and win10 performed better. but the ltsc installation got a bit buggy in the past so i change here to 10-pro last year. while my second machine is default win11, then 10pro, and a remnant with latest ltsc from 2021. i wont call all perfect, but in special view to this thread it seems i left a lot of issues behind me with excessive tweaking and hardening and other software. the given example here with eset and its update reminder - eset ever was my favorite, but also this masterpiece has too much intrusion into processes it never should do. to mention that i trashed every new windows here in the first 2 attempts, so its not that i dispraise (missbilligen) the usage, but i avoid it as much i can and warn about. i did heavy tweaking and patching in XP, less in win7, and close to none in win8/10/11. a forward progress for more working and less wasting time while stability stays and fixing whats never has been broken. tl&dr

 

I was referring to the fact my PC has never been eligible for Win 11 upgrade;

 

@itman. Ah OK, thanks. I interpreted "now" to mean it was before, as in pre-update. I was thinking that was a bit odd....

 

Server 2019 KB5035849 gives error 0xd0000034 while trying to install. Just reporting it, I'm sure I'll figure out what I want to do about it.

 

Well, let's see how it will go this time.

https://i.ibb.co/N1RGFtN/Image-730.png

OK, it went fine.

 

I've only updated my machine at work, Win 11 Enterprise. No issues so far.

 

Same here.

 

All good in the hood with the offered updates today - 5 x win 10 & 3 x win 11 done & dusted. Two more to go. Only one machine had errors to repair on a SFC afterwards - that machine always does though.