Edge running on Server 2019 automatically elevates itself which prevents me from signing in

%3CLINGO-SUB%20id%3D%22lingo-sub-1278289%22%20slang%3D%22en-US%22%3EEdge%20running%20on%20Server%202019%20automatically%20elevates%20itself%20which%20prevents%20me%20from%20signing%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1278289%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20currently%20setting%20up%20a%20new%20Server%202019%20RDS%20server%20to%20replace%20our%20old%20Server%202012%20R2%20server%20and%20I%20want%20to%20set%20up%20Edge%20as%20our%20main%20browser%20in%20case%20that%20we%20want%20to%20browse%20the%20internet.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20ran%20the%20latest%20stable%20installer%20and%20everything%20works%20fine%20except%20that%20Edge%20doesn't%20allow%20me%20to%20sign%20in%20because%20it%20somehow%20automatically%20elevates%20itself%20when%20launched%20on%20the%20new%20Server%202019%20RDS%20and%20keeps%20complaining%20that%20%22Sign%20in%20is%20not%20supported%20when%20running%20Microsoft%20Edge%20as%20an%20administrator.%20Please%20relaunch%20Microsoft%20Edge%20as%20a%20non-administrator%20and%20try%20signing%20in%20again.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20accounts%20that%20are%20working%20from%20this%20RDS%20are%20local%20admin%20(it%20acts%20as%20a%20jumphost%20for%20our%20domain%20admins)%20so%20it's%20possible%20to%20run%20Edge%20as%20an%20administrator%2C%20but%20I%20haven't%20configured%20anywhere%20to%20explicitly%20launch%20Edge%20with%20elevated%20permissions.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETrying%20to%20sign%20into%20Edge%20with%20exact%20same%20settings%20(installer%2C%20user%20account%2C%20permissions%2C%20GPO%20settings)%20on%20our%20old%20Server%202012%20R2%20and%20another%20Server%202016%20RDS%20server%20works%20fine%20so%20I%20don't%20understand%20what's%20going%20on%20here.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20also%20tried%20to%20use%20the%20Edge%20server%20beta%2C%20but%20that%20results%20in%20the%20same%20behaviour.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThoughts%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1278337%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20running%20on%20Server%202019%20automatically%20elevates%20itself%20which%20prevents%20me%20from%20signing%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1278337%22%20slang%3D%22en-US%22%3EI%20have%20the%20same%20issues%20on%20Windows%20server%20and%20Windows%20Sandbox%2C%20this%20limitation%20should%20be%20removed%20and%20even%20if%20not%20by%20default%2C%20we%20need%20to%20have%20an%20option%20in%20the%20settings%20to%20remove%20this%20and%20sign%20into%20browser%20even%20with%20Admin%20access.%20Chrome%20and%20Firefox%20both%20allow%20this.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1442695%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20running%20on%20Server%202019%20automatically%20elevates%20itself%20which%20prevents%20me%20from%20signing%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1442695%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F607793%22%20target%3D%22_blank%22%3E%40Skeb1ns%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3ESame%20issue%20here%2C%20but%20we%20are%20logging%20in%20directly%20as%20Domain%20Admins.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1445171%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20running%20on%20Server%202019%20automatically%20elevates%20itself%20which%20prevents%20me%20from%20signing%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1445171%22%20slang%3D%22en-US%22%3E%3CP%3EOh%2C%20this%20is%20bizarre.%20I%20ran%20the%20Compatibility%20Troubleshooter%20and%20that%20actually%20seemed%20to%20make%20this%20work%2C%20but%20then%20I%20got%20this%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22image_001.png%22%20style%3D%22width%3A%20572px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F197011i98752E59393897C2%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22image_001.png%22%20alt%3D%22image_001.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Hi,

 

I'm currently setting up a new Server 2019 RDS server to replace our old Server 2012 R2 server and I want to set up Edge as our main browser in case that we want to browse the internet. 

 

I've ran the latest stable installer and everything works fine except that Edge doesn't allow me to sign in because it somehow automatically elevates itself when launched on the new Server 2019 RDS and keeps complaining that "Sign in is not supported when running Microsoft Edge as an administrator. Please relaunch Microsoft Edge as a non-administrator and try signing in again."

 

The accounts that are working from this RDS are local admin (it acts as a jumphost for our domain admins) so it's possible to run Edge as an administrator, but I haven't configured anywhere to explicitly launch Edge with elevated permissions.

 

Trying to sign into Edge with exact same settings (installer, user account, permissions, GPO settings) on our old Server 2012 R2 and another Server 2016 RDS server works fine so I don't understand what's going on here.

 

I also tried to use the Edge server beta, but that results in the same behaviour.

 

Thoughts?

 

3 Replies
Highlighted
I have the same issues on Windows server and Windows Sandbox, this limitation should be removed and even if not by default, we need to have an option in the settings to remove this and sign into browser even with Admin access. Chrome and Firefox both allow this.
Highlighted

@Skeb1ns 

Same issue here, but we are logging in directly as Domain Admins.

Highlighted

Oh, this is bizarre. I ran the Compatibility Troubleshooter and that actually seemed to make this work, but then I got this:

 

 

image_001.png