Slimming down Build too Boot from 1GB

So i did some test the smallest i can get windows core only is 500 530 MB give or take.

I can of course use WinxShell. But lets say i want full windows but to slim it down. how can i exclude things from build? is it possible to get it any smaller.

Hi, Bigbadmoshe
I don't know what features you want except change WinXShell => Windows Explorer.

boot.wim(windows explorer)
Windows\explorer.exe         +4.2MB +1.8MB
Windows\System32\CatRoot      +22MB  +12MB
Windows\System32\config       +24MB   +5MB
Windows\System32\*.dll       +125MB  +42MB

increase wim size 70MB

boot.wim(WinXShell)
Windows\WinXShell.exe          +3MB +1.2MB
Windows\System32\CatRoot       +0MB    0MB(default winre.wim)
Windows\System32\config        +0MB    0MB(default winre.wim)
Windows\System32\*.dll         +0MB    0MB(default winre.wim)

increase wim size <5MB


if you want slim down, you need disable other features. Change to windows explorer will only increase the size.

windows core, full windows means normal windows 10? windows server 2019? or PE?
not clearly.

I saw <100MB, 200MB, 300MB PEs with Windows Explorer. The size slimed down has no relation with WinXShell.
use WinXShell will be even smaller.

My final build is 842 MB and wont run on hyper-v with less than 2 GB ram.

Cache size of 512 or 1024

I have 3 settings enable. and default build type

WoW64 - Switch to Admin - IE 11

Added Drivers 17 MB
Program Files 352 MB
Windows 1.6 GB

How can i slim down the windows folder so that i can load it in 1 GB of ram.

PS. I know i can use Programs on USB/DVD but i am having issues with the tools that i use to boot getting it to work.

Old post may give some ideas
http://theoven.org/index.php?topic=834.msg10609#msg10609
-》
Try maximum compression to get smallest possible wim with Win10XPE
This may get you boot..
+
If not enough do some delete before wim pack
+
Using enu source will get smallest wim

****
I understand what you are after but
Topic title give wrong impression like  WinxShell causing too much size.
As Slore wrote, WinxShell do not cause a significant size increase.

+
Use smallest size at fbwf setting.
 

Edit:
Thanks for updating topic title

Use smallest size at fbwf setting.

Sorry lost me there :)

WoW64 - Switch to Admin - IE 11

Use x86 Source, as the x86 files tend to be smaller in size

Use smallest size at fbwf setting.

Sorry lost me there :)

Using
Ctrl+F
On tutorial and faq topics useful.

Ctrl+F --> fbwf

http://theoven.org/index.php?topic=834.msg10611#msg10611

I do not know exact place of this option or setting  on Win10XPE, idea same.

Just an idea:

If You can remove fbwf completely,
(I guess only deleting fbwf.sys enough ?)
On such case use a very small RamDrive (imdisk) with temp folder on ramdrive ( eg B:\Temp) to get things work fine.

Ps:
I do not know exact place of this option or setting  on Win10XPE to do above, idea same since Gena and SE
-->
If you lost me again, further follow James instructions.

FBWF is controlled by the registry in the latest versions of Win10PE.

Use (For minimal RAM requirements):
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\FBWF,WinPECacheThreshold,512

However this does not change the uncompressed size of your WIM, only the amount of extra space on X:\ when booted.

Hi Bob.Omb

Fbwf always controled by registry so far I know ( since pe1 Gena)
Only patch required to increase limits ?

Correct me If I am wrong...
( I never dig deep about latest fbwf but made a lot of test to check upper limit and compression in the past )

*
I guess lowest limit is 64 ?

RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\FBWF,WinPECacheThreshold,64

Lowest value would be better to boot with 1 GB.ram
(to be sure fbwf do not cause failure at boot when value is not available on ram
+windows also needs ram to operate which is more important )

Maybe lowest limit also changed since I last look ?

*
Let me know If I miss something.

From what I know, it used to be supported in the registry, then was not.  And now it is supported again. I know registry didnt work for 1607/1703. You would need custom FBWF.cfg for them.

Thanks bob.omb

I guess I figure out after same search.

paying price not related to core stuff....

And now it is supported again.

Good, I hope using a low WinPECacheThreshold value like 32 or 64 get Bigbadmoshe boot. 

(@Bigbadmoshe, In case required also test other values starting from lowest 32 to 64 96 128 160 ....)

*

However this does not change the uncompressed size of your WIM, only the amount of extra space on X:\ when booted.

I do not know if:
booting from wim uncompressed to ram
or
booting from wim put wim to memory and use from there (staying compressed small size)

ms made lots of development for phones & tablets that have low space or memory, I thought 2nd should be the case, I may be wrong.

Anyway... I guess lots of things now at Bigbadmoshe to test....

Setting a registry value of 128 yielded a 400MB size X on x64 test Build this morning

Setting a registry value of 128 yielded a 400MB size X on x64 test Build this morning

I was able to get with a clean no options checked 460 MB boot.wim.

how did you get 400?

That 400MB is the FBWF  Memory Cache Minimum size (I was able to obtain via registry value tested)  - Not Boot.wim Size...

Remember you are trying to get Under 2GB due to Available Memory...

Recording the Target Folder Size (Boot.wim Expanded) plus the Memory Cache needs to be less than 2GB

As Lance suggested - you may be able to still decrease Memory Ram Cache size

If You can remove fbwf completely,
(I guess only deleting fbwf.sys enough ?)
On such case use a very small RamDrive (imdisk) with temp folder on ramdrive ( eg B:\Temp) to get things work fine.

This is all about Extra Memory Available to System AFTER loading the Boot.wim into Memory..
So you goal is to reduce the TARGET folder size (Note: x86 Files are smaller in size)

Also Note If loading Drivers from a folder on Y - they are loaded (Expanded) into Memory TOO...

That 400MB is the FBWF  Memory Cache Minimum size (I was able to obtain via registry value tested)  - Not Boot.wim Size...

Remember you are trying to get Under 2GB due to Available Memory...

Recording the Target Folder Size (Boot.wim Expanded) plus the Memory Cache needs to be less than 2GB

As Lance suggested - you may be able to still decrease Memory Ram Cache size

If You can remove fbwf completely,
(I guess only deleting fbwf.sys enough ?)
On such case use a very small RamDrive (imdisk) with temp folder on ramdrive ( eg B:\Temp) to get things work fine.

This is all about Extra Memory Available to System AFTER loading the Boot.wim into Memory..
So you goal is to reduce the TARGET folder size (Note: x86 Files are smaller in size)

Also Note If loading Drivers from a folder on Y - they are loaded (Expanded) into Memory TOO...

So i will be honest. This goes way beyond my understanding.

If i change the WinPE Cache size in build core, this is not what you are referring to?

I am going to read up more on FBWF.

WinPE Cache size + Expanded Boot.wim
Has to be less than 2GB

The Smallest WinPE Cache size - I was able to Get was 400MB with a tested (WinPE Cache size) Registry value of 128MB
Thus if you use RamDisk instead of WinPE Cache size (FBWF) you could reduce Memory cache a little more...
But, we are only talking a few MB reduction here

So not sure if anyone cares.

Using x86 total iso is 560 MB. 512 cache size boots fine into hyper-v with 1GB.

Of course have removed many many extras so it's a bare bones pe.

I am so interested in how Sergei is able to make boot.wim files of less than 400MB.

Sergei probably only uses a part of boot.wim (or winre.wim)
A bit like it is done in PESE with the Standard file copy...

Win10XPE uses the full Winre.wim with lightweight WinSxS and some language folders deleted.
thus, It preserves all functionality including for example Refresh your PC...

I gave up on the (lightened) Standard file copy in XPE.
It is too much work to find the new files to include, delete old ones, and to check again and again all the features, each time Windows is updated, every 6 months.
It is safer with the full light winre.wim and by trusting the work done by Microsoft.
Also, $MS has progressed well since windows 7, they have the expertise, and the original boot.wim (or winre.wim) is getting better and better.

All the projects around, have probably also helped to make them better 
I haven't been contacted "directly", except by the anti-piracy team
But it would be a pleasure and I am open to participate in some tasks, when they want and will need it.