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.

[Waddizzle]

I would advise anyone who does not understand know what the Windows Registry is to disregard the advice given in this thread.  The Registry is not something to be edited by the uninformed.  The potential to crash the OS outweighs any potential benefit from going in an editing it ourself.

I repeat my advice to configure your Windows OS to never automatically do anything when you insert, or install, a temporary data storage device, such as a USB stick, or even a Canon camera.  Instead, rely on the Canon installation software to configure the automatic behaviors for you.

[RobertTheFat]

---

@Waddizzle wrote:

I would advise anyone who does not understand know what the Windows Registry is to disregard the advice given in this thread.  The Registry is not something to be edited by the uninformed.  The potential to crash the OS outweighs any potential benefit from going in an editing it ourself.

I repeat my advice to configure your Windows OS to never automatically do anything when you insert, or install, a temporary data storage device, such as a USB stick, or even a Canon camera.  Instead, rely on the Canon installation software to configure the automatic behaviors for you.

---

Although some registry key changes are dangerous, the change proposed here is not one of them. Note that it's user-specific; so if it did have a seriously bad effect, it could be edited out using a different account.

Waddizzle's point is valid, though. Registry changes should be attempted only by system administrators who fully understand what they're doing. Though it's rather unlikely, it's at least possible to make an error that could require re-installation of the operating system.

[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.

[skippy12]

---

RobertTheFat wrote

---

Although some registry key changes are dangerous, the change proposed here is not one of them. Note that it's user-specific; so if it did have a seriously bad effect, it could be edited out using a different account.

Waddizzle's point is valid, though. Registry changes should be attempted only by system administrators who fully understand what they're doing. Though it's rather unlikely, it's at least possible to make an error that could require re-installation of the operating system.

---

I agree with both Robert's and Waddizzle's points.  One should be very careful when changing anything in the registry.  You will note that I put a warning at the top of my post.  I work in IT.  So, I have a lot of experience deep down in the guts of computers.

However, if the registry change were any more complex than this, I would not have posted it.  So, I believe even an initiant would be able to figure it out.  Further more, you will note from my post that the value is entered and then removed.  So, it is not even a setting that is even left in play.

Also, I chose the words of my post very, very carefully.  I said "resolved", not "solved".  This is the set of steps that worked on my machine.  I am not sure why or exactly how (although I would love to know being the techy that I am).  Struggling with this problem, being a huge Canon fan, and finding this thread, I just thought I would like to engage in this community and offer what I had found worked for me.

[perkcan]

Waddizzle said, "Instead, rely on the Canon installation software to configure the automatic behaviors for you."

The entire reason for this post is that the Canon software does NOT configure the behavior correctly on Windows 10.  It doesn't matter whether it is a problem with Canon software or Microsoft operating system--the fact that it does not work as expected and does not work like in previous versions of Windows is the problem.  

Of course someone can mess up the registry if not careful, but it is rather naive to think we should "trust" the companies to fix all the bugs.  I trusted Microsoft support last week when they told to me update Windows 10 to fix Store App problems, only to worsen the problem until Windows kept crashing and blue screening.  The support person "promised" me that it would fix the problem.  Does my anecdote nullify good advice about being careful?  Certainly not, but a simple warning should be sufficient--no need to discourage people from learning and trying more than they already know.  

Especially with old hardware and software, companies do not always have users' best interest in mind.  I have seen this problem time and time again... after a little while, updates to driver and support software begin to loose features and becomes buggy.  This has been particularly true with some digital cameras and printers.  The argument is that companies cannot continue to create new drivers and software forever.  That sounds reasonable, but for the companies which DO update their software and keep things current... even for older versions... I remain a loyal customer.  Companies who just let their products fade into obsolecense and become junk... well, I look around and go elsewhere for my next purchase.

[Waddizzle]

"Waddizzle said, "Instead, rely on the Canon installation software to configure the automatic behaviors for you."

The entire reason for this post is that the Canon software does NOT configure the behavior correctly on Windows 10.  It doesn't matter whether it is a problem with Canon software or Microsoft operating system--the fact that it does not work as expected and does not work like in previous versions of Windows is the problem.  " 

Yes, the Canon software does configure previous versions of Windows correctly, as well as Windows 10.  However, there are some settings in the OS that can prevent proper configurations.  Virus and malware software are notorous for doing this without your immediate knowledge.  Some versions of Windows 10 lack mulit-media drivers found in previous versions os Windows.

If your software is not working as expected, then there is another influencing factor involved.  The vast majority of users are not experiencing issues.  Only a small handful seem to have issues.   Frequently, users with issues are not running Intel CPUs.  There are a host of possibilities that could cause unexpected behavior, none of which have anything to do with Canon's software.

The most likely factors are mismatched file type associations, and undesireable default behaviors when USB devices are detected.  Sometimes, an update to one application can negatively impact other applications, particularly when it comes media software.  Everybody wants their application to be the boss for all file types.

[perkcan]

Pardon me for not being overly exact in my wording and for over-generalizing the problem.  I now realize that I must be one of the small percentage of people that experience such problems with the Canon software on Windows 10 and that the problem must certainly stem from something I did wrong.  It is sad really--that my experience as a Windows developer for many decades, and being a computer expert has not helped me configure my systems properly.  I’ll confess my sin that one of the two computers which experience this problem has an AMD processor.  Sorry for that.  The point of my original post was to point out that I was having problems on just two of my computers**.

(* Disclaimer:  These bugs may or may not exist on your machine.  If you have no problems with your software, congratulations on choosing the perfect combination of hardware and for keeping your computer configured exactly.  Really, you have no need to be reading this forum since it is only a small percentage of people who needs to mess with this forum and apparently you are not one of them.  Go your way and enjoy your computer with the rest of the vast majority.  If you do return to these forums, rather than helping solve the issue, please just remind us of corporate virtue and remind us how dangerous registry edits can be.  If you do have similar problems, it’s most likely that you have already screwed up something or you have obtained a defective computer, perhaps not having an Intel CPU.  If you expect to find a solution to the problem, I’m sorry but you are most likely incompetent and should not attempt to fix anything yourself, especially if it has anything to do with the registry.  You can either 1) go buy a new computer with Intel processor only, 2) reinstall everything from scratch, 3) better yet buy a new camera, or 4) do all of the above.  If none of those are options, you should wait until the manufacturers eventually produce new software which will fix the problem.  Visit their website every week and install all new software immediate, because you can trust that eventually it will all work.  On the other, it may not work if you continue to screw up your configuration.  Just stop that and let your hardware and software work together in harmony, will you?)

[RobertTheFat]

---

@perkcan wrote:

Pardon me for not being overly exact in my wording and for over-generalizing the problem.  I now realize that I must be one of the small percentage of people that experience such problems with the Canon software on Windows 10 and that the problem must certainly stem from something I did wrong.  It is sad really--that my experience as a Windows developer for many decades, and being a computer expert has not helped me configure my systems properly.  I’ll confess my sin that one of the two computers which experience this problem has an AMD processor.  Sorry for that.  The point of my original post was to point out that I was having problems on just two of my computers**.

(* Disclaimer:  These bugs may or may not exist on your machine.  If you have no problems with your software, congratulations on choosing the perfect combination of hardware and for keeping your computer configured exactly.  Really, you have no need to be reading this forum since it is only a small percentage of people who needs to mess with this forum and apparently you are not one of them.  Go your way and enjoy your computer with the rest of the vast majority.  If you do return to these forums, rather than helping solve the issue, please just remind us of corporate virtue and remind us how dangerous registry edits can be.  If you do have similar problems, it’s most likely that you have already screwed up something or you have obtained a defective computer, perhaps not having an Intel CPU.  If you expect to find a solution to the problem, I’m sorry but you are most likely incompetent and should not attempt to fix anything yourself, especially if it has anything to do with the registry.  You can either 1) go buy a new computer with Intel processor only, 2) reinstall everything from scratch, 3) better yet buy a new camera, or 4) do all of the above.  If none of those are options, you should wait until the manufacturers eventually produce new software which will fix the problem.  Visit their website every week and install all new software immediate, because you can trust that eventually it will all work.  On the other, it may not work if you continue to screw up your configuration.  Just stop that and let your hardware and software work together in harmony, will you?)

---

In a parallel thread it has been pointed out that some of the problems people have experienced with Canon software under Windows 10 can be traced to the fact that some editions of Windows 10 don't include the Windows Media Player or don't have it enabled by default. Since you're a self-identified Windows expert, I won't insult you by trying to tell you how to correct that omission; but if you haven't touched that base already, you may want to look into it.

[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.