1
0
Fork 0
mirror of https://github.com/ventoy/Ventoy.git synced 2026-03-03 00:07:49 -05:00

[issue]: After formatting USB using Ventoy2Disk.exe, Ventoy partition does not show in File Explorer on USB plug-in #1593

Open
opened 2026-02-20 21:06:38 -05:00 by deekerman · 66 comments
Owner

Originally created by @rewritten1 on GitHub (Nov 26, 2022).

Official FAQ

  • I have checked the official FAQ.

Ventoy Version

1.0.82

What about latest release

Yes. I have tried the latest release, but the bug still exist.

Try alternative boot mode

No. I didn't try these alternative boot modes.

BIOS Mode

UEFI Mode

Partition Style

GPT

Disk Capacity

256GB

Disk Manufacturer

Corsair Voyager GTX SCSI Disk Device

Image file checksum (if applicable)

No response

No response

What happened?

I prepared a Corsair Voyager GTX SCSI USB drive for Ventoy using the Ventoy2Disk.exe utility with the following options:

  • Secure Boot Support: Unchecked
  • Partition Style: GPT
  • Partition Configuration
    • File System For Ventoy Partition: exFAT, NTFS
    • Preserve some space at the end of the disk: Unchecked
    • Align partitions with 4KB: Checked

I clicked the "Install" button and it created the Ventoy drive successfully. However, after unplugging and re-plugging in the USB drive, the USB drive's Ventoy partition takes forever to show in File Explorer and other programs. Sometimes, the Ventoy partition never shows up in File Explorer and other programs. Sometimes, I receive timeout errors by Windows and the USB LED light continuously flashes trying to mount the Ventoy partition in File Explorer.

Formatting this drive with only one partition allows the USB to mount successfully consistently. Tested unplugging and re-plugging and couldn't get the File Explorer hang delay to occur when the USB has one partition.

Ventoy2Disk.exe log: log.txt

Originally created by @rewritten1 on GitHub (Nov 26, 2022). ### Official FAQ - [X] I have checked the official FAQ. ### Ventoy Version 1.0.82 ### What about latest release Yes. I have tried the latest release, but the bug still exist. ### Try alternative boot mode No. I didn't try these alternative boot modes. ### BIOS Mode UEFI Mode ### Partition Style GPT ### Disk Capacity 256GB ### Disk Manufacturer Corsair Voyager GTX SCSI Disk Device ### Image file checksum (if applicable) _No response_ ### Image file download link (if applicable) _No response_ ### What happened? I prepared a Corsair Voyager GTX SCSI USB drive for Ventoy using the Ventoy2Disk.exe utility with the following options: - Secure Boot Support: Unchecked - Partition Style: GPT - Partition Configuration - File System For Ventoy Partition: exFAT, NTFS - Preserve some space at the end of the disk: Unchecked - Align partitions with 4KB: Checked I clicked the "Install" button and it created the Ventoy drive successfully. However, after unplugging and re-plugging in the USB drive, the USB drive's Ventoy partition takes forever to show in File Explorer and other programs. Sometimes, the Ventoy partition never shows up in File Explorer and other programs. Sometimes, I receive timeout errors by Windows and the USB LED light continuously flashes trying to mount the Ventoy partition in File Explorer. Formatting this drive with only one partition allows the USB to mount successfully consistently. Tested unplugging and re-plugging and couldn't get the File Explorer hang delay to occur when the USB has one partition. Ventoy2Disk.exe log: [log.txt](https://github.com/ventoy/Ventoy/files/10095787/log.txt)
Author
Owner

@ventoy commented on GitHub (Nov 27, 2022):

I have no idea about this.
Let's ignore Ventoy for now, if you just create two partitions manually as Ventoy does, does it show in File Explorer OK?

@ventoy commented on GitHub (Nov 27, 2022): I have no idea about this. Let's ignore Ventoy for now, if you just create two partitions manually as Ventoy does, does it show in File Explorer OK?
Author
Owner

@rewritten1 commented on GitHub (Nov 28, 2022):

I have no idea about this. Let's ignore Ventoy for now, if you just create two partitions manually as Ventoy does, does it show in File Explorer OK?

I created a second partition using diskmgmt.msc on the corsair USB drive and attempted to unplug and re-plug the USB drive at least 10 times to try to reproduce the issue. Each of the 10 times, both USB partitions appear in File Explorer with no delay.

image

@rewritten1 commented on GitHub (Nov 28, 2022): > I have no idea about this. Let's ignore Ventoy for now, if you just create two partitions manually as Ventoy does, does it show in File Explorer OK? I created a second partition using diskmgmt.msc on the corsair USB drive and attempted to unplug and re-plug the USB drive at least 10 times to try to reproduce the issue. Each of the 10 times, both USB partitions appear in File Explorer with no delay. ![image](https://user-images.githubusercontent.com/37819602/204203319-7203b3f7-9ba3-48d9-881d-8da2b1b0bb13.png)
Author
Owner

@rewritten1 commented on GitHub (Nov 29, 2022):

Is there anything else I can try to provide to help find the cause of this problem? Seems to only affect my USBs when they are formatted with the tool. Is there a manual configuration I can try running from the command prompt or powershell?

@rewritten1 commented on GitHub (Nov 29, 2022): Is there anything else I can try to provide to help find the cause of this problem? Seems to only affect my USBs when they are formatted with the tool. Is there a manual configuration I can try running from the command prompt or powershell?
Author
Owner

@steve6375 commented on GitHub (Nov 29, 2022):

Try testing drive with fakeflashtest or h2testw or just filling it with video files and then playing first and last one. Sounds like a fake flash drive

@steve6375 commented on GitHub (Nov 29, 2022): Try testing drive with fakeflashtest or h2testw or just filling it with video files and then playing first and last one. Sounds like a fake flash drive
Author
Owner

@rewritten1 commented on GitHub (Nov 30, 2022):

Try testing drive with fakeflashtest or h2testw or just filling it with video files and then playing first and last one. Sounds like a fake flash drive

Here's the result from h2testw after running the write+verify operation:

image

@rewritten1 commented on GitHub (Nov 30, 2022): > Try testing drive with fakeflashtest or h2testw or just filling it with video files and then playing first and last one. Sounds like a fake flash drive Here's the result from h2testw after running the write+verify operation: ![image](https://user-images.githubusercontent.com/37819602/204816715-20503ffb-bcdf-4ac5-a85d-ab98b15cdcc7.png)
Author
Owner

@steve6375 commented on GitHub (Nov 30, 2022):

Can you try a different USB drive and also a different OS/PC?
Many thousands of people use Ventoy without any problem, so this problem only seems to effect you. So it is probably something odd about your USB drive or system or maybe antivirus/antimalware software?

@steve6375 commented on GitHub (Nov 30, 2022): Can you try a different USB drive and also a different OS/PC? Many thousands of people use Ventoy without any problem, so this problem only seems to effect you. So it is probably something odd about your USB drive or system or maybe antivirus/antimalware software?
Author
Owner

@rewritten1 commented on GitHub (Nov 30, 2022):

I tried with a different generic USB that is not as large, 2GB in size, and I could not reproduce the stalling/hang problem in File Explorer. I tried another USB flash drive, a Sandisk Extreme Pro USB 3.0 128GB, and the stalling/hang problem in file explorer returned. Tested both USBs on another computer with Windows 10 instead of Windows 11, and they too had the same stalling/hang problem.

So far, I am experiencing this issue with large capacity USB drives on Windows. The small capacity USBs mount instantly in File Explorer after Ventoy has formatted them.

@rewritten1 commented on GitHub (Nov 30, 2022): I tried with a different generic USB that is not as large, 2GB in size, and I could not reproduce the stalling/hang problem in File Explorer. I tried another USB flash drive, a Sandisk Extreme Pro USB 3.0 128GB, and the stalling/hang problem in file explorer returned. Tested both USBs on another computer with Windows 10 instead of Windows 11, and they too had the same stalling/hang problem. So far, I am experiencing this issue with large capacity USB drives on Windows. The small capacity USBs mount instantly in File Explorer after Ventoy has formatted them.
Author
Owner

@steve6375 commented on GitHub (Dec 1, 2022):

What happens if you just use the default Ventoy options (run Ventoy2Disk.exe but do not change any options)?
Are you using standard Windows 10 and 11 - Retail? Pro? any added software? Modified OS in any way?
Can you think of how your Windows systems may be different from other peoples Windows systems?

@steve6375 commented on GitHub (Dec 1, 2022): What happens if you just use the default Ventoy options (run Ventoy2Disk.exe but do not change any options)? Are you using standard Windows 10 and 11 - Retail? Pro? any added software? Modified OS in any way? Can you think of how your Windows systems may be different from other peoples Windows systems?
Author
Owner

@rewritten1 commented on GitHub (Dec 17, 2022):

What happens if you just use the default Ventoy options (run Ventoy2Disk.exe but do not change any options)? Are you using standard Windows 10 and 11 - Retail? Pro? any added software? Modified OS in any way? Can you think of how your Windows systems may be different from other peoples Windows systems?

I just got a replacement USB drive from Corsair to finally test this. I left all the default options for Ventoy2Disk.exe using release 1.0.84 and it still hangs on insertion. This is what my Windows 11 File Explorer looks like when Windows is trying to read and mount the drive letter:
explorer_This_PC_tUE40XAzV5
It slowly fills up the gray bar with green until the mount operation times out. When it times out, the USB mounts the drive letter, F:, and I can save files to it normally. I can only reproduce this behavior when Ventoy2Disk.exe formats the drive.

  1. I am using Windows 11 Education, retail channel. Yes, there is a lot of added software on this installation. In terms of OS modification, the only thing I can think of is the DisplayFusion Pro 9.9 software that could modify OS files. However, I'm not entirely sure if it does or not.

  2. That's a good question. I have two monitors, wireless keyboard and mouse, 4 PCIe add-in cards, an nvme drive. I don't know, its nothing too crazy. I'm gonna install a clean installation of Windows 11, fully updated, with no third party software to see if I get the same behavior. I still need to try it on a different system other than mine. I won't be able to until we get closer to the end of this year.

Edit: Format logs.
log.txt

@rewritten1 commented on GitHub (Dec 17, 2022): > What happens if you just use the default Ventoy options (run Ventoy2Disk.exe but do not change any options)? Are you using standard Windows 10 and 11 - Retail? Pro? any added software? Modified OS in any way? Can you think of how your Windows systems may be different from other peoples Windows systems? I just got a replacement USB drive from Corsair to finally test this. I left all the default options for Ventoy2Disk.exe using release 1.0.84 and it still hangs on insertion. This is what my Windows 11 File Explorer looks like when Windows is trying to read and mount the drive letter: ![explorer_This_PC_tUE40XAzV5](https://user-images.githubusercontent.com/37819602/208278260-e7359207-d9d2-4da8-bf77-9a9eb05d2478.png) It slowly fills up the gray bar with green until the mount operation times out. When it times out, the USB mounts the drive letter, F:, and I can save files to it normally. I can only reproduce this behavior when Ventoy2Disk.exe formats the drive. 2. I am using Windows 11 Education, retail channel. Yes, there is a lot of added software on this installation. In terms of OS modification, the only thing I can think of is the DisplayFusion Pro 9.9 software that could modify OS files. However, I'm not entirely sure if it does or not. 3. That's a good question. I have two monitors, wireless keyboard and mouse, 4 PCIe add-in cards, an nvme drive. I don't know, its nothing too crazy. I'm gonna install a clean installation of Windows 11, fully updated, with no third party software to see if I get the same behavior. I still need to try it on a different system other than mine. I won't be able to until we get closer to the end of this year. Edit: Format logs. [log.txt](https://github.com/ventoy/Ventoy/files/10253098/log.txt)
Author
Owner

@ventoy commented on GitHub (Dec 17, 2022):

Try this CI release to see whether it behave differently:
https://github.com/ventoy/Ventoy/actions/runs/3720691355
https://www.ventoy.net/en/doc_github_ci.html

@ventoy commented on GitHub (Dec 17, 2022): Try this CI release to see whether it behave differently: https://github.com/ventoy/Ventoy/actions/runs/3720691355 https://www.ventoy.net/en/doc_github_ci.html
Author
Owner

@rewritten1 commented on GitHub (Dec 17, 2022):

Try this CI release to see whether it behave differently: https://github.com/ventoy/Ventoy/actions/runs/3720691355 https://www.ventoy.net/en/doc_github_ci.html

Tried the latest CI release and it still hangs on insertion.
log.txt

Also, I got two new error messages when trying to access the drive in File Explorer and Initialize the drive from Diskmgmt after Ventoy formatted the drive:
explorer_Location_is_not_available_0HGQ6Ai9J5

mmc_Virtual_Disk_Manager_4SG9xG48ec

@rewritten1 commented on GitHub (Dec 17, 2022): > Try this CI release to see whether it behave differently: https://github.com/ventoy/Ventoy/actions/runs/3720691355 https://www.ventoy.net/en/doc_github_ci.html Tried the latest CI release and it still hangs on insertion. [log.txt](https://github.com/ventoy/Ventoy/files/10253136/log.txt) Also, I got two new error messages when trying to access the drive in File Explorer and Initialize the drive from Diskmgmt after Ventoy formatted the drive: ![explorer_Location_is_not_available_0HGQ6Ai9J5](https://user-images.githubusercontent.com/37819602/208279894-5918dc02-6990-4cd9-9941-4f4a25b7e11d.png) ![mmc_Virtual_Disk_Manager_4SG9xG48ec](https://user-images.githubusercontent.com/37819602/208279902-5b3c34e7-ae95-4dbf-abd3-c1222a81a3f2.png)
Author
Owner

@ventoy commented on GitHub (Dec 17, 2022):

After install Ventoy, manually reformat the Ventoy partition again with Windows disk manager.

@ventoy commented on GitHub (Dec 17, 2022): After install Ventoy, manually reformat the Ventoy partition again with Windows disk manager.
Author
Owner

@rewritten1 commented on GitHub (Dec 17, 2022):

After install Ventoy, manually reformat the Ventoy partition again with Windows disk manager.

I performed a manually reformat immediately after ventoy install, unplugged and re-plugged the USB. However, the USB still stalls on insertion.

@rewritten1 commented on GitHub (Dec 17, 2022): > After install Ventoy, manually reformat the Ventoy partition again with Windows disk manager. I performed a manually reformat immediately after ventoy install, unplugged and re-plugged the USB. However, the USB still stalls on insertion.
Author
Owner

@ventoy commented on GitHub (Dec 17, 2022):

When install Ventoy, try reserve large amount of space, for example, reserve 200GB.

@ventoy commented on GitHub (Dec 17, 2022): When install Ventoy, try reserve large amount of space, for example, reserve 200GB.
Author
Owner

@rewritten1 commented on GitHub (Dec 17, 2022):

Logs: log.txt

image
Still, the USB drive has trouble mounting in a timely manner.

Also, here is a video representation of the issue I face (I only ever showed screenshots of the behavior): https://www.youtube.com/watch?v=TtZNdBrVGd0

@rewritten1 commented on GitHub (Dec 17, 2022): > Logs: [log.txt](https://github.com/ventoy/Ventoy/files/10253198/log.txt) ![image](https://user-images.githubusercontent.com/37819602/208281735-9dc3969d-7569-4286-8ef7-0212cb76556d.png) Still, the USB drive has trouble mounting in a timely manner. Also, here is a video representation of the issue I face (I only ever showed screenshots of the behavior): https://www.youtube.com/watch?v=TtZNdBrVGd0
Author
Owner

@steve6375 commented on GitHub (Dec 18, 2022):

Can you try a USB 2 port and all ports (front, rear, sides).
If you dont have a USB 2 port, connect the USB drive to a USB 3 port using a USB 2 extension cable.

@steve6375 commented on GitHub (Dec 18, 2022): Can you try a USB 2 port and all ports (front, rear, sides). If you dont have a USB 2 port, connect the USB drive to a USB 3 port using a USB 2 extension cable.
Author
Owner

@rewritten1 commented on GitHub (Dec 18, 2022):

Can you try a USB 2 port and all ports (front, rear, sides). If you dont have a USB 2 port, connect the USB drive to a USB 3 port using a USB 2 extension cable.

I have the ASUS PRIME Z690-P D4 motherboard in my system. I'm reviewing its manual and it says it has two USB 2 ports in the rear. I plugged in this USB drive into both and they make the USB drive appear immediately! I tried 8 times, 4 times each per USB 2 port, and each time it showed up in File Explorer right away.

Hmm, so if its my USB 3 ports that are causing it to hang, how should I go about fixing that?

@rewritten1 commented on GitHub (Dec 18, 2022): > Can you try a USB 2 port and all ports (front, rear, sides). If you dont have a USB 2 port, connect the USB drive to a USB 3 port using a USB 2 extension cable. I have the ASUS PRIME Z690-P D4 motherboard in my system. I'm reviewing its manual and it says it has two USB 2 ports in the rear. I plugged in this USB drive into both and they make the USB drive appear immediately! I tried 8 times, 4 times each per USB 2 port, and each time it showed up in File Explorer right away. Hmm, so if its my USB 3 ports that are causing it to hang, how should I go about fixing that?
Author
Owner

@steve6375 commented on GitHub (Dec 19, 2022):

Try ALL USB ports - there are also two USB 3 (blue) ports in the rear. Do they work?
Try using a USB 2 cable in the USB 3 port - USB 3 PORT - USB 2 CABLE - USB 3 DRIVE
You will need a USB 2 male-female cable. Again try ALL USB 2 and 3 ports.
If you find rear usb 3 ports work ok but front usb 3 ports don't work then could be:

  1. You are using wrong mainboard pcb header connection for the front port module
  2. There is a design flaw in front usb cable or module, perhaps grounding or shielding issue.
  3. You have another usb device connected to front usb module which is causing electrical interference with usb 3 flash drive. E.g. Bluetooth or WiFi or wireless mouse/kbd dongle. If so, connect the 'bad' device to a rear usb port instead of the front usb module.
@steve6375 commented on GitHub (Dec 19, 2022): Try ALL USB ports - there are also two USB 3 (blue) ports in the rear. Do they work? Try using a USB 2 cable in the USB 3 port - USB 3 PORT - USB 2 CABLE - USB 3 DRIVE You will need a USB 2 male-female cable. Again try ALL USB 2 and 3 ports. If you find rear usb 3 ports work ok but front usb 3 ports don't work then could be: 1. You are using wrong mainboard pcb header connection for the front port module 2. There is a design flaw in front usb cable or module, perhaps grounding or shielding issue. 3. You have another usb device connected to front usb module which is causing electrical interference with usb 3 flash drive. E.g. Bluetooth or WiFi or wireless mouse/kbd dongle. If so, connect the 'bad' device to a rear usb port instead of the front usb module.
Author
Owner

@rewritten1 commented on GitHub (Dec 19, 2022):

Try ALL USB ports - there are also two USB 3 (blue) ports in the rear. Do they work? Try using a USB 2 cable in the USB 3 port - USB 3 PORT - USB 2 CABLE - USB 3 DRIVE You will need a USB 2 male-female cable. Again try ALL USB 2 and 3 ports.

I was able to find a USB 2.0 male-female extension cable and plugged in my USB to it. I plugged the extended USB cable to every single USB port on my system (two Case USB 3.0 ports and two USB 2.0 ports, two USB 3.0 ports and the teal USB port all on the back of my motherboard.) For each insertion, I visually inspected the File Explorer GUI and watched for the Ventoy USB drive to appear. For all ports connected to using the USB 2.0 extension, the USB appeared in File Explorer GUI near instantly each time.

@rewritten1 commented on GitHub (Dec 19, 2022): > Try ALL USB ports - there are also two USB 3 (blue) ports in the rear. Do they work? Try using a USB 2 cable in the USB 3 port - USB 3 PORT - USB 2 CABLE - USB 3 DRIVE You will need a USB 2 male-female cable. Again try ALL USB 2 and 3 ports. I was able to find a USB 2.0 male-female extension cable and plugged in my USB to it. I plugged the extended USB cable to every single USB port on my system (two Case USB 3.0 ports and two USB 2.0 ports, two USB 3.0 ports and the teal USB port all on the back of my motherboard.) For each insertion, I visually inspected the File Explorer GUI and watched for the Ventoy USB drive to appear. For all ports connected to using the USB 2.0 extension, the USB appeared in File Explorer GUI near instantly each time.
Author
Owner

@steve6375 commented on GitHub (Dec 19, 2022):

Sure, but what about two rear usb 3 ports without a cable?

@steve6375 commented on GitHub (Dec 19, 2022): Sure, but what about two rear usb 3 ports without a cable?
Author
Owner

@rewritten1 commented on GitHub (Dec 19, 2022):

Sure, but what about two rear usb 3 ports without a cable?

Without the extension cable, my USB still hangs for minutes when I plug it into either USB 3.0 port at the rear of my motherboard.

@rewritten1 commented on GitHub (Dec 19, 2022): > Sure, but what about two rear usb 3 ports without a cable? Without the extension cable, my USB still hangs for minutes when I plug it into either USB 3.0 port at the rear of my motherboard.
Author
Owner

@steve6375 commented on GitHub (Dec 19, 2022):

That is surprising.
can you disconnect ALL other USB devices and try it again.
Even disconnect mouse and kbd if USB - you can still see how Explorer reacts.

@steve6375 commented on GitHub (Dec 19, 2022): That is surprising. can you disconnect ALL other USB devices and try it again. Even disconnect mouse and kbd if USB - you can still see how Explorer reacts.
Author
Owner

@rewritten1 commented on GitHub (Dec 19, 2022):

That is surprising. can you disconnect ALL other USB devices and try it again. Even disconnect mouse and kbd if USB - you can still see how Explorer reacts.

I disconnected all other USB devices from my system and tried my USB into both rear USB 3.0 ports again:

I still encounter the same insertion hang in File Explorer GUI.

@rewritten1 commented on GitHub (Dec 19, 2022): > That is surprising. can you disconnect ALL other USB devices and try it again. Even disconnect mouse and kbd if USB - you can still see how Explorer reacts. I disconnected all other USB devices from my system and tried my USB into both rear USB 3.0 ports again: <img src="https://user-images.githubusercontent.com/37819602/208468750-c68612b5-24de-4ae6-92df-27f58b41a719.png" width="50%" height="50%" /> <img src="https://user-images.githubusercontent.com/37819602/208469925-44ada6fc-2954-47d1-b77e-71e1beb94492.png" width="50%" height="50%" /> I still encounter the same insertion hang in File Explorer GUI.
Author
Owner

@steve6375 commented on GitHub (Dec 19, 2022):

That's very strange! Maybe it is a driver problem? Or possibly some strange software you have installed? Usb 3 works at rates approx 2.4megahz and other devices can interfere with it but the rear usb 3 ports should be electronically well designed. Maybe some other device is causing a problem like PCI cards?
Is your pc home built? Anything special about it? Cards, PSU, peripherals, ?

@steve6375 commented on GitHub (Dec 19, 2022): That's very strange! Maybe it is a driver problem? Or possibly some strange software you have installed? Usb 3 works at rates approx 2.4megahz and other devices can interfere with it but the rear usb 3 ports should be electronically well designed. Maybe some other device is causing a problem like PCI cards? Is your pc home built? Anything special about it? Cards, PSU, peripherals, ?
Author
Owner

@rewritten1 commented on GitHub (Dec 19, 2022):

That's very strange! Maybe it is a driver problem? Or possibly some strange software you have installed? Usb 3 works at rates approx 2.4megahz and other devices can interfere with it but the rear usb 3 ports should be electronically well designed. Maybe some other device is causing a problem like PCI cards? Is your pc home built? Anything special about it? Cards, PSU, peripherals, ?

Yes, this PC is home built. It has standard hardware installed into the slots and USB ports. Peripherals include:

  1. Logitech - ERGO M575 mouse
  2. Logitech K350 keyboard
  3. Logitech unifying receiver (for mouse and keyboard)
  4. AudioEngine A2+ USB speakers
  5. TP-Link UH720 USB hub
  6. Xbox Wireless Adapter USB dongle
  7. Rodecaster Pro 2 USB connection

The power supply is a Seasonic PRIME TX-1000 PSU.

These are the cards in my system as it relates to PCI cards/NVMe drives

  1. Seagate FireCuda 530 NVMe
  2. EVGA GeForce RTX 3090 FTW3 ULTRA GAMING add-in card
  3. Intel Optane P5800X add-in card
  4. ASUS PCE-AX58BT wireless add-in card
  5. Corsair Force MP600 NVMe
  6. Elgato 4k60 PRO MK.2 capture add-in card
  7. Crucial SSD in SATA port

In addition, here's a diagram of what slots they are installed into:
image

@rewritten1 commented on GitHub (Dec 19, 2022): > That's very strange! Maybe it is a driver problem? Or possibly some strange software you have installed? Usb 3 works at rates approx 2.4megahz and other devices can interfere with it but the rear usb 3 ports should be electronically well designed. Maybe some other device is causing a problem like PCI cards? Is your pc home built? Anything special about it? Cards, PSU, peripherals, ? Yes, this PC is home built. It has standard hardware installed into the slots and USB ports. Peripherals include: 1. Logitech - ERGO M575 mouse 2. Logitech K350 keyboard 3. Logitech unifying receiver (for mouse and keyboard) 4. AudioEngine A2+ USB speakers 5. TP-Link UH720 USB hub 6. Xbox Wireless Adapter USB dongle 7. Rodecaster Pro 2 USB connection The power supply is a Seasonic PRIME TX-1000 PSU. These are the cards in my system as it relates to PCI cards/NVMe drives 1. Seagate FireCuda 530 NVMe 2. EVGA GeForce RTX 3090 FTW3 ULTRA GAMING add-in card 3. Intel Optane P5800X add-in card 4. ASUS PCE-AX58BT wireless add-in card 5. Corsair Force MP600 NVMe 6. Elgato 4k60 PRO MK.2 capture add-in card 7. Crucial SSD in SATA port In addition, here's a diagram of what slots they are installed into: ![image](https://user-images.githubusercontent.com/37819602/208482261-edf7667f-94c5-4899-84a6-3cf683894838.png)
Author
Owner

@steve6375 commented on GitHub (Dec 19, 2022):

Well the USB peripherals are irrelevant since you disconnected ALL of them and still got the problem.

Do you have a USB 3 male to female USB extension cable - you could try that too because sometimes the braid/screening in a good quality USB 3 cable can absorb the high frequency interference on the ground and data lines on a USB 3 device and can fix a conducted rf noise issue.

It could be a driver issue - maybe Optane driver?
or ASUS PCE-AX58BT wireless add-in card may be causing a problem by generating electrical noise which is interfering with the USB 3 data I/O signals or ground..

Easiest thing to do is maybe just pull out the wireless card from the PCI slot - just as a test.
If that doesn't fix then maybe uninstall the Optane driver?

After that, you will have to remove all of the other peripherals.

I think this has to do with I/O data corruption at fast USB 3 speeds but I am not sure what it is caused by.

@steve6375 commented on GitHub (Dec 19, 2022): Well the USB peripherals are irrelevant since you disconnected ALL of them and still got the problem. Do you have a USB 3 male to female USB extension cable - you could try that too because sometimes the braid/screening in a good quality USB 3 cable can absorb the high frequency interference on the ground and data lines on a USB 3 device and can fix a conducted rf noise issue. It could be a driver issue - maybe Optane driver? or ASUS PCE-AX58BT wireless add-in card may be causing a problem by generating electrical noise which is interfering with the USB 3 data I/O signals or ground.. Easiest thing to do is maybe just pull out the wireless card from the PCI slot - just as a test. If that doesn't fix then maybe uninstall the Optane driver? After that, you will have to remove all of the other peripherals. I think this has to do with I/O data corruption at fast USB 3 speeds but I am not sure what it is caused by.
Author
Owner

@rewritten1 commented on GitHub (Dec 22, 2022):

Well the USB peripherals are irrelevant since you disconnected ALL of them and still got the problem.

Do you have a USB 3 male to female USB extension cable - you could try that too because sometimes the braid/screening in a good quality USB 3 cable can absorb the high frequency interference on the ground and data lines on a USB 3 device and can fix a conducted rf noise issue.

It could be a driver issue - maybe Optane driver? or ASUS PCE-AX58BT wireless add-in card may be causing a problem by generating electrical noise which is interfering with the USB 3 data I/O signals or ground..

Easiest thing to do is maybe just pull out the wireless card from the PCI slot - just as a test. If that doesn't fix then maybe uninstall the Optane driver?

After that, you will have to remove all of the other peripherals.

I think this has to do with I/O data corruption at fast USB 3 speeds but I am not sure what it is caused by.

I will give this a try and report my findings. In addition, I have another PC coming to me that is AMD-based to compare the behavior of what happens when I insert a Ventoy-formatted USB drive. I am going to have Windows 10 installed on the AMD PC, too, so I can compare if the OS version introduced a bug with my USB device.

@rewritten1 commented on GitHub (Dec 22, 2022): > Well the USB peripherals are irrelevant since you disconnected ALL of them and still got the problem. > > Do you have a USB 3 male to female USB extension cable - you could try that too because sometimes the braid/screening in a good quality USB 3 cable can absorb the high frequency interference on the ground and data lines on a USB 3 device and can fix a conducted rf noise issue. > > It could be a driver issue - maybe Optane driver? or ASUS PCE-AX58BT wireless add-in card may be causing a problem by generating electrical noise which is interfering with the USB 3 data I/O signals or ground.. > > Easiest thing to do is maybe just pull out the wireless card from the PCI slot - just as a test. If that doesn't fix then maybe uninstall the Optane driver? > > After that, you will have to remove all of the other peripherals. > > I think this has to do with I/O data corruption at fast USB 3 speeds but I am not sure what it is caused by. I will give this a try and report my findings. In addition, I have another PC coming to me that is AMD-based to compare the behavior of what happens when I insert a Ventoy-formatted USB drive. I am going to have Windows 10 installed on the AMD PC, too, so I can compare if the OS version introduced a bug with my USB device.
Author
Owner

@rewritten1 commented on GitHub (Dec 22, 2022):

Well the USB peripherals are irrelevant since you disconnected ALL of them and still got the problem.

Do you have a USB 3 male to female USB extension cable - you could try that too because sometimes the braid/screening in a good quality USB 3 cable can absorb the high frequency interference on the ground and data lines on a USB 3 device and can fix a conducted rf noise issue.

It could be a driver issue - maybe Optane driver? or ASUS PCE-AX58BT wireless add-in card may be causing a problem by generating electrical noise which is interfering with the USB 3 data I/O signals or ground..

Easiest thing to do is maybe just pull out the wireless card from the PCI slot - just as a test. If that doesn't fix then maybe uninstall the Optane driver?

After that, you will have to remove all of the other peripherals.

I think this has to do with I/O data corruption at fast USB 3 speeds but I am not sure what it is caused by.

While I wait for the PC to arrive, I went ahead and installed a new copy of Windows 10 64-bit Version 22H2 on the Corsair NVMe. I fully updated the Windows OS to the latest build version (Windows 10 22H2, OS Build 19045.2364) and tried my ventoy formatted USB again. Each time I inserted the Ventoy USB in this copy of Windows 10, it came up immediately in File Explorer, no delay or error.

Perhaps my issue is software related? I tried the USB in Safe Mode on my Windows 11 installation and it still exhibited the same behavior. I am not sure if perhaps my Windows 11 installation has some corruption somewhere for it to persist within Safe Mode. I will continue to try different combinations of configuration.

@rewritten1 commented on GitHub (Dec 22, 2022): > Well the USB peripherals are irrelevant since you disconnected ALL of them and still got the problem. > > Do you have a USB 3 male to female USB extension cable - you could try that too because sometimes the braid/screening in a good quality USB 3 cable can absorb the high frequency interference on the ground and data lines on a USB 3 device and can fix a conducted rf noise issue. > > It could be a driver issue - maybe Optane driver? or ASUS PCE-AX58BT wireless add-in card may be causing a problem by generating electrical noise which is interfering with the USB 3 data I/O signals or ground.. > > Easiest thing to do is maybe just pull out the wireless card from the PCI slot - just as a test. If that doesn't fix then maybe uninstall the Optane driver? > > After that, you will have to remove all of the other peripherals. > > I think this has to do with I/O data corruption at fast USB 3 speeds but I am not sure what it is caused by. While I wait for the PC to arrive, I went ahead and installed a new copy of Windows 10 64-bit Version 22H2 on the Corsair NVMe. I fully updated the Windows OS to the latest build version (Windows 10 22H2, OS Build 19045.2364) and tried my ventoy formatted USB again. Each time I inserted the Ventoy USB in this copy of Windows 10, it came up immediately in File Explorer, no delay or error. Perhaps my issue is software related? I tried the USB in Safe Mode on my Windows 11 installation and it still exhibited the same behavior. I am not sure if perhaps my Windows 11 installation has some corruption somewhere for it to persist within Safe Mode. I will continue to try different combinations of configuration.
Author
Owner

@ghost commented on GitHub (Dec 23, 2022):

Windows 11 22H2 has a bug where file transfer speeds are slower than they should be. Maybe that's causing the drive to take so long to show up? Either that, or you have some sort of driver issues.

@ghost commented on GitHub (Dec 23, 2022): Windows 11 22H2 has a bug where file transfer speeds are slower than they should be. Maybe that's causing the drive to take so long to show up? Either that, or you have some sort of driver issues.
Author
Owner

@ghost commented on GitHub (Dec 23, 2022):

I tried with a different generic USB that is not as large, 2GB in size, and I could not reproduce the stalling/hang problem in File Explorer. I tried another USB flash drive, a Sandisk Extreme Pro USB 3.0 128GB, and the stalling/hang problem in file explorer returned. Tested both USBs on another computer with Windows 10 instead of Windows 11, and they too had the same stalling/hang problem.

So far, I am experiencing this issue with large capacity USB drives on Windows. The small capacity USBs mount instantly in File Explorer after Ventoy has formatted them.

Interesting, so it persists even on 2 completely different PCs running different Windows versions. Maybe indexing is slowing Explorer down? Well, since the drive is empty after being formatted, then there's nothing there to index, so it can't be indexing. Have you tried accessing the drive through CMD/Powershell to see if it hangs there?

@ghost commented on GitHub (Dec 23, 2022): > I tried with a different generic USB that is not as large, 2GB in size, and I could not reproduce the stalling/hang problem in File Explorer. I tried another USB flash drive, a Sandisk Extreme Pro USB 3.0 128GB, and the stalling/hang problem in file explorer returned. Tested both USBs on another computer with Windows 10 instead of Windows 11, and they too had the same stalling/hang problem. > > So far, I am experiencing this issue with large capacity USB drives on Windows. The small capacity USBs mount instantly in File Explorer after Ventoy has formatted them. Interesting, so it persists even on 2 completely different PCs running different Windows versions. Maybe indexing is slowing Explorer down? Well, since the drive is empty after being formatted, then there's nothing there to index, so it can't be indexing. Have you tried accessing the drive through CMD/Powershell to see if it hangs there?
Author
Owner

@Sunrongguo2008 commented on GitHub (Dec 25, 2022):

Can you try to reproduce this problem on windows 10 system?

@Sunrongguo2008 commented on GitHub (Dec 25, 2022): Can you try to reproduce this problem on windows 10 system?
Author
Owner

@Sunrongguo2008 commented on GitHub (Dec 25, 2022):

My usb drive also had this problem in win 11, but in win 10, this problem doesn't happen anymore.

@Sunrongguo2008 commented on GitHub (Dec 25, 2022): My usb drive also had this problem in win 11, but in win 10, this problem doesn't happen anymore.
Author
Owner

@rewritten1 commented on GitHub (Dec 25, 2022):

Can you try to reproduce this problem on windows 10 system?

I installed a clean copy of Windows 10 22H2 and fully updated it and I could not reproduce the USB issue. I will test again on an AMD system with windows 11 sometime Jan next year.

I updated my optane driver, optane SSD firmware and the Intel rapid storage device driver to the latest. Still the same USB issue on my Intel windows 11 system.

@rewritten1 commented on GitHub (Dec 25, 2022): > Can you try to reproduce this problem on windows 10 system? I installed a clean copy of Windows 10 22H2 and fully updated it and I could not reproduce the USB issue. I will test again on an AMD system with windows 11 sometime Jan next year. I updated my optane driver, optane SSD firmware and the Intel rapid storage device driver to the latest. Still the same USB issue on my Intel windows 11 system.
Author
Owner

@rewritten1 commented on GitHub (Dec 25, 2022):

Windows 11 22H2 has a bug where file transfer speeds are slower than they should be. Maybe that's causing the drive to take so long to show up? Either that, or you have some sort of driver issues.

Drivers are up to date. I needed a new optane, nvme and Intel rapid storage driver. Still facing the issue on my Windows 11 computer. I will try reproducing this issue on a new AMD cpu computer and see if it happens there sometime in Jan.

@rewritten1 commented on GitHub (Dec 25, 2022): > Windows 11 22H2 has a bug where file transfer speeds are slower than they should be. Maybe that's causing the drive to take so long to show up? Either that, or you have some sort of driver issues. Drivers are up to date. I needed a new optane, nvme and Intel rapid storage driver. Still facing the issue on my Windows 11 computer. I will try reproducing this issue on a new AMD cpu computer and see if it happens there sometime in Jan.
Author
Owner

@rewritten1 commented on GitHub (Dec 30, 2022):

I'm really confused right now. After updating both the Intel NVMe and Rapid Storage drivers from the intel website, the problem with my USB hanging File Explorer now only happens once on each of the USB ports available on my computer. Then, on subsequent insertions to the same USB port, the USB shows up immediately in File Explorer with any issues. I want to say that the two driver installs managed to fix the issue I reported here, but, I'm not really sure. I'm unable to reproduce the problem again with my USB drive.

Really, really strange. But, at least its working for me now. Thank you everyone for your input!

@rewritten1 commented on GitHub (Dec 30, 2022): I'm really confused right now. After updating both the Intel NVMe and Rapid Storage drivers from the intel website, the problem with my USB hanging File Explorer now only happens once on each of the USB ports available on my computer. Then, on subsequent insertions to the _same_ USB port, the USB shows up immediately in File Explorer with any issues. I want to say that the two driver installs managed to fix the issue I reported here, but, I'm not really sure. I'm unable to reproduce the problem again with my USB drive. Really, really strange. But, at least its working for me now. Thank you everyone for your input!
Author
Owner

@jianboss1991 commented on GitHub (Feb 2, 2023):

U盘安装完 Ventoy 以后,插到系统中识别非常慢,复现问题

Ventoy Version
1.0.88

BIOS Mode
UEFI Mode

Partition Style
GPT

Disk Capacity
128GB

Disk Manufacturer
thinkplus TU100 Pro

PC1:9400F+ASUS主板
PC2:thinkpad X1 Extreme Gen 3 (CPU:10885H)

估计是:USB Attached SCSI 设备+USB3.0+WIN11 的BUG

48f31d7772f14fcd71a5dbfafa543a5

@jianboss1991 commented on GitHub (Feb 2, 2023): U盘安装完 Ventoy 以后,插到系统中识别非常慢,复现问题 Ventoy Version 1.0.88 BIOS Mode UEFI Mode Partition Style GPT Disk Capacity 128GB Disk Manufacturer thinkplus TU100 Pro PC1:9400F+ASUS主板 PC2:thinkpad X1 Extreme Gen 3 (CPU:10885H) 估计是:USB Attached SCSI 设备+USB3.0+WIN11 的BUG ![48f31d7772f14fcd71a5dbfafa543a5](https://user-images.githubusercontent.com/49179272/216246119-dae9beff-d1db-425e-b12c-5b65785a46cc.png)
Author
Owner

@Sunrongguo2008 commented on GitHub (Feb 2, 2023):

U盘安装完 Ventoy 以后,插到系统中识别非常慢,复现问题

Ventoy Version 1.0.88

BIOS Mode UEFI Mode

Partition Style GPT

Disk Capacity 128GB

Disk Manufacturer thinkplus TU100 Pro

PC1:9400F+ASUS主板 PC2:thinkpad X1 Extreme Gen 3 (CPU:10885H)

估计是:USB Attached SCSI 设备+USB3.0+WIN11 的BUG

48f31d7772f14fcd71a5dbfafa543a5

和我一样型号的U盘,一样的系统(win11),一样的问题
我多次格式化了此U盘(低格和高格),最后,这个BUG奇迹般地消失了

@Sunrongguo2008 commented on GitHub (Feb 2, 2023): > U盘安装完 Ventoy 以后,插到系统中识别非常慢,复现问题 > > Ventoy Version 1.0.88 > > BIOS Mode UEFI Mode > > Partition Style GPT > > Disk Capacity 128GB > > Disk Manufacturer thinkplus TU100 Pro > > PC1:9400F+ASUS主板 PC2:thinkpad X1 Extreme Gen 3 (CPU:10885H) > > 估计是:USB Attached SCSI 设备+USB3.0+WIN11 的BUG > > ![48f31d7772f14fcd71a5dbfafa543a5](https://user-images.githubusercontent.com/49179272/216246119-dae9beff-d1db-425e-b12c-5b65785a46cc.png) 和我一样型号的U盘,一样的系统(win11),一样的问题 我多次格式化了此U盘(低格和高格),最后,这个BUG奇迹般地消失了
Author
Owner

@Aleksards commented on GitHub (Feb 10, 2023):

Unfortunately, I have the same problem as described above. Windows 11 22H2, USB SSD Transcedent 480GB, Ventoy 1.0.88. When connected to USB on different PCs (2 laptops and 1 desktop PC), the drive is detected for a very long time. Windows 11 installed a clean Pro version, without third-party software. Without Ventoy, there are no problems with the drive.

When connecting a drive with Ventoy to a computer with Windows 10 22H2, the problem is not observed.
Sorry for my english, google translate.

@Aleksards commented on GitHub (Feb 10, 2023): Unfortunately, I have the same problem as described above. Windows 11 22H2, USB SSD Transcedent 480GB, Ventoy 1.0.88. When connected to USB on different PCs (2 laptops and 1 desktop PC), the drive is detected for a very long time. Windows 11 installed a clean Pro version, without third-party software. Without Ventoy, there are no problems with the drive. When connecting a drive with Ventoy to a computer with Windows 10 22H2, the problem is not observed. Sorry for my english, google translate.
Author
Owner

@rewritten1 commented on GitHub (Feb 10, 2023):

I spoke too soon. Now, the USB behavior is back to doing the same thing in my first post. It seems there is something that Windows doesn't like about USB with multiple partitions. Which is wildly strange because for the past two months, I wasn't running into this issue. I don't know what changed. Immediately after formatting the USBs I am testing with to be single partition, all of these mount delays and error messages go away.

@rewritten1 commented on GitHub (Feb 10, 2023): I spoke too soon. Now, the USB behavior is back to doing the same thing in my first post. It seems there is something that Windows doesn't like about USB with multiple partitions. Which is wildly strange because for the past two months, I wasn't running into this issue. I don't know what changed. Immediately after formatting the USBs I am testing with to be single partition, all of these mount delays and error messages go away.
Author
Owner

@steve6375 commented on GitHub (Feb 10, 2023):

The usual reason is you are using a fake capacity usb drive which has no memory in the last half of the drive.

@steve6375 commented on GitHub (Feb 10, 2023): The usual reason is you are using a fake capacity usb drive which has no memory in the last half of the drive.
Author
Owner

@rewritten1 commented on GitHub (Feb 10, 2023):

And if the USB is not one with a fake capacity, do you think the problem that @AleksanderS faced with Ventoy on a clean installation of Windows 11 without third-party software mean maybe Microsoft shares part in the blame of why the USB drives are taking forever to detect? Perhaps it isn't an issue that Ventoy is introducing at all. I thought the intel rapid storage drivers would keep my issue with it resolved but it ended up returning :/

@rewritten1 commented on GitHub (Feb 10, 2023): And if the USB is not one with a fake capacity, do you think the problem that @AleksanderS faced with Ventoy on a clean installation of Windows 11 without third-party software mean maybe Microsoft shares part in the blame of why the USB drives are taking forever to detect? Perhaps it isn't an issue that Ventoy is introducing at all. I thought the intel rapid storage drivers would keep my issue with it resolved but it ended up returning :/
Author
Owner

@steve6375 commented on GitHub (Feb 10, 2023):

It depends on the storage driver. Most windows storage drivers have very long timeouts and multiple retries on errors. So if there was a read error on any sector, it often takes ages to timeout and report an error to the calling code.
If the partition 2 at the very end of the usb drive cannot be accessed then you can expect problems. Ventoy always creates a small partition at the very end of the drive, some other products don't.

@steve6375 commented on GitHub (Feb 10, 2023): It depends on the storage driver. Most windows storage drivers have very long timeouts and multiple retries on errors. So if there was a read error on any sector, it often takes ages to timeout and report an error to the calling code. If the partition 2 at the very end of the usb drive cannot be accessed then you can expect problems. Ventoy always creates a small partition at the very end of the drive, some other products don't.
Author
Owner

@Aleksards commented on GitHub (Feb 10, 2023):

My USB drive is not "Chinese", the capacity is checked and tested. Model SSD USB 3.1 480GB Transcend (TS480GESD240C).
Made a BackUP of the driver "USB_Attached_SCSI_(UAS)_Mass_Storage_Device) from Windows 10. Tomorrow I'll try to install Windows 11 and "slip" the driver from Windows 10

@Aleksards commented on GitHub (Feb 10, 2023): My USB drive is not "Chinese", the capacity is checked and tested. Model SSD USB 3.1 480GB Transcend (TS480GESD240C). Made a BackUP of the driver "USB_Attached_SCSI_(UAS)_Mass_Storage_Device) from Windows 10. Tomorrow I'll try to install Windows 11 and "slip" the driver from Windows 10
Author
Owner

@steve6375 commented on GitHub (Feb 10, 2023):

Why not just test the drive? Run FakeFlashTest.exe or h2testw.exe or use windows to create an NTFS partition 1 and an NTFS partition 2 in the last 1gb. Then copy video files to partition 2 to fill it and then try to play them.

@steve6375 commented on GitHub (Feb 10, 2023): Why not just test the drive? Run FakeFlashTest.exe or h2testw.exe or use windows to create an NTFS partition 1 and an NTFS partition 2 in the last 1gb. Then copy video files to partition 2 to fill it and then try to play them.
Author
Owner

@Aleksards commented on GitHub (Feb 10, 2023):

USB drive tested FakeFlashTest.exe or h2testw.exe. The question is that in Windows 10 everything works fine, but in Win 11 when connected, the definition is very long. And yes, the problem is most likely in windows, and not ventoy. You can leave everything as it is, but sometimes you need to urgently connect a flash drive and transfer data, but you have to wait a couple of minutes until the flash drive is detected by the system. Whether the drive is empty or not doesn't matter.
I'll continue testing tomorrow :)

@Aleksards commented on GitHub (Feb 10, 2023): USB drive tested FakeFlashTest.exe or h2testw.exe. The question is that in Windows 10 everything works fine, but in Win 11 when connected, the definition is very long. And yes, the problem is most likely in windows, and not ventoy. You can leave everything as it is, but sometimes you need to urgently connect a flash drive and transfer data, but you have to wait a couple of minutes until the flash drive is detected by the system. Whether the drive is empty or not doesn't matter. I'll continue testing tomorrow :)
Author
Owner

@ekszz commented on GitHub (Jul 7, 2023):

This is likely to be caused by a firmware bug in the bridge chip of the USB driver.
When the bridge chip of the solid-state USB disk (such as Lenovo TU100 Pro) or mobile hard disk box you use is ASMedia (such as ASM235CM, ASM225CM, ASM1153E, etc.), some old versions (such as 171120_D1_1E_80.bin) of the firmware will cause the USB driver with multiple partitions to be recognized very slowly under WIN11. Even timed out.
Try to upgrade to a different version of the firmware to solve it. I tried the firmware version 210830_D1_00_00.bin on the ASM235CM chip, and the problem completely disappeared.
There are many leaked firmware and mass production tool on the Internet. Try it :)

@ekszz commented on GitHub (Jul 7, 2023): This is likely to be caused by a firmware bug in the bridge chip of the USB driver. When the bridge chip of the solid-state USB disk (such as Lenovo TU100 Pro) or mobile hard disk box you use is ASMedia (such as ASM235CM, ASM225CM, ASM1153E, etc.), some old versions (such as 171120_D1_1E_80.bin) of the firmware will cause the USB driver with multiple partitions to be recognized very slowly under WIN11. Even timed out. Try to upgrade to a different version of the firmware to solve it. I tried the firmware version 210830_D1_00_00.bin on the ASM235CM chip, and the problem completely disappeared. There are many leaked firmware and mass production tool on the Internet. Try it :)
Author
Owner

@Aleksards commented on GitHub (Jul 8, 2023):

This is likely to be caused by a firmware bug in the bridge chip of the USB driver. When the bridge chip of the solid-state USB disk (such as Lenovo TU100 Pro) or mobile hard disk box you use is ASMedia (such as ASM235CM, ASM225CM, ASM1153E, etc.), some old versions (such as 171120_D1_1E_80.bin) of the firmware will cause the USB driver with multiple partitions to be recognized very slowly under WIN11. Even timed out. Try to upgrade to a different version of the firmware to solve it. I tried the firmware version 210830_D1_00_00.bin on the ASM235CM chip, and the problem completely disappeared. There are many leaked firmware and mass production tool on the Internet. Try it :)

Thanks for the info.
I flashed asm235cm with version 210830_D1_00_00, the disk detection worked. The activity indicator also works.

@Aleksards commented on GitHub (Jul 8, 2023): > This is likely to be caused by a firmware bug in the bridge chip of the USB driver. When the bridge chip of the solid-state USB disk (such as Lenovo TU100 Pro) or mobile hard disk box you use is ASMedia (such as ASM235CM, ASM225CM, ASM1153E, etc.), some old versions (such as 171120_D1_1E_80.bin) of the firmware will cause the USB driver with multiple partitions to be recognized very slowly under WIN11. Even timed out. Try to upgrade to a different version of the firmware to solve it. I tried the firmware version 210830_D1_00_00.bin on the ASM235CM chip, and the problem completely disappeared. There are many leaked firmware and mass production tool on the Internet. Try it :) Thanks for the info. I flashed asm235cm with version 210830_D1_00_00, the disk detection worked. The activity indicator also works.
Author
Owner

@yrzd6 commented on GitHub (Sep 9, 2023):

Oh, I had the same problem with my ventoy on Windows 7, when I inserted my USB drive, Explorer showed that it was hanging.

@yrzd6 commented on GitHub (Sep 9, 2023): Oh, I had the same problem with my ventoy on Windows 7, when I inserted my USB drive, Explorer showed that it was hanging.
Author
Owner

@yrzd6 commented on GitHub (Sep 9, 2023):

I formatted my USB drive, and it was fine! It's confusing.

@yrzd6 commented on GitHub (Sep 9, 2023): I formatted my USB drive, and it was fine! It's confusing.
Author
Owner

@wgetnz commented on GitHub (Oct 3, 2023):

My usb drive also had this problem in win 11, but in win 10, this problem doesn't happen anymore.

@wgetnz commented on GitHub (Oct 3, 2023): My usb drive also had this problem in win 11, but in win 10, this problem doesn't happen anymore.
Author
Owner

@GitSak commented on GitHub (Oct 30, 2023):

The same problem.
I have three different original Samsung portavle SSDs, and I use them with various laptops and computers every day. On almost every computer, Windows 10/11 takes a very long time to detect the SSD. Even when using a hub with an additional power supply, which easily powers a 3.5" HDD. As a temporary solution, I have to restart PC. The issue only occurs after Ventoy( Ventoy2Disk.exe ) formats the drive. When there's only one partition on the disk, or format any other soft, there are no problems. The Ventoy version is the latest.

@GitSak commented on GitHub (Oct 30, 2023): The same problem. I have three different original Samsung portavle SSDs, and I use them with various laptops and computers every day. On almost every computer, Windows 10/11 takes a very long time to detect the SSD. Even when using a hub with an additional power supply, which easily powers a 3.5" HDD. As a temporary solution, I have to restart PC. The issue only occurs after Ventoy( Ventoy2Disk.exe ) formats the drive. When there's only one partition on the disk, or format any other soft, there are no problems. The Ventoy version is the latest.
Author
Owner

@rewritten1 commented on GitHub (Oct 31, 2023):

The issue definitely feels like its caused by the USB bridge chip in some USB thumb drives like the one in my Corsair GTX. I did not feel comfortable updating the firmware on the Corsair GTX, so, I ended up purchasing a newer USB drive, the OWC Envoy Pro Mini USB-C + USB-A, that uses a completely different USB bridge chip. All of the problems I was facing with the Corsair GTX USB have completely disappeared since switching to the OWC Envoy Pro Mini USB drive. Some weird behavior in Windows when working with USB drives with multiple partitions is causing it to hang.

@rewritten1 commented on GitHub (Oct 31, 2023): The issue definitely feels like its caused by the USB bridge chip in some USB thumb drives like the one in my Corsair GTX. I did not feel comfortable updating the firmware on the Corsair GTX, so, I ended up purchasing a newer USB drive, the OWC Envoy Pro Mini USB-C + USB-A, that uses a completely different USB bridge chip. All of the problems I was facing with the Corsair GTX USB have completely disappeared since switching to the OWC Envoy Pro Mini USB drive. Some weird behavior in Windows when working with USB drives with multiple partitions is causing it to hang.
Author
Owner

@GitSak commented on GitHub (Oct 31, 2023):

Personally, I don't use flash drives; only portable SSD or regular 2.5-inch drives in an enclosure. I encounter an issue, most often with Windows 11, after formatting Ventoy. Interestingly, it's recognized perfectly fine in the BIOS, and LiveCD loads without any problems. The issues occur specifically after booting Windows in the standard way.

@GitSak commented on GitHub (Oct 31, 2023): Personally, I don't use flash drives; only portable SSD or regular 2.5-inch drives in an enclosure. I encounter an issue, most often with Windows 11, after formatting Ventoy. Interestingly, it's recognized perfectly fine in the BIOS, and LiveCD loads without any problems. The issues occur specifically after booting Windows in the standard way.
Author
Owner

@steve6375 commented on GitHub (Oct 31, 2023):

There are two 'types' of drive which Windows recognises. It is simply determined by one bit in the identify data which is returned by the controller firmware of a mass storage device, it is called the RMB or Removable Media Bit. It is intended to tell an OS whether the device is a Removable drive (i.e. can be unplugged by the user easily) or non-removable (e.g. permanently attached such as an internal hard disk). Windows treats these two types differently (esp. Disk Manager). There was a big change after the 1st year of Windows 10 release when removable media could have more than one partition on the drive, before that Windows would not create a multiple-partition removable drive (unless sectors were written directly by a 3rd party partition/format program).
Many GTX USB flash drives have the RMB bit reset = fixed media, whereas most other flash drives report as a removable drive. So when dealing with Windows, you need to know what version of Windows you have and what type of drive you have (removable or non-removable).
Also, the treatment of removable media flash drives by Windows (esp. Disk Manager and Explorer) is still buggy in Win 10 (don't know about win 11) so you need to be very careful if you have a removable USB drive and it has more than one partition (as Ventoy drives do) because Windows/Explorer/Disk Manager can do strange things and even lie to you!
RMPrepUSB.exe will tell you which type the device is or you could use diskpart.

In addition, the 2nd partition created by Ventoy is an EFI boot partition and Explorer may or may not show this partition/mount it/give it a volume drive letter depending on what version of Windows it is, what type of drive it is and what is in the registry for that drive and the volumes on that drive.

@steve6375 commented on GitHub (Oct 31, 2023): There are two 'types' of drive which Windows recognises. It is simply determined by one bit in the identify data which is returned by the controller firmware of a mass storage device, it is called the RMB or Removable Media Bit. It is intended to tell an OS whether the device is a Removable drive (i.e. can be unplugged by the user easily) or non-removable (e.g. permanently attached such as an internal hard disk). Windows treats these two types differently (esp. Disk Manager). There was a big change after the 1st year of Windows 10 release when removable media could have more than one partition on the drive, before that Windows would not create a multiple-partition removable drive (unless sectors were written directly by a 3rd party partition/format program). Many GTX USB flash drives have the RMB bit reset = fixed media, whereas most other flash drives report as a removable drive. So when dealing with Windows, you need to know what version of Windows you have and what type of drive you have (removable or non-removable). Also, the treatment of removable media flash drives by Windows (esp. Disk Manager and Explorer) is still buggy in Win 10 (don't know about win 11) so you need to be very careful if you have a removable USB drive and it has more than one partition (as Ventoy drives do) because Windows/Explorer/Disk Manager can do strange things and even lie to you! RMPrepUSB.exe will tell you which type the device is or you could use diskpart. In addition, the 2nd partition created by Ventoy is an EFI boot partition and Explorer may or may not show this partition/mount it/give it a volume drive letter depending on what version of Windows it is, what type of drive it is and what is in the registry for that drive and the volumes on that drive.
Author
Owner

@GitSak commented on GitHub (Oct 31, 2023):

It's interesting that PC reboot resolves the issue. After rebooting, portable removable SSD is recognized without any problems. Moreover, if the flash drive takes a long time to be detected before the PC restart, and you initiate the restart at that moment, the computer won't perform the task until the device will be detected. This can take quite a while, so you have to unplug and plug it back in immediately after the restart.

@GitSak commented on GitHub (Oct 31, 2023): It's interesting that PC reboot resolves the issue. After rebooting, portable removable SSD is recognized without any problems. Moreover, if the flash drive takes a long time to be detected before the PC restart, and you initiate the restart at that moment, the computer won't perform the task until the device will be detected. This can take quite a while, so you have to unplug and plug it back in immediately after the restart.
Author
Owner

@wgetnz commented on GitHub (Oct 31, 2023):

Anyone have a solution? I don't have this problem on Windows 10 1909 or before

@wgetnz commented on GitHub (Oct 31, 2023): Anyone have a solution? I don't have this problem on Windows 10 1909 or before
Author
Owner

@thedag commented on GitHub (Nov 17, 2023):

I had the exact same problem right now, on a Dell Precision laptop with Windows 11 23H2. I used Ventoy on another Win11 box to create the drive, but had a bunch of ISOs on another laptop that I just wanted to throw in there, and only the VTOYEFI partition got mapped to a drive by Windows.

But in my case when I opened up diskmgmt.msc both partitions on the drive were shown correctly. The VENTOY one first, with exFAT, and the small EFI partition (32 MB) with FAT as the second, exactly how it's supposed to be.

All I had to do was right-click the VENTOY partition and assign a drive letter to it. A file explorer instance was even opened up for me when I did that... (typical Microsoft way, I really think they should stop guessing what users want to do, even if for once they guessed right, but I digress).

Perhaps it'll behave the same way the next time around, IDK, but it was a very easy fix at least. And it seems to me, given that the drive looks to be as it's supposed to be, that this is more likely a Windows issue than a Ventoy one... although realistically, if they want to fix the broken user experience, they are going to have to work around the problems Microsoft create for them... :)

@thedag commented on GitHub (Nov 17, 2023): I had the exact same problem right now, on a Dell Precision laptop with Windows 11 23H2. I used Ventoy on another Win11 box to create the drive, but had a bunch of ISOs on another laptop that I just wanted to throw in there, and only the VTOYEFI partition got mapped to a drive by Windows. But in my case when I opened up `diskmgmt.msc` both partitions on the drive were shown correctly. The VENTOY one first, with exFAT, and the small EFI partition (32 MB) with FAT as the second, exactly how it's supposed to be. All I had to do was right-click the VENTOY partition and assign a drive letter to it. A file explorer instance was even opened up for me when I did that... (typical Microsoft way, I really think they should stop guessing what users want to do, even if for once they guessed right, but I digress). Perhaps it'll behave the same way the next time around, IDK, but it was a very easy fix at least. And it seems to me, given that the drive looks to be as it's supposed to be, that this is more likely a Windows issue than a Ventoy one... although realistically, if they want to fix the broken user experience, they are going to have to work around the problems Microsoft create for them... :)
Author
Owner

@wgetnz commented on GitHub (Mar 13, 2024):

I successfully solved my problem. It is indeed caused by the ASM235CM firmware. I will upload my firmware, but this does not apply to the hardware used. Please use it with caution. I am not responsible for the problems caused.
ASM235CM220906固件.zip

@wgetnz commented on GitHub (Mar 13, 2024): I successfully solved my problem. It is indeed caused by the ASM235CM firmware. I will upload my firmware, but this does not apply to the hardware used. Please use it with caution. I am not responsible for the problems caused. [ASM235CM220906固件.zip](https://github.com/ventoy/Ventoy/files/14588103/ASM235CM220906.zip)
Author
Owner

@rewritten1 commented on GitHub (Mar 13, 2024):

I successfully solved my problem. It is indeed caused by the ASM235CM firmware. I will upload my firmware, but this does not apply to the hardware used. Please use it with caution. I am not responsible for the problems caused. ASM235CM220906固件.zip

Thanks! Could you post the links to the flasher tool and instructions you used to perform the flash operation?

@rewritten1 commented on GitHub (Mar 13, 2024): > I successfully solved my problem. It is indeed caused by the ASM235CM firmware. I will upload my firmware, but this does not apply to the hardware used. Please use it with caution. I am not responsible for the problems caused. [ASM235CM220906固件.zip](https://github.com/ventoy/Ventoy/files/14588103/ASM235CM220906.zip) Thanks! Could you post the links to the flasher tool and instructions you used to perform the flash operation?
Author
Owner

@neonWOP commented on GitHub (Mar 14, 2024):

Hello all

It was very interesting to read this.
I had similar problems over the years with windows and usb drives/devices, especially when a high number of devices plugged in to the same port('s). For many years i used devmanpro to manually, every 3 to 6 month, remove "grey" devices in device manager.

But there is a much simpler way to do this.

DriveCleanup
Device Cleanup Tool
https://www.uwe-sieber.de/drivetools.html

I assume windows registry is "overfilled" with usb devices so that after a number of times pluggin in it stucks.. at least thats my way of explenation.

greetings from vienna
wop

@neonWOP commented on GitHub (Mar 14, 2024): Hello all It was very interesting to read this. I had similar problems over the years with windows and usb drives/devices, especially when a high number of devices plugged in to the same port('s). For many years i used devmanpro to manually, every 3 to 6 month, remove "grey" devices in device manager. But there is a much simpler way to do this. DriveCleanup Device Cleanup Tool https://www.uwe-sieber.de/drivetools.html I assume windows registry is "overfilled" with usb devices so that after a number of times pluggin in it stucks.. at least thats my way of explenation. greetings from vienna wop
Author
Owner

@Tom4tot commented on GitHub (Jun 12, 2024):

Just to add another fix for me: I had to manally add a letter to my USB with the Disk Management utility from Windows
Screenshot  2589

@Tom4tot commented on GitHub (Jun 12, 2024): Just to add another fix for me: I had to manally add a letter to my USB with the Disk Management utility from Windows ![Screenshot 2589](https://github.com/ventoy/Ventoy/assets/32274750/0c1474a2-a098-405b-81c7-9afe6f637343)
Author
Owner

@runishiwo commented on GitHub (Apr 9, 2025):

我也出现了相同的问题,win10是直接识别的,win11就加载很慢,后来根据别人说的将EFI分区ID改为42隐藏后问题解决了,不过移动硬盘会被识别为动态硬盘。

@runishiwo commented on GitHub (Apr 9, 2025): 我也出现了相同的问题,win10是直接识别的,win11就加载很慢,后来根据别人说的将EFI分区ID改为42隐藏后问题解决了,不过移动硬盘会被识别为动态硬盘。
Author
Owner

@yangbohz commented on GitHub (May 21, 2025):

我也出现了相同的问题,win10是直接识别的,win11就加载很慢,后来根据别人说的将EFI分区ID改为42隐藏后问题解决了,不过移动硬盘会被识别为动态硬盘。

我也是有相同的问题,但是同样的USB移动硬盘,里面有更多的大文件,没有这个问题,是否ventoy的分区存在某种bug?

@yangbohz commented on GitHub (May 21, 2025): > 我也出现了相同的问题,win10是直接识别的,win11就加载很慢,后来根据别人说的将EFI分区ID改为42隐藏后问题解决了,不过移动硬盘会被识别为动态硬盘。 我也是有相同的问题,但是同样的USB移动硬盘,里面有更多的大文件,没有这个问题,是否ventoy的分区存在某种bug?
Author
Owner

@DriveTHUNDER commented on GitHub (Aug 16, 2025):

Assign a letter to the ventoy drive through disk manager. worked for me

@DriveTHUNDER commented on GitHub (Aug 16, 2025): Assign a letter to the ventoy drive through disk manager. worked for me
Author
Owner

@gpshonik commented on GitHub (Aug 20, 2025):

Had the same exact issues as described by the OP. I purchased some enclosures based on the ASM325CM chipset and the ventoy boot ssd drives no longer have any detection delays or issues in Windows 11.

@gpshonik commented on GitHub (Aug 20, 2025): Had the same exact issues as described by the OP. I purchased some enclosures based on the ASM325CM chipset and the ventoy boot ssd drives no longer have any detection delays or issues in Windows 11.
Author
Owner

@zjy2931 commented on GitHub (Sep 8, 2025):

Had the same exact issues as described by the OP. I purchased some enclosures based on the ASM325CM chipset and the ventoy boot ssd drives no longer have any detection delays or issues in Windows 11.

Can it only be solved by updating the motherboard? This is also too costly

@zjy2931 commented on GitHub (Sep 8, 2025): > Had the same exact issues as described by the OP. I purchased some enclosures based on the ASM325CM chipset and the ventoy boot ssd drives no longer have any detection delays or issues in Windows 11. Can it only be solved by updating the motherboard? This is also too costly
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Ventoy-ventoy#1593
No description provided.