I think it is known that McAfee Stinger can behave badly.
I'm saying it *is* behaving badly.
I'm not sure it should be in the stable since it is known to attack itself when implemented as a PA.
Most recently it is post XP. If everyone else is no longer using XP that is fine.
I don't need this App, it was a superfluous check on top of what I already have for viri, malware, etc.
I suggest this should be dropped unless someone feels strongly about it. After saying it had a new version, once, it tried to install itself in my Program directory and generally behaved like a drunken college student thereafter. Let me into your Registry, please, let me know about your registry, let me at least touch it ...
No thanks.
I'd be interested in other opinions.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
I just ran an outdated version on Windows XP and it fired up as expected. The app has to be run as admin and will temporarily write to HKLM, HKCU, and Program Files if you run a scan. It then must be run a second time to ensure it fully cleans everything up. This is mentioned in the messagebox that pops up each time you run it. If you don't like that, you shouldn't use it.
Sometimes, the impossible can become possible, if you're awesome!
I can understand an outdated version working as it used to work but doesn't now. e.g. the X close button in the top right corner doesn't appear but does work if you know where it should be.
If this is an XP v. current Stinger conflict then I'm happy to drop it.
Wm
I meant outdated as in a day old with one point release having been released after it to show that it wouldn't try to update itself.
The UI is a bit wonky on XP now. It says it supports XP as long as it has IE8. But I'd wager they no longer test it since XP is discontinued.
Sometimes, the impossible can become possible, if you're awesome!
I'm not interested in something that is interested in IE8 or indeed any other version of IE as it is a browser that has been disabled here for years.
End as far as I am concerned. Thanks for looking into it.
Edit: I've had to forcibly remove it as it leaves behind a file called stinger.opt; I doubt that is XP specific
Wm
Like it or not, IE is part of Windows. Multiple pieces of Windows rely on it and use it. As does lots of Windows software. Even the PA.c Platform uses the Wininet components to handle downloading. If you manually break IE, you'll break all kinds of software. For that reason, we don't support modded Windows installs using something like nLite or tools which 'remove' Internet Explorer.
You need to run McAfee Stinger Portable a second time and not click Scan after running it once for it to properly clean up. This is explained via a message on every start.
If you've manually killed IE on Windows XP, it's likely interfering with Stinger's operation and could cause it to crash or wind up in an non-runnable state.
Sometimes, the impossible can become possible, if you're awesome!
Let's leave it. I know what I've done and why
Edit: I run a script once a week or so to see if MS have anything to offer me. IE isn't a necessary part of that however much someone wants it to be.
Wm