hello

About this discussion https://github.com/ventoy/Ventoy/issues/660


For me

......   For the libraray

----------- SCAN SUMMARY -----------
Known viruses: 8903510
Engine version: 0.102.4
Scanned directories: 11
Scanned files: 63
Infected files: 3
Data scanned: 15.27 MB
Data read: 4011.18 MB (ratio 0.00:1)
Time: 39.144 sec (0 m 39 s)
.......
clamscan -r ventoy-1.0.30 | grep Trojan
LibClamAV Warning: cli_scanxz: decompress file size exceeds limits - only scanning 27262976 bytes
/home/a/ventoy-1.0.30/tool/x86_64/xzcat: Unix.Trojan.Mirai-7640640-0 FOUND
/home/a/ventoy-1.0.30/tool/x86_64/hexdump: Unix.Trojan.Mirai-7640640-0 FOUND
/home/a/ventoy-1.0.30/tool/x86_64/ash: Unix.Trojan.Mirai-7640640-0 FOUND

and for the USB KEY
clamscan -r /mnt | grep Trojan
/mnt/ventoy/ventoy.cpio: Unix.Trojan.Mirai-7640640-0 FOUND




what to decide ?

ventoy-1.0.30 版本制作
配置选项  没勾选安全启动支持提示下图 安全引导

 用其他PE工具EasyU 制作U盘PE进入没提示 
想知道这个和其他工具制作的 区别。

Hello,
I have a total of 3 external hard drives:  2x 3,5" (2TB resp. 1TB) and 1x 2,5" (4TB). I use Ventoy 1.0.30.  On the two 3.5" hard drives I can install Ventoy normally. It doesn't matter whether I use the MBR or the GPT partition style.  I can boot from both hard drives without any problems.
When I install Ventoy on the 2.5" hard drive, I can only do it in GPT partition style (because MBR only supports hard drives up to 2TB). However, when I boot from this drive, I only get a black screen with "VT" in the upper left corner. is displayed.  I had the same problem with the old version 1.0.27, but then it was not "VT", but "GR". is displayed at boot time.  Why won't Ventoy boot from this hard drive ?

版主好
最近我在给联想y470p这款笔记本上使用ventoy，测试win7安装镜像和微PE的PE镜像时，会卡在windows LOGO位置，请问怎么解决？

30版本的不支持移动硬盘吗?  安装后无法启动  机器是DELLC6100

Attached Files

Thumbnail(s)
   

斑竹好

    因为一些安装需要使用legacy引导方式，采用1.0.30版本创建u盘引导，发现有些问题。目前发现的问题是使用8G容量以下可以进行引导
安装，超过该容量则无法进行引导和安装，不知道是不是小bug，具体的可以参考附件的一些测试说明和结果。
    附件内测试使用了1.0.20版本进行了对比，谢谢。

Attached Files

  ventoy test.docx (Size: 637.74 KB / Downloads: 11)

Does anybody has any DOS to successfully boot with Ventoy for updating BIOS/UEFI/Firmware etc.?

I have FreeDos.ima but this type of image is only supported by Grub4DOS and not supported by Ventoy.

Would be appreciated if someone could provide with some working type of image with DOS/FreeDOS/PCDos etc.

Thanks.

I have a PPKG file that I would like to have automatically detected during a windows 10 installation.

The current process is as follows:
Boot Windows 10 with Ventoy
When the OOBE screen comes up, we insert the USB stick with the PPKG file
Windows 10 completes its final configuration

What I would like to do:
Boot Windows 10 with Ventoy
Choose the PPKG file (or perhaps an autounattend.xml?)
Windows 10 installs/completes on its own

I know there is a plugin to do unattended installations, but I haven't found a way to "inject" the PPKG.

Any advice or direction is appreciated.

Hello

I want to use the persistence for ubuntu in version 20.04 installed in legacy mode.

I have tried a few times to make it work without success.

Today I updated to version v30. It still doesn't work in my context.

Here is the content of my persistence file.

Thank you very much for your cool tool! I switched to it entirely, meaning with the use of the Windows VHD Boot Plugin only VHDs reside on my hard disk's ventoy partition. This way I can separate my workspaces in a clean way. I like that very much!

Now, when a new windows version is released I would like to do a clean install to a new, empty VHD. So I did the following:

1) Inside my booted Windows VHD I start the "Disk Management" tool of Windows. There I create a new VHD on the ventoy partition, attach it and initialize it. Just an example picture which tool I mean:



2) In Rufus I choose "Windows To Go" and install the image to the VHD. Just an example picture:



3) After that image creation has completed I restart to Ventoy boot menu and choose the newly created VHD to boot.
3) Then it boots and Windows configures for the first start and everything seems fine.
4) However, after a minute it fails with the following error message:



Could anybody please give me advice on how to create a bootable VHD based on a regular Windows iso? Probably I am missing some important step here.


Greetings