The current KaOSx LiveDVD has been on 27 April 2022, but our formerly tested KaOSx was only at 2020, please update once to be up to date

Good morning,

i have an m.2 with 2 tb and reserved additional storage space when installing ventoy 1.0.73.

Unfortunately, I found out that I can't update to version 1.0.74 because the button is grayed out.

in a test with a usb stick and no reserved memory, i can update to 1.0.74 without any problems.



attached is a section of the log file.

hello
There is a problem with the software
Version 1.0.74
I get the error not a secure boot platform 14
The computer is Lenovo
Thanks

Hello everyone, I specify that I do not know English and I wrote in Italian and then use an automatic translator, so if you find written things not understandable have patience and ask for clarification.

I have a problem with the installation of Ventoy on Windows 10 Enterprise.

I had a version just above 1.0.50, since it had recently I clicked on the "Update" button, the result was that ventoy stopped working.

I picked up Ventoy 1.0.72 and installed it from scratch, which doesn't even install.
I thought that, as sometimes happens, some software versions come out that have problems and I waited for the next version, but this one doesn't install either.

I found an old version, 1.0.18, in my pc, I try to install it and.... IT INSTALLS, too bad it doesn't work, I send Ventoy to hell.

After a while I see that 1.0.74 has been released and I try with this, failure confirmed.

I start to investigate, and in the log file I find an "Error 5" message.
I search on the net and I find some things that, for me that I am less than a software expert, are not very understandable.
In an answer, however, I find a feasible thing "first of all try to disable the antivirus" (I use the Windows one), I try it and Ventoy installs!

Could someone please explain to me why Ventoy used to install and now it doesn't anymore, unless I disable the antivirus?

Thank you.

VENTOY最新版1.0.74
ISO文件1为爱快官网最新的3.6.3正式版（也使用过旧版3.5的ISO文件）
ISO文件2为qnap_install | 胡瓜网盘 (misi.fun)里面的 Ox_install_UEFI_BIOS.iso 文件[url=http://j.misi.fun:5007/1/main/qnap_install][/url]

使用的机器是蜗牛C款双网口机器
现象：
ISO文件1：
使用rufus将ISO文件写进U盘就能正常启动安装（同一台机器，不变动任何硬件）
早期版本的VENTOY启动能正常安装爱快的3.5（某个版本之前的VENTOY版本。不太能确定是哪个版本后不能正常安装，以前是使用VENTOY在同一台机子上是能正常安装爱快的）
现在的VENTOY版本启动用安装爱快ISO（3.6.3或3.5早期ISO)不能正常启动ISO（表现为机器重启或提示错误的引导什么的，英文不好不太懂）


ISO文件2：
这是制作黑QNAP引导盘的ISO文件
同样使用上面的机器，
使用rufus将ISO写U盘，U盘启动，登陆后(用户名和密码均为admin),屏幕上方会显示包含tc和admin字眼的信息，能正常使用教程里面的指令
使用ventoy启动ISO文件，同样的操作登陆后，屏幕上方不会显示包含tc和admin字眼的信息，不能使用教程里面的指令

向管理员反映

Original Windows 10 21H2 ISOs do not work in UEFI mode(secure boot disabled), if they are based on the uncompressed install.wim. This includes updated ISOs from MSDN(see examples below) and the ones that Rufus downloads(vanilla RTM 21H2 from November). On the other hand, ISOs based on the compressed install.esd, like the ones that the "Media Creation Tool" creates, work just fine. Tested on an older Gigabyte Z77 and on a new Asus B560. Result is a blinking cursor above the blue Windows logo, and that's it.

Examples of ISOs that don't work:

• en-us_windows_10_consumer_editions_version_21h2_updated_april_2022_x64_dvd_a545527b.iso
  
• en-us_windows_10_business_editions_version_21h2_updated_april_2022_x64_dvd_38bad9d1.iso
  
• en-us_windows_10_consumer_editions_version_21h2_updated_march_2022_x64_dvd_86f47135.iso
  

I tested EasyOS 3.4.1 with Ventoy and it was OK, no problem.
Today I've tested EasyOS 3.4.7, but it does not boot and give an error and a Kernel Panic.

erro: file '/lib/modules/5.15.35/kernel/drivers/dax/dax.ko' not found.
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I tested on two different systems, on ACER EeePC 1015CX, 320 GB HDD and 2 GB ram and on
HP Z220 Workstation 128 GB SSD and 1 TB HDD, 16 GB ram.
To test I used Verbatim Store'n'Go 8 GB and Kingston DataTraveler 100 G3 32GB.

I also verify that the problem appears with version 3.4.3 and is present in version 3.4.4, 3.4.5, 3.4.6, 3.4.7 of EasyOS.

I use Ventoy version 1.0.74.

Writing EasyOS-3.4.7-amd64.img on the same key using Win32DiskImager-1.0.0-binary run OK.

Hi @ventoy

With the ventoy Update button in the ventoy2disk.exe file, we can manually update our current system to a higher version. How about we make the update process automatically update Ventoy to a higher version by putting an Auto Update button on the interface?
When a new version of Ventoy comes out, it should ask the user if you want to update to the new version. When the Update button is pressed, the system will automatically update the VTOYEFI section over the internet in the background.
In this way, those who want can update their system manually, and those who want can update it automatically over the internet.

Hi, I'm using Ventoy for a new recovery disk at my workplace's IT department.
On the extra GRUB menu (/ventoy/ventoy_grub.cfg), I have a menu item that runs a cat command to display what software versions are used on the disk. Currently the menu item entry is programmed like this: (some parts I've pulled from Ventoy's other partition under Linux, like vtInputKey)

I started using Ventoy about two weeks ago.  It has already been a great help to me.  I built a Windows 10 Ventoy USB drive and added Hiren’s BootCD PE to it.  This worked well on my two Windows 10 PCs (a desktop with two monitors and a laptop).  It also worked on a friend’s PC.
 
About a week later I added the EaseUS Recovery iso to the Ventoy drive.  On the desktop the new iso would not load and caused the system to hang.  On the laptop it launched and ran successfully.
 
Over the next 24 hours I added two more iso files to the Ventoy drive: AOMEI PE and Macrium Reflect Rescue.
 
All the iso files operated successfully on the laptop, but on the desktop the iso file that is second alphabetically will not run.  N.B. Changing the name of the problem iso file so that another file is second alphabetically transfers the problem to the file that is now second alphabetically.  I suspect that the second monitor is the cause of the problem.

Has anyone else experienced this problem?  Does anyone have any advice?