Surface-Laptop-Go VS Ventoy

Currently following this guide, but having issues with disabling TPM. The option is no longer within the surface uefi menu, so I need to know how detrimental it is to having tpm enabled/disabled. Secondly, this is my first time attempting a physical install as i’ve done multiple VMs in the past, but I am getting stuck/confused on creating an EFI if anyone would be kind enough to help with a walkthrough/a more detailed description of what I’m essentially doing. Thanks in advance!

I just want to clarify, that this link is not for an EFI. It's a guide. https://github.com/olm3ca/Surface-Laptop-Go

Needed iGPU.plist from https://github.com/olm3ca/Surface-Laptop-Go

Here

CPU: Intel i5-1035G1 (Icelake) GPU: Intel UHD Graphics (Iris Plus Graphics G1) RAM: 8GB Soldered to motherboard Wifi: Intel Killer Wifi 6 AX1650i (201NGW) Audio: Intel Ice Lake-LP Smart Sound Technology (Realtek ALC274 codec) Touchpad: ELAN SSD: stock 128GB or 256GB NVME M.2 - easy upgradable. Mine is 1TB Full instructions posted here: https://github.com/olm3ca/Surface-Laptop-Go

Ventoy is an open-source tool to create a bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. Using Ventoy, we can create live USB for multiple distros in one flash disk. This is a revolutionary feature compared to other tools, e.g., Etcher, Rufus, etc, that can only create one live USB at a time. This tool is so important. Don't call yourself a distro hopper if you don't know this tool.

I'm thinking you mean Ventoy? They say they can load vhd and img files, though I've only tried ISO's myself.

https://www.ventoy.net/

View on GitHub

I faced it too. There is a PR on the ventoy GitHub repository that fixes Proxmox boot.

https://github.com/ventoy/Ventoy/actions/runs/7088423200

> While this works, I find this method a bit tedious to use, at least compared to Ventoy [0].

I find ventoy more tedious, because you can't use it on your hard drive with a sane partitioning scheme.

The only reason is because of how the ventoy detection hardcode the partition boundaries in its checks, and it means Ventoy can only run with the partitions set in a way that may lead to alignment issues like write-amplification: I've detailed that in https://github.com/ventoy/Ventoy/issues/1342

Ideally I'd have a 10G partition after the EFI (or it could even be the EFI itself) with a few ISOs for rescue purposes + a UEFI entry to avoid having to use a bootable USB, but that's not possible with Ventoy unless I accept Ventoy choices of partition boundaries:

                (pMBR->PartTbl[0].StartSectorId != 2048 ||

I downloaded and made a bootable USB Ventoy (https://www.ventoy.net) with its Windows GUI app in my updated 64-bit W10 Pro PC. However, I couldn't seem to get VirtualBox v7.0.12 to boot it. I read VirtualBox can boot from bootable USB flash sticks so it should work. Am I missing something?

So, yes. The installer will need to install grub to that first partition. You can install ventoy to a usb drive, put a windows iso there and your q4os iso. In case you mess up big time, you can reinstall windows.