X10pe looks for the cdusb.y and if it finds it it mounts that directory as y xpe also expects there to be Only One copy of the cdusb.y having two causes breakage so after initial build you need to Goto the iso prebuild folder and cut the programs and cdusb.y file and move it to the root of the drive BEFORE clicking the rebuild iso button #Ventoy how to add iso how to#I can't make heads or tails of the engrish in that post to see how to make ventoy do thatįor now I just moved the programs folder,cdusb.y the root of the drive with the iso #Ventoy how to add iso driver#I suppose if the fingerprint driver in Windows gets updated the fingerprint reader will be messed up again in Linux though.Basically what needs to happen is that win10xpe expects the root of the iso to be mounted under y: after boot and thats not happening On subsequent Linux boots everything’s OK. The good news is you only have to resolve the boot and fingerprint issue once. It doesn’t alter the RTC so it doesn’t alter the time on Linux. At least all that’s required here is to set it to detect the local time zone and sync. Oh and Windows always boots up with the incorrect time. There’s an excellent script which can remove all fingerprints and reset the reader in Linux, just use this and re-enroll your fingerprints. I didn’t even enroll any fingerprints in Windows, just installing the driver did it. I didn’t do this, disabling it is enough.Īlso if you had enrolled fingerprints in Linux, installing the Windows fingerprint reader driver will cause a conflict and the fingerprint reader will no longer work in Linux. I know there are Linux scripts to remove the Windows boot loader completely. A semi-permanent fix is to go into your BIOS (F2 on boot), go to “Boot” - select “First” as EFI boot order, go to EFI boot devices, highlight the Windows boot loader and press space which should remove the “X” from the Windows boot loader. #Ventoy how to add iso install#Windows did install its own boot manager and place it in front of my Linux GRUB install, so I could no longer boot and got a Windows boot manager error message since the Ventoy USB was unplugged.įortunately this was easy enough to fix, press F12 on boot and select your Linux drive. This all worked well with warm reboots, but I shutdown and did a cold boot and now I discover Windows didn’t play nice. It functions as a full Windows install on my Framework, doesn’t alter my Linux install on my SSD and lets me do all the other things you can do with Ventoy like add other Linux install environments. HEY WAIT! You can! You can install a Windows VM. I would much rather have Windows run off a Ventoy drive so I could also use it for Linux installs. I have Windows 10 in a VM but it’s misconfigured and can’t access USB. I won’t have this very soon once I sell my old laptop. Also WTG can only be written by Windows, and a fast Windows PC at that. The entire drive gets taken up and can’t be used for other things. I previously ran it in a Windows To Go drive, but WTG is so limiting. It cannot run by command line, it needs to install to a GUI and since the Windows installer doesn’t have this type of environment, it errors out with a “this version of Windows is not supported” error. Unfortunately WD Dashboard doesn’t run this way. #Ventoy how to add iso update#I just kept pressing F12 as the logo appears on boot).Īnd inspired by this success, I tried to run the WD Dashboard software to update the firmware in my WD SN850 SSD I have installed. Reboot your computer and use F12 to access the boot menu (this can take a few tries to get the timing right. I didn’t have a “Windows To Go” or a windows machine to use, but I wanted to do the BIOS upgrade.Ĭopy the ISO onto your new Ventoy USB driveĭownlaod the BIOS exe and put the exe on the USB drive also
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |