-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Could not hook" and "DLL initialization failed" #166
Comments
Are you running some other security software that may interfear with sandboxie? |
Just Windows Defender. |
Ah that may be chrome related its know that chrome sometimes causes a few error messages, if aside of the messages everything works than i would say just hide them |
There's no other running anti-malware. I disabled Defender and excluded the Sandboxie directory. |
@DavidXanatos Perhaps it would be better to remove those errors by default without user intervention in a future update... if you're interested, these are the required steps to reproduce them:
|
@isaak654 The issue was caused by a mitigation policy chrome has set which has interfered with the hooking mechanism, this issue will be fixed in the nextbuild |
I got the following errors while opening Google Calendar in Sanboxie while running Procmon.
I've included Procmon output filtered by removing successful events and anything but Chrome, Sandboxie, Explorer and the basic Windows system files.
Logfile.xlsx
Here's the errors:
SBIE2303 Could not hook CoGetObject (33, 1655)
SBIE2303 Could not hook RegisterDragDrop (33, 1655)
SBIE2318 DLL initialization failed for 'ole32.dll'
SBIE2303 Could not hook CM_Add_Driver_PackageW (33, 1655)
SBIE2318 DLL initialization failed for 'cfgmgr32.dll'
SBIE2303 Could not hook SetCurrentProcessExplicitAppUserModelID (33, 1655)
The text was updated successfully, but these errors were encountered: