The Empirical Manifesto

1. While installing Windows 11, if your computer does not meet the hardware requirements, you will see a message stating, "This PC can't run Windows 11." Windows 11 setup blocked due to missing hardware requirements.



2. When you see the above message, press Shift+F10 (Or Shift+fn+F10) on your keyboard at the same time to launch a command prompt. At the command prompt, type regedit and press enter to launch the Windows Registry Editor.



3. When the Registry Editor opens, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\Setup, Right-click on the Setup key and select New > Key.



4. When prompted to name the key, Type LabConfig and press enter.



5. Now right-click on the LabConfig key and select New > DWORD (32-bit) value and create a value named BypassTPMCheck, and set its data to 1.



6. Once you configure the BypassTPMCheck key-value under the LabConfig key, close the Registry Editor, and then type exit in the Command Prompt followed by enter to close the window. You will now be back at the message stating that the PC can't run Windows 11.



7. Click on the "X" button in the Windows Setup dialog, then confirm, Yes.



8. You will now be back at the screen prompting you to select the version of Windows 11 you wish to install. You can now continue with the setup, and the hardware requirements will be bypassed, allowing you to install Windows 11.

Steps to create a virtual machine disk descriptor file:

    Connect to the ESXi host as root through SSH or DCUI.
    Navigate to the directory that contains the virtual machine disk with the missing descriptor file using the command:

    cd /vmfs/volumes/DATASTORE_NAME/VM_NAME
     
    Identify the type of SCSI controller the virtual disk is using by examining the virtual machine configuration file (.vmx ). The controller is identified by the line scsi#.virtualDev , where # is the controller number.

    This example uses lsilogic :

    scsi0.present = "true"
    scsi0.sharedBus = "none"
    scsi1.present = "true"
    scsi1.sharedBus = "virtual"
    scsi1.virtualDev = "lsilogic"
     
    Identify and record the exact size of the -flat file using this command:

    ls -l vmdisk0-flat.vmdk

    -rw------- 1 root root 4294967296 Oct 11 12:30 vmdisk0-flat.vmdk
     
    Use the vmkfstools command to create a new temp virtual disk:

    # vmkfstools -c 4294967296 -d thin temp.vmdk

    The command uses these flags:
        -c size
        This is the size of the virtual disk.
        -d thin
        This creates the disk in thin-provisioned format.

The temp.vmdk and temp-flat.vmdk files are created as a result.

Note: To save disk space, we create the disk in thin-provisioned format using the type thin. The only consequence, however, is that the descriptor file contains an extra line that must be manually removed in a later step if the original disk is not Thin provisioned.

    Delete temp-flat.vmdk, as it is not needed. Run this command:

    rm -i temp-flat.vmdk
     
    Rename temp.vmdk to the name that is required to match the orphaned -flat file (or vmdisk0.vmdk , in this example):

    mv -i temp.vmdk vmdisk0.vmdk
     
    Edit the descriptor file using "vi" text editor ( vi vmdisk0.vmdk, in this example)
     
        Under the Extent Description section,
            Use command "Insert" to allow modifications on the descriptor file.
            Locate and change the name of the -flat file to match the orphaned -flat. Once completed - hit "Esc" to exit this mode.
        Find and remove the line ddb.thinProvisioned = "1" if the original .vmdk was not a thin disk. If it was, retain this line. Use command ":wq!" to save and exit "vi" editor.

        The virtual machine is now ready to power on. Verify your changes and ensure the Disk chain is consistent before starting the virtual machine.
         
    To check the disk chain for consistency, run this command against the disk descriptor file:

    vmkfstools -e filename.vmdk

    For a complete chain, you see output similar to:
    Disk chain is consistent.

    For a broken chain, you see a summary of the snapshot chain and then an output similar to:
    Disk chain is not consistent : The parent virtual disk has been modified since the child was created. The content ID of the parent virtual disk does not match the corresponding parent content ID in the child (18).

vmkfstools -c 100m virtualdisk.vmdk -d eagerzeroedthick

vmkfstools -i virtualdisk.vmdk -d thin virtualdisk_thin.vmdk
mv virtualdisk-flat.vmdk virtualdisk-flat.vmdk.OLD
mv virtualdisk_thin-flat.vmdk virtualdisk-flat.vmdk

UNREGISTER in GUI
REGISTER in GUI
VERIFY DISK TYPE

rm virtualdisk-flat.vmdk.OLD
rm virtualdisk_thin.vmdk

# esxcli software vib install -v ht*ps://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vib20/nvme/VMW_bootbank_nvme_1.2.1.34-1vmw.670.0.0.8169922.vib

# esxcli software vib install -v ht*ps://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vib20/vmware-esx-esxcli-nvme-plugin/VMware_bootbank_vmware-esx-esxcli-nvme-plugin_1.2.0.32-0.0.8169922.vib

# reboot