a few months ago i started getting sbie error messages like: 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) SBIE2101 Object name not found: , error ConnectPort (C0000022) access=001F0000 initialized=1 SBIE2101 Object name not found: , error ConnectPort (C0000022) access=001F0000 initialized=1 SBIE2101 Object name not found: , error ConnectPort (C0000022) access=001F0000 initialized=1 i am getting stuff like that on both win10pro64 v2004 running sbie 5.33.3 and win10hom64 v1909 running sbie 5.43.6 what should i do ?
FWIW ~ I've had ..HideMessage..long time - Code: SbieCtrl_HideMessage=2303,CoGetObject (33, 1655) SbieCtrl_HideMessage=2303,RegisterDragDrop (33, 1655) SbieCtrl_HideMessage=2318,ole32.dll
The messages above are messages that can be hidden as doing so wont affect using the sandboxed program (in your case I think it is using Edge), next time you see this messages, click Hide for each of them. You ll find the Hide button within the body of the message. The other messages, you can also Hide them if the sandboxed program works fine. Bo
how do i know that sbie is working safely if it is giving error messages? what is the point of the messages if they can be hidden and ignored?
If the sandboxed program works well, thats a sign that the message can be ignored. Many of the Sandboxie messages are information and not necessarily errors that we have to deal with. Like with Windows messages in the Events log, they are very hard to understand sometimes and (like in W10 now specially) if things are working properly, they can be ignored. Bo
FWIW ~ "Could not hook" and "DLL initialization failed" #166 https://github.com/sandboxie-plus/Sandboxie/issues/166#
