Please fix Chrome process cancelations due to QWAVEdrv [SOLVED]

[cornflake]

This is now a problem for logging in to ebay as well, on Windows 8.1 and Windows 10, and will not work unless qwave bypass is enabled.

[bo.elam]

This is now a problem for logging in to ebay as well, on Windows 8.1 and Windows 10, and will not work unless qwave bypass is enabled.

If you don't want to allow access to Qwave, stop using Chrome. I use Firefox, I don't enable the setting in any sandbox and have never seen any message related to Google hangouts or visited any site that's broken because I don't enable Qwave. Supposedlty we might see the Qwave thing in other browsers but I havent seen it in Firefox. Switch browsers and forget about it or enable access to Qwave, those are your choices.

Bo

[cornflake]

Syrinx gave me two fixes to this issue either of which works in Windows 8.1 (and probably WIndows 10 as well). Thanks!

#1: Add this line to a sandbox to block Chrome from attempting to communicate with the QWAVE driver:

Code: Select all

ClosedFilePath=\Device\QWAVEdrv

or #2: Disable the QWAVE service:
services.msc > Quality Windows Audio Video Experience (QWAVE) > Startup > Disabled and stop the service if it's running.

I went with #1 that way apps not running in sandboxie can still take advantage of QWAVE. Is there a good way to enable #1 globally? I could add it to [GlobalSettings] but any new sandbox I create still has Template=qWave so would the template settings in the sandbox override the global closedfilepath?

[Barb@Invincea]

Hello cornflake,

I tested the ClosedFilePath, and it did allow the QWAVE service to run, however, no crashes appeared when the qwave template was disabled in a specific Sandbox.

You can find how Global and Sandbox settings override by looking at the bottom part of this section:
https://www.sandboxie.com/index.php?SandboxieIni
Any of the Sandbox settings will be overridden from the Global settings if added to a Sandbox.

You could try to add ClosedPipePath=\Device\QWAVEdrv in the GlobalSettings, as well as the ClosedFile path setting provided by Syrinx. The most restrictive option should be the one that will be selected. However, since no matter what setting I use, the qwave service gets started, I am not sure this will satisfy.

Regards
Barb.-

[Syrinx]

There are two entries for qwave, the service: QWAVE and the driver: QWAVEdrv
My suggestion was based on the template but I hadn't tested it myself so thanks for reporting on the service starting anyway Barb.
A workaround which seems to do the trick via [GlobalSettings] is to instead use:

Code: Select all

ClosedFilePath=*\QWAVE*

As Barb said it does apply Closed over Open so no need to worry about the pre-included template on new boxes. Tested it just now on Windows 10 x64, Chrome:ebay login page, SBIE 5.21.2 though I have started drinking so a re-test or verification would be helpful :P
The resource manager wasn't showing an X for anything QWAVE related tho with this updated ClosedFilePath the service didn't start. I was able to test it with a global ClosedFilePath= and an OpenPipePath= inside the specific box for an actual file and the global Closed won.

P.S. Is there even a ClosedPipePath= ?

Update: This workaround also blocks the qwave.dll which is needed for some applications to run properly. One such example is Discord which can not properly start without it so if this workaround is applied this should be high on your troubleshooting list if other software has issues.

[cornflake]

I went with ClosedFilePath=*QWAVE* in [GlobalSettings] to stop the service from being started. That's kind of excessive since it blocks anything with the name qwave but it's fine with me. Also it works even if a sandbox has Template=qWave. Thanks