Win7 x64 SP1 without WinSXS = installation failed?

[Rck]

Hello guys,

I'm using licenced NTLite to customize Win10 ISO without any problem since years, and I would like to come back to Win7 world
However, it seems I'm blocked when I want to remove the WinSXS component from Win7 :

• I'm customizing official msdn "en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso"
  SHA-1 = 0bcfc54019ea175b1ee51f6d2b207a3d14dd2b58
  https://archive.org/details/win7-pro-sp1-english
• I'm using NTLite 2025.8.10552 (64 bit) on one Win10x64 host to open > install.wim > 3. Windows 7 Professional image
• I only remove the component WinSXS:
  
  
• I apply the modification to the image:
  
  
• When testing the iso, Windows could not be installed on a simple VM (bios MBR + hdd SATA):
  

What I'm missing ?
In my memory, this simple task was working fine a few years ago !

 

[tistou77]

At this point normally, it's not install.wim that's the problem, but boot.wim
Maybe missing drivers to integrate into boot.wim (index 2)

 

[garlin]

The last step WinPE Setup does before exiting, is run "bcdboot C:\Windows /s C:"

When that fails, it's normally caused by a storage driver conflict. Check if you have the right RAID (RST) or SATA driver added to both boot.wim & install.wim images.

 

[Rck]

Hi guys, thanks for replying!

When I'm testing the original en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso into the same VM, I don't have any problem to install windows, so original boot.wim + install.wim are fine with my environement test.
The only modification I made with NTLite is removing WinSXS from install.wim, how can it break book.wim ?

 

[tistou77]

Are you getting an error when installing on a VM or a "physical partition" ?
If it's on a partition, then you may be getting an error that you don't encounter in a VM.
We've already encountered this "problem" with nuhi, where it was fine on a VM but it bugged with a classic installation (not yours, but others).

If it's also on a VM, then it's weird but it's been a very long time since I tested W7

 

[g-force]

I only remove the component WinSXS:
View attachment 14804

Could you explain why you remove that component? It`ll break any later updates, i don`t see any advantage.

 

[tistou77]

Could you explain why you remove that component? It`ll break any later updates, i don`t see any advantage.

If you don't use WU, remove updates under Windows, etc... for example

 

[Rck]

Are you getting an error when installing on a VM or a "physical partition" ?
If it's on a partition, then you may be getting an error that you don't encounter in a VM.
We've already encountered this "problem" with nuhi, where it was fine on a VM but it bugged with a classic installation (not yours, but others).

If it's also on a VM, then it's weird but it's been a very long time since I tested W7

Yes, it's a very simple VM under proxmox with config like this:

boot: order=sata0;ide2
cores: 2
cpu: host
ide2: team:iso/W7.iso,media=cdrom,size=3944256K
keyboard: fr
machine: pc-i440fx-7.2
memory: 2048
name: W7
net0: virtio=00:00:99:00:00:94,bridge=vmbr0
numa: 0
onboot: 0
ostype: win7
sata0: local-lvm:vm-9994-disk-0,cache=unsafe,discard=on,size=30G
scsihw: virtio-scsi-single
sockets: 1
tablet: 0
vga: std,memory=32

And I got "zero" problem when using the original msdn ISO i want to tune for my VM

 

[Rck]

Could you explain why you remove that component? It`ll break any later updates, i don`t see any advantage.

Yes I know, my goal is to create a Win7 VM image with minimal hard drive footprint and just a few services, so I will also remove a lot more component (like windows update) after I sort this WinSXS removing problem. (problem only occurs with Win7, on Win10 it's working perfectly)

 

[tistou77]

And I got "zero" problem when using the original msdn ISO i want to tune for my VM

When you delete the component, what folders remain in the WinSxS directory ?
Some are mandatory for installation, I don't think it is removed but just in case

 

[Rck]

When you delete the component, what folders remain in the WinSxS directory ?
Some are mandatory for installation, I don't think it is removed but just in case

Good suggestion!
When I open install.wim on the original ISO and check into %temp%\NLTmpMnt\Windows\winsxs, I got 9956 root folders (folder properties = 40108 files, 10062 folders):


After the WinSXS removal, and Apply > Stop before saving image


I got 711 root folders (folder properties = 19607 files, 817 folders):


So it's not empty, but maybe something is missing there, don't know, maybe I could explore some windows logs when installing to find what is failing, but there are not easy to read.

Maybe you can try on your side with the msdn Win7 iso and check if you have the same problem ?
https://archive.org/details/win7-pro-sp1-english

 

[tistou77]

I could test that tomorrow evening, otherwise I don't see the Catalogs directory in your screens, it's empty but mandatory for the installation for example

 

[g-force]

I created some Win7-ISO, you`ll find them on my homeserver: [REDACTED]

Mod note: Per forum rules, links to private ISO's are not allowed. You may DM to individual users, but not post them in threads.

 

[Rck]

I could test that tomorrow evening, otherwise I don't see the Catalogs directory in your screens, it's empty but mandatory for the installation for example

Okay, I promise I did'nt delete it manually
Is there any way to test old version of NTLite without bothering Nuhi ?

 

[Rck]

Mod note: Per forum rules, links to private ISO's are not allowed. You may DM to individual users, but not post them in threads.

@Mod:
Is my link to msdn win7 iso at archive.org was okay ?

g-force:
do you mean you where able to just remove WinSXS from one of your win7 iso and it was installing fine on a VM ? if yes, what version of NTLite are you using ?

 

[garlin]

Okay, I promise I did'nt delete them manually
Is there any way to test old version of NTLite without bothering Nuhi ?

You can use archive.org to search for older NTLite downloads.
https://web.archive.org/web/20250000000000*/https://www.ntlite.com/download/

@Mod:
Is my link to msdn win7 iso at archive.org was okay ?

It's tolerated as long as the ISO is presumably an unmodified image (especially for older Windows which have disappeared from MS servers). But unless you have a verified checksum, it's on your own risk to download it.

Checksums are easy to find for English (US) versions, but harder for the other language editions.

 

[Rck]

You can use archive.org to search for older NTLite downloads.
https://web.archive.org/web/20250000000000*/https://www.ntlite.com/download/

Thanks for the tips Garlin !
I could dive into this if I'm alone with this problem.

It's tolerated as long as the ISO is presumably an unmodified image (especially for older Windows which have disappeared from MS servers). But unless you have a verified checksum, it's on your own risk to download it.

Checksums are easy to find for English (US) versions, but harder for the other language editions.

Fine, that's why I give the SHA-1 of the official msdn EN iso I want to tune
https://archive.org/details/win7-pro-sp1-english

• "en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso"
  SHA-1 = 0bcfc54019ea175b1ee51f6d2b207a3d14dd2b58

 

[tistou77]

Just tested with NTLite, the necessary folders in WinSxS are present.
If I have time tonight, I'll try to install it (but not in a VM, on a dedicated partition).

 

[Rck]

Just tested with NTLite, the necessary folders in WinSxS are present.
If I have time tonight, I'll try to install it (but not in a VM, on a dedicated partition).

Thanks for testing Tistou !

Q1: did you use the same ISO ? (SHA-1 = 0bcfc54019ea175b1ee51f6d2b207a3d14dd2b58)
Q2: could you check the properties of %temp%\NLTmpMnt\Windows\winsxs folder ? (we should have the same number of files)

• before applying change: winsxs folder properties = 40108 files, 10062 folders
• after applying change: winsxs folder properties = 19607 files, 817 folders

 

[tistou77]

Thanks for testing Tistou !

Q1: did you use the same ISO ? (SHA-1 = 0bcfc54019ea175b1ee51f6d2b207a3d14dd2b58)
Q2: could you check the properties of %temp%\NLTmpMnt\Windows\winsxs folder ? (we should have the same number of files)

• before applying change: winsxs folder properties = 40108 files, 10062 folders
• after applying change: winsxs folder properties = 19607 files, 817 folders

Used the ISO from your link
And like you, same number of files and folders after deletion