Firefox / Edge not responding with ESET banking protection

[Dmytro9099]

Hi.
Windows 8.1 64-bit
Firefox 96.0.1
Sandboxie Classic 5.55.7
Firefox freezes and not responding when i run it in sandboxie. It appears after update to ver 96.0.1. Disabling extensions didn't help.
A clean reinstall Firefox, disabling antivirus protection didn't help
Here I find user with same problem ( but in german): https://www.camp-firefox.de/forum/thema/134153-firefox-96-0-sandboxie-problem-ursachensuche/

[isaak654]

It's so weird to read about all these issues with Firefox and Thunderbird.... maybe some extra effort should be put to investigate about the update system (on both products) that seems to affect the sandboxes somehow.

[Rngexile]

FF + TB + sandboxie user here since +15 years.
Lucky user, never had a problem.

Today : FF 96.01 + Win 10 last + sandboxie-plus 1.07 + many dedicated FF boxes (all hardened, some with new privacy mode) and many FF's profiles, many extensions + Win Defender AV + windows exploit protection with some tweaks from base config to add some (not all can be used with FF).
No problem at all.

I installed FF (and TB) outside sandboxie, without install update service and disabled updates with BITS (https://www.askvg.com/tip-block-firefox-to-download-updates-using-bits-on-windows/). FF is configured to check updates and let me chose when to install them (outside sandboxie, ofc), it may be related ?
Old gen CPU intel i7-3770K, without some new security stuff with new gen, it may be related ?

[isaak654]

I found out this portion of code that controls the browser updates interferences:

Sandboxie/Sandboxie/core/dll/proc.c

Lines 2224 to 2228 in 0da573a

	if (Dll_ImageType == DLL_IMAGE_MOZILLA_FIREFOX) {
	MatchExe = L"updater.exe";
	MatchDir = L"\\mozilla firefox\\updates\\";
	SoftName = L"Mozilla Firefox";

I would suggest to replace the MatchDir line with:
MatchDir = L"\\Mozilla\\updates\\";

and adding below the Firefox code:

    } else if (Dll_ImageType == DLL_IMAGE_MOZILLA_THUNDERBIRD) {

        // the following Proc_IsProcessRunning condition may be optional here
        if (! Proc_IsProcessRunning(L"thunderbird.exe"))
            return FALSE;

        MatchExe = L"updater.exe";
        MatchDir = L"\\Mozilla\\updates\\";
        SoftName = L"Mozilla Thunderbird";

A long time ago, the updates folder was located in %ProgramFiles%, but this doesn't seem the case anymore with Mozilla products (at least on my setup).

UPDATE: my suggestion was partially applied here for 1.0.8 build.

[isaak654]

Hi.
Windows 8.1 64-bit
Firefox 96.0.1
Sandboxie Classic 5.55.7
Firefox freezes and not responding when i run it in sandboxie. It appears after update to ver 96.0.1. Disabling extensions didn't help.
A clean reinstall Firefox, disabling antivirus protection didn't help

Can you notice any difference with hardware acceleration disabled? Did you try to create a new sandbox too?

[Dmytro9099]

Hi.
Windows 8.1 64-bit
Firefox 96.0.1
Sandboxie Classic 5.55.7
Firefox freezes and not responding when i run it in sandboxie. It appears after update to ver 96.0.1. Disabling extensions didn't help.
A clean reinstall Firefox, disabling antivirus protection didn't help

Can you notice any difference with hardware acceleration disabled? Did you try to create a new sandbox too?

I disabled hardware acceleration and created new sandbox ( after issue appeared, I updated to last SB ver with uninstalling previous one). But it didn't help. There is processes that created in sandbox, while FF freeze after launch

It turned out, that 2-3 minutes later, FF eventually runs, but it still freeze around 2 min every time i open new page.
In addition, FF Shut downs incorrectly. There is log from FF crashreporter:
CrashReporter.txt

[randyabr]

I too found Firefox either not opening or stop responding, etc. with Sandboxie Plus v 1.07. I too tried uninstalling and reinstlling everything. This is what worked instantly for me.

Uninstall Firefox and then install the Firefox enterprise version. The enterprise version is a stable version that only gets security updates on a regular basis and not feature updates. After doing this FF opened right up. In fact, perhaps a bit faster.
I was going to downgrade to a previous version but Mozilla recommended trying the enterprise version before downgrading due to security considerations.

hxxps://www.mozilla.org/en-US/firefox/enterprise/

[0x391F]

It turned out, that 2-3 minutes later, FF eventually runs, but it still freeze around 2 min every time i open new page. In addition, FF Shut downs incorrectly. There is log from FF crashreporter: CrashReporter.txt

+1, the same problem. Firefox works eventually after a few minutes.
OS: Windows 10 Enterprise LTSC 2021 x64 (21H2)
Sandboxie 5.55.8 / Sandboxie-Plus v1.0.8

[DavidXanatos]

@0x391F does deletign the box content solves your issue?

[Gishmasters]

The same with firefoxportable 96.01 but even worse - firefox doesnt opening. This issue came with 96 release, with older 95 no problems.

[mustwakeup]

This issue came with 96 release, with older 95 no problems.

BUT i have dual boot w7x64 and w10x64 and this only occur in w10x64. I try many other browsers, - include firefox based browsers - and this is only in firefox.

[0x391F]

@0x391F does deletign the box content solves your issue?

No, it doesn't.

[ghost]

Win10 21H2 64Bit + Firefox 96.0.1/96.0.2 + Sandboxie Classic 5.55.8
I think this issue may caused by anti-virus software(I use the ESET Internet Security).
I found the issue solved in my computer after I disabled the "Banking & Payment Protection" function of ESET(must disable it in the standalone Advanced setup page, not only in the Main Window->Setup page).

[0x391F]

Win10 21H2 64Bit + Firefox 96.0.1/96.0.2 + Sandboxie Classic 5.55.8 I think this issue may caused by anti-virus software(I use the ESET Internet Security). I found the issue solved in my computer after I disabled the "Banking & Payment Protection" function of ESET(must disable it in the standalone Advanced setup page, not only in the Main Window->Setup page).

Yeah, it works! What a strange bug!

[mustwakeup]

Thanks, works now.

[Gishmasters]

DavidXanatos

Hello! Will you plane to fix it in future release? Disableing the "Banking & Payment Protection" in Eset is works, but this is temporary solution at this moment.

[Foosec]

Can confirm the Eset issue. Disabling Banking & Payment Protection works.
No such issue in Chrome however.

[0x391F]

This bug seems doesn't reproduce anymore, now I using ESET Internet Security 15.1.12.0 and Sandboxie-Plus v1.1.3.

[isaak654]

This issue was reintroduced again in ESET Internet Security v16.0.22.0:
https://www.wilderssecurity.com/threads/eis-update-do-not-allow-ff-to-run-sandboxed.448495/

Sandboxie PLUS 1.5.0 and later
Firefox v106.0.1 and later
Windows 10 22H2 (OS Build 19045.2130)
EIS v16.0.22.0 / 16.0.24.0 / 16.0.26.0

Note: NOD32 template is still needed in Sandboxie.ini because it contains the following line:

Sandboxie/Sandboxie/install/Templates.ini

Line 2127 in 9272a07

OpenIpcPath=*\BaseNamedObjects*\NODCOMM*

Workaround 1: #1545 (comment) - #2472 (comment) (reproducible video)
Workaround 2: #2472 (comment)

History with ESET support

Oct. 31, 2022 - It was opened the ESET ticket 00445436 about the Firefox issue through this form

Nov. 22, 2022 - This is what I received from the ESET italian support right before closing my ticket:

Good morning

I have received feedback from ESET HQ but unfortunately there is no solution to the issue at the moment.
In the meantime however it has been reported as a bug and they are working on it but I cannot tell you when they will patch it.

Best regards

Nov. 23, 2022 - #2472 (comment)

Microbe has now contacted ESET, and an ESET developer has come back to Microbe, to say that ESET has classified this issue as a bug, which is expected to be resolved in future updates.

Jan. 16, 2023 - Still unfixed with ESET Internet Security 16.0.26.0, the workaround is still needed.

Apr. 4, 2023 - This issue was fixed with ESET Internet Security 16.1.14.0.

[gab12]

I confirm Disabling banking and payment protection fixes the problem on firefox and chrome (Workaround). Specifically "Secure all browsers" disabled suffices.

Thank you

[isaak654]

According to some feedbacks, this issue was fixed with the release of ESET 16.1.14.0.