Tried that yesterday, and again just now ... no change! Think I'll stop all the little programs that come up when I start the computer and see if that allows SB to work. If so, I can add each one back, one at a time and see which one is the culprit.

Walt

Here's something new. Removing all the startup programs didn't help. In desparation, I "restored" my computer to Monday, Feb. 7.
When I click on the SB icon nothing happened. The red dots stayed, but nothing happened.
I then opened the resource access monitor and ran the SB and got the following: (a much smaller file than the previous one). I'm completely confused about what has happened to SB (and seems I can't restore any further back).

(Drive) \Device\CdRom0
(Drive) \Device\Floppy0
(Drive) \Device\HarddiskVolume1
(Unk) 00000002 \Device\CdRom0
(Unk) 00000002 \Device\Ide\IdeDeviceP0T0L0-3
Clsid -------------------------------
File/Key -------------------------------
Image -------------------------------
Image *:\program files\sbie\start.exe
Image c:\program files\billp studios\winpatrol\patrolpro.dll
Image c:\program files\i hate this key deluxe\ihtkh.dll
Image c:\program files\sbie\sbiedll.dll
Image c:\program files\sbie\sbiemsg.dll
Image c:\trayit\trayit4!.dll
Image c:\windows\system32\advapi32.dll
Image c:\windows\system32\clbcatq.dll
Image c:\windows\system32\comdlg32.dll
Image c:\windows\system32\comres.dll
Image c:\windows\system32\fltlib.dll
Image c:\windows\system32\gdi32.dll
Image c:\windows\system32\guard32.dll
Image c:\windows\system32\iertutil.dll
Image c:\windows\system32\imagehlp.dll
Image c:\windows\system32\imm32.dll
Image c:\windows\system32\kernel32.dll
Image c:\windows\system32\msctf.dll
Image c:\windows\system32\msvcrt.dll
Image c:\windows\system32\netapi32.dll
Image c:\windows\system32\normaliz.dll
Image c:\windows\system32\ntdll.dll
Image c:\windows\system32\ole32.dll
Image c:\windows\system32\oleaut32.dll
Image c:\windows\system32\rpcrt4.dll
Image c:\windows\system32\secur32.dll
Image c:\windows\system32\setupapi.dll
Image c:\windows\system32\shell32.dll
Image c:\windows\system32\shlwapi.dll
Image c:\windows\system32\urlmon.dll
Image c:\windows\system32\user32.dll
Image c:\windows\system32\version.dll
Image c:\windows\system32\wininet.dll
Image c:\windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202\comctl32.dll
Ipc -------------------------------
Ipc \BaseNamedObjects\!IETld!Mutex
Ipc \BaseNamedObjects\_!MSFTHISTORY!_
Ipc \BaseNamedObjects\c:!documents and settings!dell!cookies!
Ipc \BaseNamedObjects\c:!documents and settings!dell!ietldcache!
Ipc \BaseNamedObjects\c:!documents and settings!dell!local settings!history!history.ie5!
Ipc \BaseNamedObjects\c:!documents and settings!dell!local settings!temporary internet files!content.ie5!
Ipc \BaseNamedObjects\C:_Documents and Settings_Dell_Cookies_index.dat_49152
Ipc \BaseNamedObjects\C:_Documents and Settings_Dell_IETldCache_index.dat_262144
Ipc \BaseNamedObjects\C:_Documents and Settings_Dell_Local Settings_History_History.IE5_index.dat_65536
Ipc \BaseNamedObjects\C:_Documents and Settings_Dell_Local Settings_Temporary Internet Files_Content.IE5_index.dat_2129920
Ipc \BaseNamedObjects\SBIE_DummyEvent_3896
Ipc \BaseNamedObjects\SBIE_ServiceInitComplete_DcomLaunch
Ipc \BaseNamedObjects\SBIE_ServiceInitComplete_RpcSs
Ipc \BaseNamedObjects\shell.{210A4BA0-3AEA-1069-A2D9-08002B30309D}
Ipc \BaseNamedObjects\shell.{7CB834F0-527B-11D2-9D1F-0000F805CA57}
Ipc \BaseNamedObjects\shell.{A48F1A32-A340-11D1-BC6B-00A0C90312E1}
Ipc \BaseNamedObjects\ZonesCounterMutex
Ipc O \BaseNamedObjects\CiceroSharedMemDefaultS-1-5-21-1229272821-861567501-1801674531-1003
Ipc O \BaseNamedObjects\CTF.Asm.MutexDefaultS-1-5-21-1229272821-861567501-1801674531-1003
Ipc O \BaseNamedObjects\CTF.Compart.MutexDefaultS-1-5-21-1229272821-861567501-1801674531-1003
Ipc O \BaseNamedObjects\CTF.Layouts.MutexDefaultS-1-5-21-1229272821-861567501-1801674531-1003
Ipc O \BaseNamedObjects\CTF.LBES.MutexDefaultS-1-5-21-1229272821-861567501-1801674531-1003
Ipc O \BaseNamedObjects\CTF.TimListCache.FMPDefaultS-1-5-21-1229272821-861567501-1801674531-1003MUTEX.DefaultS-1-5-21-1229272821-861567501-1801674531-1003
Ipc O \BaseNamedObjects\CTF.TimListCache.FMPDefaultS-1-5-21-1229272821-861567501-1801674531-1003SFM.DefaultS-1-5-21-1229272821-861567501-1801674531-1003
Ipc O \BaseNamedObjects\CTF.TMD.MutexDefaultS-1-5-21-1229272821-861567501-1801674531-1003
Ipc O \BaseNamedObjects\Sandboxie_DeviceIdList
Ipc O \BaseNamedObjects\Sandboxie_DeviceSetupClasses
Ipc O \LsaAuthenticationPort
Ipc O \Security\LSA_AUTHENTICATION_INITIALIZED
Ipc X \BaseNamedObjects\!IETld!Mutex
Ipc X \BaseNamedObjects\_!MSFTHISTORY!_
Ipc X \BaseNamedObjects\c:!documents and settings!dell!cookies!
Ipc X \BaseNamedObjects\c:!documents and settings!dell!ietldcache!
Ipc X \BaseNamedObjects\c:!documents and settings!dell!local settings!history!history.ie5!
Ipc X \BaseNamedObjects\c:!documents and settings!dell!local settings!temporary internet files!content.ie5!
Ipc X \BaseNamedObjects\C:_Documents and Settings_Dell_Cookies_index.dat_49152
Ipc X \BaseNamedObjects\C:_Documents and Settings_Dell_IETldCache_index.dat_262144
Ipc X \BaseNamedObjects\C:_Documents and Settings_Dell_Local Settings_History_History.IE5_index.dat_65536
Ipc X \BaseNamedObjects\C:_Documents and Settings_Dell_Local Settings_Temporary Internet Files_Content.IE5_index.dat_2129920
Pipe -------------------------------
Pipe X \Device\NamedPipe\lsarpc
Pipe X \Device\NamedPipe\wkssvc
WinCls -------------------------------
WinCls X Progman
WinCls X TrayItHook
WinCls X WinPatrol

Walt

The latest log indicates only Start.exe is running in the sandbox:



As opposed to earlier logs which shows more programs:



The first thing that should happen in the sandbox is that Start.exe runs SandboxieRpcSs.exe. According to your latest log, SandboxieRpcSs.exe did not start. And the fact that you see red dots but nothing is happening, that means Start.exe is waiting for SandboxieRpcSs.exe.

So the question is what is interfering with SandboxieRpcSs.exe.

* * *

As a first step, I would suggest: (1) in Sandboxie Control, go to Sandbox menu, Set Container Folder, and select a new location instead of C:\SANDBOX. For example instead of C:\Sandbox\%USER%\%SANDBOX% enter C:\NewSandbox\%USER%\%SANDBOX%
Then create a new sandbox, to be sure you're using default settings in Sandboxie. And try running Firefox in this new sandbox.

* * *

If this doesn't work, and you don't mind experimenting, I would suggest that you fully uninstall the other programs that appear in your log. That means WinPatrol, I Hate This Key Deluxe, TrayIt, and COMODO. I'm not saying never reinstalling them again -- just uninstall long enough to try to see if this makes any difference. I understand it's a hassle but I don't know what else to suggest here.

I tried a new location as you suggested and also created a new Sandbox and same problem occurred.
I certainly can uninstall the programs you mention, but first I went to the fileSandboxieRpcSs.exe in the Sbie folder and got an error message.

I will attach the first two error messages, but the third which is a long scrolling report was too big to copy. Theoretically, the report is sent to someone (or someplace).

That in itself is not an indication of any problem. SandboxieRpcSs is not designed to run outside the sandbox, and it can crash in this way if you run it outside the sandbox.

I just remember something from a problem report not long ago:

http://www.sandboxie.com/phpbb/viewtopic.php?p=63980#63980



Perhaps you should try it.

I ran the Kaspersky file and it seemed to have found one file that it removed, but this did not allow SB to open.
I decided that the problem was most likely Comodo which I had updated and so I removed (uninstalled) it. But still no help.
So, I ran regedit and "find" .. comodo, and removed all items showing comodo in the registry ... and voila, sandboxie now works again.

So, again, t hank you for all the time and effort you spent working with me on this problem and I guess I'd better get another firewall.

Walt

Glad to hear you figured out the cause of the problem. But I'm sorry to hear it is a conflict that cannot be fixed in some way. Some people have reported an incompatibility between COMODO and Sandboxie but I've never been able to reproduce the problem.