(In reply to Gabriele Svelto [:gsvelto] from comment #15) > The other type which appears to be more common is a failure with an `ERROR_ACCESS_DENIED` failure when launching a content process, and this seems to affect Windows 10 installations only. Greg. Raymond can you have a look please? This appears to be induced primarily by SbieDll.dll, signed by "Tonalio GmbH", which I think is [Sandboxie](https://github.com/sandboxie-plus/Sandboxie/discussions/3526), an open-source sandboxing utility. So far I've seen DLL versions 5.62.2.0, 5.67.7.0, and 5.69.6.0, so I think it's unlikely that this is either a single user with a misconfigured sandbox or a recently-released DLL with behaviors. Bug 1900175 seems to be about the right timeframe and process-context. Pinging :bobowen for further plausibility assessment while I go test Sandboxie + Nightly.
Bug 1895174 Comment 16 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Gabriele Svelto [:gsvelto] from comment #15) > The other type which appears to be more common is a failure with an `ERROR_ACCESS_DENIED` failure when launching a content process, and this seems to affect Windows 10 installations only. Greg. Raymond can you have a look please? This appears to be induced primarily by SbieDll.dll, signed by "Tonalio GmbH", which I think is [Sandboxie](https://github.com/sandboxie-plus/Sandboxie/discussions/3526), an open-source sandboxing utility. So far I've seen DLL versions 5.62.2.0, 5.67.7.0, and 5.69.6.0, so I think it's unlikely that this is either a single user with a misconfigured sandbox or a recently-released DLL with (**EDIT:**) new behaviors. Bug 1900175 seems to be about the right timeframe and process-context. Pinging :bobowen for further plausibility assessment while I go test Sandboxie + Nightly.