We had the same problem. We were running stinger32.exe( v.188.8.131.527 ) on an off-network system that had IE6 installed and is Windows XP, SP3, 32-bit. When we went back on network, we upgraded to IE8 then took it back off network, reran stinger32.exe and it was fine.
Our dilemma is we can't put IE8 on the target system at this point. So our idea is to make the USB HDD from which we are deploying our updates bootable. We would put IE8 on it. We boot into the USB HDD. We have a couple of questions:
Sugam Shrestha and Sandra Carney
Edited by Moderator to add missing details:
Kindly Clarify the below ,
1) Whether you are trying to boot Win XP from an External HDD ? If Yes will you be removing the existing Internal HDD?
2) Whether are you going to use external HDD for installing Windows Updates alone - IE 8
3) Stinger will check the Default Program Files directory for IE 8 present in the Master Internal drive wherein Windows is Installed - Were you referring to change this path to the External HDD?
I apologise. I tried to branch the entire conversation out so that I could move it to Application Control and half of the posts were left behind. Not my fault, but the board's.
Anyway if you want to start over again here, now that I've moved it, then that's fine.
I've added the salient comments to the first post here.
Message was edited by: Ex_Brit on 09/03/14 10:02:39 EDT AM
To answer the question about installing IE8 on the external drive...you can't do that unfortunately. It has to be installed in the operating system and the operating system can't be installed on an external drive, unless that drive is eSATA and set in the BIOS to boot first.Message was edited by: Ex_Brit on 09/03/14 10:50:02 EDT AM
Sorry I brought up Application Control. This is not central to our problem. I was merely clarifying what we are installing. The central problem is that stinger doesn't work because we only have IE6 on the target system.
Ex_Brit answered my question regarding installing IE8 on an external drive.
So my next question is can I tell stinger through some sort of command line option, environment variable, or registry setting to not check for updates. It is failing in the check for updates due to no access to the internet.
No I don't believe there is a way other than unchecking the rootkit scan optiion because it is that option that looks for updates.
But Selvan is the support guy and he may know more than I.Message was edited by: Ex_Brit on 09/03/14 7:39:47 EDT PM
>> For test i've upgraded one PC to IE8 and i still get the message 'Stinger executable modified and may be infected'.
Stinger executable is now signed using a newer digital certificate. This cert maybe be part of the root certificates trusted by older OS like WinXP.
If a windows update was applied - this is resolved. One can also manually apply the root certificate patch to XP. Get it from: http://www.microsoft.com/en-us/download/details.aspx?id=41084
The windows update would be great. Unfortunately, the target system is a medical device that has already gone through validation. We are at the end of the release cycle and are out of time. Are there any other options?
We still get the message, too. That isn't the problem. The trouble starts in the next step which is with IE6, stinger attempts to look for updates and fails out. It never conducts the scan. It never brings up the options dialog. When we installed IE8 as a test, then the next step consisted of bringing up the dialog. Once the dialog was dismissed, it conducted the scan.