Windows 10 64 bit won't print in Sandboxie v 5.12

[rollrxgirl]

Win 10 x64
Sandboxie 5.12 64 bit
Firefox 48
Comodo Internet Security Premium (thanks to this forum, I've already done all the workarounds to get Sandboxie and Comodo to play nicely together and it appears to work other than my printing issue)
Iobit Malware Fighter 4.2
Key Scrambler 3.10.0.0
Flash 22.0 r0 v 22.0.0.209 (up to date)

Okay I think I've listed everything of critical importance but please tell me if you need any additional info and I'll be very happy to provide it.

Anytime I try to print in Firefox (to any printer - I've changed default from Cute PDF to HP Photosmart C4200 to Foxit Reader to Microsoft Print to PDF with absolutely no change in error messaging) I get the following pop up error messages:

"splwow64.exe - Application Error
The application was unable to start correctly (0xc00000e5). Click OK to close the application."

I click OK and it then pops up about three more times before it finally closes but never allows me to print.

What do I need to do to correct this? Thanks in advance! I really hope you can help like you did before.

[Craig@Invincea]

Are you getting any notifications from SBIE about giving access outside the sandbox to print?? You should have a pop up box.

Anytime you need to print, that has to go outside of the sandbox, you can try adding this to your SBIE .ini file:

Code: Select all

OpenFilePath=c:\windows\system32\spool\printers\*

[rollrxgirl]

Are you getting any notifications from SBIE about giving access outside the sandbox to print?? You should have a pop up box.

Anytime you need to print, that has to go outside of the sandbox, you can try adding this to your SBIE .ini file:

Code: Select all

OpenFilePath=c:\windows\system32\spool\printers\*

I'm not getting any notifications from SBIE at all when I attempt to print. I added the code you suggested to the .ini file, saved, and opened a new Sandboxie browser yet nothing changed. I'm still getting the same error messaging.

[Craig@Invincea]

Alright, let's have you get us a proc mon:
Get the software here https://technet.microsoft.com/en-us/sys ... nitor.aspx

Steps
Close any programs that are not needed.
Run Procom (not sandboxed)
and then try and fire up Browser and print something (sandboxed of course). Of
Nothing happens, like your report them...
stop capturing events in Procmon (under file)
then Save the results (under file, make sure "save all events it ticked") and
save in PML format.
These files can be large, so post somewhere we can download and look (link)
OR (Please zip them!) and send to Support@sandboxie.com

[rollrxgirl]

Alright, let's have you get us a proc mon:
Get the software here https://technet.microsoft.com/en-us/sys ... nitor.aspx

Steps
Close any programs that are not needed.
Run Procom (not sandboxed)
and then try and fire up Browser and print something (sandboxed of course). Of
Nothing happens, like your report them...
stop capturing events in Procmon (under file)
then Save the results (under file, make sure "save all events it ticked") and
save in PML format.
These files can be large, so post somewhere we can download and look (link)
OR (Please zip them!) and send to Support@sandboxie.com

Okay, so I downloaded and ran the Procmon application with all my background running programs closed - including Comodo. I was curious so I browsed the log file and saw a few things with my Firefox add-ons so I have tried disabling the Foxit plugin (no effect) and tried again with Greasemonkey disabled (again no effect). I am not a techie person so I am hopeful that you can see something that I could not. Here's the link to the zipped log: https://www.sendspace.com/file/dfrfuw I really appreciate your help! Thank you!

Edit: I also tried disabling ALL Firefox add-ons and it had no effect.

[Curt@invincea]

I can see in the PML that Comodo is causing this problem. You can try blocking it with ClosedFilePath=C:\Windows\System32\guard64.dll, but it may not like that. You can also try excluding splwow64.exe in Comodo.

If that doesn't work, try uninstalling it completely.

[rollrxgirl]

I can see in the PML that Comodo is causing this problem. You can try blocking it with ClosedFilePath=C:\Windows\System32\guard64.dll, but it may not like that. You can also try excluding splwow64.exe in Comodo.

If that doesn't work, try uninstalling it completely.

Excluding splwow64.exe in Comodo worked! Thank you! You might want to add this fix to the big Comodo thread to help others avoid this same nightmare scenario if they also get stuck. I totally appreciate all the help you guys have given me. I love your program and your customer service!