I don't want to repair or uninstall it but make it go away from startup (it appears as disabled). Also, I don't know why, but after installing 22H2 CTRL T is no longer selecting all files and folders but CTRL A is instead.
Try this registry key Code: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
For unsupported systems Earlier, using the reg tweak to disable the system req like secure boot, TPM etc, that trick was working in both, W11 setup.exe was working for in-place upgrade & clean installation for W11 21h2 branch But now, in the latest W11 22H2 branch, using the same (reg) trick, working for a Clean installation but blocking while trying to in-place upgrade via the setup.exe from W11 22H2 build (i.e. IPU from 22621.675 to 22621.819) Anyone facing this same & know any workaround for this? Or is there any new workaround for the latest W11 22H2 branch?
The reg tweaks only worked for clean installs, they were done on the boot.wim index 2 registry. Replacing/deleting/renaming appraiserres.dll still works for ISO clean installs and ISO upgrades but then you can't check the download new drivers and updates during upgrade box, else it will be overwritten by the original one. These options work fine for all win 11 builds, including IP DEV channel builds: https://forums.mydigitallife.net/threads/dynamic-windows-11-setup-tpm-bypass.84063/ (WU/ISO upgrades) https://forums.mydigitallife.net/threads/win-11-boot-and-upgrade-fix-kit.83724/ (option 2 for ISO Clean install/ISO upgrades)
Let's hope they finally fix that filecopy/transfer rate bug that's been going on forever now! Nah, I'm certainly not going to hold my breath!
The announcement about not getting new builds this week was for the dev channel, updates can be released.
I just restarted my computer, and I got the "Updates are underway" message as it was shutting down. But after going into the Updates History, there is nothing reported as being installed. The build number is the same... Does anyone have any ideas what it was, did it happen to you?
Driver/Defender stuff, etc...etc..., seen this many times on my vm tests, when shutting down for the first time.