Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

After Registry Mechanic runs, I have to go back to View and enable the Toolbars

  • 6 svar
  • 1 har dette problem
  • 1 visning
  • Seneste svar af togo1919

more options

Is there a speedier way to do re-enable these Toolbars?

Is there a way to prevent Registry Mechanic from modifying the settings.

Otherwise, Firefox 17.0.1 has been working well.

This was an issue on my old laptop and now on my new laptop.

Thanks for any assistance!

Is there a speedier way to do re-enable these Toolbars? Is there a way to prevent Registry Mechanic from modifying the settings. Otherwise, Firefox 17.0.1 has been working well. This was an issue on my old laptop and now on my new laptop. Thanks for any assistance!

Valgt løsning

Okay. I got some feedback from RM.

It appears I cannot fine-tune which files do and do not get removed when RM runs with Privacy Cleaning enabled.

I can, however, get RM to leave the browser toolbars intact by using the settings shown in the attached capture.

Thanks for the help - my firefox is working well now!

Læs dette svar i sammenhæng 👍 2

Alle svar (6)

more options

That's strange. Toolbar configuration normally is stored in a file named localstore.rdf in your Firefox profile folder. Why would Registry Mechanic touch that??

The localstore.rdf file does sometimes become corrupted and cause behavioral problems all on its own. You can rename the file and customize from scratch.

Open your current Firefox settings (AKA Firefox profile) folder using

Help > Troubleshooting Information > "Show Folder" button

Switch back to Firefox and Exit

Pause while Firefox finishes its cleanup, then rename localstore.rdf to something like localstore.old

Restart Firefox. (If your home page appears, optionally restore your previous session using History > Restore Previous Session) Hopefully now your changes will be remembered.

more options

Hello,

I went through these steps, and after restarting, I had to go through the process of showing all the toolbars once more.

I shut down Firefox, and the toolbars remain visible.

Additional info: When Registry Mechanic has eliminated my toolbars from view, I am still able to open and close Firefox a number of times and have the toolbars be visible each time.

They will remain visible even after reboots - until Registry Mechanic runs again.

more options

Okay. More info.

I found that if I disable Privacy Cleaning in Registry Mechanic, the Toolbars on Firefox remain visible after Registry Mechanic runs.

I just found a log file for RM, for when Privacy Cleaning runs - here are the first few lines of what's removed for Firefox:

[Firefox Browser] C:\Users\ToGo\AppData\Roaming\Mozilla\Firefox\Profiles\89g494na.default\sessionstore.js

C:\Users\ToGo\AppData\Roaming\Mozilla\Firefox\Profiles\89g494na.default\formhistory.sqlite

C:\Users\ToGo\AppData\Roaming\Mozilla\Firefox\Profiles\89g494na.default\localstore.rdf

C:\Users\ToGo\AppData\Roaming\Mozilla\Firefox\Profiles\89g494na.default\downloads.sqlite

C:\Users\ToGo\AppData\Local\Mozilla\Firefox\Profiles\89g494na.default\Cache\_CACHE_001_

I will check on the RM side to see if there's a way to have RM NOT delete the localstore.rdf file each time Privacy Cleaning runs.

I'll provide feedback here if I get it from RM.

more options

In the short run, maybe create your own localstore-backup.rdf file for future restoration by making a copy of your current file.

more options

Note that it is usually best not to use such external cleanup software to cleanup files in the Firefox Profile Folder and do this via build-in Firefox means or extensions to avoid files from getting corrupted.

more options

Valgt løsning

Okay. I got some feedback from RM.

It appears I cannot fine-tune which files do and do not get removed when RM runs with Privacy Cleaning enabled.

I can, however, get RM to leave the browser toolbars intact by using the settings shown in the attached capture.

Thanks for the help - my firefox is working well now!