You need to disable all your antivirus software temporarily, including Windows Defender.
Source :
Question: https://community.lecrabeinfo.net/topic/11838-ventoy/?do=findComment&comment=108373
Answer: https://community.lecrabeinfo.net/topic/11838-ventoy/?do=findComment&comment=108418
What is the purpose of the "Backup" folder and the "TEMP" folder?
All that we place in the drossier System / Drivers opens when starting which tools? Mini windows 10? Do you have to configure Ventoy.json for this?
When starting Jayro's Lockpick, Médicat VHD and mini windows 10, the letters of the system drive and the drive of the USB key will be automatically the same each time?
All that we place in the drossier System / Drivers opens when starting which tools? Mini windows 10? Do you have to configure Ventoy.json for this?
When starting Jayro's Lockpick, Médicat VHD and mini windows 10, the letters of the system drive and the drive of the USB key will be automatically the same each time?
1.) The Backup and Temp folders are used by some of the other ISOs, so I just keep them there to avoid issues.
2.) The System/Drivers folders load drivers for Mini Windows 10 and Malwarebytes only, as they're made from the same config in WinBuilder. You don't have to touch ventoy.json at all.
3.) With MediCat VHD, The C:/ drive will always be the VHD you're using, but for the most-part, the drive letters should remain the same unless you change them. Mini Windows 10's boot.wim will always mount itself as a RAMdisk in RAM as drive X:/ for itself. And Drive Y:/ is the MediCat USB it's booted from.
2.) The System/Drivers folders load drivers for Mini Windows 10 and Malwarebytes only, as they're made from the same config in WinBuilder. You don't have to touch ventoy.json at all.
3.) With MediCat VHD, The C:/ drive will always be the VHD you're using, but for the most-part, the drive letters should remain the same unless you change them. Mini Windows 10's boot.wim will always mount itself as a RAMdisk in RAM as drive X:/ for itself. And Drive Y:/ is the MediCat USB it's booted from.
Sometimes a USB is stubborn, and you need to fully repartition it. I open AOMEI Partition Assistant, blow away any partitions on the USB, and make a new FAT32 partition, then try Ventoy2Disk again. Works for me every time. I usually unplug and replug the USB after the new partition is made too, just to give it a "clean start".
To see if at the next update I need to change these files or at least worry about it.
I also had this problem a few months ago with a very cheap rotten USB stick. I had solved it by transferring the ventoy-partition from a working USB stick. Otherwise, I would buy a new USB drive if I were you, they are incredibly cheap.
Hey, this looks great but I have some questions after trying it.
1) When I load the portable Windows thingy, it doesn't seem to see my disks. It can see itself but not my main PC's SSD. The other bootables like the Linux one does correctly show all partitions.
2) Can the screen scaling or resolution in such portable Windows be adjusted? On my regular 1920x1080 display, everything looks small, and I cannot see any setting to change this. I do notice a Ventoy setting to adjust resolution but it only appears to affect the Ventoy menu and no change there applied within WinPE/Windows. I tried Googling this but got mixed results and nothing conclusive.
3) On many ISO's, I'm getting a "No bootfile found for UEFI! Maybe the image does not support X64 UEFI!". I'm not sure what I need to do to fix this issue. Is this a BIOS issue? A Ventoy issues? I'm a bit confused.
Thank you.
1) When I load the portable Windows thingy, it doesn't seem to see my disks. It can see itself but not my main PC's SSD. The other bootables like the Linux one does correctly show all partitions.
2) Can the screen scaling or resolution in such portable Windows be adjusted? On my regular 1920x1080 display, everything looks small, and I cannot see any setting to change this. I do notice a Ventoy setting to adjust resolution but it only appears to affect the Ventoy menu and no change there applied within WinPE/Windows. I tried Googling this but got mixed results and nothing conclusive.
3) On many ISO's, I'm getting a "No bootfile found for UEFI! Maybe the image does not support X64 UEFI!". I'm not sure what I need to do to fix this issue. Is this a BIOS issue? A Ventoy issues? I'm a bit confused.
Thank you.
1.) Sounds like you need to add your SATA drivers to the /System/Drivers/ folder on the USB.
2.) Some screens play nice, some don't... That's beyond my control.
3.) Read the [BIOS] or [UEFI] tags in the ISO names, that tells you what boot mode is needed for that ISO. That's why I put them there. If the boot menu is green, you're in UEFI, and any [UEFI] tagged ISO will boot. If you're in the red menu, then you're in BIOS mode, and any ISOs with [BIOS] tags should work. They are not interchangeable, but some [UEFI] ISOs will work in [BIOS] mode.
2) Hopefully you would be able to integrate some sort of scaling or resolution functionality in the future/
3) I read that reply as a bit patronising, but the software I was loading was marked UEFI, and the USB was in UEFI mode with the green text, when the issue I described occured.
EDIT: I'll add that I did try multiple IOS's, first was Active Data Studio and the other were some UEFI tools from the Backup and Restore category. Many but not all would produce the error described and I am certain the USB was in UEFI mode.
Last edited by Lewis3563,
Similar threads
-
- Portal
