Anyone seeing occasional OLE init / hook failed errors from sandboxie?

In Windows 8 x64 using sb 5.31.4 and the latest chrome occasionally I see this error:

SBIE2303 Could not hook CoGetObject (33, 1655)
SBIE2303 Could not hook RegisterDragDrop (33, 1655)
SBIE2318 DLL initialization failed for 'ole32.dll'

I don't know what it means. Everything appears to work normal. If I should report somewhere else please tell me where.

  • In reply to Pankaj goyal:

    Pankaj goyal

    I have the same issue.

    I have windows 10 ltsc 64 bit.

    Kaspersky Internet security 20

    NVT OS Armor

    NVT Exe Radar Pro

    Windows 10 firewall control

    Um, maybe you do not want to hear that you're probably running programs with Known Conflicts.
    https://www.sandboxie.com/KnownConflicts
    And, maybe you do not want to hear that Kaspersky Support...advises not to run other security solutions with Kaspersky.

    $.02

  • I have the same problem with Chrome and SBIE 5.31.6 on windows 8.1 64

    Firefox, on the other hand works fine sandboxed.

    Does anyone know if these messages mean that chrome isn't completely sandboxed?

  • This seems to be caused by a new feature of Chrome 79, "Audio Sandbox" (see https://support.google.com/chrome/a/answer/7679408/).

    Since I use Windows, I disable this by modifying registry at HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome => Add DWORD value "AudioSandboxEnabled" => Set it to 0

    Please note that I'm not sure if this would compromise security of Chrome. Anyway, it works for me and the error messages go away.

  • In reply to Adam Smyth:

    I have no Chrome...

    In my opinion is not usual to add key in the SO, for try to solve a Sophos problem.

    If this 'solution' is a real solution, so dear Sophos, fix the problem re writing the code

    and eventually save us from this long time hell.

    With no audio, is not possible to use Sandboxie.

     

     

    Ah, this morning Windows 10 inform me that sandboxie is NOT COMPATIBLE with SO!   :)

  • In reply to Adam Smyth:

    I don't know why but that doesn't work for me :-(

    I found another solution. Now i start Chrome with this command line 

    "C:\Program Files\Sandboxie\Start.exe" Chrome.exe --no-sandbox 

    and seems that work, but maybe is not good for the security of the system

  • In reply to Adam Smyth:

    Adam Smyth

    This seems to be caused by a new feature of Chrome 79, "Audio Sandbox" (see https://support.google.com/chrome/a/answer/7679408/).

    Since I use Windows, I disable this by modifying registry at HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome => Add DWORD value "AudioSandboxEnabled" => Set it to 0

    Please note that I'm not sure if this would compromise security of Chrome. Anyway, it works for me and the error messages go away.

     

    can't locate  HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome  , got only microsoft under polices tree

  • In reply to Q cai:

    Not sure about your case. Mine had an already-existing key "HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome", and I just created the DWORD value "AudioSandboxEnabled".

    You could try adding new keys of "Google\Chrome" under "HKEY_LOCAL_MACHINE\Software\Policies". Again, can't guarantee there's no side effect.

    BTW, my Chrome is the enterprise version, downloaded from here: https://enterprise.google.com/chrome/chrome-browser/, running on Windows 8.1. This might be different from the more common version.

  • In reply to Adam Smyth:

    Adam Smyth

    Not sure about your case. Mine had an already-existing key "HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome", and I just created the DWORD value "AudioSandboxEnabled".

    You could try adding new keys of "Google\Chrome" under "HKEY_LOCAL_MACHINE\Software\Policies". Again, can't guarantee there's no side effect.

    BTW, my Chrome is the enterprise version, downloaded from here: https://enterprise.google.com/chrome/chrome-browser/, running on Windows 8.1. This might be different from the more common version.

     

    got mine here https://www.google.com/chrome/?standalone=1&platform=win64

    currently using cunsumer version. wondering what's difference between these two.

    losing patience with sbie . windows installer stopped working for months. 

    widely used applications become increasingly unsupported

  • I've been getting this message for the Chrome browser (79.0.3945.88 and on the previous version) lately on Win 10 64-bit using Sandboxie v5.31.6 and now with v5.33.1. 

    Sandboxie works fine with Firefox and with the Brave browser. 

    Chrome continues to work as far as I can see, BUT I no longer trust that it is secured with Sandboxie at the moment.

     

    Very. Disappointed.

  • In reply to Miss Identified:

    1. I have switched to the Brave browser for time being. It seems to work just fine in Sandboxie v5.31.6. and v5.33.1.

    2. The Outlook 2016 seems to work just fine with Sandboxie v5.31.6 and under v5.33.1, I get authentication errors left and right.

    3. For time being, I am staying with v5.31.6 and monitor the forum to see if further updates become available.

     

    I am asking  Sophos to please clarify the support of Sandboxie going forward. There are a lot of folks here who depend on this application. Thank you.

  • BUMP in hopes that something may be seen and fixed one day.  Also had to use Brave browser to post... wtf?

    There have now been at least couple of browser updates since my last post to this thread now, but using it with Sandboxie 533.1 (64-bit) I'm STILL getting the 3 errors, as reported in the first post. Current Chrome browser Version 79.0.3945.130 (Official Build) (64-bit).

    Brave browser, using the exact same version, (Brave is up to date Version 1.2.43 Chromium: 79.0.3945.130 (Official Build) (64-bit))

    is still fine in Sandboxie, along with Firefox. No pop-up code errors at all.

    Since Brave is Chromium-based why does it work without showing errors and yet Chrome always gives me that pop-up?

    I do not feel safe browsing the web without the protection of Sandboxie after all these years, so I'm hoping that Sophos sort this problem out asap as it's been going on for months now.

  • In reply to Miss Identified:

    This appears to be related to Google Chrome's sandbox and it's been hardened to prevent anyone from hooking these functions.

    You can try running chrome without it's sandbox (--no-sandbox on the command line)?

  • In reply to Akhilesh@Sophos:

    This is how I start Chrome : "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disk-cache-dir=C:\_Cache  --enable-features="dns-over-https<DoHTrial -no-sandbox"

    Bill

  • In reply to BilleBarrett:

    This command line didn't work for me either. However the following did:

    "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disk-cache-dir=C:\_Cache  --enable-features="dns-over-https<DoHTrial" --no-sandbox

  • In reply to Akhilesh@Sophos:

    Um, anything wrong with simply adding Hide ?   5.33.1

    SbieCtrl_HideMessage=2303,ReleaseStgMedium (33, 1655)
    SbieCtrl_HideMessage=2303,CoGetObject (33, 1655)
    SbieCtrl_HideMessage=2303,RegisterDragDrop (33, 1655)
    SbieCtrl_HideMessage=2318,ole32.dll

    I'm not seeing change to my Chrome browsing by adding HideMessage.