My Triple-boot PC – experimental

Windows 11 <==> Unsupported/bypass methods used

3 OSs: Windows 10 Home, Windows 11 Home, Windows 11 Pro

Was single boot Windows 7 Home, after I had upgraded to Windows 10 Home, after dual-boot by installing – bypass restrictions – Windows 11 Home, on another partition, and all this on an HDD 1TB – MBR – 4 Partitions – two OSs.

Recently, I added an SSD and initialized to MBR, thereafter I installed Windows 10 Pro as a triple-boot PC, and just a week before, I upgraded the Windows 10 Pro to Windows 11 Pro bypass…

In other words,

After successfully installing the first Windows OS, later the second OS as dual-boot, and lastly, the third to be a triple-boot PC… the initial boot screen is like the screenshot [you will NOT FIND the keywords: “HOME” or “PRO”, instead of the first Windows 11=”On Volume 3″ is Home and 2nd one “On Volume 5” is Pro]: you have the choice to choose one of the 3 installed Windows OS… to boot with the PC 🖥️…

Default boot OS is the first one on the top, here Windows 11 Pro (On volume 5)

In my case, the first OS Windows 10 is the Home version, Windows 11 (On Volume 3) is also Home – a bypass version, and lastly, Windows 11 (On Volume 5) is the Pro version bypassing version, of the restrictions of Windows 11 on old Hardware of this experimental PC.

About my storage hardware: I have a 1TB HDD and a 512GB SSD.

On HDD there are 4 partitions of which two are for Windows 11 and 10 Home versions, the others are system small partitions, and lastly, on SSD I have the Windows 11 Pro bypass version.

Some other notes:

In this screenshot during the Boot process – OSs do not have “Home” or “Pro” instead they have plain Windows 10 or Windows 11… names.

Also, because having two Windows 11 OSs the one first installed is “On Volume 3” and the last installed is “On Volume 5” to distinguish between the PC boot with OS, and it’s putting these labels by itself. The PC does not put “Home” or “Pro” labels and Windows 11 (On volume 5) is the Pro version all others are “Home” versions. If a dual boot system was e.g. Windows 10 & 11 the screen would be without “On Volume X”… because would be self-distinguishable.
Because all OSs are Windows the chosen OS screen is the modern traditional screen. If a Linux OS is installed alongside a Windows dual-boot OS, the screen to choose OS may be black and not blue.

You have 30 seconds to decide the preferred boot OS, and this period can be set up from inside any of Windows’s OS Settings, you can also, set up the default OS, and this default will be the first OS in the list… during boot/post of the PC.

To face the Windows OS many updates at least two per month normally, from Microsoft, I have taken over the following actions in each of my Windows OS:

I have pinned the Windows Settings/Control Panel to the Taskbar to Create a Restore Point.

Also, in this Settings window’s other Tabs, you can set the Default Boot OS of the 3 installed, the Time you must choose an OS, on PC boot, set OS Environment Variables, etc. Settings of the OS you are currently using.

If updating one OS of the three, I make sure it is the default OS, due to some auto restarts during the Windows OS update may require…

As you see in the last two screenshots below, as said and before, you have 30 seconds to decide the preferred current boot OS, you can set this period from inside any Windows OS (same Settings Window but another Tab as Create Restore Point popup Window) and also you can set up the default OS, if don’t choose any OS on boot up process, this default will BOOT and be the first OS in the list… during boot/post of the PC.

Create macOS Sonoma [14.x] ISO without a Mac Computer and FREE

The basic idea of FREE ISO is:
“Use a free non-trusted macOS Sonoma VM in a Hypervisor like VMware Workstation Pro to create from it a macOS Sonoma ISO (Trusted)”

In my case the VM was Ventura 13.x [a year ago created Ventura.iso from this VM, see here the blog post for this], and updated to Sonoma 14.0, After this the non-Trusted VM macOS Updated to macOS Sonoma’s latest…. 14.1.

After Updating to MacOS 14.1 Sonoma, now I will create an ISO Sonoma14.1.iso file… useful for Virtual Machines, etc. Also, this should be a Trusted ISO, you can log in with Online internet accounts free of worries of malware…

STEPS CREATE macOS_Sonoma.iso


STEP-1: Download Sonoma Installer from the Apple Mac App Store

STEP-2: Choose Quit Install MacOS

STEP-3: After this the last session is to give some commands from the CLI/Terminal – [see the end of this blog post for the commands]:

STEP-4: COPY outside the VM

The Sonoma.iso should be in your Desktop of the VM MacOs Sonoma.

You can copy the ISO file to an external USB Stick Storage device:

Sonoma 14.1.iso vs Ventura 13.x.iso:

Code Download for Section 3:

Terminal Commands to Download and Execute here (file.txt file).

If you want the ISO file ready to download – Please send an email to and I will send you the download link….


Problems with nested Virtualization in VMware VMs & the Solution worked for me

Host OS: Windows 11 Pro


Guest OS: downloaded from here free Dev Version valid ~3 mo: VMware version:

After having downloaded unzipped and imported to VMware Workstation Pro 17.0.2.

Nested Virtualization problems followed by solution:




IF Nested Virtualization problems CONTINUE GO TO STEP 2


SOLUTION STEP-2 [After Step-1 still not working]

The process to turn off virtualization-based Security:

Below are steps that can be followed to turn off virtualization-based Security for Windows 10 Home & Pro:
For Microsoft Windows 10 Pro & above:

Go To: Edit group policy ( gpedit.msc )
Go to Local Computer Policy > Computer Configuration > Administrative Templates > System
Double-click on Device Guard on the right-hand side to open.
Double Click on “Turn On Virtualization Security” to open a new window
It would be “Not Configured”, Select “Disable” and click “OK”
Close the Group Policy Editor.
Restart the system


If you still having problems put in the article comments and I will reply soon!