Read this if you experience PDF printing hanging on Windows

[OrKoN]

With M125 Chrome uses sandboxes for printing (https://crbug.com/338553158) which may require additional permissions on the Chrome installation folder:

See https://pptr.dev/troubleshooting#chrome-reports-sandbox-errors-on-windows for how to set permissions.

[TiAlRo]

Thanks for this explanation!

Instead of icacls $HOME/.cache/puppeteer/chrome /grant "ALL APPLICATION PACKAGES:(OI)(CI)(RX)", the command should be icacls %USERPROFILE%/.cache/puppeteer/chrome /grant *S-1-15-2-1:(OI)(CI)(RX).

%USERPROFILE% is the Windows equivalent of $HOME and S-1-15-2-1 is the SID – the user friendly name does not work in non-english Windows.

[Mansion-dotcom]

I need

[mariusrak]

Will this be fixed? Could it at least print a warning on installation with link to workaround? Thanks.

[OrKoN]

The fix will be available once Puppeteer ships Chrome 127.

[ako-v]

My puppeteer version is win64-127.0.6533.72, I used icacls $HOME/.cache/puppeteer/chrome /grant "ALL APPLICATION PACKAGES:(OI)(CI)(RX)", nothing changed, and still had this problem!
then I looked at this puppeteer folder, and found another folder named "chrome-headless-shell" so I ran; icacls $env:USERPROFILE/.cache/puppeteer/chrome-headless-shell /grant *S-1-15-2-2":(OI)(CI)(RX)", and now the pdf generation works.