Ever since I updated to the latest EOS Utility 2.14.0 (3/13/14), my Apple Airport Extreme has been dropping all wireless devices connected to my home network (i.e. my iphones, ipads, and even my wife's laptop which is connected by wireless only). My wired PC running Windows 8.1 Pro (which is the computer I use for my EOS Utility and Photoshop) still connects to the internet and the wired network, along with other wired devices. However, all wireless devices stop working as soon as this process starts (shortly after logging in).
Through a few agonizing weeks of trying to find out what was causing the issue (I didn't know at the time the issue was related to the EOS Utility update), I discovered accidentally while watching the processes in task manager that a process called Canon EOS UPNP Detector (32 bit) was running and consuming a large portion of my CPU time (15% or more even though I didn't have the EOS Utility running and no camera was connected). I killed the process and, wah lah, my wireless devices reconnected immediately. I could not believe this so I had to repeat it several times to verify this was indeed the culprit. I don't know how or what starts the Canon EOS UPNP Detector process except rebooting the computer. I reboot, the process starts and my Wi-Fi dies. I kill the process and Wi-Fi revives itself. I don't know how to stop this process from starting on boot up, but at least now I can rest assured that I know what is killing my wireless network and stop the process after any reboots.
Anyhow, I though I would post this in case anyone else was pulling their hair out as I was trying to find this annoying bug. I communicated this to Canon tech support and they gave me a case number and are following up on the issue.
I don't know if this bug affects Wi-Fi on other routers or configurations, but it definitely does it on my Airport Extreme (the latest version) and my Windows 8.1 Pro system.
FYI. The Canon process does not start until you log on to the Windows 8.1 Pro PC. If I reboot, but don't log in, my Wi-Fi works fine, but if I log in and the Canon EOS UPNP Detector process starts, my Wi-Fi dies until I kill the process in Task Manager. Also, I had not issues with previous versions of EOS Utility. This all started when 2.14.0 came out which, ironically, was supposed to be the Windows 8.1 compatible version, at least according to the Canon EOS driver web site.
Through a few agonizing weeks of trying to find out what was causing the issue (I didn't know at the time the issue was related to the EOS Utility update), I discovered accidentally while watching the processes in task manager that a process called Canon EOS UPNP Detector (32 bit) was running and consuming a large portion of my CPU time (15% or more even though I didn't have the EOS Utility running and no camera was connected). I killed the process and, wah lah, my wireless devices reconnected immediately. I could not believe this so I had to repeat it several times to verify this was indeed the culprit. I don't know how or what starts the Canon EOS UPNP Detector process except rebooting the computer. I reboot, the process starts and my Wi-Fi dies. I kill the process and Wi-Fi revives itself. I don't know how to stop this process from starting on boot up, but at least now I can rest assured that I know what is killing my wireless network and stop the process after any reboots.
Anyhow, I though I would post this in case anyone else was pulling their hair out as I was trying to find this annoying bug. I communicated this to Canon tech support and they gave me a case number and are following up on the issue.
I don't know if this bug affects Wi-Fi on other routers or configurations, but it definitely does it on my Airport Extreme (the latest version) and my Windows 8.1 Pro system.
FYI. The Canon process does not start until you log on to the Windows 8.1 Pro PC. If I reboot, but don't log in, my Wi-Fi works fine, but if I log in and the Canon EOS UPNP Detector process starts, my Wi-Fi dies until I kill the process in Task Manager. Also, I had not issues with previous versions of EOS Utility. This all started when 2.14.0 came out which, ironically, was supposed to be the Windows 8.1 compatible version, at least according to the Canon EOS driver web site.