Safety camera update not working

MikeSheffield

I am sorry for the troubles with the Communicator Plugin. Internet Explorer is the only Windows browser currently compatible. The developers are working on a solution to replace the Communicator Plugin in the future but there is no official ETA. In Internet Explorer 11 on Windows 10 you will get the message to add my.garmin.com to trusted sites. Once this is complete you will have to check the box "Stop receiving this notification" for the message to stop popping up.

In Internet Explorer it is usually better to install the plugin through the CommunicatorPlugin_420.exe installer. If you continue to have troubles after installation, please see the FAQ articles below or contact Product Support by phone.

Why isn't the Garmin Communicator Plugin detected in my browser after installing it?https://support.garmin.com/support/searchSupport/case.faces?caseId={5a6a7780-f7f2-11e3-c98c-000000000000}

Why does my Downloadable Content freeze at 50%?https://support.garmin.com/support/searchSupport/case.faces?caseId={d8b5a180-ebba-11de-ce85-000000000000}

Curt

Internet Explorer is the only Windows browser currently compatible. The developers are working on a solution to replace the Communicator Plugin in the future but there is no official ETA.

This really is an appalling situation. It has caused many users a great deal of trouble - myself included - that will only increase more rapidly as computers are replaced. There was considerable warning that plugins were going to become deprecated. It would be some consolation if the developers would give an ETA for a solution - noting that the E is for Estimated! I am hoping it will be a facility added to Express.

I launched Internet Explorer 11 (what a terrible browser!) ....

Really? I hardly use anything else and find it far better than Chrome, FireFox etc

mavison

I am sorry it is inconvenient to use Internet Explorer and that we don't have an estimated time for a solution to the plugin issue. You can also try using Safari on the PC. Even though we only support the Mac version of Safari, some users have had success using it with Windows as well.

Dave

Doh!

I have to say I'm pretty appalled at this response.

According to comments from the Firefox end, what is needed is for Garmin to obtain signing-off of their PlugIn from the Firefox/Mozilla developers - something which all developers knew would be needed. Yet this evidently hasn't been done. Equally, M/s Edge was well trailed before its launch, and has been around for some months now - yet still no Garmin compatibility in sight. As a US company I'd have expected Garmin to at least be on top of the Microsoft situation.

Some visible evidence that rectification is under way, plus an acknowledgement that "we've messed up", would be welcome . . .

Not sure who you spoke to at the 'Firefox end' but support for all NPAPI plug ins are being withdrawn by browsers because of security issues.

There is no way Garmin can get their plug in approved, nor can anyone else. As already posted you can still use IE11 so there is no immediate problem.

SUSSAMB -
This is a rather silly post IMHO.

First, I have eight plugins within Firefox which work perfectly well. Only one which doesn't - Garmin.

Second, by your own claim, the Garmin plugin is supposed to work OK with IE11 (and is required by it). Support not 'withdrawn' there then??

Third, browsing the various postings on a number of forums makes clear this has been a problem for virtually a year (although it's not affected me for all of that time).

Fourth - why should Garmin now announce it only works with one browser? You may like IE11 - plenty of people don't, and should be able to choose to use Firebox, or Edge, or Safari if they prefer them.

NPAPI plug ins are being withdrawn. That decision has nothing to do with Garmin.

As for wanting all the other browsers to accept NPAPI plug ins that isn't going to happen and eventually IE won't either. You could try complaining to the browser companies but here's some info on Firefox

http://www.pcworld.com/article/2990991/browsers/firefox-will-stop-supporting-npapi-plugins-by-end-of-2016-following-chromes-lead.html

Note that, according to that, support for NPAPI plug ins will be withdrawn on an 'unspecified' date in 2016, guess that date has come.

You really are shooting at the wrong horse :)