View Single Post
Old 05-25-2017, 04:58 PM   #36
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,828
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by theducks View Post
Were you doing a generic install or a Custom install?

I have been doing every (generic) update since 2011 and never had that happem
How do you know?

It's only a problem if you have files that have an extension that calibre register's itself as a candidate handler. If those extensions do not have an existing default handler, Windows will make calibre the default handler. As a consequence when you hit Enter on a file with such an extension it will be added to the current calibre database.

File extensions are not 'unique', e.g. one of the ebook formats uses the same extension as one of Autocad's file types - that's how I discovered the issue.

People who drive Windows from their file manager more likely to be sensitive to the issue than those who drive Windows from program launchers such as desktop shortcuts, start menus, Launchy, RocketDock et cetera.

Kovid wouldn't have added the Environment variable and the calibre-debug option if it hadn't been a problem for some users.

BR
BetterRed is offline