Sandboxie Support

Initially I thought the Windows 8.1 printing problem was just on 64-bit Windows 8.1, but turns out it also affected 32-bit Windows 8.1.

Version 4.07.03 should fix this problem (which is specific to Windows 8.1).

Related topic:
http://www.sandboxie.com/phpbb/viewtopic.php?t=16845

Excellent. Works now.

Note for others: Had to run
before printing worked (or you can simply reboot )

I wonder why you needed to restart the spooler service. That was not necessary in my tests, but let's see what others report.
In case this happens again, please take a look at spoolsv.exe using Process Explorer, the View > Show Lower Pane command (Ctrl+L).
You should see one resource/handle with the name \RPC Control\LRPC-xxxxxxxxxxxxxxx.
If you see more than one, or if you see something like \RPC Control\OLExxxxxxxxxxxx instead, please let me know.

Thank tzuk! Problem fixed here on Win8.1 x64 and didn't have to stop\restart the spooler service nor restart windows for it to work properly.

dja2k

tzuk wrote:I wonder why you needed to restart the spooler service. That was not necessary in my tests, but let's see what others report.

No idea. The printers simply still were not visible after SBIE upgrade, until spooler restart... No problems since then.

Was working fine after the upgrade, but not anymore after a restart. As soon as I press PRINT, Firefox crashes and closes itself.

dja2k

Printing not working, window popping up saying no printer installed. All sandboxed applications are affected. Win 8.1 64 Bit Sandboxie 4.07.04

edit: a reboot solved the problem

Printing still doesn't work on Win 8.1. x64. Sandboxie 4.07.04. (Message: no printer installed)
If I stop and restart spooler service it works - but then ONLY for sandboxed programs and only for the current session.

Interesting to see an \RPC CONTROL\OLE* resource in your screenshot, SLE.
Tell me please, when you restart the spooler service, do you still see an OLE resource in spoolsv.exe ?

tzuk wrote:Tell me please, when you restart the spooler service, do you still see an OLE resource in spoolsv.exe ?

No after restart of spooler service RPC CONTROL\OLE is gone. But only until i reboot machine...

I want to clarify: When you restart your computer, your spoolsv.exe starts and has both an LRPC and an OLE resource?

* * *

If you restart spoolsv.exe and it comes up with just the LRPC resource, can you identify when it adds the OLE resource?
Does it do that in response to something that you do?

Are you trying to print in the sandbox and outside the sandbox at the same time?

* * *

I've been experimenting a bit with printing on my test 64-bit Windows 8.1 system and everything seems to work fine
even when I switch between more than one user account, and between printing in the sandbox and printing outside
the sandbox. So I need to understand what to do to trigger the errors.

tzuk wrote:I want to clarify: When you restart your computer, your spoolsv.exe starts and has both an LRPC and an OLE resource?

Right, just after reboot of pc both handles are there. Before I start something in a sandbox.

tzuk wrote: If you restart spoolsv.exe and it comes up with just the LRPC resource, can you identify when it adds the OLE resource?
Does it do that in response to something that you do?

I works some time after spooler restart via CLI (for printing within and without the sandbox) but after some time the OLE resource came back. I tried some time but wasn't able to find a more specific pattern until now.

No printing jobs inside and outside at the same time.

If there is something possible to trigger it deeper (procmon?) than just let me know.

I have no idea how to trigger these OLE resources in spoolsv.exe. I don't see them on my test system. But I will add some code to treat the OLE resource the same way as the LRPC resource, and we'll see if that fixes the problem.

Maybe I am facing a similar problem but I keep getting that same error as SLE. Thanks tzuk for looking into it.

dja2k

I reviewed the code again and I'm afraid I don't see where the OLE resource would fit. So no solution yet I'm afraid. I'd like to ask you to check something else. You say that after restarting the spooler service, it works for a while. Can you please use Process Explorer and check if the actual name of that LRPC resource changes?

That is to say, restart spooler, check and note exact name of that LRPC resource, also note the process ID for spoolsv.exe. Then after a while, when printing stops working, look at spoolsv.exe again. Is it the same process ID, and does the LRPC resource still have the same name?