我习惯在windows的sources下放置$oem$文件夹来实现安装完毕的操作系统中有一些特定的文件，但是检查目前的文件注入插件，只能在PE中注入，没有办法向安装完毕的系统中注入。尝试使用autorun.bat的方式将所需的文件拷贝至挂载盘中，结果发现挂载盘是UDF格式，只读的，也实现不了。有没有其他的方案可以实现呢？把需要的文件放入iso中当然可以，但是这样的话，一旦有新的iso，还得重新制作iso，就失去ventoy的便捷性了。

i am using an hp laptop (15s fq 2000) and the firmware is american megatrend. i was hoping ventoy’s method would help overcome whatever is creating a problem, but the same as with other installers, the lubuntu 22.04 worked fine and the ubuntu got stuck at the welcome screen. maybe someone here knows what the issue might be, or let me know if it is unrelated and i should be looking elsewhere.

When I disable UEFI the stick boots fine as soon as I enable UEFI the stick is not properly recognized and does not boot at all. I get a recovery windows screen even the USB is on the top. The bios shows the brand of the USB Stick in non uefi mode while in uefi mode it does not show the brand from the USB stick which is also quite strange. 
I am using a Acer Aspire V15 Nitro Black Edition ....

any ideas? I tried with GPT and MBR .....no difference .....

Hello

Sorry if the subject is already present, I confess to having done a lot of research without success...

Below are screenshots to show my config

Everything is OK in green
No extra slash...
At launch, I can select my ISO and my template, but at the end of the Windows installation, I have Cortana which host and I have to select the language...

My template is ignored, but why?

Can you help me ?

Thanks in advance

EDIT : Info : Rufus with same .xml (rename unattend.xml) in root folder = No Problem...

Attached Files

Thumbnail(s)
           

There is an esd file, I tried to convert it to vim to run. The result is a startup error. Tell me what am I doing wrong
Windows 7 AIO
https://www.dropbox.com/s/o7gngv8nf168d2...l.esd?dl=0

出现如下提示：
end Kernel panic - not syncing:Attempted to kill init!exit
请问是怎么回事呢？

I've booted "systemrescue-9.03-amd64.iso" many times with no problem on my Asus Rog Laptop.

I just changed the RAM (same size - just faster Ripjaws CL34 instead of stock CL40).  For what it is worth, the ram works fine, but not at the advertised speed (motherboard has no options to set CL, and seems to use old speeds instead... but I digress).

Since changing the RAM, I can no longer boot systemrescue-9.03-amd64.iso (I *can* boot a 32gb "dd" image of windows recovery - just not the iso) - it reports an out-of-memory problem, and returns to the ventoy menu.

How the brand of RAM might make any difference here I have no idea.

I created a whole new Ventoy USB and tried again (same problem).

If I change back to the old ram, I'll return here and let you know if it now works again.

I just did this, and it works:

In Windows 11, Start -> Recovery -> Create Recovery USB  (to make a 32gb USB stick)

In Linux (vmware in my case):-

dd if=/dev/sdb bs=8225280 of=Windows_Recovery.img

Mount the ventoy USB into linux, and copy the "Windows_Recovery.img" file onto it.

Reboot

TaDa!! (tested works) - I can now "restore my windows" (and run the recovery tools etc) from my external SSD!

I would like to be able to trigger ventoy installations/updates to USB devices via a script.

Are there command line options that would allow me to do this?

The new Linux distro experimental EasyOS can not be launched using Ventoy.  Here`s the feedback of the creator of Easy OS:

Quote:"What jumps out immediately in that photo is "mnt/zram0".

It seems that you haven't told the kernel where easy.sfs is.
From the photo, it has found initrd, but not easy.sfs.
The three files, vmlinuz, initrd and easy.sfs should all be together.
The kernel will use these parameters to find easy.sfs: specified on the kernel commandline, with "wkg_uuid=" and "wkg_dir=" parameters.
Instead of wkg_uuid, you could use "wkg_label=" or "wkg_dev="
In the latter case, if the working-partition is /dev/sdb2, then use "wkg_dev=sdb2".

But if you are booting from usb, then the drive letters may change, so best to use filesystem uuid or label.

So whatever bootloader you are using, you have specified where initrd is, but have not told the kernel where the ext4 working partition is (and where to find easy.sfs)."