Problem installing Ms Antispyware

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I downloaded Ms Antispyware today and the installer reports several errors. I
have attached the log file (from my temp folder) below.

Note: this machine had installed Ms Antispyware in the past, but I had to
remove it when testing another antispyware solution.
At this moment there is NO other antispyware running on the machine.

--
Robert

=================================================

Error 1904.Module C:\WINDOWS\system32\GCCollection.dll failed to register.
HRESULT -2147220473. Contact your support personnel.
Error 1904.Module C:\Program Files\Microsoft
AntiSpyware\gcAntiSpywareLibrary.dll failed to register. HRESULT
-2147220473. Contact your support personnel.
Error 1904.Module C:\Program Files\Microsoft AntiSpyware\gcASPrivacyLib.dll
failed to register. HRESULT -2147220473. Contact your support personnel.
Error 1904.Module C:\Program Files\Microsoft AntiSpyware\GCCollection.dll
failed to register. HRESULT -2147220473. Contact your support personnel.
Error 1904.Module C:\Program Files\Microsoft AntiSpyware\gcASSoapLib.dll
failed to register. HRESULT -2147220473. Contact your support personnel.
Error 1904.Module C:\Program Files\Microsoft AntiSpyware\gcTCPObjLib.dll
failed to register. HRESULT -2147220473. Contact your support personnel.
Error 1904.Module C:\Program Files\Microsoft AntiSpyware\gcASThreatAudit.dll
failed to register. HRESULT -2147220473. Contact your support personnel.
Error 1904.Module C:\Program Files\Microsoft AntiSpyware\shellextension.dll
failed to register. HRESULT -2147220473. Contact your support personnel.
Error 1904.Module C:\Program Files\Microsoft
AntiSpyware\gcSoftwareUpdateLib.dll failed to register. HRESULT -2147220473.
Contact your support personnel.
Error 1904.Module C:\WINDOWS\system32\hashlib.dll failed to register.
HRESULT -2147220473. Contact your support personnel.
=== Logging stopped: 10/02/2006 21:25:42 ===
 
Robert--that log is largely opaque to us these days. Do you, in fact, see
any operational issues with the install?
 
Bill Sanderson said:
Robert--that log is largely opaque to us these days. Do you, in fact, see
any operational issues with the install?
Click to expand...
I am not sure what you mean with 'opaque' (English is not my native
language). The issues that I see is that the software doesn't work after the
install.
 
Engel said:
Hello Robert,

Are you the administratior? trying to install the program.
Click to expand...

Yes I am.
I also have run SPF /Scannow to check system files, but that did not help.
 
Sorry - What I meant was that we are unlikely to be able to diagnose an
issue from the contents of the errors.log file.

This is what I would try:

1) uninstall Microsoft Antispyware (it is possible that this may not
succeed--let us know)

2) delete \program files\microsoft antispyware and all subfolders. You
will lose access to any quarantined items, history, and custom settings.

3) reinstall Microsoft Antispyware from a current version download, taking
care to be logged in as an administrator.


--
 
Bill,
This is what I would try:

1) uninstall Microsoft Antispyware (it is possible that this may not
succeed--let us know)

2) delete \program files\microsoft antispyware and all subfolders. You
will lose access to any quarantined items, history, and custom settings.

3) reinstall Microsoft Antispyware from a current version download, taking
care to be logged in as an administrator.
Click to expand...

I tried all of that. Removed remainin Dlls from windows\system32
(GcCollection.DLL, GcUncompress.DLL and Hash.dll) and tried it both as local
adminin and as domain admin.

Unfortunately that doesn't make a difference.

There must be something wrong in my configuration, but I wish the error
message was a little more helpful. It doesn't tell much.

This is definitely something they need to fix before they release this
product.
 
Sorry this is such an issue. I've tended to stay out of threads involving
the "numbered errors" 'cause I don't have a sure-fire fix, and clearly this
one is no exception.

It might be useful to see the precise error messages involved in registering
a given .dll file

regsvr32 hashlib.dll

for example, would be the command-line command needed to do that. You
should get a small result window indicating success, or--something else!

In some cases you may need to worry about paths to the dll in question.

Are you running any active software which is intended to detect or prevent
changes to system programs or installed software? Have you taken any steps
to "lock down" permissions on system folders?

--
 
Bill,
Sorry this is such an issue. I've tended to stay out of threads involving
the "numbered errors" 'cause I don't have a sure-fire fix, and clearly this
one is no exception.

It might be useful to see the precise error messages involved in registering
a given .dll file

regsvr32 hashlib.dll
Click to expand...

I have tried that. I get an error 'DlLReguisterServer failed' error
0x8002801c'. Similar error for the other DLLs.
Are you running any active software which is intended to detect or prevent
changes to system programs or installed software? Have you taken any steps
to "lock down" permissions on system folders?
Click to expand...

I am running as admin and I have disables antivirus, firewall, the whole
lot. Still the same problem.

I can only conclude that this product is not ready for market yet.
 
The beta1 product is a slightly modified third-party product. The company
which produced this product, GiantSoftware--was purchased by Microsoft 3
weeks before the beta1 product was first released.

Not to disagree entirely with your conclusion, let me just say that a
Microsoft reworked version of this product, which will be branded Windows
Defender. Early versions of Windows Defender are already available to beta
testers of Vista. However, it is expected that users of earlier Windows
versions will be able to test this product soon--certainly by the end of
March.

I can understand your feelings about the set of errors you are seeing, and
the inability of the peer support in these forums to work around them. I'd
urge you to keep an eye out for announcements of beta2, Windows Defender,
however, and consider testing that further when it is available.

All the references I can find to the DLLRegister error you cite talk about
permissions on the registry branches involved. I suspect that what is
happening is that the permissions on these keys were set for the original
installing user, and that you are now reinstalling as a different user. I
can hypothesize what's necessary to fix this, but it isn't something I'd
want to do as part of this kind of informal support conversation--messing
about in the registry can be risky.

So my advice, tempered by my understandings about when beta2 will be
available, is to wait for the release of beta2 and try the product again at
that point.

I certainly hope I'll hear from you if you do that and experience any of the
same problems!

--
 
Back
Top