wimlib

@synchronicity

Although this is not technically problem(minimal for using with setup.exe), maybe before release 1.9 final can you look please to bad parsing ProductName ?

@k3dar7 so you make a snapshot with wimlib, and replace the original install.wim with the one from wimlib on the installation media ? Or is it more complicated ?

only little more complicated...
1. on running windows system run: sysprep /oobe /generalize /shutdown (this remove hw dependent ...

hi, synchronicity

image created and all is auto filled (xml windows elements and also flags) :)

compare with info from image saved using ImageX i see only diference:
using wimlib-1.9.0-BETA5 => Product Name: Windows 7 Home Premium
using ImageX under WinPE3 => Product Name: Microsoft® Windows ...

hi,

seem it work :) setup.exe now installed fine from image captured using:

wimlib-imagex capture /dev/nbd0p2 install.wim "Windows 7 PROFESSIONAL" "Captured using wimlib" --compress=fast --check --flags "Professional" \
--image-property WINDOWS/SYSTEMROOT="WINDOWS" --image-property WINDOWS/ARCH ...

Sure for user friendly way is ideal automatically, but is please possible before you try implement this, try implement (if is easy for you) any user total unfriendly, but working way ? :)

With only one language element is not problem. I have some original "Dell MUI Windows7" (Pro, Home, 32, 64 ...

if capture windows7 installation from hdd to wim (on linux, using wimlib-1.8.3), then is not compatible with windows 7 setup.exe

same problem as here , where you find that setup.exe need defined elements ARCH and SYSTEMROOT (and maybe others missed)...

is please any chance to implement to wimlib ...