11-24-2023, 01:33 PM
Hello.
I have recently started using Ventoy with succes.
However there is one very nuisance. A Ventoy prepared USB-stick (under Windows 10), if a extra ISO is to be added, takes maybe 4 minutes before recognized by the PC (with Windows 10). Before recognizing, all USB-related programs (and Windows Explorer), fail to start. After recognizing, all functions well and normal. Even unplugging and replugging the USB-stick gives then no problem (untill replugging in a new started PC).
The are many reports from different peaple about the same problem.
I found that the Ventoy-stick has a FAT16 Ventoy-system partition.
I have earlier found, on my PC with Windows 10, that memory-cards which are FAT16 formatted (so 2GB or 4GB cards) give serious confusing recognizing problems. Probably because there are several different recognizing ID-'s for FAT16. When I applied FAT32 for those cards all problems were over.
So I suggest to the developer of Ventoy to change the Ventoy-system partition to FAT32, in my expectation that then the long recognizing problem under Windows10 is over.
I have recently started using Ventoy with succes.
However there is one very nuisance. A Ventoy prepared USB-stick (under Windows 10), if a extra ISO is to be added, takes maybe 4 minutes before recognized by the PC (with Windows 10). Before recognizing, all USB-related programs (and Windows Explorer), fail to start. After recognizing, all functions well and normal. Even unplugging and replugging the USB-stick gives then no problem (untill replugging in a new started PC).
The are many reports from different peaple about the same problem.
I found that the Ventoy-stick has a FAT16 Ventoy-system partition.
I have earlier found, on my PC with Windows 10, that memory-cards which are FAT16 formatted (so 2GB or 4GB cards) give serious confusing recognizing problems. Probably because there are several different recognizing ID-'s for FAT16. When I applied FAT32 for those cards all problems were over.
So I suggest to the developer of Ventoy to change the Ventoy-system partition to FAT32, in my expectation that then the long recognizing problem under Windows10 is over.