you can use this command to protect usb or hdd against virus attack or file delete by human mistake

CMD with admin right to protect the flash usb or hdd

user this command

01-diskpart

02-list disk

03-select disk (number?)

04-attributes disk set readonly

--------------------------------------------------------------------

cmd with admin right to unprotect the flash usb or hdd so you can write to usb or hdd

CMD

diskpart

01-list disk

02-select disk (number?)

03-attributes disk clear readonly

so i am trying to get vhd onto my ventoy drive (windows) I dragged the file from github into my 'Ventoy' drive, (including the actual vhd file), and it did not work. (windows10), also, do apple laptop work with secure boot?

My system has UEFI firmware.  When I ask to display my UEFI Boot menu, I get the 2 NVRAM permanent entries but  instead of 1 entry for my Ventoy UFD, I get two.

UEFI Kingston Datatraveler 3.0PMAP Partition 2  - if I select this one, Ventoy works great
UEFI Kingston Datatraveler 3.0PMAP Partition 3 - if I select this one, I'm returned to the UEFI boot menu

It is a dynamic, UFD based entry.  It doesn't exist in my NVRAM.  If I remove the Ventoy UFD these two entries do not show up.  Do you know why this 2nd entry is showing up.  More an inconvenience than anything.

In continuation of the topics:  mod Ventoy Menu Tip Plugin(Design ventoy ventoy 1.0.72)
1. Changed "Hardware Information" ( hwinfo.cfg.....).  Start "F9". Result:
   
   
   
2. Added support for text files - *.cfg.  The encoding of the UTF-8 file.
3. *.cfg files can not only be read, but also run as menu Grub2, Syslinux or Pxelinux.
          

Example of running grub.cfg on video.

You can download the modified files from the following links:
mod_ventoy-1.0.78-linux.tar.gz
mod_ventoy-1.0.78-livecd.iso
mod_ventoy-1.0.78-windows.zip

Hello

I am trying to boot an old HP dc7700 withj a Ventoy stick without success (screen remains black) 
(F10->System BIOS and Setup Utility, copyright 1982-2006)

Is this PC too old to boout from for Ventoy?

Thank you!

Harry




PS
others/modern PCs can be booted from this stick

• 2022/07/01 --- 1.0.78 release
  

1. Improvement for Boot Conf Replace Plugin now can replace at most 2 files. Notes
   
   
2. Update Super-UEFIinSecureBoot-Disk to v3.4 (#1695)
   
3. .ventoyignore also works in F2 Browser Mode.
   
4. Fix the bug when booting latest KaOS. (#1696)
   
5. Fix a bug when booting TrueNAS Core 13.0. (#1684)
   
6. Fix a bug when booting StorageCraft StorageProtect SPX. (#1683)
   
7. Auto remove the redundant trailing slash when set directory path on VentoyPlugson page.
   
8. languages.json update
   
9. New ISO support (total 920+)
   
10. Document: How To Delete Ventoy Secure Boot Key
    

I have three images in the "ISO" folder .iso, 
Windows_7_&_10_Pro_x86_x64_30.05.2021.iso,
Windows_7_Pro_x86_x64_15.12.2021.iso,
Windows_10_21H2_19044.1766_x64.iso.
I assigned the Windows_1 icon to the last two, and the image Windows_10_21H2_19044.1766_x64.iso.
I want to assign a Super icon_1. 
But I can't do it. Tell me where the error is, what am I doing wrong?

"menu_class": [       
        {
            "key": "Windows",
            "class": "Windows_1"
        },
        {
            "dir": "ISO",
            "class": "Super_1"
        },
        {
            "key": "WinPE",
            "class": "WinPE_1"
        },
        {
            "key": "Memtest",
            "class": "Memtest_1"
        }
    ],

    "image_list": [
        "/ISO/Windows_10_21H2_19044.1766_x64.iso",
        "/ISO/Windows_7_&_10_Pro_x86_x64_30.05.2021.iso",
        "/ISO/Windows_7_Pro_x86_x64_15.12.2021.iso",
        "/WinPE/WinPE_Sergei_Strelec_x86_x64_04.01.2022.iso",
        "/Memtest/Memtest86+_4.3.7_&_9.4.iso"
    ],

    "menu_alias":[
        {
            "image":"/ISO/Windows_10_21H2_19044.1766_x64.iso",
            "alias":"Windows 10      21H2  Pro    x86 x64  19044.1645"
        },
        {
            "image":"/ISO/Windows_7_&_10_Pro_x86_x64_30.05.2021.iso",
            "alias":"Windows 7 & 10  21H1  Pro    x86 x64              30.05.2021"       
        },
        {
            "image":"/ISO/Windows_7_Pro_x86_x64_15.12.2021.iso",
            "alias":"Windows 7            Pro    x86 x64              15.12.2021"
        },
        {
            "image":"/WinPE/WinPE_Sergei_Strelec_x86_x64_19.07.2021.iso",
            "alias":"WinPE Sergei Strelec        x86 x64              19.07.2021"
        },
        {
            "image":"/WinPE/WinPE_Sergei_Strelec_x86_x64_04.01.2022.iso",
            "alias":"WinPE Sergei Strelec        x86 x64              04.01.2022"
        },
        {
            "image":"/WinPE/WinPE_Super.iso",
            "alias":"WinPE Super        ( no boot UEFI )"
        },
        {
            "image":"/Memtest/Memtest86+_4.3.7_&_9.4.iso",
            "alias":"Memtest86+            4.3.7  &  9.4"
        }
    ]
}

Hello

it happend that I selected the wrong OS/ISO to boot the PC from.  In order to interrupt the boot process (of the unwanted OS), I pressed Ctr+Alt+Del. This does infact reset the PC, but the "Ventoy-screen" is not loaded/shown again. It's necessary to power off/on the PC.


Why that? Has that something to do with Ventoy?


Thank's a lot!

Harry

Hello forum,

would like to add a LUKS-partition, preferably between the large NTFS-partition and the 32MB FAT16 partition.
(e.g. with a tool like gparted)

Is this a good idea?


Thank you!

Harry

My system is set for UEFI boot. I made a VHD of medicat (GPT, Ventoy 1.77, NTFS). 
I then created a Ventoy 1.77 USB disk (GPT, NTFS).
I put the medicat.VHD on the Ventoy USB disk, created a /ventoy folder, and put the Windows 10 ventoy_vhdboot.img into the /ventoy folder.
On boot the Ventoy menu appears, but when I select the medicat target I get an error and am unable to boot:
File: \Windows\system32\winload.efi
Status: 0xc000000f
Info: The application or operating system couldn't be loaded because a required file is missing or contains erros.

Note:
- The medicat VHD boots successfully in VirtualBox
- Ventoy (GPT) installed directly onto the USB disk boots fine
- Medicat installed directly onto the USB disk boots fine


I've tried all of the following:
- Partition VHD with MBR
- Partition Ventoy USB with MBR
- Format Ventoy USB as exFat
- Tried the Windows 7 ventoy_vhdboot.img (different failure)
I see the same issue in all cases.