For the last two days, I've been trying to track down issues popping up in Sandboxie after installing the latest version of both Firefox 132.0 and Sandboxie Plus 1.15.1. The issue is caused by the new version of Firefox 132.0 which causes files (dll files) to be blocked by Sandboxie causing a complete crash of Firefox itself. I also noticed it's triggering the built in Microsoft Defender Antivirus to go into overdrive by this. The files being blocked by Sandboxie is in c:\Program Files\Mozilla Firefox which is the mozglue.dll but if you allow this file to be allowed in Sandboxie 'Resource Access' then the next file to be blocked is nss3.dll so it seems the c:\Program Files\Mozilla Firefox folder is causing the issue. I have not tried allowing the entire folder yet to see if this fixes the issue. This issue was with a clean install of Sandboxie 1.15.1 so I tried it with a clean install of the last version of Sandboxie 1.14.10 and got the same results. The last/previous version of Firefox works without issues in Sandboxie 1.14.10. I haven't tried the last/previous version of Firefox in Sandboxie 1.15.1 yet because that's a lot of installing and uninstalling of software but I'm still testing. The issue is with the latest Firefox 132.0 so something changed in this version that Sandboxie doesn't like. Additional details below: Sandboxie Plus (various versions) (64-bit) [Red Box] Windows 10 (64-bit) Firefox 132.0 (64-bit) Thunderbird 128.4.0 (64-bit) Microsoft Edge (64-bit) # # Sandboxie configuration file # [GlobalSettings] Template=7zipShellEx Template=Edge_Fix Template=OfficeClickToRun Template=OfficeLicensing Template=WindowsLive Template=WindowsRasMan DefaultBox=DefaultBox FileRootPath=\??\%SystemDrive%\Sandbox\%USER%\%SANDBOX% KeyRootPath=\REGISTRY\USER\Sandbox_%USER%_%SANDBOX% IpcRootPath=\Sandbox\%USER%\%SANDBOX%\Session_%SESSION% NetworkEnableWFP=y [UserSettings_458A04FA] SbieCtrl_AutoStartAgent=SandMan.exe -autorun BoxGrouping=efaultBox SbieCtrl_EnableAutoStart=y [DefaultBox] Enabled=y BlockNetworkFiles=y BorderColor=#0423ee,off,6 Template=OpenBluetooth Template=SkipHook Template=FileCopy Template=qWave Template=BlockPorts Template=LingerPrograms Template=AutoRecoverIgnore ConfigLevel=10 Template=Edge_Force Template=Firefox_Force Template=Thunderbird Template=BlockAccessWMI UseFileDeleteV2=y UseRegDeleteV2=y ForceProcess=thunderbird.exe ProcessGroup=<StartRunAccess>,thunderbird.exe,plugin-container.exe,msedge.exe,firefox.exe ProcessGroup=<InternetAccess>,thunderbird.exe,msedge.exe,firefox.exe NotifyStartRunAccessDenied=n ClosedIpcPath=!<StartRunAccess>,* NormalFilePath=firefox.exe,D:\Data NormalFilePath=firefox.exe,D:\Jerry NormalFilePath=firefox.exe,D:\Sweepstakes OpenFilePath=firefox.exe,C:\Users\Rockin' Jerry\AppData\Local\Mozilla OpenFilePath=firefox.exe,C:\ProgramData\Mozilla-1de4eec8-1241-4177-a864-e594e8d1fb38 OpenFilePath=thunderbird.exe,C:\ProgramData\Mozilla-1de4eec8-1241-4177-a864-e594e8d1fb38 OpenFilePath=firefox.exe,C:\Users\Rockin' Jerry\AppData\Roaming\Mozilla\Firefox\Profiles\qmv6y2wr.default-release\storage OpenFilePath=firefox.exe,C:\Users\Rockin' Jerry\AppData\Roaming\Mozilla\Firefox\Profiles\qmv6y2wr.default-release\gmp-widevinecdm\4.10.2710.0 OpenFilePath=msedge.exe,C:\Users\Rockin' Jerry\AppData\Local\Microsoft\Edge NormalFilePath=firefox.exe,C:\Users\Rockin' Jerry\AppData\Roaming\Mozilla ReadFilePath=firefox.exe,C:\Users\Rockin' Jerry\Desktop ReadKeyPath=HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FileExts\ ReadKeyPath=HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\Shell\Associations\UrlAssociations\ AllowNetworkAccess=!<InternetAccess>,n ProtectHostImages=y AlertBeforeStart=y HideFirmwareInfo=y RandomRegUID=y HideDiskSerialNumber=y HideNetworkAdapterMAC=y HideNonSystemProcesses=y RecoverFolder=D:\Sweepstakes RecoverFolder=D:\Jerry RecoverFolder=D:\Data UseSecurityMode=y UsePrivacyMode=y AutoDelete=y
Hi, sorry for hijacking the thread a bit, but was anyone experiencing any problems with Firefox 131.0.3 already? I don't remember exactly when I updated Firefox 131.0 to .1, .2 and .3 but with .3 and maybe even .2, I've been experiencing issues on all kind of websites, buttons not responding sometimes, contents not fully loading up sometimes etc. A page refresh helps sometimes, other times terminating and emptying the sandbox then starting Firefox anew etc. It's not full on crashing as on the screenshot of the original post above, but still... And I haven't updated anything else, no Windows updates or anything. My setup: Firefox 131.0.3 (64-bit) Sandboxie Classic 5.67.3 (64-bit) Windows 10.0.19045.4412 (64-bit)
@DjKilla This issue isn't new. In some cases, such as when using about:support, Firefox tries to access files in the Program Files directory with write permissions, which results in those files being copied to a sandbox. Try using the following setting: Code: DontCopy=%ProgramFiles%\Mozilla Firefox\* Also, delete the sandboxed Firefox files from C:\Sandbox\user\DefaultBox\drive\C\Program Files\Mozilla Firefox. @Bellzemos I didn't experience the issue you mentioned with the setup below. I don't use any third-party antivirus. Try it with a clean browser profile. Firefox 132.0.0 (64-bit) Sandboxie Plus 1.15.1 (64-bit) Windows 10.0.19045.5011 (64-bit)
I thought it was a new issue. Never had this happen before and other versions of Firefox work fine. I was just going to add the %ProgramFiles%\Mozilla Firefox\* folder today as read only in 'Resource Access' to see if that works. Glad I saw your post first. As usual, thanks again for your help! I'll do a clean install again with your code.
The 'Read Only' setting could work, but I'm not entirely certain. I may have tried it before. Ultimately, 'DontCopy' appears to be the most suitable option. Additionally, the 'Open' settings can serve as an exclusion for 'ProtectHostImages=y.'
Added the code you posted and everything is working good again. Strange I was hit by this issue and the only thing that changed was updating to the latest version of Firefox. If others over time have had the same issue, I'm surprised the code hasn't been added into Sandboxie to prevent this.
Hi, late reply I know, sorry. The issue I'm having comes and goes. It soulds ridiculous but it's true. One day browsing youtube or something it's terrible, sometiems only ~10% of the page elements get displayed on the screen and a refresh fixes the problem, then sometimes there is no problem at all. Today I have finally updated Firefox from 131.x to 132.x version and on certain pages with embedded videos I started getting the "File is too large to copy into sandbox - xul.dll" warning. Why does Sandoboxie want to copy this file into the sandbox, does it need to, in order for Firefox to function properly? I have hidden the message and it seems to be working ok. If I should encounter any problems I will use the setting below in the Sandboxie.ini. Code: DontCopy=%ProgramFiles%\Mozilla Firefox\* Thank you.
I wrote that setting for DjKilla's issue, so there's no need for you to use it. By default, Sandboxie does not allow writing to files on the host system, so in order to write to those files, they first need to be copied to the sandbox.
Yes, I just find it curious that it wasn't trying to copy xul.dll into sandbox before I updated FF from v131 to v132. Or maybe it was and xul.dll was smaller before the update. I'm not sure, but since I hid the warning message it's all good. Thank you.
