Hi,

Sorry for that, and thank you for reaching out! That's the issue we are currently investigating. Could you please clarify the following:

1. Have you recently manually moved the profile you're using to a new device using folder copying?
2. Do you have errors in the Browser Console (Ctrl+Shift+J or open from the menu) about SQLite not being able to connect to the ProfilesDatastoreService?
3. If the answers to the both questions above are positive, you might be able to resolve the issue by visiting about:config, finding the toolkit.profiles.storeID preference, clearing it and then restarting the browser. Does that work for you?

Looking forward to your update!

And is you Firefox version 147.0.3?

Hi @Denys,

Thanks for reply!

Yes the version is 147.0.3. And yes the bug linked seems to be my issue too.

I started with a profile manually created in a non-default path, which was created probably a year ago.

There is a big bunch of errors from the console, but after a quick search I don't see anything mentioning `ProfilesDatastoreService`. Let me know if you would like to see a copy of printouts.

And I've done the fix anyways, which did nothing.

Hm, could you please try another thing:

1. Go to about:support and click Open Folder next to Profile Folder.
2. Go one directory above the Profiles directory, to the Firefox folder.
3. Check if there's a folder named Profile Groups (exactly like that). If not, create it.
4. Restart the browser. Does the issue persist?

I don't have the profile at a default location, and its path looks like this (when clicked Open Folder): `D:\Users\ccl013\BrowersFiles\FireFoxProfiles\Main\Root` So, there's no "Firefox" folder; and no "Profile Groups" folder can be found. If I want to create it, should I put it into which level of my path?

In Windows it should be in %AppData%\Mozilla\Firefox\ by default.

Hi TyDraniu, I do have `Profile Groups`under `%AppData%\Mozilla\Firefox\`. There's a bunch of files in it too. Should I try clear it?

No, I don't think so.

FYI I've upgraded to 147.0.4, and the same issue still persists.

So bug 2014616 didn't fix it for you. Please create a new bug on bugzilla.

Created one here: https://bugzilla.mozilla.org/show_bug.cgi?id=2017751