There is a security patch which is downloading without the user's intervention.
All you need to do is start TruClient Firefox, and the update is installed "automagically." There is no need to start the browser as stand-alone, either. The Truclient session will cause the install By Itself.
So far, it APPEARS - but is not fully confirmed - you can get around the problem with these steps:
- Replace the ../bin/firefox directory with the opriginal version from the CD.
- Reboot
- Unplug the network cable.
- Start the Firefox install from within LoadRunner/bin directory
- Enable the menus (<alt> key)
- tools menu, select Options, click the "Advanced" button, then "Updates" tab
- Turn off ALL UPDATES.
To proof out the fix:
- create a new Truclient - Firefox protocol script
- Click "develop script"
- Now you should be OK.... Back up the Firefox directory (since it's now not going to update) and keep it handy - you may get nailed a few more times, we're not yet sure.
If you see the "Select Your Add-ons" screen (Attachment TC-FFx_Patched_Start.png) you're running a "patched" version of firefox, and the TruClient add-on is disabled - it's incompatible.
The second image (if the system is working, I can't be sure it's uploading correctly) shows the "Update History" for Firefox. the fix is "firefox 12.0 (20120420145725)", it is a security update, and I can't seem to get rid of it.
Of note: It looks like it affects old scripts, precluding viewing the steps or editing the script.
It looks like NEW scripts may work.
The reason for all the uncertainty is, the patch appears to download regardless of whether or not we open firefox stand-alone.
I ran the steps above before I took the screenshot of the Update History, and the machine was unplugged from the network while I did the steps for disable the updates.
I then opened FFx stand-alone, and - "HEY! There's the security update in the update history!"
+++
An aside: There are two services in Windows for updates. One is know, and you can simmply turn off the automatic updates.
There's a second one, for whem M$ decides you MUST have this fix. It's always on, unless you go digging through KBs and find out how to turn it off. Your machines all have this back door built in if they run Winblows.
Maybe Firefox decided to do the same?
---------->>> PLEASE UPDATE WITH ANY FINDINGS FROM FOLLOWING THESE STEPS. We REALLY need keep things stable, our environment here stinks. (No control, no Admin access, a User Access Control software called "Beyond Trust" which stops us from doing about half our job, and a change rate that a glacier considers slow. We upgraded to Windows 7 THIS YEAR; windows 10 comes out in JUNE. We went to LR 11.52 Last Year, October. So I REALLY need any other eyes on this to shoot back their findings, PLEASE!)