Quote:
Originally Posted by DoctorOhh
I can't judge the merits of your claim. I can only say it did not happen to me. For anyone reviewing this thread in the future, if you find yourself in this situation, simply reset your associations back to their defaults. |
Well 'it' did happen to me 2 years ago. Because the Windows Open With/Default handler 'feature' has long been a Pandora's Box some Windows users, such a me, have always kept file associations under a very tight reign. Many of the file types for which calibre registered itself as a handler, had no existing default - so Windows in its infinite wisdom made calibre.exe the Default handler.
theducks refers to some media players taking over everything in sight, that was certainly true a few years ago (VLC, MPC, Real Player and Quicktime come to mind). But more recent versions of some of those programs now offer a selectable list (that includes None) at install time - albeit usually in custom/advanced install.
Maybe
splinetime is of the same school as me, less is better, least is best. I was a bit surprised when Kovid introduced this feature, it seemed to go against the grain of calibre keeping its fingers out of the Windows Registry, as does the more recent feature of using a common AppId for the different variants of calibre.exe. My understanding is that they are MS 'best practice' guidelines, in my 30+ years of working with MS and their products I've found some of their past 'best practices' were absolute BS.
In part at least, I believe it was as a result of my interaction with Kovid over the matter (I can't recall where, could have been at launchpad), that he introduced the Environment variable, which prevents calibre registering any file associations; and the calibre-debug option which can undo any existing calibre file associations. I have provided links to relevant manual pages in post #27. Because they are calibre specific those two features are far simpler to use than the Windows 10 specific procedure you reference.
BR