Just wondering mate, have you given any thoughts of adding no internet loading ability into this great patch, or is it already there by default.
sorry must be wording it badly. Lets try it again, Your FIX KIT allows unsupported machines to load the Operating system. With M$ now adding you must be connected to the web soon as yet another requirement to load the program, does your KIT already allow those with no internet access to load the program, or are you considering adding it as an extra feature. Hope that makes sense.
Now it does I doubt it can be automated, the rebooting \bypassnro causes could screw up installs i can imagine.
thanks for the reply. Its no biggie, I am keeping all the various methods one can use if not on the internet to see what works in the future. Your answer of course makes a lot of sense. Why mess with the perfection of your kit.
You no longer will be able to make a local account and have to log in with your Microsoft login is what they will be doing. I don't know if there can be a workaround. Edit: I'll need to see if my answer file that makes a local account still works.
This works but i doubt it can be automated or it's useful to do it and the reboot it does can screw with oobe.cmd, setupcomplete,cmd or firstlogon.cmd. + Not an issue, local accounts can still be created.
Currently there are a couple of work arounds that still work, and a couple loopholes that M$ have also closed. That means M$ is quite active at present shutting down methods that surface. How long they keep trying is another matter.
Hi Enthousiast, long time no talk, hope you are fine. I have Win10 and macOS dual boot on separate SSDs for the last 3 years. I almost haven't used Win at all. I'd like to upgrade Win10 to 11 on an unsupported CPU, TPM and Secure Boot turned off in BIOS (required for macOS boot). Is Replace/Rename/Delete enough to upgrade via WU? I read a lot about adding Regedit bypasses in order to do it. Is it no longer required? Thanks!
You can use a fixed by option 2 ISO to upgrade by ISO or run the fix cmd from @BAU for upgrading (replacing appraiserres.dll still works but that needs a bit of precise timing).
Deleting appraiserres.dll worked for me for 22000.xxx, but failed when I tried to install 22557.1. However your script worked very well.
hello. I have used the script to prepare the final w11 iso 22000.588, and although it has been installed, I get a message on the screen that "the computer does not meet the requirements"
This was coming. Firstly there is NOTHING WRONG with the ISO. It has installed perfectly. Windows from it seems 22000.588 will have that nag message for systems that dont comply. So yes its has installed fine, that message will appear on all non supported builds. Look up the current ways to remove that message (at this typing there are a couple of registry entries to add manually, BUT that may change with different builds).
I have this gut feeling that M$ thought that few people would be able to load Windows 11 on unsupported machines. BUT as time went by, M$ saw there are quite a few workarounds that allow people to use Windows 11 on any machine. In fact too many that they can stop --- so M$ has decided they have to move to the next level, ------ The good ol NAG MESSAGE (WATERMARK). How this nag message evolves will be interesting. Already there are ways to remove it, so one wonders how long M$ will persist trying to force this. To state again, this fix WILL ALLOW windows 11 to load properly and fully on your machine. The nag message has to be removed separately after Windows 11 is loaded.
Apply Code: reg add "HKEY_CURRENT_USER\Control Panel\UnsupportedHardwareNotificationCache" /v SV2 /t REG_DWORD /d 0 /f as admin and refresh your desktop