Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 14,172
» Latest member: nimareq
» Forum threads: 1,694
» Forum posts: 6,790

Full Statistics

Online Users
There are currently 178 online users.
» 0 Member(s) | 173 Guest(s)
Applebot, Baidu, Bing, Google, Yandex

Latest Threads
Running Out of Disk Space...
Forum: Ventoy Discussion Forum
Last Post: longpanda
5 hours ago
» Replies: 7
» Views: 256
CachyOS vDisk (vtoyboot) ...
Forum: Ventoy Discussion Forum
Last Post: alain81
Yesterday, 01:25 PM
» Replies: 0
» Views: 67
Persistence not working w...
Forum: Ventoy Discussion Forum
Last Post: petergb
Yesterday, 10:47 AM
» Replies: 2
» Views: 170
Resolution issue on Windo...
Forum: Ventoy Discussion Forum
Last Post: pete
04-28-2026, 01:38 AM
» Replies: 10
» Views: 17,430
- Add a "Quality of Life"...
Forum: Ventoy Discussion Forum
Last Post: crasadure
04-24-2026, 03:57 PM
» Replies: 0
» Views: 402
Problem with Vantoy and a...
Forum: Ventoy Discussion Forum
Last Post: capitainealbator
04-24-2026, 07:51 AM
» Replies: 3
» Views: 606
problems installing windo...
Forum: iVentoy Discussion Forum
Last Post: roy
04-23-2026, 12:36 PM
» Replies: 1
» Views: 1,327
Ventoy enroll key manager...
Forum: Ventoy Discussion Forum
Last Post: MBSTech
04-22-2026, 03:23 PM
» Replies: 33
» Views: 102,621
iVentoy 1.0.27 release
Forum: iVentoy Discussion Forum
Last Post: longpanda
04-21-2026, 12:33 AM
» Replies: 0
» Views: 341
iVentoy stuck on new firm...
Forum: iVentoy Discussion Forum
Last Post: roy
04-20-2026, 02:46 PM
» Replies: 3
» Views: 714

 
  CachyOS vDisk (vtoyboot) not working
Posted by: alain81 - Yesterday, 01:25 PM - Forum: Ventoy Discussion Forum - No Replies

Hi there!
I installed CachyOS in a virtual machine using Hyper-V (with option "generation 2" selected). Then I installed the vtoyboot script (vDisk Boot Plugin --> latest vtoyboot-1.0.36 release) and converted the VHDX file to VHD so it could boot with Ventoy.
The installation boots and runs fine in Hyper-V.
I then renamed the *.vhd file to *.vtoy. At boot, in Ventoy, I selected the correct CachyOS vtoy file, but it does not load and I receive the following error shown below. If I press Enter, after a few moments the same message appears again.

Quote:You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, or "exit" to continue bootup.

Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.

Press Enter to continue.

I followed this exact same procedure with Linux Mint and it works correctly in Ventoy, but for some reason CachyOS does not.
Do you have any idea why?

Print this item

solved Persistence not working with LMDE7
Posted by: petergb - 05-07-2026, 06:51 AM - Forum: Ventoy Discussion Forum - Replies (2)

Greetings all,

I have recently set up a 128GB USB stick with Ventoy thus:
sudo bash Ventoy2Disk.sh -i -L FZV3 -r 20000 /dev/sdc

On the main partition of the stick I have placed 4 versions of Linux Mint
linuxmint-20.3-mate-64bit.iso
linuxmint-21.3-cinnamon-64bit.iso
linuxmint-21.3-mate-64bit.iso
linuxmint-22.3-mate-64bit.iso

Each of these versions of Linux Mint has a 2GB persistence file associated with it. I created a 2GB Persistence file using CreatePersistentImg.sh, then copied the file to the USB stick into the same folder as the isos, and then renamed it to suit the particular iso. Then I used:
sudo bash VentoyPlugson.sh /dev/sdc
...and the browser-based configuration utility to associate the persistence file with the appropriate iso. I repeated this process for all the 4 versions of Linux Mint.

All this worked very well! All 4 versions boot OK with or without persistence, and I have verified that the persistence is actually working as it should.

Now comes the problem. I want to try out LMDE7, so I went through the same steps as above with the LMDE7 iso, and then associating it with a 2GB persistence file using the browser-based configuration utility. It all looked like it had gone OK, no obvious error messages.

After doing this I can boot into LMDE7 using the Ventoy stick, and the option for persistence appears on the Ventoy menu as expected - but the persistence does not work.

It would be great to get the persistence working for LMDE7. Can anybody help, please?

Ventoy is 1.1.10 x86_64.
Ventoy Version in Disk: 1.1.10
Disk Partition Style : MBR
Secure Boot Support : YES

Linux 5.15.0-177-generic x86_64

If you need further information then please ask.

with best wishes, petergb.

Print this item

  Running Out of Disk Space Using Persistence With Mint
Posted by: jakolodziej - 05-06-2026, 10:25 PM - Forum: Ventoy Discussion Forum - Replies (7)

Ventoy Experts:

I have a relatively new Dell PC (i7, 16GB memory, 1T SSD disk drive, NVDA graphics card) that came with Windows 11 pre-installed. I am not a big fan of Windows 11 (or any other Microsoft product for that matter!), so I decided to run Linux Mint. I got a SanDisk Ultra 256GB USB3.0 drive and loaded Ventoy 1.1.10 and Linux Mint 22.2 on it. I used the Ventoy instructions and some YouTube videos with no significant problems. That worked great until I rebooted - that's where I learned about the significance of a Live version! I poked around and learned about "persistence", so I did that with no significant problems. That has worked well for me until recently. I now keep getting Mint OS warnings about low disk space (the output of "du" currently shows I have 11M avail on "/"). I did find and use the "ExtendPersistentImg.sh" script to expand my persistence file, and that seemed to work correctly. The problem, however, "persists" (pun intended!) - I am VERY low on available disk space. Sooo, I am reaching out to the experts for help. What do I need to do to solve this problem? I have searched the forums here and found a few posts in the past with a similar (actually identical) problem, but there were no answers. I suppose I could move the "/" directory (or maybe just /home) to the 1T SSD drive, but my goal with this was to have everything on the USB stick.My plan is/was to run one ".iso" (the latest version of Mint) with lots of available space for emails/files/etc.

Thanks for the help.

Print this item

  - Add a "Quality of Life" option, to disable Teams, Outlook, Copilot and other Micros
Posted by: crasadure - 04-24-2026, 03:57 PM - Forum: Ventoy Discussion Forum - No Replies

Hi @ventoy

Rufus has added improvements to the Windows User Experience in its new version.
[Image: windows-user-experince-windows11.jpg]


- A "Quality of Life" option has been added to disable Teams, Outlook, Copilot, and other annoying applications that Microsoft requires.
    QoL improvements(Don't force Copilot,Ondrive,Outlook,Fast Startup,etc)

Is there a chance this feature could also be added to Ventoy?


https://github.com/pbatard/rufus/blob/ma...ngeLog.txt

Print this item

solved Problem with Vantoy and a 10 years old computer
Posted by: capitainealbator - 04-21-2026, 05:21 PM - Forum: Ventoy Discussion Forum - Replies (3)

Hello all,

I tried Vantoy 1.1.11 on an USB stick but...on my 10 years old computer (the BIOS isn't UEFI) , I have like a 256 colours screen, no mouse and all is slow (please see the video )

Please could you help me ?

https://fromsmash.com/XaxFm7fVqL-ct?e=Zn...GZyZWUuZnI=

Thanks very much for your help,
Kind regards from France
Thierry



Attached Files
.pdf   2026-04-17_205846.pdf (Size: 67.62 KB / Downloads: 2)
Print this item

Heart iVentoy 1.0.27 release
Posted by: longpanda - 04-21-2026, 12:33 AM - Forum: iVentoy Discussion Forum - No Replies

  • 2026/04/20 --- 1.0.27 release
  1. Add arm64 linux build. Now iVentoy can run in arm64 machine. (e.g. Raspberry PI)

  2. Only 64-bit Windows builds will be provided in future updates.

  3. Fix the ISO uploading issue.

  4. Fix some boot issue for Windows7, WindowsServer 2012R2.

  5. Bugfix

Print this item

  Ventoy Tuxedo OS with persistence ?
Posted by: Bear - 04-20-2026, 07:55 AM - Forum: Ventoy Discussion Forum - No Replies

Hello, 
I'm new to Ventoy. I've managed to get it working with Mint and Kali ISOs using persistence, 
but I'm stuck with tuxedo persistence. Has anyone tried and succeeded in getting it to work? 
Regards, Bertrand

Print this item

  problems installing windows 11 with the unattended file
Posted by: xeno - 04-16-2026, 01:26 PM - Forum: iVentoy Discussion Forum - Replies (1)

hello everyone, I'm trying to install Windows 11 via Iventoy with a response file on a Dell laptop in UEFI mode, the disks seem to crash and the installation begins, but an error is written at 55% when installing Windows 11. My unattended.xml:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urnConfusedchemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <SetupUILanguage>
                <UILanguage>ru-RU</UILanguage>
            </SetupUILanguage>
            <InputLocale>ru-RU</InputLocale>
            <UILanguage>ru-RU</UILanguage>
            <SystemLocale>ru-RU</SystemLocale>
            <UserLocale>ru-RU</UserLocale>
        </component>
        <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DiskConfiguration>               
<Disk wcm:action="add">
                    <CreatePartitions>
                        <CreatePartition wcm:action="add">
                            <Order>1</Order>
                            <Type>EFI</Type>
                            <!-- <Type>Primary</Type> -->
                            <Size>100</Size>
                        </CreatePartition>
                        <CreatePartition wcm:action="add">
                            <Order>2</Order>
                            <Type>MSR</Type>
                            <Size>16</Size>
                        </CreatePartition>
                        <CreatePartition wcm:action="add">
                            <Order>3</Order>
                            <Type>Primary</Type>
                            <Extend>true</Extend>
                        </CreatePartition>
                    </CreatePartitions>
                    <ModifyPartitions>
                        <ModifyPartition wcm:action="add">
                            <Order>1</Order>
                            <PartitionId>1</PartitionId>
                            <Format>FAT32</Format>
                            <Label>System</Label>
                        </ModifyPartition>
                        <ModifyPartition wcm:action="add">
                            <Order>3</Order>
                            <PartitionId>3</PartitionId>
                            <Format>NTFS</Format>
                            <Label>Windows</Label>
                        </ModifyPartition>
                    </ModifyPartitions>
                    <DiskID>$$VT_WINDOWS_DISK_MAX_SIZE$$</DiskID>
                    <WillWipeDisk>true</WillWipeDisk>
                </Disk>
            </DiskConfiguration>
<ImageInstall>
                <OSImage>
                    <InstallFrom>
                        <MetaData wcm:action="add">
                            <Value>6</Value>
                            <Key>/IMAGE/INDEX</Key>
                        </MetaData>
                    </InstallFrom>
                    <InstallTo>
                        <DiskID>$$VT_WINDOWS_DISK_MAX_SIZE$$</DiskID>
                        <PartitionID>3</PartitionID>
                    </InstallTo>
                </OSImage>
            </ImageInstall>
           
            <UserData>
                <AcceptEula>true</AcceptEula>
                <FullName>-</FullName>
                <Organization>-</Organization>
              <!--  $$VT_MAC_COLON_LOWER$$ $$VT_SERVER_IP$$  $$VT_LOCAL_IP$$/$$VT_NET_MASK_LEN$$
                $$VT_IMG_PMD5_HTTP_URL$$ -->
            </UserData>
        </component>
    </settings>
    <settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <RegisteredOrganization>-</RegisteredOrganization>
        </component>       
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <OOBE>
              <HideEULAPage>true</HideEULAPage>
              <NetworkLocation>Work</NetworkLocation>
              <ProtectYourPC>3</ProtectYourPC>
            </OOBE>
            <AutoLogon>
                <Enabled>true</Enabled>
                <LogonCount>2</LogonCount>
                <Username>administrator</Username>
                <Password>
                    <Value>123456</Value>
                    <PlainText>true</PlainText>
                </Password>
            </AutoLogon>
            <UserAccounts>
                <AdministratorPassword>
                    <Value>123456</Value>
                    <PlainText>true</PlainText>
                </AdministratorPassword>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>public</Value>
                            <PlainText>true</PlainText>
                        </Password>
                        <DisplayName>public</DisplayName>
                        <Group>Administrators</Group>
                        <Name>public</Name>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
            <RegisteredOrganization>-</RegisteredOrganization>
            <RegisteredOwner>-</RegisteredOwner>
        </component>       
    </settings>
</unattend>


Don't pay attention to the smiley face in unattended.xml

(04-16-2026, 01:26 PM)xeno Wrote: hello everyone, I'm trying to install Windows 11 via Iventoy with a response file on a Dell laptop in UEFI mode, the disks seem to crash and the installation begins, but an error is written at 55% when installing Windows 11. I also want to add that I have the achi drive type in my bios. My unattended.xml:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urnConfusedchemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <SetupUILanguage>
                <UILanguage>ru-RU</UILanguage>
            </SetupUILanguage>
            <InputLocale>ru-RU</InputLocale>
            <UILanguage>ru-RU</UILanguage>
            <SystemLocale>ru-RU</SystemLocale>
            <UserLocale>ru-RU</UserLocale>
        </component>
        <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DiskConfiguration>               
<Disk wcm:action="add">
                    <CreatePartitions>
                        <CreatePartition wcm:action="add">
                            <Order>1</Order>
                            <Type>EFI</Type>
                            <!-- <Type>Primary</Type> -->
                            <Size>100</Size>
                        </CreatePartition>
                        <CreatePartition wcm:action="add">
                            <Order>2</Order>
                            <Type>MSR</Type>
                            <Size>16</Size>
                        </CreatePartition>
                        <CreatePartition wcm:action="add">
                            <Order>3</Order>
                            <Type>Primary</Type>
                            <Extend>true</Extend>
                        </CreatePartition>
                    </CreatePartitions>
                    <ModifyPartitions>
                        <ModifyPartition wcm:action="add">
                            <Order>1</Order>
                            <PartitionId>1</PartitionId>
                            <Format>FAT32</Format>
                            <Label>System</Label>
                        </ModifyPartition>
                        <ModifyPartition wcm:action="add">
                            <Order>3</Order>
                            <PartitionId>3</PartitionId>
                            <Format>NTFS</Format>
                            <Label>Windows</Label>
                        </ModifyPartition>
                    </ModifyPartitions>
                    <DiskID>$$VT_WINDOWS_DISK_MAX_SIZE$$</DiskID>
                    <WillWipeDisk>true</WillWipeDisk>
                </Disk>
            </DiskConfiguration>
<ImageInstall>
                <OSImage>
                    <InstallFrom>
                        <MetaData wcm:action="add">
                            <Value>6</Value>
                            <Key>/IMAGE/INDEX</Key>
                        </MetaData>
                    </InstallFrom>
                    <InstallTo>
                        <DiskID>$$VT_WINDOWS_DISK_MAX_SIZE$$</DiskID>
                        <PartitionID>3</PartitionID>
                    </InstallTo>
                </OSImage>
            </ImageInstall>
           
            <UserData>
                <AcceptEula>true</AcceptEula>
                <FullName>-</FullName>
                <Organization>-</Organization>
              <!--  $$VT_MAC_COLON_LOWER$$ $$VT_SERVER_IP$$  $$VT_LOCAL_IP$$/$$VT_NET_MASK_LEN$$
                $$VT_IMG_PMD5_HTTP_URL$$ -->
            </UserData>
        </component>
    </settings>
    <settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <RegisteredOrganization>-</RegisteredOrganization>
        </component>       
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <OOBE>
              <HideEULAPage>true</HideEULAPage>
              <NetworkLocation>Work</NetworkLocation>
              <ProtectYourPC>3</ProtectYourPC>
            </OOBE>
            <AutoLogon>
                <Enabled>true</Enabled>
                <LogonCount>2</LogonCount>
                <Username>administrator</Username>
                <Password>
                    <Value>123456</Value>
                    <PlainText>true</PlainText>
                </Password>
            </AutoLogon>
            <UserAccounts>
                <AdministratorPassword>
                    <Value>123456</Value>
                    <PlainText>true</PlainText>
                </AdministratorPassword>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>public</Value>
                            <PlainText>true</PlainText>
                        </Password>
                        <DisplayName>public</DisplayName>
                        <Group>Administrators</Group>
                        <Name>public</Name>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
            <RegisteredOrganization>-</RegisteredOrganization>
            <RegisteredOwner>-</RegisteredOwner>
        </component>       
    </settings>
</unattend>

Don't pay attention to the smiley face in unattended.xml

Print this item

Exclamation iVentoy stuck on new firmware
Posted by: roy - 04-15-2026, 03:32 PM - Forum: iVentoy Discussion Forum - Replies (3)

Hi, I use iVentoy to deploy windows on some machines, but I recently experienced some issues on new firmware. When I select PXE boot in the BIOS iVentoy downloads and then gets stuck and not showing the menu. Originally I used iVentoy version 1.0.21 but also tried 1.0.25 and 1.0.26, this did not make a difference. Also a BIOS update did also not help.

I tried different BIOS settings and different boot files to no avail.
The same config and images still work on the older motherboards, and the logs from both are almost identical.

Machine boots successfully
UEFI version 2.22.189 - 2024 AMI
Motherboard: ASUS Pro WS TRX50-SAGE WIFI

Code:
2026/04/10 10:54:18.808 [TFTP] Parse tftp option(tsize,0)
2026/04/10 10:54:18.808 [TFTP] Parse tftp option(blksize,1468)
2026/04/10 10:54:18.808 [TFTP] Unsupported tftp option windowsize 4
2026/04/10 10:54:18.808 [TFTP] TFTP RRQ client x.x.x.x:1320 download <iventoy_loader_16000_uefi> start ...
2026/04/10 10:54:18.808 [TFTP] DHCP ExternalNet client x.x.x.x should use loader ipxe.x64.snponly.efi.0
2026/04/10 10:54:18.808 [TFTP] Start send file iventoy_loader_16000_uefi to x.x.x.x:1320 with blksize 1468, has oack 1
2026/04/10 10:54:18.808 [TFTP] Recv an ERROR opcode pkt from client x.x.x.x:1320.
2026/04/10 10:54:18.919 [TFTP] Parse tftp option(blksize,1468)
2026/04/10 10:54:18.919 [TFTP] Unsupported tftp option windowsize 4
2026/04/10 10:54:18.919 [TFTP] TFTP RRQ client x.x.x.x:1321 download <iventoy_loader_16000_uefi> start ...
2026/04/10 10:54:18.919 [TFTP] DHCP ExternalNet client x.x.x.x should use loader ipxe.x64.snponly.efi.0
2026/04/10 10:54:18.919 [TFTP] Start send file iventoy_loader_16000_uefi to x.x.x.x:1321 with blksize 1468, has oack 1
2026/04/10 10:54:18.973 [TFTP] Finished send file to x.x.x.x:1321 with blksize 1468 blks 206
2026/04/10 10:54:22.953 [HTTP] DHCP external subnet mode notify discovery client x.x.x.x ipxe/xx-xx-xx-xx-xx-xx-xx/uefi/mask:m.m.m.m/gw:g.g.g.g/dns:d.d.d.d
2026/04/10 10:54:22.953 [PXE]  Client xx-xx-xx-xx-xx-xx-xx start PXE install in UEFI X64 mode.

Machine boot fails
UEFI version 2.22.1299 - 2026 AMI
Motherboard: ASUS W880-ACE SE
Code:
2026/04/10 10:45:09.454 [TFTP] Parse tftp option(tsize,0)
2026/04/10 10:45:09.454 [TFTP] Parse tftp option(blksize,1468)
2026/04/10 10:45:09.454 [TFTP] Unsupported tftp option windowsize 4
2026/04/10 10:45:09.454 [TFTP] TFTP RRQ client x.x.x.x:1974 download <iventoy_loader_16000_uefi> start ...
2026/04/10 10:45:09.454 [TFTP] DHCP ExternalNet client x.x.x.x should use loader ipxe.x64.snponly.efi.0
2026/04/10 10:45:09.454 [TFTP] Start send file iventoy_loader_16000_uefi to x.x.x.x:1974 with blksize 1468, has oack 1
2026/04/10 10:45:09.455 [TFTP] Recv an ERROR opcode pkt from client x.x.x.x:1974.
2026/04/10 10:45:09.764 [TFTP] Parse tftp option(blksize,1468)
2026/04/10 10:45:09.764 [TFTP] Unsupported tftp option windowsize 4
2026/04/10 10:45:09.764 [TFTP] TFTP RRQ client x.x.x.x:1975 download <iventoy_loader_16000_uefi> start ...
2026/04/10 10:45:09.764 [TFTP] DHCP ExternalNet client x.x.x.x should use loader ipxe.x64.snponly.efi.0
2026/04/10 10:45:09.764 [TFTP] Start send file iventoy_loader_16000_uefi to x.x.x.x:1975 with blksize 1468, has oack 1
2026/04/10 10:45:09.800 [TFTP] Finished send file to x.x.x.x:1975 with blksize 1468 blks 206
2026/04/10 10:45:13.858 [HTTP] DHCP external subnet mode notify discovery client x.x.x.x ipxe/xx-xx-xx-xx-xx-xx-xx/uefi/mask:m.m.m.m/gw:g.g.g.g/dns:d.d.d.d
2026/04/10 10:45:13.858 [PXE]  Client xx-xx-xx-xx-xx-xx-xx start PXE install in UEFI X64 mode.



Attached Files Thumbnail(s)
   
Print this item

  华为RH2288H V2服务器上无法启动
Posted by: hxpro - 04-15-2026, 08:21 AM - Forum: Ventoy Discussion Forum - No Replies

今天要给华为RH2288H v2服务器装系统,BIOS里改为EFI引导,重启后无法识别ventory的U盘引导。

Print this item