WARNING-on PC Calibre takes over MANY file associations

[BetterRed]

Originally Posted by AnotherCat

I hope so BR as it would shorten your troubleshooting job if it is.

I cannot recall if XP had the same option in Default Programs or not (Windows 7 did, and that's as far back as I can recall ) but even if it did, so was not new to your user, it is an easy mistake to make.

Good grief, so it does - I don't think I've been there before. How do things get in the left hand column?

I always use Nor Sofer's File Types Manager or do it all from the shell menu.

BR

[AnotherCat]

Originally Posted by BetterRed

...How do things get in the left hand column?...

I cannot say authoritatively but it would be a pretty safe bet that the applications that register the files they can open, in the manner described by Kovid, end up there.

There is quite a fleet of them in my left hand column.

[sherman]

I have to admit that on a recent update of Calibre, my windows 8.1 installation (both my physical PC AND my VM), some file types are now associated with Calibre, including the likes of RAR archives. I don't recall setting Calibre as the default program, but I can't be certain that I did not do so.


Actually, now that I think about it, RAR files were never associated with any program, so maybe the default behaviour is to take over file associations if they are not already assigned to another program? On my system, EPUBs are still associated with ADE.

[JSWolf]

I have Calibre installed under Windows 8.1 Pro and it did not take over any file extensions.

[BetterRed]

Originally Posted by JSWolf

I have Calibre installed under Windows 8.1 Pro and it did not take over any file extensions.

Jon, did you do the install before calibre 2.20 hit the deck. That's when the changes relating to Default Programs were released. I think the Default Programs changes only apply to new installs not updates.

BR

[sherman]

Originally Posted by BetterRed

Jon, did you do the install before calibre 2.20 hit the deck. That's when the changes relating to Default Programs were released. I think the Default Programs changes only apply to new installs not updates.

BR

My issue was definitely after an update, although it only seemed to affect filetypes with no previous association.

[BetterRed]

Originally Posted by sherman

My issue was definitely after an update, although it only seemed to affect filetypes with no previous association.

Most programs (.MSI and .EXE installs), seem to leave things alone after the initial install. At one time VLC would register itself and claim everything in sight on installs and updates, but that seems to be fixed now.

BR

[sfuller]

calibre registers with default programs, telling it what filetypes it is capable of opening. It does not register itself as the default handler for any filetype.

That is the key. In Windows 8 and above in control panel->default programs->choosing a program and then selecting "set this program as the default" will associate Calibre with 40 file types, which is probably what happened. Choosing Calibre Viewer would associate 30 file types.

As much as I enjoy and use Calibre the "I don't care what you believe" seems harsh when obviously you understand what this feature (set default programs) does, or you wouldn't have chosen to add the entries to register the program.

I've attached screenshots showing what extensions Calibre and Calibre viewers can be set to. Choosing "Set this program as default" is the equivalent of checking every box by clicking one button.

It's normal to use this to restore associations that another program may have changed. While Calibre "can" open all these file types, it might be better to restrict the list to ""common" file types to avoid this issue.

[kovidgoyal]

Once again, calibre does not associate itself as the default handler for any filetypes. Only informing the operating system of what filetypes a program is capable of handling, without becoming the default handler, is simply good practice.

The fact that windows has a button that can be used to make a program the default handler for all filetypes it is capable of handling, and people misuse this button is a UI issue in windows. You should urge Microsoft to remove that button, or make it clear what it does. It is not a reason for programs to artificially limit the filetypes they report themselves as being capable of handling.

[splinetime]

I run Windows 10. I have used calibre quite a while, with no issues. This last time I updated, it did in fact take all file associations, and further will not release for me (by unchecking in windows default types).

The snarky answer did nothing to address something that in fact has happened. I did NO associate, options changing or fiddling. I followed the usual install dialog.

Regardless of whether you are the developer, the coder, etc... this behavior did occur. I had to uninstall to get my associations fixed. This may be a very rare combination of things. It did do the described behavior.

Thank You,
Kevin

[splinetime]

By the way, I did not use the windows associate button. You seem highly aggressive in your answer. I am not looking to argue I am saying this happened WITHOUT MY CHOOSING THIS BEHAVIOR. Thank You.

[BetterRed]

@splinetime - see following pages in the calibre User Manual

calibre - Environment variables - CALIBRE_NO_DEFAULT_PROGRAMS

calibre-debug command --default-programs option

BR

[theducks]

Originally Posted by splinetime

By the way, I did not use the windows associate button. You seem highly aggressive in your answer. I am not looking to argue I am saying this happened WITHOUT MY CHOOSING THIS BEHAVIOR. Thank You.

You are arguing.
Snarky?
The original post was in 2015. This is 2017.

'ALL' is a mighty big word.
Even a 'few' would be unusual.
It frequently happens to me, that some (like, Media players) software, takes over (becomes the default) every possible file type it could remotely deal with. Calibre does not. It adds to the 'Open With' list, just like many other programs. The only time it becomes 'Default', is when there was no other handler for that BOOK file type.
I've installed, many fresh Calibre installs on: XP, W7, W10, Ubuntu, Linux Mint and have not seen this 'take over'.
Do you remove other file associations, leaving a association hole, waiting to be filled?

[DoctorOhh]

Originally Posted by splinetime

I run Windows 10. I have used calibre quite a while, with no issues. This last time I updated, it did in fact take all file associations, and further will not release for me (by unchecking in windows default types).

Since the developer just restored the "Open with" functionality I won't automatically dismiss your claim. From the change log.

Release: 2.85.1 [12 May, 2017]

Bug Fixes

• version 2.85.1 contains a fix for a regression that cause the Open with action to go missing from the right click menu of the Book details panel

Now I don't believe this had anything to do with your situation, but the fix is in the ballpark.

This is why you shouldn't post to 2 year old threads. There was obviously not an issue with calibre 2 years ago. Posting to this thread makes your claim seem dead on arrival. Calibre 2.2 and 2.85.1 are 83 versions apart.

Moderator Notice
When at all possible please do not post in ancient threads. Calibre software is updated nearly every week. An old thread is rarely related to current issues. This though may well be completely related, but I don't have the insight to determine that answer.

Originally Posted by splinetime

The snarky answer did nothing to address something that in fact has happened. I did NO associate, options changing or fiddling. I followed the usual install dialog.

The original "snarky answer" was proved accurate since 3 million + users failed to show the affect from an update or install at the time. Back then the code was reviewed and it was not a fault with calibre.

Originally Posted by splinetime

Regardless of whether you are the developer, the coder, etc... this behavior did occur. I had to uninstall to get my associations fixed. This may be a very rare combination of things. It did do the described behavior.

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.

[BetterRed]

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