[WinNTSetup v5.4.1]

Seems we lost some posts here. Reattach last WimHost fix.

WIMHost_1.0.0.7.zip

[WinNTSetup v5.4.1]

1 hour ago, wuliyen said:

How to keep all files in \Windows\WinSxS\FileMaps?

Not, possible with the WinSxS.ini.

These folder are always deleted:

\Windows\servicing\LCU
\Windows\WinSxS\Temp\InFlight
\Windows\WinSxS\Temp\PendingRenames
\Windows\WinSxS\Backup
\Windows\WinSxS\FileMaps

They should be only needed by Windows Update.
I'll rethink the last 4, maybe add an option for this.

[WinNTSetup v5.4.1]

Yeah, installing optional components isn't supported with default minwin profile.

Replace Tools\x64\WIMHost.exe

If you add a ! at line begin it should keep all version.

 

[WinNTSetup v5.4.1]

The filter

\Windows\WinSxS\Manifests\amd64_microsoft.activedirectory.management_31bf3856ad364e35_10.0.17763.*

matches for both:

\Windows\WinSxS\Manifests\amd64_microsoft.activedirectory.management_31bf3856ad364e35_10.0.17763.1_none_095c3cc5ce4cc481.manifest
\Windows\WinSxS\Manifests\amd64_microsoft.activedirectory.management_31bf3856ad364e35_10.0.17763.1490_none_6621891b47f3382c.manifest

Every wildcard filter will only keep the newest component (17763.1490), all older we be removed.

Whats are you trying to accomplish with all these files?

[WinNTSetup v5.4.1]

2 hours ago, sakatgg said:

Another question, Compact LZX compression does not work on Server 2019, is this how it was designed from the start? Is it possible to enable Compact LZX compression on Server 2019?

Hmm, WimBoot wasn't supported by Server version, so I skipped the the apply modes.
But it seems that Compact mode works. I'll check more Server version and remove this restriction in next version.

 

1 hour ago, click-click said:

If I do that and and try to create another partition, Windows will only recognize the first partition because it sees the flash as a removable disk. Is there a way arround this?

Good, question with Win10/11 this is no longer a problem.
You can try with bootice, it can partition the flash drive with multiple partitions.
It allows you to assign a drive letter to only 1 partition at the time.

Not sure how WinNTSetup's drive letter assignment will behave in this case 
Will have to check this out ...

[WinNTSetup v5.4.1]

Yeah, this is a problem with obsolet version removal.

This filter

\Windows\WinSxS\%ARCH%_microsoft-windows-d..erservice.resources_31bf3856ad364e35_10.0.17763.*_%LANG%_*

matches both, so only one remains.

For now you could solve it with 2 filters:

\Windows\WinSxS\%ARCH%_microsoft-windows-d..erservice.resources_31bf3856ad364e35_10.0.17763.*_%LANG%_3a6bba1e80fb955e*
\Windows\WinSxS\%ARCH%_microsoft-windows-d..erservice.resources_31bf3856ad364e35_10.0.17763.*_%LANG%_7226aa566821f809*

 

[WinNTSetup v5.4.1]

You should format the boot partition with FAT32, not the entire disk.

create a small let's say 500 MB FAT32 partition for the boot files and use the remaining space as you want

[WinNTSetup v5.4.1]

If you use NTFS, there properly no option unless this UEFI supports NTFS.

[WinNTSetup v5.4.1]

2 hours ago, click-click said:

I'm still somewhat confused how the BIOS option ALL in WinNTSetup is supposed to work.

The "ALL" is just passed to bcdboot.exe, which than creates BIOS and UEFI boot files.
If it does not boot in UEFI mode, than either the boot partition is ignored (maybe it's NTFS) 
or the UEFI is a bit picky and does not look for the EFI boot loader on a MBR disk.

If the UEFI allows it, try to start the loader manually: \EFI\Boot\bootx64.efi

 

@dimo70
Yes just use WinNTSetup to apply the backuped WIM, it will change drive letter assignment and create a new boot entry.

[WinNTSetup v5.4.1]

@dimo70 Don't merge the old x86 version into the same folder with newer x64 one.
They have different folder layout, so there will be problems.

 

[WinNTSetup v5.4.1]

Yes, with your BCD it actually should show the new menu.

Reproduced! Seems there is a difference with bootems that also effects menu style.

bcdedit -set {emssettings} bootems No

 

[WinNTSetup v5.4.1]

You still have 3 lines: "bootmenupolicy          Standard"
that you should change to: "bootmenupolicy          Legacy"

If you don't want to do it with bootice than use bcdedit

bcdedit -set {current} bootmenupolicy Legacy
bcdedit -set {b2c1b3c3-8029-11ee-a83b-c85b76503892} bootmenupolicy Legacy
bcdedit -set {5070e151-81b7-11ee-a844-c85b76503892} bootmenupolicy Legacy

 

@sharicov@gmail.com
There is MinWin if you left click on "Mode" label. That let's you create a minimal windows.
The other 2 features make no sense. First OS than create boot files.

If you already have some VHD's mount them and use BCDBoot.exe to create boot files.
Or use WinNTSetup and leave the source combo box empty while
selecting boot partition and the mounted VHD.

[WinNTSetup v5.4.1]

Usually the default selection is the one were bootmenupolicy is relevant.
Post the BCD here:

bcdedit > BCD.txt

 

[WinNTSetup v5.4.1]

You make the whole thing complicated.
What do you mean with volume BCD. You should have one on your physical disk's boot partition
and another one inside the VHD.

If you physical boot the VHD, than one of your physical disk is used.
if you attach the VHD to a virtual machine, than the BCD inside is used.

[WinNTSetup v5.4.1]

Use Professional mode, than right click create and add new element if it does not already exists.

[WinNTSetup v5.4.1]

You can use bootice to set BootMenuPolicy to legacy for every boot option.

But make sure you also disable fastboot for every system,
cause this is there reason for these additional reboots (making a clean shutdown).

[WinNTSetup v5.4.1]

Yes, I file backed copy is slow. Sadly wimlib only uses 1 thread to do the apply stuff.
Volume copy mode, runs on the max speed of your hardware, but if the destination drive is smaller
there is no guarantee that it will work. the last cluster have to fit into the new partition.

Even the shrink option may not be able to move some system files.

[WinNTSetup v5.4.1]

Maybe you use Windows 7 or some other old OS, here?

By default WinCopy uses a wimlib capture and apply, but without actually creating a WIM file.
So yes, WimScript.ini is needed and if not set by command line, that the default one is used.

Not sure what problem wimlib has, that error codes could be during scan and apply.
I uploaded a "b" version that will add wimlib error file to the console output.

Anyway you could also try volume mode of WinCopy by adding "-volume" to the command line.

[WinNTSetup v5.4.1]

WinNTSetup_x64.exe wincopy-cli S: T:

S: - source drive
T: - target drive

[WinNTSetup v5.4.1]

Yeah, Disk2VHD is properly only thought to copy entire disk and boot it in a VM.

Also be careful with creating a VHD entry with bootice, that's not fully supported, better mount and use bcdboot for it.

WinNTSetup's Wincopy should do what you want.

[WinNTSetup v5.4.1]

Uploaded a fix version, the RunAsTI ini option should not be needed anymore.

[WinNTSetup v5.4.1]

Would call that a lazy question, took just 5 minutes to try and verify that it boots normally.

[WinNTSetup v5.4.1]

There is nothing to worry about.
WinNTSetup just check if the target partition has the set FILE_ATTRIBUTE_NOT_CONTENT_INDEXED.
That is what the last checkbox of drive properties (if unchecked) means.

Only in that case, WinNTSetup will inherit FILE_ATTRIBUTE_NOT_CONTENT_INDEXED to all files and folder,
that will be applied from the wim/esd file.

[WinNTSetup v5.4.1]

The RunAsTI problem will be fixed.

Are you sure the second problem isn't caused by this NTLite source?
Please post the log file H:\Windows\Logs\WinNTSetup\*\WinNTSetup.log

And what happens if you manually run bcdboot.exe?

bcdboot H:\Windows /s H: /f BIOS

[WinNTSetup v5.4.1]

Good, I will add a fallback for RunAsTI setting.

About the crash, is there anything in windows eventlog?