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

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.

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.

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!   :)

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

Adam Smyth said:

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

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.

Adam Smyth said:

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