try this first, it needs to be admin command prompt not powershell net stop bits net stop wuauserv net stop appidsvc net stop cryptsvc net stop msiserver cd \Windows Ren SoftwareDistribution SoftwareDistribution.old cd \Windows\System32 Ren C:\Windows\System32\catroot2 Catroot2.old net stop cryptsvc rmdir /S /Q CatRoot2 net start bits net start wuauserv net start appidsvc net start cryptsvc net start msiserver reboot Catroot2 is nearly always the culprit.. If dism fails you need to download the base image and run it directing dism to the image so it can repair the dism infrastructure. You can create the image using uup dump and convert to iso Command is Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:H:\sources\install.esd:1 /limitaccess .. Change the drive letter to your mounted iso
I've figured out that the logon delay in VMWARE is due to the virtualization. Doing a real setup on my machine the 22000.120 build runs at light speed and the logon is a matter of nanoseconds.
WHen I right click on Start I get the option for Windows Terminal and Windows Terminal (Admin). They launch Powershell windows.
Can try just typing "cmd" in powershell and see if it opens a command prompt. Sorry I'm not actually running win11 beta on my main machine. Otherwise, it should be located at c:\windows\system32\cmd.exe
You should learn how to use Terminal then. You can open tabs within it of more Powershell windows....OR even the command prompt! Terminal encompasses both.
So I figured out that the error was caused only due to the fact that I was using just a local account. As soon as I linked my insider account, the update was downloaded and installed. I guess Microsoft is really discouraging the use of only local accounts on Windows now.
If that were true internet would have exploded and all users with offline/local accounts would have experienced the same problem. Most likely it was just a glitch.