Can't Launch in XP

  • Thread starter Thread starter Jordan
  • Start date Start date
J

Jordan

Running XP Pro SP2 and was able to install app with no problem. The problem
occurs when opening the app, the "Loading Microsooft Antispyware" screen
pops up for a split second, then disappears.
Though its listed in my system tray, I still can't launch it and run a scan.
I loaded this on my Win2000 laptop and its works fine.
 
Greetings,

You are certianly not alone...I am experiencing a similar
problem. I installed MSASb on the first of two
workstations and it's works like a champ. However, when
I went to do the same on the second workstation, the
install went fine, but that's where the honeymoon
ended...if I tried to initiate a scan by right-clicking
or double click on the systray icon...POOF...a flash of
activity and then nothing, not even a hung process as far
as I can tell :(

I realize there are the usual mob of cowardly, misguided
Anti-MS cretins lurking and wasting bits and bytes as
usual, so I certainly don't want to add gasoline to the
fire, but I must say I do find it somewhat peculiar that
in the short time since the GIANT acquisition, this
product has gone in reverse from a highly regarded and
very stable production release to "beta", with whatever
*necessary* changes causing strange errors and
misbehaviors. The cliche, "If it ain't broke, don't fix
it!", keeps haunting me as I type this...guess there's a
reason why it's a cliche ;)

I will post back if I discover a solution/workaround. In
the meantime, I'm hoping someone else may be able to shed
a little more light on the subject :)

Sys1: XP Pro SP1a
Sys2: XP Pro SP1a

-----Original Message Below-----<
Click to expand...

"Running XP Pro SP2 and was able to install app with no
problem. The problem occurs when opening the
app,the "Loading Microsooft Antispyware" screen pops up
for a split second, then disappears. Though its listed in
my system tray, I still can't launch it and run a scan. I
loaded this on my Win2000 laptop and its works fine."
 
Hello again,

If, by chance, you have to come to read this thread while
looking for answers to why MSASb doesn't launch after a
successful install, I've found a potential solution that
worked for me :) and hopefully will for you...

1. Browse to C:\Program Files\Microsoft AntiSpyware (or
location where you installed MSASb)

2. Open errors.log

3. Upon doing so, I found numerous entries for the
following error:

Component 'COMDLG32.OCX' or one of its dependencies not
correctly registered: a file is missing or
invalid::GIANTAntiSpywareMain:MDIfrmMain:LoadHeader::1/10/
2005 hh:mm:ss AM:XP:1.0.501

Sidebar: Hmmm...funny, I never received this error before
now even with numerous other programs accessing the
Common Dialog functions and not reporting any
difficulties, but, then again, this *is* an ActiveX
Control, not exactly MS's best display of programming
prowress or pinnacle of technical achievement ;)

Ohhh, how I do "long" to see a secure, stable WinOS, at
least as secure and stable as can be reasonably achieved
once the decision is made to stop supporting DOS
dinosaurs and countless other outdated, thoroughly
antiquated relics of programs way, way past their prime
in order to *enable* hidebound luddites afraid of
embracing the future...

Enough editorializing already, back to the issue at hand.
Further research confirmed the problem...

4. COMDLG32.OCX is now apparently corrupted for some
unknown reason, requiring one of two solutions:

a) First option - re-register the OCX using Regsvr32

b) Second option - install a fresh copy of the OCX

5. To re-register the OCX, click Start then Run...

6. Type Regsvr32 c:\windows\system32\comdlg32.ocx then
press Enter

(note: search first to validate the path where
comdlg32.ocx resides on your system)

7. This didn't work for me, the OCX was totally shot :(

....on to Option #2...

8. Search the Web for a replacement OCX

9. Once located and downloaded, *RENAME* the old version
of the OCX (i.e. comdlg32.ocx to comdlg32.bak)

10. Install the OCX in the same directory as the old
version

11. Register the OCX

12. Click Start then Run...

13. Type Regsvr32 c:\windows\system32\comdlg32.ocx then
press Enter

14. You should receive a confirmation message saying the
new OCX is registered

15. Uninstall MSASb (if you haven't done so already),
reboot your computer and then re-install MSASb

Worked for me...I hope it does the same for you...

Good Luck...
 
Thanks for the detective work and posting the fix.

I've seen, in these groups, more than one OCX fingered in this way.
Another thread had RICHTX32.OCX in a similar error message.

So--the key is reading errors.log, and re-registering, or obtaining a clean
version of and re-registering, the relevant control, it appears.
 
Back
Top