[Mozilla Enterprise] ESR68.2.0 on one Win10 laptop and user won't launch

[Timo Pietilä]

I would reinstall ESET first. I just fixed a computer that had antivirus 
blocking spooler service from starting just by reinstalling that said 
antivirus program. Those things go haywire sometimes and start blocking 
things they are not supposed to block.

Timo Pietilä

On 30.10.2019 15.27, James M. Pulver wrote:
> I have a somewhat odd issue with a Lenovo X1 Carbon 6th gen running
> Windows 10 1809 LTSC and just deployed 68.2.0ESR over 60.8.0ESR. This
> laptop is a "kiosk" for us, which means it autologins to a useraccount,
> vaclab. This is a domain account. This laptop was just out for repair
> and had the m.2SSD and motherboard replaced. We just re-imaged it with
> our image just prior to the 68.2.0 deployment, so it hadn't been used or
> had Firefox launched before the upgrade.
> 
> As the vaclab account, Firefox won't run. It will launch 2 firefox.exe
> processes for about 30 seconds and they will either then trigger Mozilla
> crash reporter, or just exit silently.
> 
> As admin users on the laptop, we can launch Firefox just fine. Because
> of the specific "kiosk" configuration, we are not allowed by GPO to log
> in as other regular users. However, on other Win10 instances that are
> Kiosks or regular users we do not see the issue. Just on this one X1,
> and with this one user.
> 
> The Crash Details for the user show a crash in an ESET plugin - we use
> ESET Endpoint Security v7.1.something - however, it's a system level
> config, and doesn't crash for the admin users - we tried 2 different
> user accounts. We also tried "pausing" ESET live protection, no change.
> We looked at ESET live logs and ESET showed nothing.
> 
> To debug, we tried deleting C:\Users\vaclab\appdata\xxxx\.mozilla
> (local, local low, and roaming). No change. I tried using Windows
> profile manager as and admin to remove the vaclab profile and re-create.
> No change. I tried as vaclab running firefox -profilemanager - weird XUL
> crash. Tested running same command as the admin users, worked fine,
> though showed 2 profiles?
> 
> I'm at either re-imaging the laptop AGAIN, or throwing it out for a
> different X1 carbon - but does anyone have ANY ideas about this failing
> just for the particular user?
>