New
#81
Thanks for the detailed info.
As for running a local account with 22H2, yes, I know multiple ways around that so that's a piece of cake
Thanks for the detailed info.
As for running a local account with 22H2, yes, I know multiple ways around that so that's a piece of cake
With Windows 11 Home the setup won't start unless the Internet is connected. After you get past the first part you can disconnect the Internet. You are then able to just create a local account.
With Windows 11 Pro it is easier because you can start with the Internet disconnected Like home you able to just create a local account.
After the first boot and login you probably want to connect the Internet so you can get updates.
BYW, while running the virtual machine with Hyper-V I can go into the settings and toggle the network off and on any time. When I upgraded to Windows 11 on this computer I had to physically disconnect and connect the Ethernet cable to do the same thing.
Actually, that changes a bit in 22H2, where the restrictions are even greater, but that's ok. Regardless of whether I'm installing home or pro, 21H2 or 22H2, I have workarounds for all of it. It's effectively a non-issue for me.
MisterEd,
I usually handle it in one of two ways depending upon what I want to do. First, I should note that I rarely ever install Home. I prefer Pro on everything . The first method will work only on Pro, but the second will work on either.
1) This method still requires an internet connection. I follow the installation up to the point where it wants me choose if I am installing for personal use or business. Rather than selecting the usual option of "personal" I choose the "business" option. I don't have it in front of me, but on the next screen I think there is some choice that says something like other options. I select that. Choose to perform a Domain Join. No, we won't actually join a domain! If you proceed, you can enter a local account name. Done! As I noted, only down side is that an Internet connection is still needed.
2) This is my preferred method. I simply drop an autounattend.xml unattended answer file in the root of my installation media. I made the answer file so that the only thing it does is create a local user account with no network connection needed. The entire rest of the setup experience is just like normal. One reason I like this method is that with a simple tweak, I can also add the workarounds for unsupported hardware to the same answer file. Or, if I want to go the full distance, I make that answer file so that it performs the entire installation from start to finish completely unattended. Easy!
I found this online. The way I did it works for both Home and Pro. I entered a bogus email address and password and then pressed Next. I get an error and it then asks me to create a local account. BTW, I entered the following:
Email address: MickeyMouse
Password: None
I was surprised something that crazy worked.
In case anyone is interested Windows 11 22H2 has not been released to the public yet. I got it as a beta from the Windows Insider Program.
Trivia. The first release of Windows I received as a Windows Insider was called Longhorn. Guess what the release name was.
That wasn't even the first version of Windows I tested. In April 1995 I beta tested Windows 95. The first release or two came on a bunch of floppy disks. I was glad when they finally switched to CDs. Windows 95 was release to the public on October1995.
Yep, I remember those. I had to install Windows from floppy many times every single day. Hated that.
When no solution will work anymore, it will have to be bored with the long password of the account that we have chosen as very long to properly secure the online account.
Last edited by itsme1; 16 Aug 2022 at 23:02.