Hello, I wanted to install VENTOY2DISK to set up Medicat on a SanDisk USB drive, but at the end of the installation, I received an error message and the USB drive is no longer visible on the PC. After a reboot, the USB drive icon appears but doesn't open. Please help me find a solution to: 1 - restore the USB drive to a usable state 2 - how to install ventoy2disk without getting an error at the end of the installation. 3 - The current state of this USB drive does not even allow it to be formatted anymore.

Unable to install ventoy2disk on USB drive : CCM

Réponse 1 / 13

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035

Hi,

Without the exact error message, I can't understand the problem with Ventoy.

Erase it with Active@ KillDisk Freeware.

http://killdisk.com/killdisk-freeware.htm

(You will find it in the start menu after installation.)

Then try Ventoy again.

Or format it with HP USB Disk Storage Format Tool.

satronicx Posted messages 694 Status Membre 3

Thank you for the response,
I just tried some attempts, but the problem remains the same since I don't have access to the USB key either to format it or to use KillDisk, but it is visible in KillDisk but not on the desktop except for the icon. As for your question "Without the exact error message," the problem is that the installation starts out fine but ends with an error message and the key disappears from the desktop.

Réponse 2 / 13

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035

What is the message from KillDisk when you choose "Erase"

Note: You must write ERASE-ALL-DATA

Réponse 3 / 13

satronicx Posted messages 694 Status Membre 3

On the desktop, the USB key icon is still present, with KillDisk stating 'device is not ready'.

Réponse 4 / 13

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035

Create a log by right-clicking in the ChipGenius window

> Paste here

Get the latest version at the bottom here:

https://www.usbdev.ru/files/chipgenius/

You can extract it with 7-Zip, but first, disable your antivirus.

The password is provided as password = usbdev.ru

Satronicx

Thank you
The ChipGenius software is in Chinese, I can manage to decipher it for manipulation, if you have a link in English that would be great.

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035 > Satronicx

It's not Chinese, it's Russian

No need for a decipherer, just click on the link to download ChipGenius v4.20.1107 (2020-11-07)

If I give you another link in English, you won't have the latest version

https://www.softpedia.com/get/System/System-Info/ChipGenius.shtml

satronicx Posted messages 694 Status Membre 3 > fabul Posted messages 42099 Registration date Status Modérateur Last intervention

The Russian software but the interface in Chinese; I don't dare to manipulate it without knowing what I'm doing.

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035 > satronicx Posted messages 694 Status Membre

Just right-click. Ok

Paste here

Réponse 5 / 13

Satronicx

Hello,
Last night I did another attempt with killdisk following your instructions, I managed to erase the USB key and it indeed worked, I did the installation of ventoy again from the beginning, but there was an error at the end of the installation as I mentioned at the very start of my post.

Réponse 6 / 13

Youri

Hello
I already made a USB key unreadable on Windows by accidentally loading a file larger than the key onto it!

Once upon a time, Medicat in 2012 created a 4.7 GB DVD
a 16 GB USB key in 2014
Later it fit on a 32 GB key for 20.8 GB with 6 7zip files
https://gbatemp.net/threads/medicat-usb-a-multiboot-linux-usb-for-pc-repair.361577/

In early 2020, a tutorial for a 32 GB key but we see 60 GB of .Bin files
with 9 7zip files in the tutorial images? We must not forget a compression step and be wary of the actual capacity of the key after formatting then

https://www.malekal.com/medicat-creer-une-cle-usb-de-secours-et-de-depannage/

(Those who help us discover these software and take the time to create image tutorials are often volunteers and have they tested the latest version 2021 on a 32 GB USB key or larger?)

I don't know how many GB it is now but after adding software, it will end up requiring a 64 GB or 128 GB USB?

I add that you want to use Ventoy which allows you to add ISOs to the key in large numbers... welcome USB disk!

Satronicx

Thank you for your comments. Indeed, I want to install Medicat (I don't have the volume in front of me) which is currently around 25 GB, on a 32 GB USB key. The problem I'm facing right now is the difficulty in installing Ventoy2Disk. I've tried the process several times, and each time it fails; I can't say why. After each failure, it's a whole acrobatic effort to reset the key to its original state, which takes a lot of time. If you have a solution, I would be delighted.

satronicx Posted messages 694 Status Membre 3 > Satronicx

Good evening,
I am still waiting to find a solution to my problem, a solution to install VENTOY2DISK. Every attempt ends with an error. No matter what I do, I always end up with this error.

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035 > satronicx Posted messages 694 Status Membre

What does the log.txt say?

satronicx Posted messages 694 Status Membre 3 > fabul Posted messages 42099 Registration date Status Modérateur Last intervention

Hello,
Honestly, I haven't seen the log, and I can't see it at the moment, knowing that if I re-install Ventoy again to use the software, it takes a lot of time to reinitialize my USB drive, at least 4 hours with KillDisk erase. It's already been done at least 6 or 7 times, and it's discouraging to have to redo it after each failed installation.

Réponse 7 / 13

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035

Tell me the brand and size of your USB stick, and do this please.

https://forums.commentcamarche.net/forum/affich-37237622-impossible-d-installer-ventoy2disk-sur-cle-usb#5

Satronicx

The Sandisk 32 GB USB drive

satronicx Posted messages 694 Status Membre 3 > Satronicx

I am following up on Fabul's question. Thank you first of all for your support. I did not understand the right-click in ChipGenius with the following message "flash memory information is sent to the clipboard," which I did not understand. Are there any other methods besides VENTOY, for example Rufus, and how to proceed? I have other tests this time with another 30GB USB key from Kingston, and it is the same as the SanDisk key.

Okay, I understood the right-click. Here are the details: Kingston USB key
Description: [F:] USB Mass Storage Device (Generic Flash-Disk)
Device Type: Mass Storage Device

Protocol Version: USB 2.00
Current Speed: High Speed
Max Current: 500 mA

USB Device ID: VID = 1908 PID = 1320
Serial Number: 0111216867

Device Vendor: Generic
Device Name: Mass Storage
Device Revision: 0001

Manufacturer: Generic
Product Model: Flash Disk
Product Revision: 1.08

Controller Vendor: BW

SanDisk USB key
Description: [F:] USB Mass Storage Device (Generic Flash-Disk)
Device Type: Mass Storage Device

Protocol Version: USB 2.00
Current Speed: High Speed
Max Current: 500 mA

USB Device ID: VID = 1908 PID = 1320
Serial Number: 0111213411

Device Vendor: Generic
Device Name: Mass Storage
Device Revision: 0001

Manufacturer: Generic
Product Model: Flash Disk
Product Revision: 1.08

Controller Vendor: BW

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035 > satronicx Posted messages 694 Status Membre

When he writes flash memory information is sent to the clipboard

You just have to paste it in your next message,

It's in the clipboard, so > Paste

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035 > fabul Posted messages 42099 Registration date Status Modérateur Last intervention

It may be your Ventoy file that is corrupted

You can re-download it here:

https://github.com/ventoy/Ventoy/releases

No other program does what it does.

satronicx Posted messages 694 Status Membre 3 > fabul Posted messages 42099 Registration date Status Modérateur Last intervention

I downloaded Ventoy from the link you kindly provided me, I tried the 32GB Kingston USB key, the problem remains the same. I have however retrieved the log, which is as follows:

[2021/06/06 01:11:40.767]
################################ Ventoy2Disk 1.0.0.2 ################################
[2021/06/06 01:11:40.768] Control Flag: 0 1 1
[2021/06/06 01:11:40.804] Windows Version : Windows 10 64-bit (Build 18363)
[2021/06/06 01:11:40.856]
===================== Enum All PhyDrives =====================
[2021/06/06 01:11:40.865] RegOpenKeyExA <SYSTEM\CurrentControlSet\Services\disk\Enum> Ret:0
[2021/06/06 01:11:40.887] RegQueryValueExA <Count> ret:0 Size:4 Value:4
[2021/06/06 01:11:40.910] GetPhysicalDriveCount: 4
[2021/06/06 01:11:40.928] Logical Drives: 0x3fc
[2021/06/06 01:11:40.938] LogicalDrive:\\.\C: PhyDrive:1 Offset:1048576 ExtentLength:392570747904
[2021/06/06 01:11:40.958] C --> 1
[2021/06/06 01:11:40.968] LogicalDrive:\\.\D: PhyDrive:0 Offset:1048576 ExtentLength:320069787648
[2021/06/06 01:11:40.978] D --> 0
[2021/06/06 01:11:40.987] LogicalDrive:\\.\E: PhyDrive:1 Offset:392572174336 ExtentLength:107534614528
[2021/06/06 01:11:40.996] E --> 1
[2021/06/06 01:11:41.037] LogicalDrive:\\.\F: PhyDrive:3 Offset:0 ExtentLength:31981568000
[2021/06/06 01:11:41.045] F --> 3
[2021/06/06 01:11:41.068] LogicalDrive:\\.\G: PhyDrive:2 Offset:1048576 ExtentLength:527561654272
[2021/06/06 01:11:41.084] G --> 2
[2021/06/06 01:11:41.095] LogicalDrive:\\.\H: PhyDrive:2 Offset:527562702848 ExtentLength:832598704128
[2021/06/06 01:11:41.104] H --> 2
[2021/06/06 01:11:41.115] LogicalDrive:\\.\I: PhyDrive:2 Offset:1360161406976 ExtentLength:838860800000
[2021/06/06 01:11:41.125] I --> 2
[2021/06/06 01:11:41.136] LogicalDrive:\\.\J: PhyDrive:2 Offset:2199045316608 ExtentLength:801536311296
[2021/06/06 01:11:41.146] J --> 2
[2021/06/06 01:11:41.159] Create file Handle:0000013C \\.\PhysicalDrive0 status:0
[2021/06/06 01:11:43.070] PHYSICALDRIVE0 size 320072933376 bytes
[2021/06/06 01:11:43.076] Create file Handle:0000013C \\.\PhysicalDrive1 status:0
[2021/06/06 01:11:43.097] PHYSICALDRIVE1 size 500107862016 bytes
[2021/06/06 01:11:43.216] Create file Handle:0000013C \\.\PhysicalDrive2 status:0
[2021/06/06 01:11:43.218] PHYSICALDRIVE2 size 3000592977920 bytes
[2021/06/06 01:11:43.255] Create file Handle:0000019C \\.\PhysicalDrive3 status:0
[2021/06/06 01:11:43.306] PHYSICALDRIVE3 size 31981568000 bytes
[2021/06/06 01:11:43.318] PhyDrv:0 BusType:SATA Removable:0 Size:320GB(320072933376) Name: ST9320325AS
[2021/06/06 01:11:43.326] PhyDrv:1 BusType:SATA Removable:0 Size:512GB(500107862016) Name: ST500LM012 HN-M500MBB
[2021/06/06 01:11:43.336] PhyDrv:2 BusType:USB Removable:0 Size:3000GB(3000592977920) Name:Seagate Expansion Desk
[2021/06/06 01:11:43.345] PhyDrv:3 BusType:USB Removable:1 Size:32GB(31981568000) Name:Generic Flash-Disk
[2021/06/06 01:11:43.356] LogicalDrive:\\.\C: PhyDrive:1 Offset:1048576 ExtentLength:392570747904
[2021/06/06 01:11:43.365] Logical Drive:C ===> PhyDrive:1
[2021/06/06 01:11:43.374] LogicalDrive:\\.\D: PhyDrive:0 Offset:1048576 ExtentLength:320069787648
[2021/06/06 01:11:43.412] Logical Drive:D ===> PhyDrive:0
[2021/06/06 01:11:43.437] LogicalDrive:\\.\E: PhyDrive:1 Offset:392572174336 ExtentLength:107534614528
[2021/06/06 01:11:43.451] Logical Drive:E ===> PhyDrive:1
[2021/06/06 01:11:43.466] LogicalDrive:\\.\F: PhyDrive:3 Offset:0 ExtentLength:31981568000
[2021/06/06 01:11:43.475] Logical Drive:F ===> PhyDrive:3
[2021/06/06 01:11:43.497] LogicalDrive:\\.\G: PhyDrive:2 Offset:1048576 ExtentLength:527561654272
[2021/06/06 01:11:43.506] Logical Drive:G ===> PhyDrive:2
[2021/06/06 01:11:43.520] LogicalDrive:\\.\H: PhyDrive:2 Offset:527562702848 ExtentLength:832598704128
[2021/06/06 01:11:43.522] Logical Drive:H ===> PhyDrive:2
[2021/06/06 01:11:43.533] LogicalDrive:\\.\I: PhyDrive:2 Offset:1360161406976 ExtentLength:838860800000
[2021/06/06 01:11:43.542] Logical Drive:I ===> PhyDrive:2
[2021/06/06 01:11:43.552] LogicalDrive:\\.\J: PhyDrive:2 Offset:2199045316608 ExtentLength:801536311296
[2021/06/06 01:11:43.561] Logical Drive:J ===> PhyDrive:2
[2021/06/06 01:11:43.575] Create file Handle:00000198 \\.\PhysicalDrive3 status:0
[2021/06/06 01:11:43.613] Read MBR Ret:1 Size:512 code:183
[2021/06/06 01:11:43.630] =========== Partition Table 1 ============
[2021/06/06 01:11:43.639] PartTbl.Active = 0x65
[2021/06/06 01:11:43.649] PartTbl.FsFlag = 0x7a
[2021/06/06 01:11:43.670] PartTbl.StartSectorId = 1869881445
[2021/06/06 01:11:43.680] PartTbl.SectorCount = 1701340021
[2021/06/06 01:11:43.690] PartTbl.StartHead = 115
[2021/06/06 01:11:43.699] PartTbl.StartSector = 51
[2021/06/06 01:11:43.710] PartTbl.StartCylinder = 405
[2021/06/06 01:11:43.719] PartTbl.EndHead = 32
[2021/06/06 01:11:43.729] PartTbl.EndSector = 53
[2021/06/06 01:11:43.739] PartTbl.EndCylinder = 441
[2021/06/06 01:11:43.749] =========== Partition Table 2 ============
[2021/06/06 01:11:43.759] PartTbl.Active = 0x20
[2021/06/06 01:11:43.769] PartTbl.FsFlag = 0x72
[2021/06/06 01:11:43.778] PartTbl.StartSectorId = 1634566756
[2021/06/06 01:11:43.788] PartTbl.SectorCount = 1919251058
[2021/06/06 01:11:43.797] PartTbl.StartHead = 112
[2021/06/06 01:11:43.807] PartTbl.StartSector = 47
[2021/06/06 01:11:43.818] PartTbl.StartCylinder = 469
[2021/06/06 01:11:43.818] PartTbl.EndHead = 32
[2021/06/06 01:11:43.838] PartTbl.EndSector = 50
[2021/06/06 01:11:43.848] PartTbl.EndCylinder = 405
[2021/06/06 01:11:43.858] =========== Partition Table 3 ============
[2021/06/06 01:11:43.868] PartTbl.Active = 0xd
[2021/06/06 01:11:43.878] PartTbl.FsFlag = 0x0
[2021/06/06 01:11:43.887] PartTbl.StartSectorId = 0
[2021/06/06 01:11:43.897] PartTbl.SectorCount = 0
[2021/06/06 01:11:43.907] PartTbl.StartHead = 10
[2021/06/06 01:11:43.916] PartTbl.StartSector = 0
[2021/06/06 01:11:43.926] PartTbl.StartCylinder = 0
[2021/06/06 01:11:43.936] PartTbl.EndHead = 0
[2021/06/06 01:11:43.945] PartTbl.EndSector = 0
[2021/06/06 01:11:43.955] PartTbl.EndCylinder = 0
[2021/06/06 01:11:43.964] =========== Partition Table 4 ============
[2021/06/06 01:11:43.977] PartTbl.Active = 0x0
[2021/06/06 01:11:43.987] PartTbl.FsFlag = 0x0
[2021/06/06 01:11:43.997] PartTbl.StartSectorId = 28049408
[2021/06/06 01:11:44.006] PartTbl.SectorCount = 442
[2021/06/06 01:11:44.016] PartTbl.StartHead = 0
[2021/06/06 01:11:44.025] PartTbl.StartSector = 0
[2021/06/06 01:11:44.035] PartTbl.StartCylinder = 0
[2021/06/06 01:11:44.045] PartTbl.EndHead = 0
[2021/06/06 01:11:44.055] PartTbl.EndSector = 0
[2021/06/06 01:11:44.069] PartTbl.EndCylinder = 0
[2021/06/06 01:11:44.083] Part1 not match 1869881445
[2021/06/06 01:11:44.095] Create file Handle:00000198 \\.\PhysicalDrive2 status:0
[2021/06/06 01:11:44.115] Read MBR Ret:0 Size:0 code:87
[2021/06/06 01:11:44.117] < ST9320325AS> is filtered for not USB type.
[2021/06/06 01:11:44.120] < ST500LM012 HN-M500MBB> is filtered for not USB type.
[2021/06/06 01:11:44.469] Load languages from json file ...
[2021/06/06 01:11:44.632] language json file len:124378 json parse:0
[2021/06/06 01:11:44.637] Total 37 languages ...
[2021/06/06 01:11:45.335] Not ventoy disk, clear secure boot option
[2021/06/06 01:11:52.596] SpaceMB:0 SizeInMB:30500
[2021/06/06 01:11:52.602] InstallVentoy2PhyDrive MBR PhyDrive3 <<Generic Flash-Disk 32GB>>
[2021/06/06 01:11:52.696] Copy boot img success
[2021/06/06 01:11:52.697] Disk signature: 0x7f9742ce
[2021/06/06 01:11:52.707] ReservedSector: 0
[2021/06/06 01:11:52.717] Lock disk for clean .............................
[2021/06/06 01:11:52.720] QueryDosDeviceA success \Device\Harddisk3\DR17
[2021/06/06 01:11:52.734] [0] CreateFileA \\.\PhysicalDrive3 code:0 000002DC
[2021/06/06 01:11:52.794] FSCTL_LOCK_VOLUME success
[2021/06/06 01:11:52.799] LogicalDrive:\\.\C: PhyDrive:1 Offset:1048576 ExtentLength:392570747904
[2021/06/06 01:11:52.809] LogicalDrive:\\.\D: PhyDrive:0 Offset:1048576 ExtentLength:320069787648
[2021/06/06 01:11:52.820] LogicalDrive:\\.\E: PhyDrive:1 Offset:392572174336 ExtentLength:107534614528
[2021/06/06 01:11:52.831] LogicalDrive:\\.\F: PhyDrive:3 Offset:0 ExtentLength:31981568000
[2021/06/06 01:11:52.841] F: is belong to phydrive3
[2021/06/06 01:11:52.855] LogicalDrive:\\.\G: PhyDrive:2 Offset:1048576 ExtentLength:527561654272
[2021/06/06 01:11:52.949] LogicalDrive:\\.\H: PhyDrive:2 Offset:527562702848 ExtentLength:832598704128
[2021/06/06 01:11:52.976] LogicalDrive:\\.\I: PhyDrive:2 Offset:1360161406976 ExtentLength:838860800000
[2021/06/06 01:11:52.992] LogicalDrive:\\.\J: PhyDrive:2 Offset:2199045316608 ExtentLength:801536311296
[2021/06/06 01:12:09.630] Deleting ALL partition(s) from disk '\\?\PhysicalDrive3':
[2021/06/06 01:12:09.631] * Partition 1 (offset: 0, size: 31981568000)
[2021/06/06 01:12:09.661] Could not delete partitions: 2147942450
[2021/06/06 01:12:09.661] Deleting all partitions ......................... OK
[2021/06/06 01:12:09.673] Lock disk for write .............................
[2021/06/06 01:12:09.683] QueryDosDeviceA success \Device\Harddisk3\DR17
[2021/06/06 01:12:09.780] [0] CreateFileA \\.\PhysicalDrive3 code:0 00000358
[2021/06/06 01:12:09.781] Opened \\.\PhysicalDrive3 for exclusive write access
[2021/06/06 01:12:09.797] FSCTL_LOCK_VOLUME success
[2021/06/06 01:12:09.809] Formatting part1 exFAT ...
[2021/06/06 01:12:09.817] Formatting Part1 exFAT ...
[2021/06/06 01:12:09.840] WriteFile error bRet:0 WriteSize:4608 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.847] WriteFile error bRet:0 WriteSize:121856 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.857] WriteFile error bRet:0 WriteSize:3899904 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.869] WriteFile error bRet:0 WriteSize:32768 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.879] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.889] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.899] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.908] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.918] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.928] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.938] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.948] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.958] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.969] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.979] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:09.989] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:10.000] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:10.010] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:10.020] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:10.030] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:10.040] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:10.050] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:10.059] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:10.069] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:10.079] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:10.089] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:10.098] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:10.108] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2021/06/06 01:12:10.119] Formatting Part1 exFAT success
[2021/06/06 01:12:10.129] mount part 13
[2021/06/06 01:12:10.138] mount exfat failed 13
[2021/06/06 01:12:10.148] FormatPart1exFAT failed.
[2021/06/06 01:12:10.159] FindProcessOccupyDisk for PhyDrive 3
[2021/06/06 01:12:10.168] QueryDosDeviceA success \Device\Harddisk3\DR17
[2021/06/06 01:12:10.307] SearchProcess: NtQueryObject failed for handle 2E0 of process 9384: Unknown error 0xc000026e
[2021/06/06 01:12:10.359] NOTE: Could not identify the process(es) or service(s) accessing \Device\Harddisk3\DR17

Réponse 8 / 13

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035

It seems that there is a process that is causing an issue, an antivirus or automatic defragmenter, or another program?

If none of that, it's difficult.

If you tried running a chkdsk /f x: (x = drive letter of the USB) on the USB just beforehand, it might ask you if you want to unmount and say that the open descriptors would no longer be valid...

After that, Ventoy might have access to the USB.

Satronicx

No change with chkdisk.

Réponse 9 / 13

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035

It seems that your ChipGenius logs for SanDisk and Kingston are the same, just one in English and the other in French, but they are not different drives.

It says Generic.

Where did you buy them?

I'm worried that they might be fakes.

If in ChipGenius you can click on "Powerful detection" after the initial analysis, do it.

Then make sure to test one drive at a time.

If you have time, you can also format your drives and test them with H2testw to check their reliability.

Satronicx

Thank you for the comments,
For the logs, one is in French and the other in English because I used our friend Translate for the first one and not for the second. Unless I made a mistake on the same log, I will check. The Sandisk USB drive was purchased from Alibaba, the second one from the supermarket. Thank you for the link to the software to check the USB drive that I downloaded and ran; for the verification to be complete, it takes at least 5 hours. I will give you the report this evening.

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035 > Satronicx

I deleted the Ventoy log because it was too long and outdated.

Réponse 10 / 13

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035

What do the H2testw logs say about the two keys?

https://forums.commentcamarche.net/forum/affich-37237622-impossible-d-installer-ventoy2disk-sur-cle-usb#23

satronicx Posted messages 694 Status Membre 3

Here is the test you proposed, SanDisk USB drive

Warning: Only 30483 of 30484 MByte tested.
The media is likely to be defective.
464 MByte OK (950272 sectors)
29.3 GByte DATA LOST (61478912 sectors)
Details: 29.3 GByte overwritten (61478912 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
0 KByte corrupted (0 sectors)
8.5 MByte aliased memory (17536 sectors)
First error at offset: 0x000000001c770000
Expected: 0x000000001c770000
Found: 0x0000000039df0000
H2testw version 1.3
Writing speed: 3.42 MByte/s
Reading speed: 8.33 MByte/s
H2testw v1.4

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035 > satronicx Posted messages 694 Status Membre

It's not a real 32GB key, it's a 512MB fake, a counterfeit, a FAKE!!

According to my research, it takes one of these tools to restore its actual capacity:

https://www.usbdev.ru/files/appotech/buildwinmptool/

You can try to get a refund from the seller.

satronicx Posted messages 694 Status Membre 3 > satronicx Posted messages 694 Status Membre

Thank you for your reply,
What is this going to be useful for https://www.usbdev.ru/files/appotech/buildwinmptool/ besides that I tried to download the latest version but the download doesn't start.

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035 > satronicx Posted messages 694 Status Membre

The download starts with my Firefox.

I've already had interruptions; during that time, I click on the download, and it resumes.

It has a firmware that makes Windows believe it’s 32GB, but in reality, it’s only 512MB.

When you write to it, sometimes it works for a few MB, but then it's like a phantom capacity of memory that doesn't really exist, so you lose your data, thinking you copied it, but it’s copied nowhere.

There’s a chance that a tool like that could restore its actual capacity of 512MB, so no more files lost in the void.

satronicx Posted messages 694 Status Membre 3 > satronicx Posted messages 694 Status Membre

Hello;
another Kingston USB flash drive
Warning: Only 30483 of 30484 MBytes tested.
The media is likely to be defective.
103.8 MBytes OK (212736 sectors)
29.6 GBytes DATA LOST (62216448 sectors)
Details: 29.6 GBytes overwritten (62216320 sectors)
0 KBytes slightly changed (< 8 bit/sector, 0 sectors)
64 KBytes corrupted (128 sectors)
64 KBytes aliased memory (128 sectors)
First error at offset: 0x0000000006770000
Expected: 0x0000000006770000
Found: 0x00000007712f0000
H2testw version 1.3
Writing speed: 1.94 MByte/s
Reading speed: 7.16 MByte/s
H2testw v1.4

Réponse 11 / 13

Satronicx

Thank you for your valuable advice, I never believed things happened this way, it's good to know, there's manipulation everywhere.
I am waiting for your response regarding my second USB drive from a different brand that I just sent.

Réponse 12 / 13

Youri

Hello
>Well spotted regarding the fake keys sold on the web and your amazing solutions, thanks.

>There was indeed a bug in the latest Medicat version that was uploaded.
Scheduled to be set to gpt by default for UEFI, it seems to only work for bios mbr.

>Ventoy also had trouble installing from Windows but installed fine from Linux (on another forum around the same time as you, Satronics)

>This person was able to start testing in mbr on a Macbook pro on Monday:

" ...your latest Medicat v21.05 copied on MBR partition (that is the only way your other project Medicat VHD is working as instructed). From within the BIOS menu, almost everything I placed on the drive, mostly ISO's, is working flawlessly, but none of them from within the UEFI menu (menus start with no problems, show the packages but after launching, a black screen appears with the freezing gray black cursor and no further activity). The former versions 21.01 and 21.03 have worked with no problems. Would it be due to the GPT switch from MBR? Even your latest Mini Windows 10 iso is not launching under UEFI menu".

Satronicx

Thank you for the support,
I am on Windows 10 with MBR and not GPT,
So I am on the GPT version which is why it keeps bugging, is there another version of Medication
Thank you

Satronicx > Satronicx

I forgot to mention that you're talking about Medicat, but does flashing the USB key with Ventoy have anything to do with Medicat? So, before the injection of the program called Medicat.

Youri > Satronicx

Probably yes, a report because it's the same programmer who chooses the Medicat programs and created the program that flashes the key if I understand correctly. He who sent the file with Ventoy included and the instructions for the whole procedure, with a very slow connection. We don't know if his file is corrupted or if there’s a bug or both. He communicates little.
Then the testers distribute the file on internet servers and // send him the results of their tests.
Sometimes they provide temporary solutions like here, the tester was able to make it work in mbr but doesn’t provide the steps. He says that older versions worked well but there were fewer programs.
Unfortunately, you arrived just when the latest version was put online and you are a tester whether you like it or not, which requires a bit more knowledge and a lot of patience.

Ventoy can be downloaded separately where Fabul indicated the link because it's a Linux distribution but you need to know how to install this distribution which seems innovative and therefore a bit special.

The installation method and then the use of the key is therefore dependent on Ventoy and the programmer who created the usage menus for the key that runs under Ventoy OS to access the programs contained in Medicat if I understand correctly.

An alternative to your Windows proposed is to install a Linux that can be Ventoy and under Linux install the key as indicated; according to the tutorial images, it's at the beginning of the installation that you must have chosen between GPT for UEFI or MBR. It’s not another version, it’s the latest version of Medicat and is supposed to work as well in UEFI as in MBR! Totally innovative.
For Linux, you would download the tar.gz file and see if it works better, and choose MBR for yourself since you want to.

Satronicx > Youri

Hello,
Thank you for all the effort you've put into my problem. I will do another test with another USB key; it will be the third one. I will keep you informed. Many thanks.

Satronicx

Hello and thank you very much,
Indeed, there was the USB key issue, I eventually bought another Sandisk key and did the Ventoy installation and it worked. To say, it's not normal that there are USB keys that you pay a lot for. So the problem was that key, my issue is therefore resolved. I learned a lot of things in this discussion, I sincerely thank all the participants for their advice.

Réponse 13 / 13

fabul Posted messages 42099 Registration date Status Modérateur Last intervention 6 035

Your Kingston drive seems to be a 128MB memory

You can run a ChipGenius to find the controller and the tool to flash it, just like the other one.

Unable to install ventoy2disk on USB drive

13 réponses

Epson printer prints unexpectedly

Texture issues in enshrouded

Announcement: online source code archive

Notice shows wr30 m

Search for a song in the series foudre

Help for programming came remote control

Windows 10 reset issues

Where is the house wii sport resort wii

Sms sfr "call me back" exists or not

Download games for ipod nano-chromatic