Not one 22000.xxx update was released on patch tuesday, it's IP so it can get updates whenever MSFT wants to. All 22000.xxx updates are released on a Thursday: 22000.65: https://forums.mydigitallife.net/threads/windows-11-hotfix-repository.83741/page-2#post-1673114 22000.71: https://forums.mydigitallife.net/threads/windows-11-hotfix-repository.83741/page-3#post-1675231 22000.100: https://forums.mydigitallife.net/threads/windows-11-hotfix-repository.83741/page-4#post-1677207 22000.120: https://forums.mydigitallife.net/threads/windows-11-hotfix-repository.83741/page-6#post-1680255
Hoooooo, I got .120 via WU...am I in danger on my old Acer Laptop now ? I see .120 is on UUP dump since 2 days ago again...whats the difference if there is any at all ? Does this mean I have a faulty .120 ?
When will Microsoft Store be updated to allow you to download and install Android Apps. I want to run Township on Windows 11 android version and see if it has the same issues as Township windows version that i am currently running on Windows 11...
You are here, isn't that a bit the same? You got banned at the same time he was (for build trolling).
Oh I know, didn't claim one will be released either. It's just random s**t people have read on the internet that this Tuesday will have a update for Windows 11. I'm just neutral to the whole thing. s**t drops when it drops. Couldn't care less.
ok so rumor that the final Windows 11 CU will be October 2021 will Insiders get Final ISO in September?
Perhaps, but I am so busy these days providing care for my disabled wife, and step-daughter: cooking, cleaning tending to their needs besides ensuring all computers are running smoothly. I really don't have time for such trivialities.
You get banned for that? Dam, i been banned for saying Trump is a horses ass, i been banned for saying Biden is a horses ass, I never got banned for saying a build is a horses ass.
Starting build threads with so-called new builds which never appeared, posting incorrect build numbers, trolling in general, having multiple accounts.. etcetc...
Shouldn't be any danger to anyone who updated their previously installed system to .120 via Windows Update. The error seems to be very specific to those who created a .120 ISO with KB5004554 pre-integrated such as those who used uupdump to create and install a fresh build for .120 specifically. Also the error only pertains to having a problem actually running the recovery environment (booting from the winre.wim from within a windows install and not an install media). After I get something to eat I'll play with reagentc and see if there's any easy fix for those who already have installed .120 this way. Again if you only updated via Windows Update, it won't affect you. Edit: Most of this information is correct except the fact that it's the actual winre.wim that is getting modified and integrated with a bad update by the uupdump script that is the problem. Anyone who is using Windows Update will still not be affected as Windows Update does not integrate winre.wim with updates.