Release v1.0.1 / 5.55.1 (pre-release)

[DavidXanatos]

This build fixes bugs introduced in the last pre-release build

Known Issues

• printing does not work, will be fixed in the next release

If you have issues with an update installation, just uninstall the previous version keeping the sandboxie.ini and reinstall the new build.

You can support the project through donations, any help will be greatly appreciated.

Changelog

Added

• added checkboxes to most major box options lists
• added SumatraPDF templates (by Dyras) #1391

Changed

• rolled back change to "OpenClsid=..." handling
• made all major lists in the box options editable

Fixed

• fixed issue with read only paths introduced in 1.0.0
• fixed BSOD issue introduced in the 1.0.0 build #1389
• fixed multiple BITS notifications while running sandboxed Chromium browsers (by isaak654) ca320ec #1081
• fixed executables selection for "Run Menu" entries (by isaak654) #1379
• fixed SetCursorPos and ClipCursor ignoring DPI awareness (by alvinhochun) #1394

Removed

• removed Virtual Desktop Manager template (by isaak654) d775807 #1326

---

This discussion was created from the release Release v1.0.1 / 5.55.1.

[BilleBarrett]

I waited to start upgrading my clients to the latest Sandboxie and the problem started.
This is a major problem, my clients are calling me telling me that they can no longer print Gmails, or documents from inside Google chrome
I changed from Classic to Plus and the problem persists,
please advise
Right now they have to use print to PDF and save the PDF and then print that.
Everyone wants to revert back to the Sandboxie that this does not happen in
note: if I run outside of Sandboxie printing is no problem.
Ran a test, monitoring the Spool folder, I see the print data getting sent into the Print spooler, & it just sits there
I check the spool service is running, it is run the same outside of Sandboxie [clasic or Plus] it gets sent to the spool folder and then to the printer.
It seems something is stopping the handoff
For some reason my computer does not do this, I see the spool file get the print job & then it goes to the printer
Why is this not happening to my client's computers?
I also noted is supposed to be set in the INI file
OpenPrintSpooler=y
AllowSpoolerPrintToFile=y

[isaak654]

The printing issue will be fixed in the next version:

• [1.0.0/1.0.1] Unable to print while sandboxed #1397
• https://www.wilderssecurity.com/threads/cannot-print.442353/#post-3055618