Ventoy Forums › Ventoy General Use —— Ventoy 使用交流 › Ventoy Discussion Forum v
Installation Fail

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
Installation Fail
AMindOfKhajiit Offline
Junior Member
**
Posts: 4
Threads: 1
Joined: Jun 2020
Reputation: 0
#1
06-10-2020, 03:18 PM (This post was last modified: 06-10-2020, 03:22 PM by AMindOfKhajiit.)
Hey guys  Smile 

Sorry in advance if my answer is already elsewhere, I'm new on this forum.
I downloaded ventoy and tried to install it on a standard 32GB usb key but the installation fail every time and tells me to plug the usb key back in and try again.

I have Windows 10 Family 1909 on a MSI GT60 2PE PC.
I can also send you the log file if-needed.

Thank you for your help.


AMindOfKhajiit.
Find
Reply
senchi Offline
Junior Member
**
Posts: 11
Threads: 1
Joined: Jun 2020
Reputation: 2
#2
06-10-2020, 09:19 PM
Hey,

Are you sure that this key is not counterfeit ? Because this problem happens a lot in fake usb keys...

you can test it with h2testw : https://www.heise.de/download/product/h2testw-50539

Regards.
Find
Reply
pckiller Offline
Junior Member
**
Posts: 1
Threads: 0
Joined: Jun 2020
Reputation: 0
#3
06-11-2020, 12:01 AM
I met the same problem.
My log file is as following:
[2020/06/11 07:52:45.295] G: is belong to phydrive2
[2020/06/11 07:52:45.295] Delete mountpoint G:\ ret:1 code:0
[2020/06/11 07:52:45.296] Will use 'G:' as volume mountpoint
[2020/06/11 07:52:45.406] Could not query VDS Disk Properties: 272149
[2020/06/11 07:52:45.407] Notice: Could not delete partitions: 183
[2020/06/11 07:52:45.407] Deleting all partitions ......................... OK
[2020/06/11 07:52:45.409] Lock disk for write .............................
[2020/06/11 07:52:45.410] QueryDosDeviceA success \Device\Harddisk2\DR20
[2020/06/11 07:52:45.411] [0] CreateFileA \\.\PhysicalDrive2 code:0 00000670
[2020/06/11 07:52:45.411] Opened \\.\PhysicalDrive2 for exclusive write access
[2020/06/11 07:52:45.415] FSCTL_LOCK_VOLUME success
[2020/06/11 07:52:45.419] Formatting part1 exFAT ...
[2020/06/11 07:52:45.420] Formatting Part1 exFAT ...
[2020/06/11 07:52:45.424] WriteFile error bRet:0 WriteSize:4608 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.428] WriteFile error bRet:0 WriteSize:59904 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.429] WriteFile error bRet:0 WriteSize:1903104 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.431] WriteFile error bRet:0 WriteSize:32768 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.432] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.432] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.433] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.433] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.433] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.434] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.434] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.434] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.435] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.435] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.436] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.436] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.436] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.437] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.437] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.438] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.438] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.438] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.439] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.439] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.440] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.440] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.440] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.441] WriteFile error bRet:0 WriteSize:512 dwSize:0 ErrCode:5
[2020/06/11 07:52:45.442] Formatting Part1 exFAT success
[2020/06/11 07:52:45.444] mount part 13
[2020/06/11 07:52:45.448] Writing part2 FAT img ...
[2020/06/11 07:52:45.448] FormatPart2Fat ...
[2020/06/11 07:52:45.451] Malloc whole img buffer success, now decompress ...
[2020/06/11 07:52:45.778] decompress finished success
[2020/06/11 07:52:45.779] VentoyProcSecureBoot 0 ...
[2020/06/11 07:52:45.779] Open ventoy efi file 00DDA158
[2020/06/11 07:52:45.780] ventoy efi file size 1277952 ...
[2020/06/11 07:52:45.782] Now delete all efi files ...
[2020/06/11 07:52:45.783] Open bootx64 efi file 00DDA59C
[2020/06/11 07:52:45.788] Write part data bRet:0 dwSize:0 code:5
[2020/06/11 07:52:45.793] Mounting Ventoy Partition .......................
[2020/06/11 07:52:46.795] LogicalDrive:\\.\C: PhyDrive:1 Offset:1048576 ExtentLength:256051917824
[2020/06/11 07:52:46.795] LogicalDrive:\\.\D: PhyDrive:0 Offset:1048576 ExtentLength:289916583936
[2020/06/11 07:52:46.795] LogicalDrive:\\.\E: PhyDrive:0 Offset:289918681088 ExtentLength:183971610624
[2020/06/11 07:52:46.796] Could not open the disk<\\.\F:>, error:433
[2020/06/11 07:52:46.796] Logical drive letter after write ventoy: <>
[2020/06/11 07:52:46.796] need to mount ventoy part1...
[2020/06/11 07:52:46.797] GetVentoyVolumeName PhyDrive 2 PartOffset:1048576
[2020/06/11 07:52:46.797] Find volume:\\?\Volume{4c9e6ccf-0000-0000-0000-100000000000}\
[2020/06/11 07:52:46.797] IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS bRet:1 code:0
[2020/06/11 07:52:46.798] NumberOfDiskExtents:1 DiskNumber:0
[2020/06/11 07:52:46.798] This volume DiskNumber:0 offset:1048576
[2020/06/11 07:52:46.798] Find volume:\\?\Volume{0be11683-0000-0000-0000-100000000000}\
[2020/06/11 07:52:46.799] IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS bRet:1 code:0
[2020/06/11 07:52:46.799] NumberOfDiskExtents:1 DiskNumber:1
[2020/06/11 07:52:46.799] This volume DiskNumber:1 offset:1048576
[2020/06/11 07:52:46.800] Find volume:\\?\Volume{5a6d816d-aab8-11ea-b068-00e04c50b733}\
[2020/06/11 07:52:46.800] IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS bRet:1 code:0
[2020/06/11 07:52:46.801] NumberOfDiskExtents:1 DiskNumber:2
[2020/06/11 07:52:46.801] This volume DiskNumber:2 offset:32256
[2020/06/11 07:52:46.801] Find volume:\\?\Volume{4c9e6ccf-0000-0000-0000-808043000000}\
[2020/06/11 07:52:46.802] IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS bRet:1 code:0
[2020/06/11 07:52:46.802] NumberOfDiskExtents:1 DiskNumber:0
[2020/06/11 07:52:46.803] This volume DiskNumber:0 offset:289918681088
[2020/06/11 07:52:46.803] Find volume:\\?\Volume{15a37c66-a594-11ea-b067-806e6f6e6963}\
[2020/06/11 07:52:46.804] GetVentoyVolumeName return 1168
[2020/06/11 07:52:46.804] Failed to find ventoy volume
[2020/06/11 07:52:46.804] OK

Finally the Udisk is still unchanged except deleting the driver name.
I have tried several udisks, none of them is successful.
Find
Reply
vmclark Offline
magLogVE
Posts: 16
Threads: 3
Joined: Jun 2020
#4
06-11-2020, 01:37 AM
(06-10-2020, 09:19 PM)senchi Wrote: Hey,

Are you sure that this key is not counterfeit ? Because this problem happens a lot in fake usb keys...

you can test it with h2testw : https://www.heise.de/download/product/h2testw-50539

Regards.
That link is not English. What is this "key" you mentioned? I saw it somewhere else but can't find reference.
Find
Reply
AMindOfKhajiit Offline
Junior Member
**
Posts: 4
Threads: 1
Joined: Jun 2020
Reputation: 0
#5
06-11-2020, 12:06 PM
Hey Guys.
Thanks for the answers.

I tested my USB flash drive but the software didn't find any errors, I'm still looking.

I also noticed that after the ventoy installation failed, the usb key doesn't appear anymore in the file explorer and in the disk manager, the disk appears as "unallocated".

I'll keep looking.
Find
Reply
KaMyKaSii Offline
Junior Member
**
Posts: 39
Threads: 3
Joined: May 2020
Reputation: 5
#6
06-11-2020, 01:43 PM
Windows is problematic. Install some live Linux (like Lubuntu) on a smaller USB stick, boot it and use the Ventoy sh script to install Ventoy on your best USB stick
Find
Reply
AMindOfKhajiit Offline
Junior Member
**
Posts: 4
Threads: 1
Joined: Jun 2020
Reputation: 0
#7
06-11-2020, 01:57 PM
(06-11-2020, 01:43 PM)KaMyKaSii Wrote: Windows is problematic. Install some live Linux (like Lubuntu) on a smaller USB stick, boot it and use the Ventoy sh script to install Ventoy on your best USB stick
Can I try to install ventoy on a shared usb key via a virtual machine or it won't work ?
Find
Reply
KaMyKaSii Offline
Junior Member
**
Posts: 39
Threads: 3
Joined: May 2020
Reputation: 5
#8
06-11-2020, 06:30 PM (This post was last modified: 06-11-2020, 06:32 PM by KaMyKaSii.)
(06-11-2020, 01:57 PM)AMindOfKhajiit Wrote:
(06-11-2020, 01:43 PM)KaMyKaSii Wrote: Windows is problematic. Install some live Linux (like Lubuntu) on a smaller USB stick, boot it and use the Ventoy sh script to install Ventoy on your best USB stick
Can I try to install ventoy on a shared usb key via a virtual machine or it won't work ?
As the OS that is managing the USB stick at a low level remains Windows, I think it will continue to have problems, but you can try it first
Find
Reply
AMindOfKhajiit Offline
Junior Member
**
Posts: 4
Threads: 1
Joined: Jun 2020
Reputation: 0
#9
06-22-2020, 10:43 AM
Hey guys,

I still haven't found the problem, which comes from my computer because I tried installing ventoy on another pc and this time it worked without too many problems. I really have no idea where it can come from.
Find
Reply
longpanda Offline
Administrator
*******
Posts: 1,358
Threads: 86
Joined: Apr 2020
Reputation: 133
#10
06-22-2020, 03:21 PM
From the log I see error code 5 (access denied). I always receive report about this.
There many reasons that will cause this error, for example anti-virus software, system protection...
So usually I will give some suggestions:
1. Temporarily close the antivirus software and retry Ventoy
2. Use some other tool to delete all the partitions in the USB and retry Ventoy
Find
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)