Thanks. I read that posting before and didn't quite understand it. There must be a simpler explanation. I have deleted both Mozilla entries on my W7 machine and notice no adverse effects. Hope it stays that way.

I dislike, intensely, any program that leaves configuration or log files .. or other file remnants (as I would call them) all over the C: drive. In this case, thinking about it, I have to assume that W7 and not Firefox causes this to happen. Oh well...

A bit off topic .. and not a viable way to go. But, while we are here, I think XP Pro was/is all that most people need .. even though I (as an average Joe user) do like some of the stuff included with W7 Pro. But, let's leave it at that. It's really off topic!

I would think that to be an odd place?Also not really understanding the superuser post - except that this might come about if you run firefox with "Run As Administrator" (maybe? or maybe it's with a different, higher privilege level, then... something?), which I'm not sure why one would do that?

I would think that to be an odd place?Also not really understanding the superuser post

its a place for the SYSTEM user account. have a look into some rights and you will find it.ofc SYSTEM dont really has no really user path in c:\users\ but to work properly it need this.services are running under SYSTEM too.

Oh, I had no problem finding it.But I did need elevated rights to actually traverse through there.

On my end, the only things (& very limited at that) are "microsoft".Nothing Mozilla, nor any other third-party.

And in that respect, I'd find it odd for a "regular" user to have anything Mozilla (or really anything else, except perhaps, microsoft) in there. (For a regular user, nothing he uses should be touching \System32\config\ IMO.)

After removing a few empty (old) folders and everything Mozilla all I have left now are Microsoft and a folder named IsolatedStorage. I'll keep an eye on this location down the road to see if Mozilla returns. Maybe I had a BSOD one time and the system saved stuff in this odd location for backup reasons...

Why ESR related? The ESR version just has channel-pref.js set to "app.update.channel", "esr". That's it. As for Frontmotion MSI, in my case, never installed a Firefox.msi .. so that's not a factor. And how could it be related to an "upcoming" ESR release...