Sandboxie-Plus 1.13.6 (Pre-Release)

Discussion in 'Sandboxie (SBIE Open Source) Plus & Classic' started by DavidXanatos, Apr 21, 2024.

  1. algol1

    algol1 Registered Member

    Joined:
    Aug 10, 2020
    Posts:
    344
    Location:
    Vienna, Austria
    Now who would've thought?! That constant nuisance of "auto-updater" is malfunctioning again!

    This time around in fact v1.13.6a IS offered for download with the usual info that all running programs will be closed during upgrade. And then the following message will pop-up:
    Clipboard-1.jpg
    Needlss to say that all 3 retries will fail either. After that the updater-section in "Global Settings" still points to v1,13.6 (without an "a").

    Next I stumbled upon the patch at GitHub and looked into it. The ONLY binary different file in there (for x64) is "SbieDll.pdb". So I manually patched that pdb-file over the original.

    When opening a sandboxed process again I immediately checked the options in Sandman. Result: The manual update-check from help-menu still would offer the v1.13.6a download that again will fail to install and the "Global Options"-updater-section still says Current: v1.13.6 (without an a) but will still indicate an available update to v1.13.6a on the preview-channel (which I'm currently subscribed to).

    This is the current situation AFTER THE MANUAL PATCH of the updated "SbieDll.pdb". So at the moment I really have no clue as to which version I'm actually on!

    Addendum: I also tried to manually shut down and exit Sandboxie altogether to force SbieDrv to close and then started looking for most recent downloads on the C:-drive to find and start the downloaded updater from there manually. Yet the ONLY very recently generated folder was found to be "c:\...\AppData\Local\Temp\sandboxie-updater" which turned out to be EMPTY on inspection. So no downloaded update-file present to run manually from there either.
     
    Last edited: Apr 26, 2024
  2. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    24,188
    Location:
    UK
    I get exactly the same issue above as @algol1 on Win 10 and Win 11 when I try to use the auto updater to go to 1.3.6a

    That is why I am still on 1.3.6

    (I did also briefly see a popup saying admin rights were required. I do have make things think they are running elevated and also drop rights selected)
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.