System Explorers Missing in 614

  • Thread starter Thread starter Paul Ward
  • Start date Start date
P

Paul Ward

In the update to build 614 I have an issue where the system
explorers appear to be missing. Clicking on the option
takes you to the correct screen however the left pane is
empty under the heading of system explorers. Also have the
same reported problem with the latest defs not sticking
with autoupdate constantly downloading, though the about
screen reports correctly.
 
Registering a VB6 dll seems to fix missing agents:
1) Open up a command prompt (start -> run -> cmd)
2) Type in the following "regsvr32 msvbvm60.dll" (without the quotes).
3) Close and re-open Windows AntiSpyware
4) If that fails, install VB6 runtime files:
http://www.softwarepatch.com/windows/vbrun6download.htm
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
 
Thanks for your help Bill, I did try to search the forum
for the solution but the search facility is currently
unavailable on the site.

The Explorer fix did not fix the issue with the defs. Will
give deleting the defs a try tomorrow......
 
Actually I need to expand on this reply. After running the
Regsvr32 cmd I actually got a load of alerts which actually
related to historical changes to my machine ie NOT live
events. Almost as if MAS was gagged before the fix. I
thought MAS was running fine under build 613 on my machine,
perhaps I am mistaken?
-----Original Message-----
Regsvr32 fixed the system explorer issue, thanks.

I now have the conflict with Spybot were MAS prevents/
alerts against Spybot from adding 139mm.com to the
restricted sites within IE. As described elsewhere this is
reported within MAS as an attempt to add the site to the
TRUSTED list.
Click to expand...
 
After serious thinking Paul Ward wrote :
The Explorer fix did not fix the issue with the defs. Will
give deleting the defs a try tomorrow......
Click to expand...

Hi

It is not working, already tried it.

Also uninstall, remove MSAS folders and registry cleaning
followed with a clean 1.0.614 install.

Found a workaround with another user but
it is not a recommended way to update definitions.

Wait for MS !
 
Thanks Plun, saved me from a lot of effort!

-----Original Message-----
After serious thinking Paul Ward wrote :

Hi

It is not working, already tried it.

Also uninstall, remove MSAS folders and registry cleaning
followed with a clean 1.0.614 install.

Found a workaround with another user but
it is not a recommended way to update definitions.

Wait for MS !
Click to expand...
 
Andre Da Costa explained on 2005-06-28 :
Yes, the best recommendation like Plun says is to shutdown MSAS from the
Notification areas, uninstall it and delete the Microsoft AntiSpyware folder
located under Program Files, restart and install back 614.
Click to expand...

Andre, I am NOT saying this !

Wait for a solution from MS I say !

If you "dig" you will find a workaround which I and
Taxman discussed, it is working but not recommended.
 
Andre Da Costa submitted this idea :
So your suggestion is to do nothing?
Click to expand...

Yes, but you already finds the workaround
within one more message..............

So it will be spread but I believe this workaround
is a little bit to wild. Mr Dodson can explain this
if he wants, i am sure that MS have solution already.

:D
 
I think you may be mistaken, and would urge an uninstall of 613 followed by
install of 614.

I really don't know what the issue is that prompted the issuance of 614, but
I believe there was something, so I'd replace the older build--your
experience may not be an anomaly.

--

Paul Ward said:
Actually I need to expand on this reply. After running the
Regsvr32 cmd I actually got a load of alerts which actually
related to historical changes to my machine ie NOT live
events. Almost as if MAS was gagged before the fix. I
thought MAS was running fine under build 613 on my machine,
perhaps I am mistaken?
Click to expand...
 
Now you've really got me interested--I don't know whether you've found THE
fix for this issue (recommended or not) or whether just beating on it long
enough finally loosened things up. Historically, I don't recall ever seeing
info from Microsoft about sticky definition updates, but maybe this will be
the time.

--
 
Thanks--I'll find that if I get the time.
--

plun said:
Andre Da Costa explained on 2005-06-28 :

Andre, I am NOT saying this !

Wait for a solution from MS I say !

If you "dig" you will find a workaround which I and
Taxman discussed, it is working but not recommended.
Click to expand...
 
Back
Top