Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Trusteer Rapport add on has been disabled by Firefox so I can no longer do my online banking. How do I get it back?

  • 55 odgovori
  • 62 ima ovaj problem
  • 139 views
  • Posljednji odgovor poslao Dave-H

more options

Back to the same old problem I'm afraid. The last update of Firefox actually asked me if I wanted to enable a Trusteer Rapport add on - which I did. Naively I thought that all my previous problems would be over. Now I've got a message telling me that the add on has been disabled because it can't be verified for use with Firefox - but I've been using it for months and Firefox asked me if I wanted to enable it!!!!! Nearly every bank and building society in the UK recommends installing and using Trusteer Rapport in order to improve the safety of one's online banking. As a result I would very much like to get Rapport working again.

My only option at the moment is to stop using Firefox.

Back to the same old problem I'm afraid. The last update of Firefox actually asked me if I wanted to enable a Trusteer Rapport add on - which I did. Naively I thought that all my previous problems would be over. Now I've got a message telling me that the add on has been disabled because it can't be verified for use with Firefox - but I've been using it for months and Firefox asked me if I wanted to enable it!!!!! Nearly every bank and building society in the UK recommends installing and using Trusteer Rapport in order to improve the safety of one's online banking. As a result I would very much like to get Rapport working again. My only option at the moment is to stop using Firefox.

Izabrano rješenje

Firefox 56 is supported by the latest release of Trusteer Rapport according to:

http://www.trusteer.com/en/latest-updates-supported-browsers

I don't know if you want to try the Update link there, or check with your bank first.

Pročitajte ovaj odgovor sa objašnjenjem 👍 9

All Replies (15)

more options

Thanks, I've used that in the past when I've been having trouble with Rapport as part of the trouble-shooting with their technical support people. All my installations eventually got the auto-update to version 3.5.1908.118, but on my XP machines it produced a BSOD on every boot, and I had to roll back to 3.5.1804.161. Anyone who is still on XP beware of that! This has happened a few times in the past, and I worked around it with the Trusteer technical support people, but that option is no longer there as they don't support XP now of course. One other problem I have with the new version even on Windows 10 is that on my system it stops Internet Explorer 11 from running. The workaround I've found is to disable the "early browser protection" function in Rapport. I have reported it to Trusteer, but I'm not holding my breath for a response now! Off-topic I know, but just an aside in case anyone else is having the same problem. It works fine with 64 bit Firefox (56). Cheers, Dave.

more options

Hi Dave-H - many thanks for the tip about disabling the "early browser protection" in the latest Rapport 1908.118. I had not tried IE11 for a while, and as you found, mine would not start either. Rapport seems to behave quite "normally" under IE11, so I can use that as an alternative if I need to!

As others have noticed, this latest Rapport update (1908.118) seems to be very buggy, and seems to give that (false) warning about not being enabled, even though it actually is. I see that Rapport error window for both FF and Chrome, even though it shows as enabled in the add-ins status page. I suspect there IS some sort of subtle loss of "status" communication (i.e. a BUG) between the Rapport Management Engine and the 2 browsers, but hopefully its INTENDED security functionality is still working (but then how do we tell - there is no "activity log" to view now in the later levels, like there is in other security products, like AV suites)? Trusteer Rapport (both the product AND its support I am sorry to say) seems to have taken a dive since IBM took it over. This is NOT a good sign, for software that is important, and recommended by major banks.

It also seems a shame to have to comment (and rant a bit here and there), on such a good forum as this, but at least this Mozilla Support Forum is Vibrant and Active (and has lots of good info and knowledgeable posters), versus the Rapport site, that seems rather Stagnant (the opposite of Vibrant I think...) :-)

Izmjenjeno od strane td47

more options

Yes, I've seen that Rapport message pop up too, which says it's installed but not enabled on Firefox. Of course it actually is and is apparently working fine! I tend to agree with you about Rapport having gone downhill since Trusteer were taken over by IBM. It is worrying that so many banks want you to use it and nag you if you don't, and I believe there are even some that will not let you use their online banking at all unless Rapport is installed. What's really baffling me is that there seems to be absolutely no technical support from Trusteer now. You can submit a case, and you still get an acknowledgement e-mail back, but unlike in the past when they contacted you back usually pretty quickly, you now get no further response at all, or at least I don't, which is really worrying for a security application! I've tried several times now to report problems, both using the program UI and on the website, and not a single response has come back.

more options

@Dave_H

I have various emails back and fro with Trusteer plus some online chats too regarding Rapport support of FF new versions. What is totally clear to me is that they have no intention whatsoever of making Rapport function 100% with the current or future versions of FF.

You will notice that any websites you already had protected with Rapport are still protected, but you can not protect new websites. To me it is quite clear they want us to use IE not FF, and they told me to use another browser if I wanted to protect additional websites. So no one should bother holding their breath for Trusteer.

more options

I agree it's annoying not to be able to add extra protected sites using Firefox, but you can add them using IE, and they will be there when you use Firefox, so it's not a great problem IMO. You only have to use IE once, just to get the site added. I think this has always been the case with Rapport on Firefox, it's nothing new. Have you had contact with Rapport technical support recently? As I said earlier, the last several support requests I've submitted to them have been completely ignored. Perhaps they've blacklisted me!

more options

Hi Dave

Haven't been in contact with them for a couple of months.

Thanks very much for the tip re: protecting website with IE and this transferring automatically to FF, I never knew that was possible. Previously all my protected websites I did directly via FF.

Much appreciated

Colin

more options

Hi Dave, yes, many thanks from me too, about adding new sites with IE. It is galling that the latest update (1908.128) has ATTEMPTED to fix the Icon UI fly-out (the square bubble is NOT empty anymore, it actually tells you that "this site needs protecting" but then there is NO action bar there to actually do it). I think they were teasing me on purpose... :-) By the way cwh777 - the database of protected sites is accessed from inside the Rapport management Engine and its support libraries itself, NOT from the browser client, so ANY working browser can add a new site, - seems like only IE right now - great shame for what WAS a good product at one time.

more options

Yes, I'd noticed that fly-out box was always blank too! Rather worrying that they can release supposed security software with such obvious bugs in it! Makes you wonder just how well the rest of it is working. My installations again show no sign of updating to 1908.128 yet. I wonder if the new Rapport version will now work on the current version of Microsoft Edge as it's supposed to. The version of Edge rolled out with the Windows 10 Creators' Update still hasn't yet been supported by Rapport, getting on for a year after it was rolled out!

more options

Both my Windows 8.1 and Windows 10 installations now have the latest 3.5.1908.128 Rapport update. My two XP installations I have had to freeze on 3.5.1804.161 as they BSOD on the later versions! I was pleased to see that IE11 now runs fine with the new version even with the "Early Browser Protection" re-enabled, so they've fixed that, and it should be OK with the default settings now.

more options

FYI: it seems that the latest update of Rapport (1908.134) now actually works with later versions of FF, even the 57.04 FF Quantum... at last!! I can actually add new sites, and the icon fly-out actually works. I tested it on Chrome just for fun (yes I know this is an FF forum, sorry).. and although the icon fly-out appears to work, when you click to protect a new site, it does not! Not tested it on Edge yet...

Izmjenjeno od strane td47

more options

td47 said

FYI: it seems that the latest update of Rapport (1908.134) now actually works with later versions of FF, even the 57.04 FF Quantum... at last!! I can actually add new sites, and the icon fly-out actually works. I tested it on Chrome just for fun (yes I know this is an FF forum, sorry).. and although the icon fly-out appears to work, when you click to protect a new site, it does not! Not tested it on Edge yet...

Wow and only 4 days before Firefox 58 is released (1/23) and another cycle of Rapport having compatibility issues with Firefox begins again.

more options

LOL, yes indeed! They seem to always be so far behind with compatibility. The latest version still doesn't work with Edge HTML 16, the current version, and as far as I know hasn't worked with any version of Edge since the first Windows 10 Creators update, which was over nine months ago now!

more options

Sorry to bring this thread up again with an off-topic issue, but I now have a problem with the last version of Rapport that works with Windows XP, which is 3.5.1804.161. It's causing a problem with my Windows XP Search Companion malfunctioning, and I would like to roll back to an earlier version. Unfortunately I didn't notice this problem and identify Rapport as the culprit until today, and I have already deleted the installers for the previous versions of Rapport. They are of course, not available anywhere any more! Does anyone have a saved version of the offline installation file for 32 bit Rapport 1908.134 which they could let me have? I think there may actually have been at least one other version in between 134 and 161, so that would be useful to try as well if possible. Thanks, Dave.

more options

Dave-H - sorry this is a late reply. I HAVE found an old version 1804.158, so if you still need it I can place it in Dropbox and let you have that, or send it you via email. I will try to see if PM is available to your profile. As it is in EXE form, I will have to ZIP it so thet your email client does not reject it.

By the way, if THAT does not work, try editing the Security Policy from the Rapport Dashboard, and change a few items until it stops interfering with the Search. I would suggest starting with "Early Browser Protection" set to NEVER.

more options

Hi @td47. Thanks for that, but I actually seem to be OK now (touch wood!) I tried uninstalling 3.5.1804.161 on my netbook, to see if any later versions would now work. They actually don't. The latest versions don't cause a BSOD on XP like the first 3.5.1908 version did, but they don't work properly with Firefox 52 ESR, the Rapport icon will not appear in the address bar as it should. When I finally gave up and put 3.5.1804.161 back on the machine, I was very surprised to find that the problem with the Search Companion seemed to have gone away! I've now uninstalled and reinstalled it on my main machine as well after completely cleaning the system of any traces, and so far the problem has been fixed on that machine too, so (fingers crossed) I can only assume that it was some residue of another later version that was perhaps causing the problem. Thanks again. Cheers, Dave.

  1. 1
  2. 2
  3. 3