Discussion in 'sandboxing & virtualization' started by ad18, Dec 16, 2013.
When approximately will Sandboxie be compatible with Windows 10?
Okay, so I updated two W7x64 machines to v4.17.5, and I'm understanding the "allow print spooler access for this session" improvement. Very nice, indeed.
However, one computer is throwing up constant "SBIE1319 Blocked spooler print to file, process " messages. To the best of my knowledge, process  is referencing svc.host, and is probably the very thing that Curt is saying should not be allowed (?). I finally hid the message.
The other machine is not showing the process  message at all.
Is there anything you can tell me about this condition?
4.17.5 is running smooth as can be, by the way... but we know that to be the case with all Sandboxie betas.
According to Curt, the spooler block is too restrictive, next beta should be better.
Probably during the summer (USA). Check this thread out.
I'll install 4.17.6 and unhide the message and see what happens. TY, Bo.
4.17.6 is out now.
I installed 4.17.6 and tried printing from Chrome. I got the 1319 message that said click to allow, but the page printed without me allowing it (before I could double-click).
That tells me the print spooler access for the session feature is not working in 4.17.6.
I am rebooting to see if the same thing happens.
Edit In: I rebooted and the same condition exists. Printing from Chrome or from Foxit Reader results in a SBIE 1319 plus a SBIE 1320 message, but I don't have to double-click the message line in order to print... it prints anyway.
Update: 4.17.5 & 4.17.6 scanned OK by Symantec at 'virustotal' .....Rep.1 must be my Norton setup.
Hi Page, I suggest you explain to Curt what you are experiencing after upgrading to 4.17.6 in a reply to this post of his in the beta 4.17 thread.
I followed your suggestion. TY
Question --- Can a Sandboxie user revert to a previous version, by installing that previous version over top of the more recent version?
Or, is the only way to go back to uninstall SBIE and install the version you want?
I simply want to go back to 4.17.5 from 4.17.6.
Hi Page, you can downgrade over the top.
Thanks, Boss. I did just that, and all seems well.
New beta is out (4.17.7).
Installed 4.17.7 on one machine... waiting to install on the other as it is in use right now.
I'm anxious to work through a couple of issues, and .7 may be the answer.
Thanks for the heads up, Bo.
Well, after installing 4.17.7, I encountered the same problem I had after installing 4.17.6 (and noted in this post last week).
That problem, specifically, being that when trying to print, the SBIE print spooler message appears, but printing occurs without me double-clicking the 1320 message line.
SBIE1319 Blocked spooler print to file,  chrome.exe, \Windows\TEMP\SPLA843.tmp
SBIE1320 To allow print spooler to write outside the sandbox for this process, please double-click on this message line
This tells me that the print spooler access for the session feature is not working in 4.17.7, for me, as it wasn't in 4.17.6... which is why I reverted to .5.
Yep, the only beta version with the print spooler feature that works properly for me, on both W7x64 machines, is 4.17.5. I can confirm that. I try to print, get the message telling me to double-click on the line, and when I do, then can print.
With .5, unlike with .6 and .7, printing does not occur until I double-click the appropriate message line.
Fine with me to use .5, just reporting what I have experienced.
Another beta version has been released, this one fixes the BSOD reported by a user.
Invincea seems to be cranking out tweaked/improved versions even faster than Tzuk managed to iirc. Impressive.
What was wrong with the way 4.17.5 print spooler work'd
Thanks for the heads up.
Got some catching up to do on versions.
Sandboxie stable version 4.18 has been released. It has important fixes, changes and improvements.
Released on 28 May 2015.
A security hole with the Windows print spooler has been plugged. An application could use the print spooler to write an arbitrary file outside the sandbox. If Sandboxie detects that the print spooler is attempting to write a file outside the sandbox at the request of a sandboxed application, it will issue "SBIE1319 Blocked spooler print to file".
NOTE: Some printer drivers write temporary files to their own work area, even when not printing to file. In these cases, you will get SBIE1319 even when printing normally (not to file). The print may still print successfully. In this situation, you can safely ignore SBIE1319, hide the error message, or open the folder as described below.
There are 3 ways to allow the print spooler to print to file:
1) If you trust the process that is printing, you can double-click the SBIE1320 (that follows SBIE1319) to allow the print spooler to write files outside the sandbox for that particular process. 2) The spooler can write files outside the sandbox according to OpenFilePath settings. This enables you to permanently open the folders a particular printer driver uses to store its work files. 3) You can manually add the setting AllowSpoolerPrintToFile=y to sandboxie.ini. This is not recommended as it leaves your sandbox open to a print spooler exploit.
Any error msgs generated when auto-deleting a sandbox will now be shown to the user.
Fixed Chrome SBIE2205 Service not implemented: Win32Init.5 (00000005)
Added Hitman Pro Alert to templates.ini
Changed hook for ChangeDisplaySettingsEx() to allow CDS_RESET. A user reported that a game (fifa15) is trying to use this and failing resulting in incorrect display colors.
Distributed File System (DFS) mapped drives are now supported (viewtopic.php?f=11&t=18825&p=100656)
VMWare HGFS (Host Guest File System) mapped drives are now supported.
A BSOD bugcheck reported by a user when using bittorrent has been removed (this was a rare situation). SbieDrv was detecting corrupted memory when no corruption had occurred.
Fixed a rare bug in clipboard handling that could crash SbieSvc.
WebEx running under Chrome would sometimes hang.
Recent Windows update in Win 8-64 causes Skype (and possibly other apps) to issue error SBIE2335 Initialization failed for process Skype.exe 33 / 0?
I updated to 4.18 but now it will not activate.
Error 12029 means the connection to the server failed (sandboxie.com). Try again or try disabling momentarily your firewall or antivirus.
Thanks for your reply. I've tried disabling av and firewall but unfortunately it didn't work. I am now waiting for a response from Sandboxie support.
Separate names with a comma.