5.01 Beta Available (latest version 5.04 RC)

[pling_man]

Do you think the bug in start.exe will be fixed before you release 5.2?

It is possible that the residual issues that are still being reported are due to start.exe being used to run the program in the Sandbox. Right-click, run sandboxed will use it, for example. This may explain why the issues are not being seen by Curt and Craig on here.

Could people with issues try running there programs forced (if they can) and see if their problem disappears. And report here.

[Chr1s]

...

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.

Hm I can reproduce the error now. After reinstalling Bitdefender Free http://www.bitdefender.com/solutions/free.html and doing a real reboot by admin cmd "shutdown /r /f /t 0" the same error is thrown again and I can't start any programs in the sandbox. The error doesn't occur right after the Bitdefender setup, a reboot is required after the virus scanner has finished its update.
When I uninstall the virus scanner and do a reboot everything is working again.
Could you please look into the issue?

Thanks in advance,
Chr1s

[Yuno]

It looks like the only problems being reported now are: slightly blurry fonts in 1 Sbie dialog box when display settings are set to 125%, a gray (or white) title bar under certain situations in FF, and problems with Steam and FF extensions that cannot be reproduced by us. It looks like 5.02 is taking shape nicely.

steam works, the games dont properly if at all. so all of us that suddenly get the same problems at the same time are just in the twilight zone or something.? or sbie got broken..is testing being done on an actual machine with x64 windows or just a virtual machine..? want to see it happening on video? things failing to start with NO ERROR, tf2 font wrong. then me doing the exact same thing again with 4.20

[AerosAtar]

...

It looks like the only problems being reported now are: slightly blurry fonts in 1 Sbie dialog box when display settings are set to 125%, a gray (or white) title bar under certain situations in FF, and problems with Steam and FF extensions that cannot be reproduced by us. It looks like 5.02 is taking shape nicely.

Going to assume you missed my post back on page 34...

I use SBIE to run multiple ARC clients at once (different accounts on each client). This works just fine in terms of the client, but there is an issue with games launched from ARC.

I run a single (main) client unsandboxed, and then multiple (secondary) clients each in its own sandbox. The problem occurs when attempting to run a game from the unsandboxed client after having launched a sandboxed version at least once.

Steps to reproduce:

• Run ARC client unsandboxed (first account).
• Launch game from unsandboxed client. Game launches unsandboxed (correct).
• Close game.
• Run ARC client sandboxed (second account).
• Lauch game from sandboxed client. Game launches sandboxed (correct).
• Close game. (optional)
• Run game from unsandboxed client. Game launches sandboxed (incorrect).

There is also the issue of no sound (cannot identify an output device), but I see that has already been reported in previous posts on this thread.

This issue was not present in version 4.2x on Win7x64, where it worked perfectly without any problems at all, so it seems to be either something introduced in this version or another compatability issue with Win10(x64) that needs to be looked into.

[Craig@Invincea]

I use SBIE to run multiple ARC clients at once (different accounts on each client). This works just fine in terms of the client, but there is an issue with games launched from ARC.

I run a single (main) client unsandboxed, and then multiple (secondary) clients each in its own sandbox. The problem occurs when attempting to run a game from the unsandboxed client after having launched a sandboxed version at least once.

Steps to reproduce:

• Run ARC client unsandboxed (first account).
• Launch game from unsandboxed client. Game launches unsandboxed (correct).
• Close game.
• Run ARC client sandboxed (second account).
• Lauch game from sandboxed client. Game launches sandboxed (correct).
• Close game. (optional)
• Run game from unsandboxed client. Game launches sandboxed (incorrect).

Yes, there are some online gaming clients at this time that do now work with SBIE and Win10. Win10 introduced a slew of changes. Example, Steam does work, but not all games may work. Games that people say don't work here, work fine for us in testing and on our home machines. So that introduces some machine dependent issues as well. We haven't tested ARC clients. It can be added to the list.

There is also the issue of no sound (cannot identify an output device), but I see that has already been reported in previous posts on this thread.

This issue was not present in version 4.2x on Win7x64, where it worked perfectly without any problems at all, so it seems to be either something introduced in this version or another compatability issue with Win10(x64) that needs to be looked into.

There was some issue related to sound a few versions back, mainly with media players and that was solved. We've always had success with sound in browsers. It is possible that it's driver issue within Win10 and SBIE cannot see or use it. Can you try a standalone media player and test it in a sb? such as VLC or potplayer..Those are some of the many we know that works.

[Craig@Invincea]

Do you think the bug in start.exe will be fixed before you release 5.2?

It is possible that the residual issues that are still being reported are due to start.exe being used to run the program in the Sandbox. Right-click, run sandboxed will use it, for example. This may explain why the issues are not being seen by Curt and Craig on here.

Could people with issues try running there programs forced (if they can) and see if their problem disappears. And report here.

That's how I mainly use SB in various forms. I don't think that's the issue.

[btm]

I haven't checked it recently but I did start a thread about noticing a difference in behavior in the 4.x builds between start/forced on Windows XP. I wouldn't discount his theory without at least testing it...

http://forums.sandboxie.com/phpBB3/view ... 11&t=21069

Just did a quick test of steam by removing it from forced, right clicked and used run as sandboxed. No issues (crashes) so far but I'll try again later when I have more time. I'm on Windows 7 x64 so if it is Windows 10 specific, like the other difference I found in XP, I obviously wouldn't see it anyway. =(

[henryg]

Any chance of making this Board's description include the latest point version of the beta? It would save having to check the first page each time.

I realise this beta has had an exceptional number of updates, but it would be sensible for any betas Board IMO. BTW has this Beta had a record number of point updates?

[Craig@Invincea]

I haven't checked it recently but I did start a thread about noticing a difference in behavior in the 4.x builds between start/forced on Windows XP. I wouldn't discount his theory without at least testing it...

http://forums.sandboxie.com/phpBB3/view ... 11&t=21069

I actually ran that test using all your steps and it did not trigger any BAD IMPERSONATION results. Win 10/64.

I have the entire procmon log for Curt.

[AerosAtar]

There was some issue related to sound a few versions back, mainly with media players and that was solved. We've always had success with sound in browsers. It is possible that it's driver issue within Win10 and SBIE cannot see or use it. Can you try a standalone media player and test it in a sb? such as VLC or potplayer..Those are some of the many we know that works.

Just checked with Winamp, and that produces sound fine, so it might be related to the other compatability issues with ARC/ARC-based games.

[btm]

I haven't checked it recently but I did start a thread about noticing a difference in behavior in the 4.x builds between start/forced on Windows XP. I wouldn't discount his theory without at least testing it...

http://forums.sandboxie.com/phpBB3/view ... 11&t=21069

I actually ran that test using all your steps and it did not trigger any BAD IMPERSONATION results. Win 10/64.

I have the entire procmon log for Curt.

Confirmed, I installed 5.01.12 on a Win 10 x64 VM and saw no Bad Impersonation results. Nothing else popped out at me either but I was only trying notepad once again, not steam, arc or any games.

P.S. Out of curiosity I tried it again on XP w 5.01.12 and still got similar results as in the thread I linked to but also received a few Bad Impersonation results both ways this time.

[Cielox00]

I'm running Windows 10 from Sandboxie version 5.01.10 and I have the following error message when attempting to sandbox most MSI installers.



Also some steam games (Garry's Mod, Counter Strike: Global Offensive) fail to launch when I install Steam into a sandbox and run it to play games. If you need any more description on what I'm doing I'll be happy to make a short screen recording of the process to help you see what the problem is. Thanks guys!

[Craig@Invincea]

I'm running Windows 10 from Sandboxie version 5.01.10 and I have the following error message when attempting to sandbox most MSI installers.



Also some steam games (Garry's Mod, Counter Strike: Global Offensive) fail to launch when I install Steam into a sandbox and run it to play games. If you need any more description on what I'm doing I'll be happy to make a short screen recording of the process to help you see what the problem is. Thanks guys!

I'm going to say that the .msi installer is corrupt.

Steam. While steam client works (as do some games) and some games do function (we can't test every one, they all unique in a way) other games that are intensive/ offer various mods and on's etc, simply may not work as they need to specific resource or be allowed to write to certain files and directories. Of course, when you're in SB, some of these host processes are unavailable (you''re isolated). If you knew what as trying to do or access what, you may be able to edit the ini file and allow some sort of access. Of course, you're defeating the purpose of SBIE then.

We've tested a few games, personally I've tested Bioshock, TF2, various flight sims on a Win7/64 box running SBIE v5.01.12 with little problem, sometimes a driver/add on wouldn't install, but the game seemed playable.

[Curt@invincea]

5.01.13 is now available.

[Yuno]

is there some debug software or "special version" of sbie or something devs can give to us that will actually capture some data to find the problem of our broken stuff with v5?

like a dev running a test trying to replicate an issue, whatever they'd be running at the time for debugging purposes, give us a copy of whatever that dev tool is?