Chrome fails to launch on Windows 10
See original GitHub issueSteps to reproduce
- Puppeteer version: 1.5.0
- Platform / OS version: Windows 10 / 1803 / 17692.1004 (Enterprise Insider Preview)
- URLs (if applicable):
- Node.js version: 10.6.0
Repro code:
const puppeteer = require('puppeteer')
async function doIt() {
const browser = await puppeteer.launch()
}
doIt().then(console.log).catch(console.log)
The result is below error:
{ Error: spawn UNKNOWN
at ChildProcess.spawn (internal/child_process.js:357:11)
at Object.spawn (child_process.js:528:9)
at Function.launch (c:\Users\z\source\repos\p\node_modules\puppeteer\lib\Launcher.js:116:40) errno: 'UNKNOWN', code: 'UNKNOWN', syscall: 'spawn' }
Windows Event Log contains below helpfull message:
Activation context generation failed for "c:\Users\z\source\repos\p\node_modules\puppeteer\.local-chromium\win64-564778\chrome-win32\chrome.exe".
Dependent Assembly 69.0.3452.0,language="*",type="win32",version="69.0.3452.0" could not be found. Please use sxstrace.exe for detailed diagnosis.
Is this something that’s related to the Windows 10 box being on an insider release?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Fix Chrome won't open or launch on Windows 11/10 PC
Fix Chrome won't open on Windows PC · Kill Chrome from Task Manager · Check if your Antivirus is blocking Chrome · Repair...
Read more >Chrome won't open in Windows 10 - Google Support
Very simple solution: Uninstall Chrome and install Firefox. Otherwise, when you see a 45 step procedure to get a browser working, you're basically...
Read more >Fix: Chrome won't open in Windows 10 / 11 - The Geek Page
Fix: Chrome won't open in Windows 10 / 11 · Fix-1 Disable Full screen Optimization · Fix-2 Run Chrome in compatibility mode ·...
Read more >FIX: Chrome Won't Open in Windows 10/11 - wintips.org
How to FIX: Chrome Won't open or Running only in Background on Windows 10/11. · Reinstall Chrome. · Change Chrome Compatibility Mode. ·...
Read more >Top 8 Fixes for Chrome Not Opening on Windows 10
1. Restart Computer · 2. Set Correct Date and Time · 3. Reinstall Chrome · 4. Rename Chrome Icon · 5. Change Compatibility...
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
Alot of folks seem to be having issues with Windows 10 etc. would be nice if the issues were prioritized instead of tickets being closed
I run this program https://github.com/GoogleChrome/puppeteer/blob/master/docs/api.md#pagetitle} (Windows 10 machine, fresh boot with no other Chrome instances started. Latest versions of Node and Puppeteer.)
The first time it runs fine, and maybe a second time. But afterwords I get this error:
(node:5152) UnhandledPromiseRejectionWarning: Error: Failed to launch chrome!
TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md at onClose (C:\Users.…\node_modules\puppeteer\lib\Launcher.js:339:14) at ChildProcess.helper.addEventListener (C:\Users.…\node_modules\puppeteer\lib\Launcher.js:329:60) at ChildProcess.emit (events.js:187:15) at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12) (node:5152) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:5152) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.