unable to inject drivers into an offline wim image

This is the persistent error i get
Error: 50. DISM does not support servicing a Windows Vista RTM or earlier os. If the os is supported check that SSShim.dll is present.

A useful bootable WinPE iso gives me a poor resolution when used which is why i decided to inject my intel UHD drivers into the wim file (based on win 11 pe). I extracted the wim from the iso and used dism gui to accomplish what i planned. Dism commands failed to

I persistently get this error
This is the persistent error i get
Error: 50. DISM does not support servicing a Windows Vista RTM or earlier os. If the os is supported check that SSShim.dll is present.

sfc /scannow shows no errors, minint reg entry is not present, bios is at default settings (secure boot off), anti virus turned off and ssshim is definitely present

my pc runs win 11 64 bit Home version

Thanks for any advise to follow to inject my graphic drivers

To witch OS you're trying to add the drivers?
You must use install.wim not install.esd
Do you know the image index you want to add the drivers to?

trying to add drivers to an existing win 11 PE wim file extracted from a bootable utility iso. There are more than one wim file present in the sources folder to boot win 10 32, win 10 64 and win 11 64 respectively - all having different but identifiable names.

Image index - did not quite comprehend but have seen this appear in the interface

Will copy-pasting the drivers into the File repository work?

perfection said:

trying to add drivers to an existing win 11 PE wim file extracted from a bootable utility iso.

Click to expand...

That could be the problem. Maybe the pe somebody made is missing something needed for dism to integrate those drivers.

Even if you can get the drivers to integrate, there will probably be other hurdles. I recall when we were doing similar with win7 pe, we ended up switching to admin, then relaunching explorer as system using a tool from sysinternals. Something like this:

from within system acount:
exec !=drvload.exe X:\Windows\System32\DriverStore\FileRepository\atiilhag.inf_x86_neutral_1d882551ede2c65b\atiilhag.inf
exec !=drvload.exe X:\Windows\System32\DriverStore\FileRepository\igdlh.inf_x86_neutral_2d255f193700d214\igdlh.inf
exec !=drvload.exe X:\Windows\System32\DriverStore\FileRepository\nv_lh.inf_x86_neutral_bbe628dbdd6fce25\nv_LH.inf

switch to admin:
REGI HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList\Guest=#0
REGI HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\AutoAdminLogon=1
REGI HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultUserName=LsaSetupDomain\Administrator
REGI HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultPassword=""
REGI HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ForceAutoLogon=1
REGI HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\StartMenuLogOff=0
EXEC !=net start gpsvc
EXEC !=%SystemRoot%\System32\tsdiscon.exe
WAIT 10000
REGI HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ForceAutoLogon=0

relaunch explorer as system:
exec !%windir%\system32\tskill explorer
exec !%windir%\system32\psexec -i -d -s explorer

Then like magic the igpu drivers worked and we had aero in pe.

Without showing your dism commands and structure of iso, hard to tell what is wrong.

From the Win 11 PE utility it should be Boot.wim.
Normally the boot.wim has two index or two "programs". One is for Recovery / maintenance and another for win 11 setup.


Open boot.wim with 7zip to find out how many index you have on yours.
You can add the drivers to the image using Dism ++

I haven't seen any documentation that explains why there are two images. It is a mystery.