chrome-launcher: Chrome launches in broken/non-functional state on Windows from Admin console

From @mmanela on August 23, 2017 16:48

This is the same bug reported on karma-chrome-launcher. If you open chrome using the chrome-launcher from an admin process, it open as a “dead” browser tab.

REPRO

Open an admin command prompt (Repro’d on Windows 10.0.15063)
Run Node ( I am using v8.4.0)
let launcher = require('chrome-launcher')
launcher.launch()
Launches dead chrome that is not functional (can’t go to any page)

If I do the same steps from a non-admin command prompt this works.

Copied from original issue: GoogleChrome/lighthouse#3099

About this issue

Original URL
State: open
Created 7 years ago
Reactions: 3
Comments: 24 (8 by maintainers)

Most upvoted comments

@samccone - Is there any update on this issue? I’m still seeing it on the most recent versions of Chrome.

I see this behavior when launching from VSCode as admin, and while I’m able to append --no-sandbox and get it to work, it causes the ominous You are using an unsupported command-line flag: --no-sandbox. Stability and security will suffer. message. Fine in general as a workaround, but if it’s something we’re going to be sharing around to the team it’s nice to not need to explain it to everyone.

veleek on Jun 13, 2019