Sandboxie 5.33.3 now available for download

The download link for the combined (32+64) installer still points to version 5.33.1.

...?downloadKey={96E8ABB5-61C3-460C-8153-D904E8FFB314} => SandboxieInstall-533-1.exe

In reply to APMichael:

 Fixed.

Akhilesh@Sophos

Great Job . i love it

In reply to Akhilesh@Sophos:

Hello Akhile,

I downloaded and installed the new version. I verified the "about sandboxie" indicated version 5.33.3.

However, the following errors that have been occurring in the earlier versions still persist in the newest version as well.

Disappointed and returning back to 5.31.6.

Please let us know if or when you intend to address these issues.

Thank You.

In reply to Maxx Payne:

I am getting the same error report as Maxx Payne.

The only thing I am running in Sandboxie 5.33.3 is a fresh install of Google Chrome browser 80.0.3987.132 (Official Build) (64-bit) on Windows 10 Pro x64.

In reply to Ryan Cruze:

Can someone tell me how to revert to version 5.31.6 when I have version 5.33.3 installed?

Where can I get the old version and how can I install it?  Do I have to uninstall 5.33.3 first?

Thanks

In reply to Ryan Cruze:

Just in case I missed something:

Be sure to provide the following information when submitting a problem report: 

1- Sandboxie and Windows version (For example Sandboxie 5.30 , Windows 10 x64 bit 1809) 

Sandboxie 5.33.3. Windows 10 Pro x64 bit 1903

2 - Affected applications version (if using a browser, include any extensions as well)

Google Chrome browser 80.0.3987.132 (Official Build) (64-bit)

(no extensions)

3 - List any antivirus installed, and their version.

None.  Just Windows Defender.

4 - Steps to reproduce the issue.

In my case I just got a new computer with a fresh install of Windows 10.  Did a fresh install of Chrome and a fresh install of Sandboxie (versions given above).  I get the error message I posted above, on occasion, when using sandboxed Chrome.

5 - Does it occur in a new sandbox with default settings?

Yes.

6 - Full error message and screenshots of it if applicable. 

Posted above.

In reply to Ryan Cruze:

Ryan Cruze

I am getting the same error report as Maxx Payne.

The only thing I am running in Sandboxie 5.33.3 is a fresh install of Google Chrome browser 80.0.3987.132 (Official Build) (64-bit) on Windows 10 Pro x64.

 

FWIW ~ I've added HideMessage= .... long time.

SbieCtrl_HideMessage=2303,ReleaseStgMedium (33, 1655)
SbieCtrl_HideMessage=2303,CoGetObject (33, 1655)
SbieCtrl_HideMessage=2303,RegisterDragDrop (33, 1655)

In reply to Ryan Cruze:

Ryan Cruze

Can someone tell me how to revert to version 5.31.6 when I have version 5.33.3 installed?

 

Where can I get the old version and how can I install it?  Do I have to uninstall 5.33.3 first?

 

Thanks 

https://www.sandboxie.com/AllVersions

Over install forward and backward has worked (in the past), for me. 

In reply to bj m:

Thans BJM.  I've been away for a while and haven't followed what is going on with Sandboxie since they announced it was being discontinued.  I know Sophos is looking to unload Sandboxie so they don't have to put any more work into it, but are they still responding at all to problems like this?

I'd rather upgrade to a version that fixes this problem than revert to an older version.  But I'm not sure how long I'll have to wait.  The errors I reported here may be the cause of some strange behaviors I'm getting that are hard to describe.

Anyone working on this issue?  If I know someone is working on it I will wait a while to see if I can upversion instead of down.  But if there isn't much hope of a near-term fix guess I'll have to downversion.

in addition to those other errors that have been reported for some versions now, which i also reported and want fixed, do you know sandboxie claims there is no update?  for some versions now, not only has it not informed, but if click to check for updates, it will say the sandboxie website does not report a new version!  i only saw due to ccleaners's healthcheck said there was an update.   i think it stopped reporting updates when sandboxie company was taken over.

i have windows 10. just windows defender.

In reply to a f1:

I don't want to pound on Sophos since in my view they are apparently being very generous offering Sandboxie for free, agreeing to release it to opensource (although not clear why that doesn't seem to be happening yet) and even apparently trying their best to fix bugs.  After all not only is it theirs, but they are still hosting this forum.  They don't have to do that.

So thank you again to Sophos for your support and generosity.

I think Sophos will take complaints no matter what they do.  If they do fixes they will be blamed by those for whom it made things worse, and if they don't do them the people who wanted the fixes in the first place will complain.

But I think it would be a good idea to be careful about fixes and updates.  If Sophos staff is not able to devote the time needed to do them to their usual standards, maybe you should not do them at all.  Don't want to make things worse for a lot of users in an attempt to create a hasty fix for a problem.

I have not been following things since the spinoff was announced so I don't know what is the most stable version.  But based on the comment here, I'll take a chance with 5.31.6 and downgrade now since it doesn't look like this is going to be quickly addressed.  Apparently that version has a chance of eliminating this specific problem.

My plan is to just install it over my currently installed 5.33.3 and let 'er rip.  Fast and dirty.  Wish me luck!

In reply to Ryan Cruze:

Sandboxie 5.33.3 Crack is the advanced software that proposes for the particular purpose of preserving your browsing session and stops the system from changes Upsers. This app provides you to run or browse the application in an isolated space which results in to prevent from making permanent or temporary.

In reply to elish jarry:

Huh?

In reply to Ryan Cruze:

I have the same problem as Maxx Payne and Ryan Cruze.
Unfortunately, the trick with the older version 5.31.6 doesn't help me either.
Even in your latest version, the bug is not fixed. Does anyone care about this mistake?

THX