Yes surely.
You just need to reinstall with the iso of Tiny11 and upon flashing with Rufus you get an option to bypass both of them. Also it is faster on older hardware.
Assuming you have yet to complete the OOBE ("out-of-the-box experience" AKA initial setup wizard) or are willing to reinstall, this guide worked for me a couple of months ago. Step 13 is where start if you're still at the OOBE.
The exact OOBE screens shown in the guide may not be a perfect match for your version of Windows 11, but the key steps should work if Microsoft haven't patched it out.
You could try to force a local User Account. First You should install it offline, without an Internet Connection.
In the Past it helps to do the following: For that You have to type in the E-Mail-Adress Field something like scammer, spammer, elon musk or example@example.com and on the Password Field only 1 Sign. But it seems that this will not work anymore.
What seems to work is a Bypass command. Here is a Video what explains it better:
What I used to do the times I installed w11 in a vm was the email address "no@thankyou.com" and type anything in the password. It will give error and go to the next step, skipping the microsoft account requirement
Another method I know off is using rufus to flash the w11 iso to a usb drive and then installing from there, as it has an option to disable the microsoft account requirement, just like nxtmighty suggested
I think I remember seeing someone ending the wifi process somehow and microsoft account requirement not appearing because theres no internet connection, but it was from the early w11 days and I'm not sure if it still works nor how it worked
I personally would recommend against tiny11 or overall any "windows distro". You don't usually know what they put in them, so it may run without microsoft spyware, but there can be another spyware or malware hidden
And even if it was open source and the malware risk was minimal or non-existent: the risk of things breaking with an update (or just overall deleted stuff coming back) is way higher than on a vanilla windows install, because some new features or system components could expect something to be there but not actually find it. Even if it was safe and worked better in the short run, it will give more problems than a normal windows version in the long run
There's also the fact that most windows distros like that one completely disable windows updates to prevent them from that problem, but that creates a new problem: lack of security updates and software incompatibility in the long run
You have to press a specific key before the windows loading icon comes in. That key is usually ESC, F2, F10 or DELETE. However, with how windows's "fast boot" feature works, this can't be done on a normal boot. Instead, you need to log into windows and then reboot (not to confuse with shutdown and then start up), or you can go to the settings app, search for something named like recovery boot options, and from there see if there is an option to boot into the UEFI directly (on windows 10 it is possible, I'm not sure if things changed on 11)
As for linux, the grub bootloader usually has a menu entry for accessing the UEFI, so if you are dualbooting linux with windows and see a menu that lets you choose which operating system to use, one of the options should be the UEFI menu
Earlier back in March, I had Win11 version 22H2 in which I was able to access the UEFI via my BIOS after pressing F12 but now I have the 23H2 version, I can't seem to do that now...
So, when the F12 Key is the Key that You must use, you could try the Following:
Completely s turn off Your PC; no Sleep Mode or Stand-By, complete down. Then press the Power Button to turn it off and immediately after that push the F12 Key again and again and again. It feels a bit stupid to do it that Way but it is worth a Try.
Totally editing your post to a completely different topic / question is not cool, should be a capital offence.
The terms "BIOS" and "UEFI" are kinda interchangeable the same thing these days, in that modern systems have UEFI instead of BIOS but most people still refer to the firmware control panel as BIOS.
You won't find either a BIOS or a UEFI control panel after selecting the Windows boot loader, because that takes over from the BIOS / UEFI firmware to actually boot into a main OS.
I don't understand You right. When You click on the Windows Boot Manager that starts Windows; that is totally normal. What do You exactly mean with ''UEFI''? UEFI is Your BIOS. BIOS is an older Word and - if You want to have it so - an older System but this Wording still exists. You can call it UEFI-BIOS, too.
Or do You mean the GRUB Menu where You can choose between Windows and Zorin?
Can you provide video of your computers current BIOS and Windows Boot Manager behaviour, and fully explain what you mean by UEFI if not the system firmware control panel accessed via F12?
I have no idea what you mean when you say you can access BIOS but not UEFI and that you expect to get into UEFI by clicking on Windows Boot Manager. That concept does not make sense to me.
I don't have Windows installed, but when my computer first turns on I can smash F12 / F2 / DEL to get either the BIOS/UEFI control panel or a short menu of bootable devices. If I don't, or if I select the main SSD as the bootable device, I get my GRUB menu that lists the installed operation systems - but GRUB, or the Windows Boot Manager, loads after the BIOS or UEFI.
My GRUB does have a menu entry to go into the UEFI firmware control panel, but it's the same control panel as I get from spamming F12 / F2 / DEL or whatever key before GRUB loads.
The BIOS Menu appears but on a Dell XPS 9520 laptop that is actually a separate thing from the blue and in white colored text UEFI Menu - where you can access other options as well.
I just looked up the manual of that laptop, and it says that the UEFI is accessed with the F2 key and you said it was the F12 key... aren't you confusing it with the boot menu? Mostly because, well...
That appears in only two places: the boot menu or the boot order in the UEFI. But it only boots windows when selecting it from the boot menu, so with all this in mind...
Could you try again, but this time with the F2 key instead of F12?