I'm using Windows 7 x64. Can anyone tell me what what changes were made to printing procedures in Windows 7; what applications need to be added to the run/access list? I tried printing in Opera and using the below configuration, Opera crashes every time I click the print icon.

snipped. --tzuk

I still can't figure out why I cannot print from applications inside a sandbox. I've added splwow64.exe to the run list for Opera, which is what SBIE said was prohibited from running. After that I get no error messages anymore, Opera just crashes every time.

Any ideas?

What happens if you remove the force for Opera, create a new sandbox and apply only minimal exclusions from
Sandbox Settings > Applications > Web Browser > Other
and then run Opera with the new sandbox?

Is Opera installed inside of a sandbox? I was wondering about the OpenPipePath exclusions.

Deleting my current opera sandbox and recreating it using only the build-it SBIE settings (Sandbox Settings > Applications > Web Browser > Other) results in the same behavior as before.

With version 3.43.14 there should no longer be crashes, but printing still doesn't work from a 32-bit program. While browsers don't usually give out any error indication, if you try to print from the 32-bit Notepad in c:\Windows\SysWow64\Notepad.exe then you will see "The handle is invalid." I'm still trying to figure this one out.

I cannot print to bullzip PDF printers while in the sandbox. I tried .13 and it failed and updated to .14 which fixed my video issues (with me testing by removing the *MMDevices* option) but now I cannot print to pdf...outside of the sandbox I can print to PDF fine...

Printing from 32-bit programs should be possible in version 3.43.15.

A few words about this:

Printer drivers in 64-bit in Windows are 64-bit, and there is a program called splwow64.exe that acts as the bridge between 32-bit programs and the 64-bit printer driver.

In my experiments -- and I've made plenty -- the splwow64.exe cannot load the printer driver inside the sandbox.

Therefore the only possible workaround was to let the sandboxed program talk to the splwow64.exe outside the sandbox.

If you're printing to a real printer then it doesn't really matter one way or another.

However if you're printing to a file, for instance with the Microsoft XPS printer, then the file will be saved outside the sandbox.

(This doesn't mean that any 32-bit program can abuse splwow64.exe to get any file it wants outside the sandbox. The output file will always be an XPS file, for example in the case of the XPS printer driver, which is created according to print commands, not arbitrary data. And you would also have to manually select where to place the file, and the 32-bit program can't influence this selection. So before anyone asks -- no, this isn't a security risk. )

And also note that if you're printing from a 64-bit program to the XPS printer, the file will be saved in the sandbox, because the splwow64.exe program isn't involved, and the printer driver runs in the sandbox.

I hope this situation won't be too confusing, but like I said, I was unable to get the splwow64.exe to run in the sandbox, so I had no other way to resolve this problem.