I did that already and posted that here, but you either missed it or something, IT WILL NOT ALLOW YOU TO UNINSTALL IT HAS THE SAME ERROR AS IF YOU ARE INSTALLING IT, MISSING "NIMUM_X64.MSI"
Did you reboot after applying it? .reg file attached, just double-click and choose to Merge into the Windows registry - reboot. Hmm, can't attach a .reg file. Just put this in a text editor and save it somewhere as Restore Classic Explorer Ribbon In Build 22000.71.reg then double click it to merge. Reboot. Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked] "{e2bf9676-5f8f-435c-97eb-11607a5bedf7}"="" [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked] "{e2bf9676-5f8f-435c-97eb-11607a5bedf7}"="" Update: Now attached as a .zip file, extract it and follow above info.
I'm sorry but this is a generic thread, not a specific thread you opened and 10 msg long, so it's clear that I haven't a full record of your attempts. Whatever... you can try to use the good old "Windows Installer CleanUp Utility" (msicuu2.exe) to remove the VCredist from the list of the installed things then reinstall it or try a slightly older one (or newer one, if available)
Sooner or later I'll do what Ettore Majorana did. (He was one of the Italian scientist who contributed the de discovery of the modern nuclear tech, when he realized what could be done whit that tech, he just decided to vanish (likely becoming a monk). His fellow Fermi was more pragmatic and the atomic bomb become a thing in less than a decade.)
According to what you say, that's what will be : Windows 10 21H2 Windows 11 21H2 MS released Windows 11 RTM quietly.
Looked into this and it seems like these 20h1 and 21h2 numbers are referring to the release dates, so it is very likely everything you said is 100% accurate. Not saying that they can't delay if they need some more time, but for the time being it looks like their plan is to release Win11 at the same time they release the Win10 21h2 update in October.
Actually, although the names have changed, the Beta channel used to be the Slow Ring, which DID regularly receive new builds that were not classed as Release builds.
Yes, but when they've done so in the past, the .1 build itself isn't classed as THE RTM build, and isn't even made available as an ISO.
I think that some people in MS decided to make the matter more confusing than has used to be, just because they like to read all the guesses and counter-guesses here on MDL
Where is the problem? The 21H2 monniker has always been used to denote which release of the OS it is. Now there are 2 OS's (10 and 11), there can easily be a 21H2 release of both of them.