Hi raid,

I made a mistake in my last post with the version number. I said I upgraded to v3.4 when it should have said v3.34 like you suggested. So I do have the official version currently running. It appears to be running ok so far. Do you know where to go to check the version number of Sandboxie's driver and service?

Thanks for the beta url. Once I know things have cleared up and everything is working ok with this version, I'll upgrade to the beta. Hopefully that fixes the Windows Shell issue.

I'm not quite sure what has occurred to get your prior Sandboxie installations mucked up.. but as for the version numbers, they will all be listed under properties in the respective file.

Typically, when there are version mismatch errors, it would be because a driver didn't properly unload during an upgrade or uninstall. Tzuk keeps all his files (excepting Sandboxie.ini) in one place so you can check them out easy enough in the Sandboxie home folder. The version numbers should all match up. I don't use the default installation folder, but I think it's C:\Program Files\Sandboxie.

I think you're right, about the driver not unloading properly. Initially, I thought the version number was listed in the registry and it didn't update completely with the newer version, which in turn triggered the error. That's why I was wondering where it was located so I could check but what you said makes more sense. I used Sandboxie quite a bit last night and everything seems to be working fine so I just upgraded to the beta version. Thanks.

And unfortunately the Windows Shell Integration crashes with this version too. I don't get it.

If you mean it still crashes in version 3.35.12 then can you crash details again? This time it will surely be useful.

Sure can, hope it helps...

Problem signature:
Problem Event Name: APPCRASH
Application Name: SbieCtrl.exe
Application Version: 3.35.11.0
Application Timestamp: 499b52bb
Fault Module Name: SbieCtrl.exe
Fault Module Version: 3.35.11.0
Fault Module Timestamp: 499b52bb
Exception Code: c0000005
Exception Offset: 000259c1
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 75e1
Additional Information 2: c89e54e61b199f9128024769c707c57d
Additional Information 3: 1e2f
Additional Information 4: 725212602d184ce82249680a434616e8

===================================================
[EDIT-update]

I just ran a little test to rule out something. I wanted to see if Sandboxie was conflicting with other software running in the background. Sometimes Creative Element Power Tools is a little too aggressive for its own good. It does cause crashes with some of the software on my system. With those I am aware of, I block the action with Defense+.

I took everything out of startup in msconfig except my graphics driver and rebooted for the test. The error generated is exactly the same, checked number-by-number. It’s not much help but at least the background software can be ruled out.

Thanks Samantha, I found the problem. I can assure you that it is a minor bug in Sandboxie Control and has nothing to do with any background processes. It should be fixed in the next beta version I release.

D-a-n-g, tzuk that was quick! What a pleasant surprise. You gotta be the fastest gunsling – err programmer around! LOL! Thanks!

Please let me know if version 3.35.13 resolves the problem.

I'm happy to report it's working. :

But... I did have trouble with the install again like I mentioned in a previous post. This is what happened.

I started the install (v3.35-13) and when it got to the point where Sandboxie informs you about installing the driver, is where things get weird. I clicked NEXT, Sandboxie continues and then reports that SandboxieControl failed to start.

Clicked OK and received this:

[***KmdUtil failed. Installation or un-installation may not complete successfully***]

Clicked OK and then:

[Version mismatch in Sandboxie:

Sandboxie Control Version 3.35.13
Service (SbieSvc): Version ?
Driver (SbieDrv): Version 3.35.11]

Rebooted and tried starting Sandboxie's Control. It loaded the Control icon in the systray but it had an '!' on the icon. When I selected to show errors, it came back with:

[SBIE2332 Service Start failed: [22/1060] The specified service does not exist as an installed service.]

Clicked OK and the exact error displayed again. Clicked OK again and exited Sandboxie.

Instead of uninstalling, I re-installed on top and the errors went away. I haven't had a chance to work with it much but Sandboxie appears to be working OK now.

1. Glad to hear that version 3.35.13 indeed fixes the shell integration problem.

2. As a matter of principle, you can generally run the SandboxieInstall again and again and again and again until all problems are fixed.

3. But it is curious why you're having problems with reinstallation. Is there any other security software that may be interfering?

That's good information to know, thanks



It's interesting that you brought that up because I was just logging in to say never mind about the errors when I saw your post.

For some reason Comodo was the culprit the whole time. I couldn't get the update to the software to work so I went out and downloaded the newer version. On a hunch... I uninstalled the old version and Sandboxie too. Then installed Sandboxie (without Comodo), no problem - the whole process went smooth. I uninstalled Sandboxie, installed Comodo and then Sandboxie again - no errors. It appears that something within Comodo (likely the Defense+ side) was preventing the driver from loading. Well, at least now everything is working as it should and I'm a happy camper.