Merits of removing Edge to save 400MB on image, and then using post install command to install it

C

chrcol

Member
Messages
193
Reaction score
19
I already have a command I run which updates it, I dont understand the logic of Microsoft including an out of date bloated browser on the install image when almost the whole thing is replaced on its first update, so seems an easy win unless... removing edge has consequences?

So long as I keep edgeupdate component, I should be ok?

Command below.

Code: 
Start-Process -FilePath "C:\Program Files (x86)\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe" -argumentlist "/silent /install appguid={56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}&appname=Microsoft%20Edge&needsadmin=True"
 
I completely remove Edge (and all its components) in the image and then install the latest version.
 
So edge update depends on edge, how are you managing to install the latest without edge update?
 
I just tried with 'winget install -e --id Microsoft.Edge' which seems to work as well, I uninstalled from programs and features, then used the winget command it keeps it in same install location as well.
 
chrcol said:
I already have a command I run which updates it, I dont understand the logic of Microsoft including an out of date bloated browser on the install image when almost the whole thing is replaced on its first update, so seems an easy win unless... removing edge has consequences?
Click to expand...
Windows includes a (now stale) static copy of Edge.wim to guarantee there's some Edge browser to begin with. If you didn't update the ISO, and lacked any outside network connection then you would still have a default browser.

A browser can still be used for local browsing and WebView2 apps, even when the Internet is blocked. Of course, MS doesn't expect anyone to use this browser build, it's a placeholder like all those outdated default Windows Apps in the image.
 
I have done the change (not yet tested) but not sure if I will keep it as despite ntlite saying 400MB plus 100MB for edge updater, the image was only reduced by about 100MB. I dont know if you know the reason for that, I noticed the summary said it was mostly hardlink removals not file removals.
 
I posted my update in the wrong thread earlier, but I think I have done something wrong. I removed all components with webview in the name, edge and edge updater. But it yielded a tiny size reduction on the ISO, it was almost all hardlinks only, not actual removed files. So for now I have reversed it as the added complexity for such a tiny saving doesnt seem worth it, but I have a gut feeling there is something I dont understand here, and there is likely a simple fix for a much larger reduction on the ISO.
 
Some components take up much more space (winsxs component, eg)
For example, one of my images (with many components removed, such as WU, Defender, etc.) is 1.28 GB in size
Install.wim is 0,99 GB
And another one for games is a bit bigger.
 
Yes, but the issue is that for the components I removed ntlite had it at circa 1 gig for all of them combined, but when I processed it, it was just hardlink removals, hardly any files were actually removed from the ISO.

400MB for edge
100MB for edge update
and another 400MB for webview.

But it only went down by 12MB.
 
chrcol said:
But it only went down by 12MB.
Click to expand...
The image?
That might be normal, it's the size within Windows, the image is "compressed" (install.wim)
On my test partition, install.wim is just over 1 GB, and the Windows installation is a little over 3 GB.
 
I came across a post a couple of days ago on the forum, which I think provides the answer, but I welcome to be corrected.

It seems if SxS (servicing stack?) is not also removed from compatibility, then to make sure nothing breaks Ntlite wont do a deep clean on the ISO. Space saving is only post install. I hope i understand that right.

But if I toggle that flag, I risk breaking windows update, package management. So I will leave it as it is.
 
You can safely remove the "Manifest Backup" component, it consists of backups of certain files.
It is the "Windows Component Store" that you need to keep for that
 
You must log in or register to reply here.
Back
Top