Windows 11 23H2 getting huge (Edge WebView2)

[abbodi86]

You cannot, only MS can package Edge.wim

 

[OpenSource Ghost]

Not even with online update + SysPrep & Generalize methods? There is at least one custom Win11 ISO with the latest WebView and is listed on the most popular of torrent indexing sites. I don't use such ISO's, but I am curious how the creators accomplishes Edge WebView integration.

It looks like the newest 22.631.2787 build allows for more options for Edge removal based on Region Policy - https://www.neowin.net/guides/here-is-a-simple-method-to-uninstall-edge-in-windows-10-and-11/ .

 

[Pater]

Yes you can include WebView using sysprep, use the evergreen installer to be found here.

 

[OpenSource Ghost]

How to cut out Edge WebView package from WinSxS? It takes some 750MB and is fully removed as actual component.

 

[nuhi]

How to cut out Edge WebView package from WinSxS? It takes some 750MB and is fully removed as actual component.

Please list the folder names that are big, and I'll check.

 

[OpenSource Ghost]

amd64_microsoft-edge-webview_31bf3856ad364e35_10.0.22621.3593_none_72d1c96606549b99

 

[francis11]

Sounds weird.
Only keep these:

View attachment 11958
And WinSxS shows:
View attachment 11959

Remove components in WinSxS will break WU and force you to do a Host Refresh every (½) monthly update.
View attachment 11960

 

[OpenSource Ghost]

I have Edge and Edge WebView removed with "DISM + Custom", leaving only WebView 2 SDK, which is tiny. I don't remove Windows Component Store to preserve file and store integrity. Every image is updated offline and rebased.

 

[nuhi]

amd64_microsoft-edge-webview_31bf3856ad364e35_10.0.22621.3593_none_72d1c96606549b99

Thanks.
Problem is that means they updated it with the latest CU (rev 3593), which means folder should remain in the WinSxS for future updates.
As you know, disable Servicing Stack compatibility before removal triggers WinSxS cleanup and that folder will be gone.

Since you update via rebasing (aka host refresh or in-place upgrade), there is no need to keep update compatibility, I would suggest to disable Servicing Stack compatibility next time and check out the size difference due to WinSxS cleanup.

 

[OpenSource Ghost]

But wouldn't Service Stack compatibility disablement prevent SFC /Scannow and DISM Scanhealth from passing? I need them both to pass integrity checks.

 

[OpenSource Ghost]

NTLite gets rid of the WebView WinSxS package in 26100 just fine, but not 22631.3668.

 

[nuhi]

But wouldn't Service Stack compatibility disablement prevent SFC /Scannow and DISM Scanhealth from passing? I need them both to pass integrity checks.

SFC compatibility option is below Servicing Stack's, you can keep it independently.

As for DISM ScanHealth, that part is more about package upgradability which we would ignore, so if SFC finds files in-place as they are in WinSxS, DISM operability is not a must, as described above for that updating method.

NTLite gets rid of the WebView WinSxS package in 26100 just fine, but not 22631.3668.

Because microsoft-edge-webview is a FoD (feature on demand) in 26100, they moved it as external, meaning on removal WinSxS can be cleaned even if keeping the servicing stack support.