Downloaded files don't go to the folder that I send them to.
I am now noticing that no matter where I tell Firefox to save a file, it always defaults to save that file in whatever folder is defined in the Options-.General->Files and Applications->Save To definition. Even when I chose the "Always ask ..." option, and click on a folder in the path that I want the file to go to, it still saves it in the "Save To" default folder. I just noticed this chang on yesterday (1/11/2018).
I save different types of files with different subject matter into their own specific folders. I never had any issues pointing them to the folder(s) that I wanted them to be saved in.
I don't have this problem when using Internet Explorer, the file gets saved in the folder that I point it to. But I don't like using IE. I like using Firefox. Is there something that I'm missing? Please let me know how I can get the ability to save a file where I want it to go, back.
Thank You,
Chuck
Изабрано решење
Thank you for your help Cor-el. But after reading your plan of action, I decided to try bringing up Firefox in Safe Mode first, and low and behold, the problem cleared. So, I restarted FF, and began disabling my add-ons one by one. It turns out that the culprit was the add-on for Ninja Download Manager.
Seems like when I first updated FF to 57.0.4, that add-on was not compatible, and remained inactive. But once the developer made the modifications to make it compatible, that add-on enabled itself, and the problem appeared.
So thanks again to all of you that offered assistance. This ticket can be closed.
Прочитајте овај одговор са објашњењем 👍 0Сви одговори (6)
What version of FF are you using?
Firefox 57.0.4 OS Win 7, 64 bit
Please uninstall Firefox. Then Delete the Mozilla Firefox Folders in C:\Program Files and C:\Program Files(x86) Then restart system. Then run Windows Disk Cleanup. (Note: This should be Pinned and run Weekly, If never done below expect 10's of gig's) Then run it again and click the button that says Cleanup System Files. Note: your Firefox Profile is saved. But you should make a back up before you do :
- https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles
- https://support.mozilla.org/en-US/kb/export-firefox-bookmarks-to-backup-or-transfer
Reinstall with Current Release Firefox 57.0.4 with a Full Version Installer
Please let us know if this solved your issue or if need further assistance.
Thank you for your response Pkshadow, I followed your instruction, and then reinstalled FF, but the problem still exists.
Boot the computer in Windows Safe mode with network support to see if that has effect in case security software is causing problems.
- http://www.bleepingcomputer.com/tutorials/how-to-start-windows-in-safe-mode/
- http://www.7tutorials.com/4-ways-boot-safe-mode-windows-10
Try to rename/remove content-prefs.sqlite in the Firefox profile folder with Firefox closed.
You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.
- Help -> Troubleshooting Information -> Profile Directory:
Windows: Show Folder; Linux: Open Directory; Mac: Show in Finder - http://kb.mozillazine.org/Profile_folder_-_Firefox
You can create a new profile to test if your current profile is causing the problem.
See "Creating a profile":
- https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
- http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.
Одабрано решење
Thank you for your help Cor-el. But after reading your plan of action, I decided to try bringing up Firefox in Safe Mode first, and low and behold, the problem cleared. So, I restarted FF, and began disabling my add-ons one by one. It turns out that the culprit was the add-on for Ninja Download Manager.
Seems like when I first updated FF to 57.0.4, that add-on was not compatible, and remained inactive. But once the developer made the modifications to make it compatible, that add-on enabled itself, and the problem appeared.
So thanks again to all of you that offered assistance. This ticket can be closed.