Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm
Solved

Profile mismatch: active profile directory empty, but history and extensions in inactive profile directory

dmercuremail đã trả lời
dmercuremail

I've been using the extension "Tree Style Tab" and "TST Colored Tabs." I've been looking for a way to disable the native Firefox tab bar, whether on top of the window or to the left side. I haven't been successful on my own.

After a couple of hours troubleshooting this with CoPilot, It suggested I post the following short summary:

============

Firefox 152.0.6 (64-bit) about:profiles shows active profile: C:\Users\dmerc\AppData\Roaming\Mozilla\Firefox\Profiles\usm8kxcr.default-release

Opening that directory from about:support shows an empty folder.

profiles.ini references: agwp164m.default-release

userChrome.css loads correctly in a separate profile but not in the profile containing my current extensions and history.

============

The details of how it came to this conclusion:

============

Based on everything you've found:

The profile with your current extensions and recent history is reported as: usm8kxcr.default-release

Opening that profile folder shows an empty directory. The only other real profile on disk is: agwp164m.default-release

We successfully proved userChrome.css loads in a different test profile (Profile 1) because the toolbar turned red. Therefore, the CSS mechanism itself works on your machine.

My conclusion is that your Firefox profile registration has become inconsistent. Firefox appears to be using a profile that does not correspond cleanly to the profile folders you're seeing in Explorer. At this point I would:

Back up the entire folder: (NOTE: DONE - backed to to another drive) C:\Users\dmerc\AppData\Roaming\Mozilla\Firefox

Keep using the profile that contains your extensions and recent history. Avoid deleting any profiles or profile folders.

Post the details you've collected to either: the Mozilla Support forum, or r/firefox

The key facts to provide are: Firefox 152.0.6 (64-bit)about:profiles shows active profile: C:\Users\dmerc\AppData\Roaming\Mozilla\Firefox\Profiles\usm8kxcr.default-release.

Opening that directory from about:support shows an empty folder.

profiles.ini references: agwp164m.default-release

userChrome.css loads correctly in a separate profile but not in the profile containing my current extensions and history. \ Those facts point to a profile-management issue rather than a Tree Style Tab or CSS issue.

The good news is that your current extensions and recent history are still accessible, so this doesn't look like data loss. The profile mapping itself needs to be untangled before custom CSS can reliably be applied.

=

It also suggested not copying any folders and files between profiles for now.

I've been using the extension "'''Tree Style Tab'''" and "'''TST Colored Tabs'''." I've been looking for a way to disable the native Firefox tab bar, whether on top of the window or to the left side. I haven't been successful on my own. After a couple of hours troubleshooting this with '''CoPilot''', It suggested I post the following short summary: ======================== Firefox 152.0.6 (64-bit) about:profiles shows active profile: C:\Users\dmerc\AppData\Roaming\Mozilla\Firefox\Profiles\'''usm8kxcr.default-release''' Opening that directory from about:support shows an empty folder. profiles.ini references: ''agwp164m.default-release'' '''userChrome.css''' loads correctly in a separate profile but not in the profile containing my current extensions and history. ======================== The details of how it came to this conclusion: ======================== Based on everything you've found: The profile with your''' current extensions and recent history''' is reported as: '''usm8kxcr.default-release''' Opening that profile folder shows an '''empty directory'''. The only other real profile on disk is: ''agwp164m.default-release'' We successfully proved userChrome.css loads in a different test profile (Profile 1) because the toolbar turned red. Therefore, the CSS mechanism itself works on your machine. My conclusion is that your Firefox profile registration has become inconsistent. Firefox appears to be using a profile that does not correspond cleanly to the profile folders you're seeing in Explorer. At this point I would: Back up the entire folder: ('''NOTE: DONE '''- backed to to another drive) C:\Users\dmerc\AppData\Roaming\Mozilla\Firefox Keep using the profile that contains your extensions and recent history. Avoid deleting any profiles or profile folders. Post the details you've collected to either: the Mozilla Support forum, or r/firefox The key facts to provide are: Firefox 152.0.6 (64-bit)about:profiles shows active profile: C:\Users\dmerc\AppData\Roaming\Mozilla\Firefox\Profiles\usm8kxcr.default-release. Opening that directory from about:support shows an empty folder. profiles.ini references: agwp164m.default-release userChrome.css loads correctly in a separate profile but not in the profile containing my current extensions and history. \ Those facts point to a profile-management issue rather than a Tree Style Tab or CSS issue. The good news is that your current extensions and recent history are still accessible, so this doesn't look like data loss. The profile mapping itself needs to be untangled before custom CSS can reliably be applied. ============= It also suggested not copying any folders and files between profiles for now.

Tất cả các câu trả lời (1)

Giải pháp được chọn

Solved!

It turns out I was using the Microsoft Store version of Firefox, not the downloadable installer from Mozilla. The MS Store version keeps its data in a different location than the Mozilla version. Once I fed that fact into CoPilot, we were able to fix the issues I was having.

Đặt một câu hỏi

Bạn phải đăng nhập vào tài khoản của bạn để trả lời bài viết. Vui lòng bắt đầu một câu hỏi mới, nếu bạn chưa có tài khoản.