X
Tryk her for at gå til webstedets mobilversion.

Supportforum

New clear profile every time after Firefox update

Skrevet

Hello.

In organization we like to use Firefox as default browser. But we have a every day problem with profiles.

After update, Firefox create new profile and not copy user data to it. So user lost hes tabs, extensions, history and e.t.c. We can see two or more profiles for one user.

For example user logon to computer with Firefox version 68.0.1. Firefox automatically update to 68.0.2, and user now have new profile without custom data.

profiles.ini looks like:

[Install308046B0AF4A39CB] Default=Profiles/6qa5a710.default-release Locked=1

[Profile1] Name=default-release IsRelative=1 Path=Profiles/6qa5a710.default-release

[Profile0] Name=default IsRelative=1 Path=Profiles/xu3ic03g.default-1561039332923 Default=1

[General] StartWithLastProfile=1 Version=2

We create powershell script for workaround issue. Script copy files from privies profile: $profileCurrent\*.sqlite" $profileCurrent\sessionstore.jsonlz4" $profileCurrent\extensions\*.*" $profileCurrent\*.json"

You mast know that in organization we user roaming profile and ue-v, so users can logon on any computer. Some computers can be with older Firefox version like 68.0.1 or new one like 68.0.2.

Please help find solution for this issues. Can Firefox account help with this? Or we mast create some more clever script?

Thank you.

Hello. In organization we like to use Firefox as default browser. But we have a every day problem with profiles. After update, Firefox create new profile and not copy user data to it. So user lost hes tabs, extensions, history and e.t.c. We can see two or more profiles for one user. For example user logon to computer with Firefox version 68.0.1. Firefox automatically update to 68.0.2, and user now have new profile without custom data. profiles.ini looks like: [Install308046B0AF4A39CB] Default=Profiles/6qa5a710.default-release Locked=1 [Profile1] Name=default-release IsRelative=1 Path=Profiles/6qa5a710.default-release [Profile0] Name=default IsRelative=1 Path=Profiles/xu3ic03g.default-1561039332923 Default=1 [General] StartWithLastProfile=1 Version=2 We create powershell script for workaround issue. Script copy files from privies profile: $profileCurrent\*.sqlite" $profileCurrent\sessionstore.jsonlz4" $profileCurrent\extensions\*.*" $profileCurrent\*.json" You mast know that in organization we user roaming profile and ue-v, so users can logon on any computer. Some computers can be with older Firefox version like 68.0.1 or new one like 68.0.2. Please help find solution for this issues. Can Firefox account help with this? Or we mast create some more clever script? Thank you.

Valgt løsning

Do`s it help me? -allow-downgrade

Firefox 67's Downgrade Protection prevents accidentally starting Firefox in a profile running a later version of Firefox. Depending on changes between the two versions, some files in a profile may not be downwards compatible. Adding this option bypasses Downgrade Protection.

Læs dette svar i sammenhæng 0
Citér

Yderligere systemdetaljer

Program

  • User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36

Yderligere information

Luk
FredMcD
  • Top 10 Contributor
4220 løsninger 58899 svar

The new upgrade should use the existing profile. Not create a new one unless something goes wrong.

Are you saying the original profile is not there, or not accessed?


Not there) Look on your desktop. Do you see a folder called; Old Firefox? Look inside. Look for the folder with the latest creation date.

https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile

https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles

https://support.mozilla.org/en-US/kb/how-run-firefox-when-profile-missing-inaccessible


Not accessed) You may have a corrupt profiles.ini file. Close Firefox. Open your file browser to this hidden location:

  • Mac: *~/Library/Application Support/Firefox/
  • Linux: *~/.mozilla/firefox/
  • Windows: %AppData%\Mozilla\Firefox\
  • *C:\Users\<user>\AppData\Roaming\Mozilla\Firefox\

Locate the profiles.ini file. Then rename or delete it.

Firefox should create a new profile.

The new upgrade should use the existing profile. Not create a new one unless something goes wrong. Are you saying the original profile is not there, or not accessed? '''Not there)''' Look on your desktop. Do you see a folder called; '''Old Firefox?''' Look inside. Look for the folder with the latest creation date. https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles https://support.mozilla.org/en-US/kb/how-run-firefox-when-profile-missing-inaccessible ---------------- '''Not accessed)''' You may have a corrupt '''profiles.ini''' file. '''Close Firefox.''' Open your file browser to this hidden location: * Mac: *~/Library/Application Support/Firefox/ * Linux: *~/.mozilla/firefox/ * Windows: %AppData%\Mozilla\Firefox\ * *C:\Users\<user>\AppData\Roaming\Mozilla\Firefox\ Locate the '''profiles.ini''' file. Then rename or delete it. Firefox should create a new profile.
Fandt du dette nyttigt?
Citér
cor-el
  • Top 10 Contributor
  • Moderator
17407 løsninger 157253 svar

Safest would be to only use a profile with the preferred .default-release file extension because in some cases Firefox prefers such a profile. A profile with a time stamp appended (I see: 1561039332923) is created as the result of a refresh.

Installs.ini stores data that is used to lock a profile against a specific installation folder.

Safest would be to only use a profile with the preferred .default-release file extension because in some cases Firefox prefers such a profile. A profile with a time stamp appended (I see: 1561039332923) is created as the result of a refresh. *https://support.mozilla.org/en-US/kb/dedicated-profiles-firefox-installation Installs.ini stores data that is used to lock a profile against a specific installation folder.
Fandt du dette nyttigt?
Citér

Spørgsmålsstiller

It seems that the problem occurs if a user with a new profile starts Firefox with an older version.

So user select create new profile.

Who force update before start up Firefox?

It seems that the problem occurs if a user with a new profile starts Firefox with an older version. So user select create new profile. Who force update before start up Firefox?
Fandt du dette nyttigt?
Citér

Valgt løsning

Do`s it help me? -allow-downgrade

Firefox 67's Downgrade Protection prevents accidentally starting Firefox in a profile running a later version of Firefox. Depending on changes between the two versions, some files in a profile may not be downwards compatible. Adding this option bypasses Downgrade Protection.

Do`s it help me? -allow-downgrade Firefox 67's Downgrade Protection prevents accidentally starting Firefox in a profile running a later version of Firefox. Depending on changes between the two versions, some files in a profile may not be downwards compatible. Adding this option bypasses Downgrade Protection.
Fandt du dette nyttigt?
Citér

Spørgsmålsstiller

Hmmm, -allow-downgrade works perfect! :)

Also I want to reconfigure UE-V template and sync only this files:

$profileCurrent\*.sqlite" $profileCurrent\*.jsonlz4 $profileCurrent\extensions\*.* $profileCurrent\*.json"

That's all, nothing else. What do you think about this?

Hmmm, -allow-downgrade works perfect! :) Also I want to reconfigure UE-V template and sync only this files: $profileCurrent\*.sqlite" $profileCurrent\*.jsonlz4 $profileCurrent\extensions\*.* $profileCurrent\*.json" That's all, nothing else. What do you think about this?
Fandt du dette nyttigt?
Citér
Stil et spørgsmål

Du skal logge ind på din konto for at svare på et indlæg. Start et nyt spørgsmål, hvis du ikke har en konto endnu.