I am trying to run the latest version of McAfee Stinger Portable, posted 13 May, but when the app runs, it comes up with some screen showing command line options and never proceeds to the main GUI of Stinger. Is anyone else experiencing this problem? I am running Windows 7 x64 and it's up-to-date. Thanks.
I just installed 11.0.0.289 here on my Windows 7 x64 box and it fired up just fine. How are you installing (manually, via platform, etc) and to what full path? Note that if installing manually, you can't check the box to run it at the end of the installer (it doesn't work right with admin apps).
Sometimes, the impossible can become possible, if you're awesome!
I am downloading the PAF from this site and extracting to a subfolder on my desktop (C:\Users\--\Desktop\McAfeeStingerPortable). I am running as Admin.
Here's all I see when I run McAfeeStingerPortable.exe:
http://i.imgur.com/YzInqYS.png
Are you right-clicking and running as admin or just running McAfeeStingerPortable.exe? Does the online component of the installer run as expected (sans errors)? Is your logged in user an admin or standard user? Within the McAfeeStingerPortable\App\Stinger directory, do you see a stinger32.exe file with an MD5 of 7c6432f50f2ca34a59fae502273ab102? What antivirus are you running? Do you have any Start Menu replacements running?
I'm asking these questions as the exact same scenario (run installer, install to Desktop directly, run McAfeeStingerPortable.exe) works without issue on my PC, running the same OS as you.
Sometimes, the impossible can become possible, if you're awesome!
I'm running as an admin. (no right click to do so). I downloaded the stinger32.exe problem to try it and it gives the same errors, so something must be amiss apart from your PAF. The MD5 matches yours (7c6432f50f2ca34a59fae502273ab102). I'm running Avast (Free) - latest version. No Start Menu replacements are running.
I disabled Avast for 10 mins. and that did not help. Same problem.
If you run stinger32.exe directly, does it run as expected?
We've found an odd issue where some PCs mistakenly pass a command line switch from PAL to the app itself. Not sure why. Can't reproduce it on any of our test machines at all. Is there anything else running or configured on your PC that you can think of?
Sometimes, the impossible can become possible, if you're awesome!
John, no. Running stinger32.exe itself produces the same error. All I get is the Command Line Options window. I hit OK and the app. exits.
If it's happening running stinger32.exe, that's an issue with the base app, not our portable wrapper. Not sure what it is, either, as I haven't seen it. I'd thought it might be the PAL bug I mentioned, but it is not. You'd need to contact McAfee to file a bug report to see this resolved. Or, if it didn't happen before, it could be a bug with this particular release.
Sometimes, the impossible can become possible, if you're awesome!
I have stinger 64bits in my windows 7 before it totally breakdown and now I'm not sure if stinger can work in windows 8.
I was having the same problem with the switches not working and finally was able to resolve it.
McAfee has changed how you type in the switch. Instead of a forward slash, you use two dashes instead.
ie:
Instead of:
/ADL
Use:
--ADL
Not sure why but that seemed to work. I'm running it on Win 7 32-bit