Puppeteer fails to launch on Windows

[szmarczak]

Steps to reproduce

• Puppeteer version: 1.12.2
• Platform / OS version: Windows 10 / 1809
• Node.js version: v11.6.0

1. await puppeteer.launch()

  Error {
    code: 'UNKNOWN',
    errno: 'UNKNOWN',
    syscall: 'spawn',
    message: 'spawn UNKNOWN',
  }

2. Running chrome.exe manually

The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.

I'm not sure this is a Puppeteer/Chromium bug

click the GIF to zoom

Make sure to watch the whole GIF till the end.

Sometimes if I copy chrome-win manually into node_modules\puppeteer\.local-chromium\win64-624492 I get that error too. So I believe its Windows fault, just not sure what to do with such information... This occurs randomly.

[szmarczak]

If someone wonders if my SSD is broken, the answer is no.

[szmarczak]

Indeed a Windows bug. Running md5sum * will show identical sums.

[szmarczak]

If you extract it and compress it again, it will show even different sums! :O Not sure what is happening.

[meotimdihia]

It always happen for me.

[szmarczak]

@meotimdihia Can you please try downloading chromium from https://download-chromium.appspot.com/ and extract it directly at .local-chromium/win64-n/chrome-win? (remember to rename the old chrome-win before)

[aslushnikov]

Let keep this closed - there's nothing we can do regarding this on Puppeteer-side.

Feel free to keep discussion going though.

[meotimdihia]

@szmarczak I downloaded your link, run it and the same alert appear.

[szmarczak]

@meotimdiha Did you try unpacking it on desktop?

[meotimdihia]

@szmarczak my mistake, I just try to unzip and run chrome.exe, and chromium is work with no problem.

I replace .local-chromium/win64-n/chrome-win and run my code: everything is work too.

[meotimdihia]

[Volune]

Don't know if it's related to the initial issue or not, but having the same problem (same error from chrome.exe), I realized in my case it is caused by the project folder having the case sensitive attribute enabled.

Fixed it by running fsutil.exe file setCaseSensitiveInfo . disable in the project folder, then reinstalling dependencies

[szmarczak]

I'll let you know in a few days if that works for me. Not at home ATM.

[szmarczak]

@Volune Indeed, your fix works! Thank you very much ❤️

@aslushnikov Can you reopen this issue as it can be fixed on Puppeteer side? Just run the command on the node_modules/pupeteer folder before Chromium installation.

[Nicofisi]

@Volune that did the trick, thank you!

Just make sure to remove the entire node_modules folder first (or run the command inside that folder I guess). I tried only running yarn remove puppeteer, then the command, then yarn add puppeteer and it didn't work, probably because the attribute was still set on node_modules.

Would be lovely to do something with this automatically though.