EOS utility behavior suddenly changed

[dts350z]

The start up behavior of EOS Utility suddenly changed, and I can't figure out (google, registry search, or in app data) how to put it back.

 

I have it set to start when a camera is connected, but after a public solar viewing event suddenly it starts with WiFi paring with every windows bootup.

 

My camera doesn't have wifi, and I don't want eos utility to start unless a camera is connected via USB.

 

The only thing I can think of is somebody's canon automatically paired with my computer as they were walking by the solar viewing booth and now my computer is looking for that camera at every start up?

 

One huge problem with that theory is I didn't have a DSLR connected at that event.

 

Any ideas?

 

 

 

 

[dts350z]

This is EOS Utility 2.14.20, the highest rev listed for my T3i at Canon.

 

I guess there is a version 3, maybe for newer cameras only?

[astroman133]

I would expect that EOS Utility would work with every camera that is supported by the SDK that it comes with.

 

Did you try disabling the "Add WFT Pairing to the Startup Folder" in the Preferences?

 

There may be some help here --> http://learn.usa.canon.com/app/pdfs/quickguides/WFT_EOS_Utility_PC.pdf

[dts350z]

The offending window is actually titled: "EOS Utility Launcher"

[astroman133]

If you examine your wireless networks in Windows, do you find any networks that you don't expect?  Perhaps a network was created when your PC sensed a camera with WiFi turned on.  I would suggest deleting that network.

[dts350z]

I would expect that EOS Utility would work with every camera that is supported by the SDK that it comes with.

 

Did you try disabling the "Add WFT Pairing to the Startup Folder" in the Preferences?

 

There may be some help here --> http://learn.usa.canon.com/app/pdfs/quickguides/WFT_EOS_Utility_PC.pdf

 

I don't see that option (but I don't have a camera connected at the moment). What tab is it on?

 

I do see the monitor folder, however.

[dts350z]

If you examine your wireless networks in Windows, do you find any networks that you don't expect?  Perhaps a network was created when your PC sensed a camera with WiFi turned on.  I would suggest deleting that network.

 

Nothing new in wireless networks...

[astroman133]

Follow the link from my previous post. Scroll down to page 5 and look at the dialog in Step 2 at the top of the page. It shows the WFT pairing checkbox on the Basic Settings tab.

[dts350z]

Mine doesn't have that (at least without a camera connected).

 

Maybe that is version 3?

 

[astroman133]

Hmmm.  I am at a loss...Your camera doesn't have WiFi.  Your version of the EOS Utility doesn't support WiFi.  There is no ad hoc network between a camera and the PC. So, what is trying to pair with what?

[dts350z]

This is what comes up when my computer boots:

 

 

and the normal dialog doesn't come up when I connect the camera with USB. The only way to get that to come up is to start the EOS 2.exe, in the EOS 2 folder.

 

I'm thinking of maybe uninstalling/deleting/cleaning the registry and starting again.

 

Irritating that we don't know what changed or how to keep it from happening again.

[astroman133]

Are you sure that there isn't some auto launch preference that you can disable?

[dts350z]

I'm assuming if I turn off auto launch it still won't start eos utility when I connect a camera via USB], but yes it would not launch EOS launcher and therefore would not bring up that dialog.

[s3igell]

There is a difference between Auto Start Apps (configured to launch as part of the Boot / Restart sequence) and Auto Launch / Default Apps (configured to launch when certain File Type is Opened or certain External Device is Connected).

 

For the Auto Start activity that is pestering you, you can check the simple Start Folder or dig deep into the whole cadre of AutoRun configurations.

[astroman133]

I get what you are saying, but not everyone goes by that convention.  Canon has an Auto Launch preference that determines whether or not the app runs automatically at login. It has nothing to do with double-clicking on a CR2 file or whether or not the camera is connected.

 

I am wondering whether Auto Launch could be disabled, but that Windows could be configured to run EOS Utility whenever the camera is connected.  That just makes it more difficult to use BYE.

[s3igell]

I get what you are saying, but not everyone goes by that convention.  Canon has an Auto Launch preference that determines whether or not the app runs automatically at login. It has nothing to do with double-clicking on a CR2 file or whether or not the camera is connected.

 

This isn't "personal convention" but rather the underlying Windows OS implementation.  And it is rather convoluted due to Win7's burden of Backwards Compatibility.

Take a look - install AutoRuns on your PC (its a Microsoft-provided App - just not part of the standard Win7 Installation Package).  You'll recognize all sorts of Support Apps and Processes that you've never though of HOW they get Started...

AutoRuns allows one to both See and to Disable items on these AutoRuns Startup Lists.

 

And you are correct, relatively few of these AutoRuns are related to Apps or DLLs registered as the Default Associations for specific File Exts.

 

I am wondering whether Auto Launch could be disabled, but that Windows could be configured to run EOS Utility whenever the camera is connected.  That just makes it more difficult to use BYE.

 

The Canon EOS Utility (in its various versions) and any WiFi-specific additional Canon Utility (I have one specific to my Canon MP620 Multi-Function WiFi Printer/Scanner), usually does have it's own "Checkbox" or "Menu Selection" that triggers the Deeper Windows AutoRun association.  But as we've been relatively unsuccessful at identifying that GUI Item, I pointed out the Low-Level Tool.

[dts350z]

Bye the way, in my opinion, the whole "EOS Utility makes BYE more difficult to run" is a misconception due the default BYE preference setting of complaining when EOS Utility is running (which I unset).

 

There is NO CONFLICT between BYE and EOS Utility running at the same time. The only caveat is that only one of them can be connected to the camera at a time.

 

I like having EOS utility start up when the camera is connected because it is an early indicator that all is right with your camera connection before you start launching all your astro software, including BYE.

 

In fact, I have found that I have more success in connecting with BYE if I first connect with EOS Utility. If I first connect with EOS Utility, then disconnect, I am 100% assured of a successful connect with BYE.  If I skip that step, I "sometimes to often" have a problem connecting with BYE. 

 

I don't claim to know why that is but I suspect that EOS utility is doing something (perhaps beyond the SDK) to reset the camera to some more sane state, ready for the SDK, than just starting from scratch with the camera AC or external DC power coming on while the USB cord is already connected and the power switch already on (My camera is inside a cooler bag, and the power to everything on the mount gets applied all at once by turning on the switch on an outlet strip).

[astroman133]

OK, I have run out of suggestions.

 

I understand your comment about both programs being able to run, but only one of them can be connected.  It may be useful for BYE to only complain about the EOS utility when the user has clicked the Connect button, but the connection failed.  That could serve as a gentle reminder that you need to disconnect the camera from the EOS Utility.

 

I did have a version of the EOS utility installed at one time, but I almost never used it and it was getting in the way so I removed it.  When my cameras (XS and T5i) are correctly connected and powered on, I have never had an issue with BYE not connecting or acting in an unexpected way. Whether I am powered with the battery or with an A/C adapter makes no difference.  Still there could be something with your camera that is slightly different from mine. If only we could ask Canon about that!

[dts350z]

Yeah I guess I'm giving up too. Removed it from the start up folder.

 

This morning I tried coping the config files from a "working" computer. No joy (and files were same size and time stamp anyway). Then uninstalled, cleaned registry, rebooted, reinstalled, no change.

 

The window that pops up is the same on the good computer, when you click open. The difference is on the "bad" computer the window opens by itself at boot time.Seems like it should be a registry setting but I can't find it. Also on the "bad" computer the real EOS utility (EOS Utility 2, vs EOS Utility Launcher) doesn't start when I plug in the camera, but BYE is connecting so I guess I'll leave it alone at this point.

 

I have a short cut to EOS utility 2 I can call up if I need it.