Windows 10 Photo app hijacks camera import

[perkcan]

Windows 10 Photo application hijacks the import of images from my Canon PowerShot.  Does anyone have information about how to successfully set CameraWindow as the default application loaded when a Canon camera is connected via USB?

(For the record, I'm not interested in commentary on the Photo App or how to use it.  I have explored the settings enough and played with it enough to already know it is an cheap, inferior program.  I simply want to configure CameraWindow how it worked on Window 7, how it was designed to work.)

Prior to Windows 10 upgrade, I had Windows 7 with CameraWindow 8 installed.  When I plugged my PowerShot SX510 into the USB (or any of my canon cameras), CameraWindow would start automatically.

Not only did CameraWindow start automatically on Windows 7 (and prior versions), but it was easy to configure the default applications for Auto Start on Windows 7.  Windows actually allowed changing the settings and honored the settings I chose.

But on Windows 10, it ALWAYS starts the Photo application.  I have changed Auto Play settings, default application settings, device settings (Control Panel - Device and Printers) for the camera, but NOTHING works to stop the new Photo App from starting.  In the Device settings, the "Download Images..." option lets me choose CameraWindow, but on the General Settings page, another option says "Import  photos and videos (Photo)" but is greyed out, so it can't be changed.  Microsoft essentially forces the use of their own software and ignores the other settings.

It is very annoying on many levels.  Perhaps the worst is that Windows 10 removed all ability for the user to configure options in this regard!   Second, the Photo app has very limited settings:  There is no control over the import process, like the folder structure, image rotation options, etc.  Finally, CameraWindow itself has no option to make itself the default.

[perkcan]

My last post was in reply to Waddizzle.  I'm surprised that Bob's message has already received 4 Kudos.  Apparently nobody got the sarcasm, or they agree with Waddizzle.  I thought that one of the primary reasons for community forums was to provide and find mutual support.  I was surprised at Waddizzle's insistance that nobody should edit the registry and that most problems are caused by people having misconfigured software, or non-Intel CPUs.   Most decent software will of course work well for the majority of people, so forums like this are also primarily for the non-majority who experience bugs.  So if someone says something does not work, it does not have to imply that it doesn't work for anyone, or that it doesn't work for the majority.  Waddizzle's attitude and explanations are contrary to a useful, informative forum.  Posting solutions exactly like what skippy12 posted is what I expect and appreciate, so it is a rather strange culture in this forum when that is not what is wanted or appreciated.  Being an expert doesn't mean that I am a know-it-all, or I that I already am aware of all possible solutions.  On the contrary Bob.  I appreciate the pointer to other issues or possible solutions, but my sarcasm was to avoid hidding details, not keeping people from it.  Rather, as an expert, I appreciate an open forum where we can communicate without the nay-sayer.

[Waddizzle]

" I was surprised at Waddizzle's insistance that nobody should edit the registry and that most problems are caused by people having misconfigured software, or non-Intel CPUs." 

I never insisted that nobody should edit the registry.  I strongly discouraged doing so.  In fact, as a general rule, I strongly discourage anyone from attempting highly technical repairs to things they are not familiar with. 

Likewise, I strongly discourage people from offering such advice, and encouraging amateurs to attempt such highly technical repairs.  What may seem easy and trivial to you, is Greek rocket science to someone lacking experience.  To assume that anyone can successfuly complete such repairs is the height of folly.

-----------------------------------------------

"Waddizzle's attitude and explanations are contrary to a useful, informative forum.  Posting solutions exactly like what skippy12 posted is what I expect and appreciate...." 

In that case, then you should also expect and appreciate warnings about attempting such tasks by inexperienced readers, too.  I gave a warning to readers who lack technical expertise.

[skippy12]

---

@RobertTheFat wrote:

Why "91" for the registry key value?

---

My research indicated this is the hexidecimal value for turning autoplay on.  The link in my post came up under a google search like "autoplay registry key location".  A similar search I am sure would lead to more technical detail on the value of 91.

[ScottyP]

If you are an IT pro and you are in there doing things the average photographer would not even consider doing in Windows (like me) perhaps your question is more on computers and less on photography and maybe it should be posted on a serious computer site like Ars Technica or something, not on this forum.  

[perkcan]

Yes this is a "computer" problem, but with specific software distributed by Canon for downloading images from Canon cameras.  As I often do for problems with software for particular hardware, I go to the manufacturer's website and forum.  Great companies with any common sense monitor forums and even encourage users to post issues and problems like I have done.  The main idea is that the community can contribute at the same time that the company observes and provides additional feedback.  This is the natural place to come and post this kind of issue.  For goodness sake, it is in the Camera > Software forum!

As I said before, the culture on this forum is rather strange that fellow users discourage the kind of detail that is supposed to make these forums truely useful.   Scott, have you considered that your recommendation should actually be turned on its head?  These forums should be used for posting issues specific to Canon Cameras and Canon software, including problems with software functions and compatibility, include detailed solutions and technical details.  If people simply want general advice on photography or answers to casual usage issues, they should find other specialized forums that would be more appropriate.  Maybe even better would be for someone at Canon to observe and respond to this type of issue.  They should create technical and/or advanced forum topics if they find their general users are scared of or cannot handle technical details necessary to fix problems.

I'm surprised that my brief mention of being a computer expert (in a sarcastic context) prompted such replies.  I was not declaring to the world that I am some kind of know-it-all.    I was simply pointing out what a silly generalization Waddizzle made when s/he implied that many (if not most) problems of this type are simply due to people configuring their systems incorrectly or that they misunderstand the settings, etc.  Besides, it's crazy to think just because I have some specialized knowledge or skill that I should go elsewhere.  On the contrary, my expertise and experience have taught me to come to forums just like this for answers and to share my experiences with the community.

[Waddizzle]

"  I was simply pointing out what a silly generalization Waddizzle made when s/he implied that many (if not most) problems of this type are simply due to people configuring their systems incorrectly or that they misunderstand the settings, etc.  "

Operator error is the most common cause of most issues.  I have nearly 40 years of experience to back up that observation.  What about you?  As far as being a computer expert, I have been a computer programmer and troubleshooter for decades. 

[EDIT]  I find your repeated objections to my simple warnings and cautions to be most unusual.

I go all the way back to a PDP-8 and an ASR-33.  "I've been fooling computers since 1971."

BTW, no one objected to your advice.  I simply posted a warning to unwary readers, that's all.