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.

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!

Setup Laravel 10.x Homestead in Windows 10/11

Section – 1 [Install Software]

vagrant_2.3.7_windows_amd64.msi –

VirtualBox-6.1.46-158378-Win.exe –

VirtualBox 6.1.46 (released July 18 2023) << This and Not the >> VirtualBox 7.0.10 platform packages – ​Windows hosts

According to:

Code Editor/IDE: PhpStorm-2023.1.4.exe or VSCodeSetup-x64-1.80.1.exe

Lastly install: Git- –

Section – 2 [ENABLE VT-x in Hardware/BIOS/UEFI if disabled]

Section – 3 [Installing Homestead]

Go To CLI Terminal in IDE/Editor or Windows Terminal or Git Bash Terminal and execute:

git clone D:\htdocs_xampp\Homestead

where D:\htdocs_xampp\Homestead the Homestead directory, after entering this directory:

cd d:\htdocs_xampp\Homestead

Next, execute the bash init.bat command from the Homestead directory to create the Homestead.yaml configuration file. The Homestead.yaml file is where you will configure all of the settings for your Homestead installation. This file will be placed in the Homestead directory: if there is a problem with the




Section – 4 [Configuring Homestead]

Follow the instructions at:

For configuring the file: Homestead.yaml

Section – 5 [Launching The Vagrant Box]

After all, the steps above, it is time to:

Launching The Vagrant Box

You must have in mind the 4 most used CLI commands FROM CLI/Terminal at d:\htdocs_xampp\Homestead\:

vagrant up # if error on this - please Section 6 below
vagrant status
vagrant suspend
vagrant ssh

Section – 6 [Configuring SSH Keys]

In case the first attempt of running:

vagrant up

you getting

Please give the command to generate ssh keys in Windows:

ssh-keygen -t rsa -C ""

This will create the:


Then you have to go to Homestead.yaml and edit the SSH Keys with the correct Keys you have just created:

authorize: C:\Users\lwdls.ssh\
     - C:\Users\lwdls.ssh\id_rsa

Then you return to Section – 5 and give the command: vagrant up

The first time you have to await some time to download the Vagrant VM – Ubuntu Server from the repositories…

After the VM OK is launched go to: http://homestead.test/phpinfo.php to see the webpage of phpinfo():



if any problem put the phpinfo.php



to stop the VM – shutdown the PC – give

vagrant suspend

To add additional sites:

Adding Additional Sites

To create a Laravel Site – start with download Laravel files with the:

At Terminal d:\htdocs_xampp\

composer create-project laravel/laravel example-laravel-app

Composer can be installed from:

Also, the composer comes preinstalled in Homestead/Vagrant/VM

And, a second way is:


vagrant up 


vagrant ssh

and from Terminal at /home/vagrant/ give the command:

 composer create-project laravel/laravel example-laravel-app

Any way you choose, be sure to edit the Homestead.yaml and every new website added to run:

vagrant reload --provision

And lastly

To run a new URL locally modify the host file at:

On macOS and Linux, this file is located at /etc/hosts. On Windows, it is located at C:\Windows\System32\drivers\etc\hosts: homestead.test another1.test another2.test

Again, according to


After, download the Laravel 10.x bootstrap code base, view the Laravel homepage accordingly by going to http://another1.test.

Happy Laravel Web Development & Coding…!