This message was deleted.

Sounds like a race condition of the policies landing and Edge wanting to load them before the IE mode settings land

I have the same thought. The thing is if the page times out and I don’t refresh it, but close Edge, the same problem occurs the next time I open the app. You would think all GPOs are applied at that point. I need a successful page load for all future page loads to work.

We don't publish Edge... but use IE Mode on our single session desktops. I think our Edge config is on logon, not at app launch due to other race conditions when we tried at launch (Ivanti Workspace Control).

It is maddening. I have a LOB app that requires the latest version of Edge running on the latest versions of W10 or Server 2022. We didn’t have Server 2022 deployed at the time so to facilitate the need I created W10 machines and hung Edge as a published app off them. I wanted to blame the problem on that, but Server 2022 does the same thing. I’m going to try your idea and publishing my intranet. After the intranet loads, can I paste in the LOB app and have it load.

is it impacting all users?

All new user profiles to the published app W10 machines, yes.

Not a real solution but a work around. May need to test. You could do an application prefetch. Which will load it in the background. Use a startup script. start edge.exe or msedge.exe" -- timeout /t 1 taskkill /IM edge.exe or msedge.exe" -- timeout /t 1 Just a work around

I got this to work. My proxy settings are set via GPP user registry entries. You know, things under HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings. For some strange reason on a new profile, publishing Edge just ignores these keys. Edge has it's own proxy GPOs and I'll need to test if they can replace the classic IE registry entries. Anyway, my fix was to include ""--proxy-server="http://proxyaddress:8080" in the command line arguments for my Edge published app. My goal was to have Edge open and go directly to an external website. Including the proxy parameter in the command arguments allows Edge to find the proxy.

Nice! Thanks for the follow-up with the fix Matt.