Chrome launches in broken/non-functional state on Windows from Admin console
See original GitHub issueFrom @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
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:24 (8 by maintainers)
Top Results From Across the Web
Manage Chrome browser with Windows device management
Manage Chrome browser with Windows device management · Step 1: Ingest the Chrome ADMX file into your Google Admin console · Step 2:...
Read more >Chrome Canary Features For Developers - Google
Nightly build for developers. Get on the bleeding edge of the web. Be warned: Canary can be unstable. Download Chrome Canary. For Windows...
Read more >Sign up for Chrome Browser Management - Google Accounts
Chrome Browser Cloud Management. Enroll and manage your browsers across Windows, Mac and Linux, right from the Google Admin console.
Read more >Get ChromeOS Flex for PC or Mac - Chrome Enterprise
Use Chrome Enterprise Upgrade to secure and manage them alongside Chromebooks in the cloud-based Google Admin console. Advanced security. Remotely wipe or ...
Read more >How to troubleshoot common problems with Chrome Browser
Learn more about Chrome Browser Cloud Management · Test with the Beta Channel of Chrome · Review the enterprise release notes · Troubleshooting...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub 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.Thanks for the response @samccone. What is the impact of running --no-sandbox ?