Born: Reported profile problems with the newly updated Firefox

Topic

New Reply

Günter Born reports that the new versions of Firefox, released yesterday — version 71 for most people and ESR (Extended Service Release) 68.3.0 for t
[See the full post at: Born: Reported profile problems with the newly updated Firefox]

3 users thanked author for this post.

jburk07, Morty, Fred

Reply | Quote

Replies

Updated Firefox yesterday and it was a bit glitchy at first but I checked this morning and they updated the glitchy JSON file early this morning so all is well. I hadn’t noticed it until I read about it this morning.

1 user thanked author for this post.

gborn

Reply | Quote

… so Mozilla updated your policies.json file this morning? After you installed the update last night?

Version 71 is just coming through for me this morning. I need to restart Firefox for it to take effect.

Reply | Quote

Does not the installer remove the policies.json file by default? Last time checked was FF 68 so not sure about later versions. Anyway, installing/updating via command line works as expected.

"Firefox Setup 71.0.exe" /DesktopShortcut=false /MaintenanceService=false /RemoveDistributionDir=false

1 user thanked author for this post.

Bill C.

Reply | Quote

The only thing I noticed this morning was a pop up that said Firefox is blocking social media trackers from a website I commonly visit.  It’s on version 71.  I have not seen any glitches at all.

1 user thanked author for this post.

Charlie

Reply | Quote

The Firefox for Enterprise support article Customizing Firefox Using policies.json states “Unlike controlling Firefox with using Group Policy, the policies.json is cross-platform compatible, making it preferred method for enterprise environments that have workstations running various operating systems.”

I updated to FF ESR v68.3.0 yesterday and haven’t noticed any issues.  I’m not sure, but I suspect the policies.json problem described in Gunter Born’s article Firefox 71/68.3esr: Profile issues and bugs during upgrade affects Firefox users in larger organizations where they must use a company-approved Firefox profile located in the \distribution folder within the Firefox installation directory.
———–
64-bit Win 10 Pro v1903 build 18362.418 * Firefox ESR v68.3.0

1 user thanked author for this post.

gborn

Reply | Quote

Currently I just receive reports from German FF users – have to wait, if it’s a global issue (some people updated several machines, and only one or two are affected).

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

1 user thanked author for this post.

woody

Reply | Quote

In briefly.

Although I can’t attribute this problem directly to Firefox, but suspect it may have been the source: junction points were either duplicates or missing.

This problem took some time to identify and resolve.

Carpe Diem {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1778 x64 i5-9400 RAM16GB HDD Firefox114.0b8 MicrosoftDefender

1 user thanked author for this post.

woody

Reply | Quote

I’m up-to-date with version 71, but in AppData it looks like this: C:\Users\bbearren\AppData\Roaming\Mozilla\Firefox\Profiles.  There is no \distribution\policies.json.

Then again, I haven’t customized Firefox, either.  It works fine for me straight up.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We were all once "Average Users". We all have our own reasons for doing the things that we do to our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

2 users thanked author for this post.

Charlie, WildBill

Reply | Quote

I have noticed an issue lately. I think it started with version 70.0.1. Even though I have resume previous session unchecked and have chosen a home page, I get a screen that says it cannot restore my previous session.

Reply | Quote

bbearren wrote:

I’m up-to-date with version 71, but in AppData it looks like this: C:\Users\bbearren\AppData\Roaming\Mozilla\Firefox\Profiles.  There is no \distribution\policies.json.

Then again, I haven’t customized Firefox, either.  It works fine for me straight up.

I just checked the B side of my dual-boot, and it’s the same.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We were all once "Average Users". We all have our own reasons for doing the things that we do to our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

1 user thanked author for this post.

WildBill

Reply | Quote

Just updated Firefox to Version 71.0 this morning; an individual user in America & not on a corporate network. No distribution\policies.json in my Mozilla Firefox folder.

As for C:\Users\<username>\AppData\Roaming\Mozilla\Firefox\Profiles\, not sure what I’m supposed to see as “xxxxxxxx.default”. Dated this morning, I see folder “1ejln7ix.default-release”. Dated late last night, I see folder “2rk07run.default-1502315497850-1561249085568”. No “policies.json” file in either folder…

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

Reply | Quote

I just updated to 70.0.1 a few days ago from 69.0.1 and had skipped a few updates in-between until I was sure most of the issues where fixed and now 71.0 arrives with issues. But even if it had no issues I’d still wait about a month or longer just to make sure.

Firefox shows 71.0 as being available for download/install when I check Help/About FF but at least the update nagging has not started to update to 71.0 just yet and maybe Mozilla needs a setting that can put off the update nagging for at least 30 days if that nagging can no longer be disabled.

Previously I had to put up with about 3 weeks worth of constant update nagging that could not be disabled and Mozilla needs some 30 day update deferral period on that update nagging for issues like this and others that may take a while to fix.

I’ll always check Ghacks and Askwoody/others anytime any new Firefox update shows up and I’ll always wait a few weeks and check again as well online to make sure no new issues are found with any new Firefox update before I’ll even consider installing the latest FF update. And it looks like version 71.0 has some serious issues and I’ll want to put off updating even longer to be safe.

 

1 user thanked author for this post.

Charlie

Reply | Quote

Same here.  I always wait awhile to update FF and never allow automatic updating.  I usually wait about a week, but sometimes longer especially when they go to a new whole number like 71.

Experience is that marvelous thing that enables you recognize a mistake as soon as you make it again.

Reply | Quote

Charlie, ‘automatic updates’ are never used here either, I always check daily for extensions only and have the FF updates completely switched off in our other devices.
This mozilla article helped me take control of the browser/extensions and how I want to use it, not mozilla 🙂
https://support.mozilla.org/en-US/kb/how-stop-firefox-making-automatic-connections

Keeping IT Lean, Clean and Mean!

2 users thanked author for this post.

Lars220, Charlie

Reply | Quote

WildBill wrote:

Just updated Firefox to Version 71.0 this morning; an individual user in America & not on a corporate network. No distribution\policies.json in my Mozilla Firefox folder.

I don’t think home consumers would normally expect to find this \distribution directory or policies.json file included with their FF installation. From the Firefox for Enterprise support article Customizing Firefox Using policies.json :

“To implement this policy support, a policies.json file needs to be created. This file goes into a directory called distribution within the Firefox installation directory. This directory is not usually included by default, so you may need to manually create this directory.”

———–
64-bit Win 10 Pro v1903 build 18362.418 * Firefox ESR v68.3.0

1 user thanked author for this post.

WildBill

Reply | Quote

[Microfix]

Updated to FF 68.3ESR on three Win8.1 devices and have encountered no issue.
However, I don’t use the integrated mozilla FF browser update, I download the entire setup file onto a USB stick from their FTP Site on release and run it seperately on each device after an initial test/check.
Awaiting the linux version update via repository.

Edit: My distro repo version of FF 68.3 ESR dropped and no issues encountered.

Keeping IT Lean, Clean and Mean!

• This reply was modified 3 years, 5 months ago by Microfix.
• This reply was modified 3 years, 5 months ago by Microfix.

1 user thanked author for this post.

KP

Reply | Quote

I just updated to version 71.0 and it totally trashed my user interface, all my custom tweaking is gone. I recovered with an image and all is back to normal. I won’t be updating again for a while. Kinda wonder if the folks at Mozilla aren’t taking update lessons from Microsoft. This isn’t the first time a Firefox update has trashed the browser. If anyone from Mozilla is reading this, how bout being a little more careful with those updates. Also, it seems like there is a Firefox update every other week lately. As the saying goes, if it ain’t broke, don’t fix it.

3 users thanked author for this post.

Charlie, Carl D, WildBill

Reply | Quote

Thanks for the heads up on this.

I’ve just checked for updates in Firefox and I’m getting the “offer” to update to 71.0. I think I’ll leave it for a while.

“As the saying goes, if it ain’t broke, don’t fix it.”

Mozilla are planning to move to a 4 week release cycle for Firefox by March next year, looks like they’re trying to outdo Chrome with their current 6 week cycle.

If they weren’t constantly adding mostly useless features that most people probably don’t need or want and wouldn’t use then I imagine quite a few staff wouldn’t have a job.

As seems to be the case with a lot of software companies (I’m looking at you, MS) these days.

PC1: Gigabyte B560M D2V Motherboard, Intel i5 11400 CPU, 16GB RAM, NVIDIA GeForce GTX 1650 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Professional 22H2 64bit.
PC2: Asus H81M-PLUS Motherboard, Intel i3-4160 CPU, 16GB RAM, NVIDIA GeForce GTX 1050 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Home 22H2 64bit.

Reply | Quote

that is even faster than MS releasing 2 feature updates a year for Win10, Carl D.

after Firefox 71, I’ll skip the 72 release and wait for Firefox 73 to come out as I will skip every other version

Reply | Quote

I googled “Firefox 71” and clicked on the first link – the Mozilla Firefox website to read up about what’s changed on ver. 71. Lots of changes.  The only problem they warn about is FF 71 having a problem with Comodo Antivirus.

Experience is that marvelous thing that enables you recognize a mistake as soon as you make it again.

Reply | Quote

Did some more reading about FF 71 – they’ve added a “Picture In Picture” feature, “native MP3 support”, and other things that I don’t need and will probably use up a lot more memory. Details on Ghacks – https://www.ghacks.net/2019/12/03/firefox-71-0-release-information-last-firefox-release-of-2019/

I really wish they would only do what is necessary to keep the browser secure.  My FF 70.0.1 works just fine.  From the looks of this topic, there’s still a 40% chance the 71 update will cause some kind of problem.  Maybe they are trying to imitate MS.

Experience is that marvelous thing that enables you recognize a mistake as soon as you make it again.

Reply | Quote

[Charlie]

Here’s more bad news!  Am I the only one interested in this?  Check this out:

https://borncity.com/win/2019/12/04/firefox-71-68-3esr-profile-issues-and-bugs-during-upgrade/

Guess I’m staying with FF 70.0.1 until something gets fixed.  Be sure to read the comments on this site.  They’re not good.

Experience is that marvelous thing that enables you recognize a mistake as soon as you make it again.

• This reply was modified 3 years, 5 months ago by Charlie.

Reply | Quote

@Charlie, that’s exactly the same link that Woody posted in this topic front blog page.

Keeping IT Lean, Clean and Mean!

Reply | Quote

Yeah, I didn’t realize that until after I submitted it and then saw what came up.  Sorry, but it’s still very important and people need to be warned.  I’ll watch and wait for more info. on this.  Thanks for the reply.

Experience is that marvelous thing that enables you recognize a mistake as soon as you make it again.

Reply | Quote

The profile bug only occurs if you or your IT dept. created a policies.json file.

https://support.mozilla.org/en-US/kb/customizing-firefox-using-policiesjson

This article is for IT Admins who want to configure Firefox on their organization’s computers.

To implement this policy support, a policies.json file needs to be created. This file goes into a directory called distribution within the Firefox installation directory. This directory is not usually included by default, so you may need to manually create this directory.

Win 10 home - 22H2
Attitude is a choice...Choose wisely

1 user thanked author for this post.

Charlie

Reply | Quote

I have Firefox update automatically.  I’ve had no problems, no issues.  It just works.  I don’t even know what version I’m on without checking Options, which I did when I read the blog post this morning.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We were all once "Average Users". We all have our own reasons for doing the things that we do to our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

2 users thanked author for this post.

Charlie, rontpxz81

Reply | Quote

Pretty much the same here.

I upgraded to 71.0 last night and it was fine, if anything it seems a little faster loading up my homepage

2 users thanked author for this post.

Charlie, rontpxz81

Reply | Quote

As lmacri said: no policies.json file anywhere on the computer, and no directory called C:\Program Files\Mozilla Firefox\distribution\ .

Firefox 72.0b2 (64 bits).

1 user thanked author for this post.

WildBill

Reply | Quote

I’m going to wait for 71.1 or 71.0.1 to be released. That has been my policy for all Firefox major version releases. There is usually a patch issue shortly after…

Windows 10 Pro 22H2

Reply | Quote

[EP]

there won’t be a 71.1 version JohnW.
a 71.0.1 version maybe – if Mozilla finds other new bugs that need to be fixed; might get a mid-December release if they do find new problems

• This reply was modified 3 years, 5 months ago by EP.

Reply | Quote

Thanks, but that’s why I included 71.0.1.

Cheers! 🙂

Windows 10 Pro 22H2

Reply | Quote

You may want to review this list of Firefox releases. Although it has not been common to release a “xx.1.x”version, that is not unprecedented.

https://www.mozilla.org/en-US/firefox/releases/

For example: Firefox 24.1.0, 31.1.0, 38.1.0, 52.1.0, 60.1.0, and most recently 68.1.0.

Although those are ESR releases, never say never! 🙂

Windows 10 Pro 22H2

Reply | Quote

forget about a 71.0.1 release JohnW. it’s not gonna happen anytime soon as Mozilla is now close to releasing a 72.0 version on the first week of January 2020.

release date of FF 72 is scheduled on 1st Tuesday of Jan. 2020 as noted here:
https://wiki.mozilla.org/Release_Management/Calendar

1 user thanked author for this post.

Steve

Reply | Quote

Since at least two weeks ago, a ver 71 FF several times at invocation threw a message
about the profile, to the effect that the specified or expected profile could not be found.

Reply | Quote

With Firefox, I am NOT a “seeker”. I find if there is an issue, the address it fast and that waiting a few days is prudent.

Agoldhammer’s comment on Post #2014603 about the social media trackers is great news. I currently use the extension called Facebook Container for that and it really helps. If the native FF application includes the functionality of containerizing the Facebook tab, that will be good, although the Facebook Container extension also works for online purchasing and other secure activities.

My Thunderbird and Firefox profile backup is a weekly thing and makes syncing my Linux and Windows version so they appear and work identically without having a formal online Firefox syncing account.

Reply | Quote

Have received notice of at least one user not being able to start Firefox at all after the autoupdate, listed as version 71… localized version, one of the smaller European languages. Not a business user, no policies.json or the like.

Not letting that update through for those with centralized management.

One case of update to 68.3 on the ESR side so far, no problems with that one except for sample size…

Reply | Quote

mn– wrote:

Have received notice of at least one user not being able to start Firefox at all after the autoupdate, listed as version 71… localized version, one of the smaller European languages. Not a business user, no policies.json or the like.

Well, cannot blame Firefox for this one, turned out to be a hardware fault. Was a spinning HDD that developed bad blocks at the same time.

Replacing with a SSD.

1 user thanked author for this post.

Charlie

Reply | Quote

Has Mozilla officially acknowledged this profile bug anywhere? Someone please post here when a fixed release is offered. Can’t afford to have my settings scrambled! FF keeps nagging at me; pity they removed the “never update” option. 🙁

1 user thanked author for this post.

Charlie

Reply | Quote

Had BSOD for the first time on this computer the day after Mozilla updated. Was the only new thing put on this computer in nearly a month. Rechecked for virus, malware, etc – all clean. Guessing the update sent something sideways – hopefully just temporarily as I seem to be good now. Don’t know if anyone else had the same issue…

(Windows 7 pro)

1 user thanked author for this post.

Charlie

Reply | Quote

Hi,

I just updated Firefox 71 on Window 7 Pro. Would not open. Uninstalled. Installed the previous version no problem. Windows user account control launches via Firefox updater. Once you agree, Firefox no longer works.

I’m currently running Firefox 71 on Ubuntu 19.10, Manjaro Gnome, Manjaro Cinnamon. No problems as of yet.

I’ve basically retired Windows 7 except for it being on a spare SSD and its on my laptop. Not sure what Mozilla did to create the Win7 issue but I try again next week to see if they got it fixed.

Reply | Quote

Maybe this from Mozilla?

Some Windows users who had previously installed and uninstalled Comodo antivirus software may not be able to start Firefox. Information on how to resolve this issue is described on support.mozilla.org or in the support knowledgebase.

Win 10 home - 22H2
Attitude is a choice...Choose wisely

1 user thanked author for this post.

lmacri

Reply | Quote

mledman wrote:

Maybe this from Mozilla? Some Windows users who had previously installed and uninstalled Comodo antivirus software may not be able to start Firefox. Information on how to resolve this issue is described on support.mozilla.org or in the support knowledgebase.

Please note that mledman’s quote is taken directly from the (revised???) FF 71 release notes at https://www.mozilla.org/en-US/firefox/71.0/releasenotes/. According to the Techdows article Fix Firefox 71 Does Not Start After Update and Firefox Forum Moderator philipp’s post at https://support.mozilla.org/en-US/questions/1274248#answer-1270830 the FF 71 startup failure can be caused by a Comodo file named IseGuard64.dll, IseGuard32.dll (or something similar) that is typically located in C:\Windows\system32\. This problem .DLL file may be present with currently running or previously uninstalled Comodo products.
———–
64-bit Win 10 Pro v1903 build 18362.476 * Firefox ESR v68.3.0

1 user thanked author for this post.

mledman

Reply | Quote

Mozilla has been issuing almost daily Firefox beta updates within the last several weeks.

What’s going on?

Carpe Diem {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1778 x64 i5-9400 RAM16GB HDD Firefox114.0b8 MicrosoftDefender

Reply | Quote

Your daily updates of FF’s nightly (as they call the channel) builds is probably part of their increased release cadence plan.

For those not familiar with it, Mozilla plans, as has been stated by @Carl-D above in post 2014753, to go to a 4 week release pace for their versions of Firefox.

January’s release will be 5 weeks after December’s, and February’s will be 5 weeks after January’s but March’s will only be 4 weeks after February’s. The 4 week pace will then be maintained until Mozilla decides differently.

 

Reply | Quote

[EP]

and Mozilla’s fast pace of releasing new Firefox versions starting in 2020 is much faster than Microsoft’s “two feature updates a year for Win10” policy – about TEN to TWELVE “feature updates” a year for Mozilla Firefox

• This reply was modified 3 years, 5 months ago by EP.
• This reply was modified 3 years, 5 months ago by EP.

1 user thanked author for this post.

WildBill

Reply | Quote

I still haven’t encountered any problems since Firefox updated me to 71.0. Again, an individual consumer & not a corporate user. With updates scheduled to hit Hot & Heavy in 2020, I’ve changed to “Check for updates but let you choose to install them”. Automatic updates for Firefox haven’t bit me yet… but better to be safe than sorry.

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

Reply | Quote

[Cybertooth]

“Keep fixing it till it breaks.” Already, two of the three browsers on my Kubuntu Linux system (Brave, Chromium) will open for just a couple of minutes and then close themselves without warning. Been happening for a couple of weeks. If Mozilla’s frenetic pace of changes breaks Firefox before Chromium fixes whatever they did, then I will literally have no way to get on the Internet on that computer.

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

• This reply was modified 3 years, 5 months ago by Cybertooth.

Reply | Quote