hexchat freezes when starting sandboxie

[RichAC]

I try to load hexchat in sandboxie, but it freezes at connecting to server and I have to terminate the application.

It works fine otherwise without sandboxie, any way to fix?

[Craig@Invincea]

Installed directly INTO Sandboxie?
SBIE Version?
OS?
3rd party security software installed? If so, what?

Very doubtful that this of program would work, these types of programs should be installed on your host and then run "as sandboxed."

Otherwise, I'd suggest a VM environment.

[RichAC]

I have the same problem.

hexchat freezes when run from sandboxie. After trying to connect to server. anybody have a clue how to fix this? Programs like this is the whole reason to use sandboxie lol. People can' physically break your pc from across the internet, and I can't afford a new one so I want to use sandboxie with it

[Curt@invincea]

Run the resource access monitor.

[Syrinx]

Just tried it with Sandboxie 5.13.2 and a random channel in hexchat with a default install [2.12.1 x64 non portable] in a default sandbox and had no crashes or issues on a Windows 7 x64 VM. I did notice hexchat has options for addons so if you have any you may want to try disabling those and see if it helps much like sometimes browser addons can cause issues...

[RichAC]

I right click on the hexchat.exe file and click run in sandboxie. it loads freezes on connecting to server. in windows 10 and 7 home 64 bit. What is your secret? I don't have any addons on sandboxie. I'm setting ssl sasl and hitting connect.

[RichAC]

Run the resource access monitor.

what is that? how?

[Syrinx]

In Sandboxie Control goto the Menu > File > Resource Access Monitor
This will open a box that should be blank if nothing is running inside sandboxie.
Run hexchat sandboxed and try to connect normally.

After you experience your issue go back to that box and select 'Copy contents to Clipboard and Close Window'
Then paste the contents here please.

Including more information concerning your other security/system software may also be helpful.

As for the addons, I was referring to hexchat as it has an area for them.

[RichAC]

Thanks for your time. Here is the paste.

(Drive) \Device\CdRom0
(Drive) \Device\HarddiskVolume10
(Drive) \Device\HarddiskVolume11
(Drive) \Device\HarddiskVolume12
(Drive) \Device\HarddiskVolume2
(Drive) \Device\HarddiskVolume9
Clsid -------------------------------
Clsid {D63B10C5-BB46-4990-A94F-E40B9D520160} RuntimeBroker
File/Key -------------------------------
Image -------------------------------
Ipc -------------------------------
Ipc \BaseNamedObjects\__ComCatalogCache__
Ipc \BaseNamedObjects\C:*ProgramData*Microsoft*Windows*Caches*{6AF0698E-D558-4F6E-9B3C-3716689AF493}.2.ver0x0000000000000001.db
Ipc \BaseNamedObjects\C:*ProgramData*Microsoft*Windows*Caches*{DDF571F2-BE98-426D-8288-1A9A39C3FDA2}.2.ver0x0000000000000001.db
Ipc \BaseNamedObjects\C:*ProgramData*Microsoft*Windows*Caches*cversions.2.ro
Ipc \BaseNamedObjects\windows_shell_global_counters
Ipc \RPC Control\epmapper
Ipc \RPC Control\OLE08D6D36D789AE6DC843D2AD1DD1B
Ipc \RPC Control\OLE7E9972BDC41A90FBA99BA47E5556
Ipc \RPC Control\OLEDFC30460E53124FF954FF7A643BF
Ipc \Sessions\1\BaseNamedObjects\__ComCatalogCache__
Ipc \Sessions\1\BaseNamedObjects\C:*ProgramData*Microsoft*Windows*Caches*{6AF0698E-D558-4F6E-9B3C-3716689AF493}.2.ver0x0000000000000001.db
Ipc \Sessions\1\BaseNamedObjects\C:*ProgramData*Microsoft*Windows*Caches*{DDF571F2-BE98-426D-8288-1A9A39C3FDA2}.2.ver0x0000000000000001.db
Ipc \Sessions\1\BaseNamedObjects\C:*ProgramData*Microsoft*Windows*Caches*cversions.2.ro
Ipc \Sessions\1\BaseNamedObjects\C:*Users******AppData*Local*Microsoft*Windows*Caches*{AFBF9F1A-8EE8-4C77-AF34-C647E37CA0D9}.1.ver0x0000000000000008.db
Ipc \Sessions\1\BaseNamedObjects\C:*Users******AppData*Local*Microsoft*Windows*Caches*cversions.1.ro
Ipc \Sessions\1\BaseNamedObjects\CrSharedMem_07865088d51c542c5715ea7bdc0bd7cc3a95cd602270279b9d8ac692e62121f5
Ipc \Sessions\1\BaseNamedObjects\CrSharedMem_08f1c7ef34d3d4f00968b8268f4ec5a4f114eabb6016e8c2f0d6d17212f7c57d
Ipc \Sessions\1\BaseNamedObjects\CrSharedMem_4de7e80633401986f5f1c798d01558740d3a824eb1a5f50b91163ce94770e4cd
Ipc \Sessions\1\BaseNamedObjects\CrSharedMem_514690ca84f6877d8294ad0bab53cecd70c759370e55c23593fe33fefed05993
Ipc \Sessions\1\BaseNamedObjects\CrSharedMem_6ab85c10c6ea8d19c25da4380ea149a7efa38034af0b4ba5cd59225faf56fb3e
Ipc \Sessions\1\BaseNamedObjects\CrSharedMem_87c9d49fa502abca3825883a629ed5c9c272b15dd4d98901ee5f30d66126a93d
Ipc \Sessions\1\BaseNamedObjects\CrSharedMem_91b66e2556d6857b4f011fe77bcf6adcf14b6a689838b45a77ab23bf742dd6a6
Ipc \Sessions\1\BaseNamedObjects\CrSharedMem_d2d00be26ed0e167564511d56a67623548d0f63dccd80484b5ae8457592253d2
Ipc \Sessions\1\BaseNamedObjects\CrSharedMem_fc55894858fadc872530e870d1b31b0de2e8d5820ad53be3e33eaf2cf65e0aac
Ipc \Sessions\1\BaseNamedObjects\SBIE_BOXED_DummyEvent_7276
Ipc \Sessions\1\BaseNamedObjects\SBIE_BOXED_DummyEvent_8924
Ipc \Sessions\1\BaseNamedObjects\SBIE_BOXED_ServiceInitComplete_DcomLaunch
Ipc \Sessions\1\BaseNamedObjects\SBIE_BOXED_ServiceInitComplete_RpcSs
Ipc \Sessions\1\BaseNamedObjects\SboxSession
Ipc \Sessions\1\BaseNamedObjects\SessionImmersiveColorMutex
Ipc \Sessions\1\BaseNamedObjects\SessionImmersiveColorPreference
Ipc \Sessions\1\BaseNamedObjects\SM0:7276:120:WilError_01
Ipc \Sessions\1\BaseNamedObjects\SM0:7276:120:WilError_01_p0
Ipc \Sessions\1\BaseNamedObjects\SM0:7276:120:WilError_01_p0h
Ipc \Sessions\1\BaseNamedObjects\SyncRootManager
Ipc \Sessions\1\BaseNamedObjects\windows_shell_global_counters
Ipc O \BaseNamedObjects\msctf.serverDefault1
Ipc O \KernelObjects\MaximumCommitCondition
Ipc O \KnownDlls\advapi32.dll
Ipc O \KnownDlls\bcryptPrimitives.dll
Ipc O \KnownDlls\cfgmgr32.dll
Ipc O \KnownDlls\clbcatq.dll
Ipc O \KnownDlls\combase.dll
Ipc O \KnownDlls\COMDLG32.dll
Ipc O \KnownDlls\gdi32.dll
Ipc O \KnownDlls\gdi32full.dll
Ipc O \KnownDlls\IMM32.dll
Ipc O \KnownDlls\kernel.appcore.dll
Ipc O \KnownDlls\kernel32.dll
Ipc O \KnownDlls\kernelbase.dll
Ipc O \KnownDlls\MSCTF.dll
Ipc O \KnownDlls\msvcp_win.dll
Ipc O \KnownDlls\MSVCRT.dll
Ipc O \KnownDlls\NSI.dll
Ipc O \KnownDlls\ole32.dll
Ipc O \KnownDlls\OLEAUT32.dll
Ipc O \KnownDlls\powrprof.dll
Ipc O \KnownDlls\profapi.dll
Ipc O \KnownDlls\PSAPI.DLL
Ipc O \KnownDlls\rpcrt4.dll
Ipc O \KnownDlls\sechost.dll
Ipc O \KnownDlls\shcore.dll
Ipc O \KnownDlls\SHELL32.dll
Ipc O \KnownDlls\SHLWAPI.dll
Ipc O \KnownDlls\ucrtbase.dll
Ipc O \KnownDlls\user32.dll
Ipc O \KnownDlls\USP10.dll
Ipc O \KnownDlls\win32u.dll
Ipc O \KnownDlls\windows.storage.dll
Ipc O \KnownDlls\WS2_32.dll
Ipc O \RPC Control\DNSResolver
Ipc O \RPC Control\lsapolicylookup
Ipc O \RPC Control\lsasspirpc
Ipc O \RPC Control\SbieSvcPort
Ipc O \Security\LSA_AUTHENTICATION_INITIALIZED
Ipc O \Sessions\1\BaseNamedObjects\CicLoadWinStaWinSta0
Ipc O \Sessions\1\BaseNamedObjects\CTF.AsmListCache.FMPDefault1S-1-5-21-135036270-2551604889-3863237831-1001
Ipc O \Sessions\1\BaseNamedObjects\MSCTF.Asm.MutexDefault1S-1-5-21-135036270-2551604889-3863237831-1001
Ipc O \Sessions\1\BaseNamedObjects\MSCTF.CtfMonitorInstMutexDefault1
Ipc O \Sessions\1\Windows\ApiPort
Ipc O \Sessions\1\Windows\SharedSection
Ipc O \Sessions\1\Windows\Theme2315112916
Ipc O \Sessions\1\Windows\ThemeSection
Ipc O \ThemeApiPort
Ipc O \Windows\Theme860292018
Pipe -------------------------------
Pipe ?
Pipe \Device\00000023
Pipe \Device\CNG
Pipe \Device\HarddiskVolume1
Pipe \Device\HarddiskVolume10
Pipe \Device\HarddiskVolume11
Pipe \Device\HarddiskVolume12
Pipe \Device\HarddiskVolume2
Pipe \Device\HarddiskVolume3
Pipe \Device\HarddiskVolume9
Pipe \Device\KsecDD
Pipe \Device\MountPointManager
Pipe \device\namedpipe\srvsvc
Pipe \device\namedpipe\wkssvc
Pipe O \Device\Afd
Pipe O \Device\NamedPipe\
Pipe O \device\namedpipe\
Pipe O \Device\NetBT_Tcpip_{70F1F4F8-9F82-4067-A18D-53091E1A9A88}
Pipe O \Device\Nsi
WinCls -------------------------------
WinCls O Shell_TrayWnd
WinCls X Progman

[Syrinx]

It is quite possible I am missing something but I don't see anything in there that I really even want to attempt opening. =(
I suppose you could try opening *\BaseNamedObjects*\CrSharedMem_* but I'd be amazed if that helped at all. :-/ Likely not even worth your time to test.

So, sorry but it looks like something else could be at play here yet at this time I haven't a clue as to what it is...

Might you be open to collecting a procmon log?