5.01 Beta Available (latest version 5.04 RC)

[Craig@Invincea]

Hello,

I am using 5.01.03 without problems except for the fonts not displaying right in some applications (e.g. banking4w).
If I upgrade to 5.01.11 or 5.01.12 I can't start any program at all in the sandbox.
If I try to start a program by using the sandboxie built in start menu or just try to start the explorer in the sandbox the following error occurs: "SBIE2224 Sandboxed program has crashed: SandboxieDcomLaunch.exe"
The same happens with any other application I try to run. It doesn't make a change if it is installed outside or inside the sandbox.

Im on Windows 10 Enterprise 64 bit with the latest patches.
Did even a clean uninstall and reinstall of sandboxie including a reboot after uninstall.
Virus scanner is Bitdefender free, a deactivation doesn't solve the issue.
I always used the combined installer.

Thanks in advance,
Chr1s

Beta v5.01.12 fixes the font issue (as does .10) And it works just fine with 10 enterprise 64. What program in particular. The only way to fix the font issue is a newer version of the beta.

[Chr1s]

The font issue isn't a problem in this case. The problem is when upgrading to newer versions.

As described no program at all is working in the sandboxie betas which have the font fix (5.01.11 & 5.01.12; I can't test 5.01.10 because I don't have the installer).
Not even the sandboxie start menue (start.exe) is working.
The following error is thrown for everything: "SBIE2224 Sandboxed program has crashed: SandboxieDcomLaunch.exe"

After downgrading to 5.01.03 everything works again.

How can we troubleshoot this?

[Craig@Invincea]

The font issue isn't a problem in this case. The problem is when upgrading to newer versions.

As described no program at all is working in the sandboxie betas which have the font fix (5.01.11 & 5.01.12; I can't test 5.01.10 because I don't have the installer).
Not even the sandboxie start menue (start.exe) is working.
The following error is thrown for everything: "SBIE2224 Sandboxed program has crashed: SandboxieDcomLaunch.exe"

After downgrading to 5.01.03 everything works again.

How can we troubleshoot this?

Okay, I was speaking with Curt, and we are curious. So, we would like you to try these steps if you're comfortable?
1. Delete SBIE, Reboot.
2. These files need to be deleted on your host (back them up for safety, and/or rename to something else) msvcr100.dll, mfc100u.dll. & Both system32 and syswow64
3. Re-install SBIE v5.01.12 beta, SBIE will replace those delete files.
4. Try to use SBIE

[Chr1s]

I tried exactly after your instructions and can confirm that the files in the system32 and syswow64 directory are recreated after installation of 5.01.12.
The problem is still persisting though.

[Craig@Invincea]

I tried exactly after your instructions and can confirm that the files in the system32 and syswow64 directory are recreated after installation of 5.01.12.
The problem is still persisting though.

Okay, Well, given that SBIE control won't even load, that leads to only a few options... But, let me ask 2 more question about your browser as OS...

you're using something OTHER than Microsoft Edge browser correct? As this is the default browser in Win 10 (if you click on sandboxed webbrowser, it will open Edge unless you change it.)
Was this Win 10 install an upgrade or a clean install?

I'm gong to have you remove SBIE again, I want you to directly download it here: http://www.sandboxie.com/SandboxieInstall64-501-12.exe

When you open it, have it overwrite the existing installation. Try and "right click" on your browser (IE, firefox, Chrome, etc.) and see if that loads.

If it does't (and other programs don't load in SBIE either) we're thinking you have some damaged .dll files as the Devs see no other reason why.

[Chr1s]

Thank you for your fast support! Sandboxie is working again

I repeated the steps for a clean uninstall with an added reboot after renaming the dlls.
Downloaded the installer again from your link, changed the standard browser (it was edge but I use chrome) and installed sandboxie.

The windows 10 installation was with the option don't keep anything, so I guess it could count as a clean install.

Thanks again and keep up the great work!
Chr1s

[Craig@Invincea]

leave windows 10 out of it for a bit, im on 7, but the same things happen with 10 anyway. oh i dont have 3d vision installed at all as its useless for me. from the quote of another user u provided, he just said "amd quad high end graphics" so im going to assume the integrated amd graphics, but im on nvidia/intel hd & theres no amd in this house for me to test on. theres another user on the previous page i think that still cant get tf2 to even start..

where do i retrieve dump files if theres any?

I'm not sure what else to tell you. I tested SBIE 5.01.12 on an old AMD quad core gaming PC with 3D graphics running Win 7 and Steam. It loaded just fine as well as TF2 and other games. Curt has similar results.

[Craig@Invincea]

Thank you for your fast support! Sandboxie is working again

I repeated the steps for a clean uninstall with an added reboot after renaming the dlls.
Downloaded the installer again from your link, changed the standard browser (it was edge but I use chrome) and installed sandboxie.

The windows 10 installation was with the option don't keep anything, so I guess it could count as a clean install.

Thanks again and keep up the great work!
Chr1s

Awesome! Thanks for being our test subject briefly and following those steps.

[pling_man]

I am using Windows 10, Firefox 40.0.3 (just updated, but same issue with 40.0.2), Sandboxie beta 5.01.12 (licenced), Limited user account.

Firefox runs fine when I run it as a forced program. But when I run it using the "Sandboxed Web Browser" shortcut on my desktop, it looks a bit different.

Specifically:

(1) The title bar appears and has wide strips at the right hand and left hand edges. When run as a forced program or un-sandboxed the title bar is grey (as it should be).
(2) In the Options search tab, the option to "Use this search engine for searches from Windows" is missing when Firefox is run from the "Sandboxed Web Browser" Icon.

I have tried re-creating the desktop shortcut from Sandboxie's Configure>Windows Shell Integration but this problem persists.

Here is the options page when running Firefox in Sandboxie using the Desktop icon:



And here is the options page when running Firefox as a Forced program:

[Craig@Invincea]

I'm going to say it's because that would require the "search" to go outside the SB and then actually search Win on your host, which by default ins't permitted. So, FF isn't aware.
As for the color variance, GDI interface with SBIE has to make compatibility adaptions and thus you may see some subtle variations. (and it always reminds you that SBIE is working lol )

[pling_man]

I don't think that is correct and think you have misunderstood my post.

Bothscreenshots are from Firefox running in a Sandbox. There is no reason that the options should display differently.

The title bar is white when I use the desktop icon with a broad gray strip at the left and right edges. Whereas it should be gray throughout.
Again, there is no reason this should display differently.

[pling_man]

I'm going to say it's because that would require the "search" to go outside the SB and then actually search Win on your host, which by default ins't permitted. So, FF isn't aware. )

On this point, the search doesn't go outside the sandbox. The search is instigated in Windows, and firefox loads (if a forced program) and searches for the text using the default search engine that is set up (in my case DuckDuckGo).

[Craig@Invincea]

I don't think that is correct and think you have misunderstood my post.

Bothscreenshots are from Firefox running in a Sandbox. There is no reason that the options should display differently.

The title bar is white when I use the desktop icon with a broad gray strip at the left and right edges. Whereas it should be gray throughout.
Again, there is no reason this should display differently.

Yes, there are plenty of reasons while it would. Sometimes you may not get even the same font (but it won't affect formatting, etc. like we saw with the font issue that was previously fixed). I've spoken to the Dev, and he confirms that this is expected, mainly in Win 10. (he was over my shoulder while I was showing him your post)

[pling_man]

But I don't see how things should be different for a Forced program and one run using the "Sandbox Web Browser" icon. And you have not explained it at all.

[Curt@invincea]

But I don't see how things should be different for a Forced program and one run using the "Sandbox Web Browser" icon. And you have not explained it at all.

Ok, we'll put that on our list of things to look into. Right after redesigning the startup sequence, hooking, and message passing for Win 10. Until then, you will just have to live with the different shading in the title bar for forced vs. regular. We might even make it a feature: shaded title bar means the browser was forced.