This message was deleted.

You can remove edge from the os layer but its a hack. You have to disable all the edgeupdate scheduled tasks in the os layer and after every time you patch or run edgeupdate you need to check to make sure they didnt create new scheduled tasks. I have seen some use a script to check for any edge scheduled tasks and disable them. https://support.citrix.com/article/CTX399422/app-layering-how-to-configure-edge-in-an-app-layering-environment

FWIW, here's my install script for Edge that I used in my OS layer:

$var_Install_Exec = "msiexec.exe"
$var_Install_Arg = "/i MicrosoftEdgeEnterpriseX64.msi DONOTCREATEDESKTOPSHORTCUT=TRUE DONOTCREATETASKBARSHORTCUT=TRUE /qn"

$proc = Start-Process -FilePath $var_Install_Exec -ArgumentList $var_Install_Arg -WorkingDirectory $PSScriptRoot -Wait -PassThru

Remove-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Active Setup\Installed Components\{9459C573-B17A-45AE-9F64-1857B5D58CEE}" -Name "StubPath" -Force

#Fixing the Microsoft Edge tile background color so that it matches the other Windows 10 tiles
Remove-Item "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.VisualElementsManifest.xml" -Force
$Shell = New-Object -ComObject ("WScript.Shell")
$Shortcut = $Shell.CreateShortcut("C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Edge.lnk")
$Shortcut.IconLocation = "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe";
$Shortcut.Save()

Get-ScheduledTask -TaskName MicrosoftEdgeUpdate* | Disable-ScheduledTask | Out-Null

$Services = "edgeupdate","edgeupdatem","MicrosoftEdgeElevationService"
ForEach ($Service in $Services){
	Set-Service -Name $Service -StartupType Disabled
	Stop-Service -Name $Service -Force
}

This prevented me from having to worry about Edge updating in another layer.

@Rob Zylowski Thank you, I will have a read 🙂 @Nick Panaccio I don't actually mind, Edge being update, in another layer. My main issue is, that when i update edge in my OS layer, to get the newest edge. Then an app or platform layer, which was installed based on an os layer, with an older version of edge, then the old version form platform/app takes precedence for the executable file (C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe), all the available versions are listed (C:\Program Files (x86)\Microsoft\Edge\Application\110.0.1587.69). But its not the newest version, that is chosen as the primary executable.

Thats why you need to worry about edge leaking into other layers. You absolute cant have that it means you have to throw away the other layer and rebuild without Edge. Nicks script is a great way to ensure you are ok.

@Rob Zylowski I have 2 questions, we actually are in this situation edge leaked into other layers.. Is there a way to identify which layer is affected with a script/utility? Initially Edge WebView wasn't in our OS layer, with citrix workspace app in our platform layer it got installed there and also in the microsoft 365 layer. The platform layer having the highest priority, it should use Edge WebView in it? Now it't not the case, we have a really old version used instead of the latest

The only way to figure out which layer is at fault is to copy the layer .vhdx file from the ELM to another server, mount it, and check for that folder. I used to have to do this for both Edge and OneDrive in the past.

Good thank you!