This post was most recently updated on December 13th, 2019.Reading Time: 2 minutes.
If you’re like me, you’re not using Adobe Reader, but rather switched to Foxit Reader years ago, and never looked back. Foxit has a great PDF printer, it’s sleek and for the most part a pleasure to use – in other words, it’s a great reader. But it’s not perfect. See, the default save location is “Foxit Drive”, and it pops up any time you try to save your document, and at least for me interrupts my workflow.
This post describes how to get rid of it, and make Foxit Reader even better!
Description of the issue
Okay, so Foxit Reader is pretty great, but they’ve got their difficulties, too. Being freeware, they kind of need to get revenue from somewhere outside the reader itself – and nowadays, that would be their Premium software, but especially their Online offering, part of which the cloud storage for PDFs is. However, a cloud storage for PDF-files is, at least for me, very much unnecessary, as I save everything in Dropbox or OneDrive anyway, so that being the default location was quite annoying.
Foxit Reader doesn’t have an option to disable Foxit Drive, though. They have a setting to disable all online features – but weirdly enough, this does not include their cloud storage option!
I guess there’s a reason for that, though – technically, their storage is not an online feature, but rather a plugin. And disabling features from the core software doesn’t affect plugins, naturally :)
So, what can you do instead?
Solution: How to disable Foxit Drive?
Being a plugin, it’s actually easy to disable. First, you’ll need to browse to your Foxit Reader installation folder – depending on your system, that’d typically be either “C:\Program Files (x86)\Foxit Software\Foxit Reader” or “C:\Program Files\Foxit Software\Foxit Reader“. Your path could be different, though.
Then open “plugins” folder, and rename “FoxitDrive.fpi” to “FoxitDrive.fpi.bak”.
And like so!
Then, just restart your Foxit Reader and it’s gone!
And so the workflow just improved a bit! :)
- How to fix “System.IO.FileSystem: Could not find a part of the path \AppData\Local\AzureFunctionsTools\Releases\3.17.0\workers. Value cannot be null. (Parameter ‘provider’)” when running Azure Functions locally? - January 12, 2021
- How to nuke the Identity Cache in Visual Studio? - January 11, 2021
- Fixing unexpected Microsoft.AspNetCore package errors after a dependency update - January 6, 2021