Back when MSAS first came out, I had an Error 1904 on installation and an
error 101 when I attempted to run MSAS on one of the five installations that
I did. Other people also had the error and there was a lot of discussion
and suggestions in the newsgroup.

I tried ALL the suggested solutions to get MSAS to install on the computer.
With no luck. I eventually gave up and uninstalled MSAS including the files
the uninstall program misses.

I had hoped that build 509 would fix the problem. It does not.

The initial installation and upgrade worked on the other four systems.

Is there a way of submitting a real "bug/issue report" to the developers on
this problem with backup data and logs?

Bill Rankin

The known issues section of the help in build .509 has the standard
prescription for what do do about 101 errors.

Can you verify that doing a change, update, still doesn't fix this on this
particular machine?

The level of interaction you're looking for just isn't possible with the
public beta. You can bet that given the number of folks out here reporting
these errors, they are not having trouble replicating them.
--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

"Bill-R" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Back when MSAS first came out, I had an Error 1904 on installation and an
> error 101 when I attempted to run MSAS on one of the five installations
> that I did. Other people also had the error and there was a lot of
> discussion and suggestions in the newsgroup.
>
> I tried ALL the suggested solutions to get MSAS to install on the
> computer. With no luck. I eventually gave up and uninstalled MSAS
> including the files the uninstall program misses.
>
> I had hoped that build 509 would fix the problem. It does not.
>
> The initial installation and upgrade worked on the other four systems.
>
> Is there a way of submitting a real "bug/issue report" to the developers
> on this problem with backup data and logs?
>
> Bill Rankin
>

I installed MSAS on 10 machines and I have the same
problem on one machine. I tried everything I could but I
have always the same problem as discribed from Bill-R.
See also my mail from the same day at 12:02 for more
information.
Daniel

>-----Original Message-----
>The known issues section of the help in build .509 has
the standard
>prescription for what do do about 101 errors.
>
>Can you verify that doing a change, update, still
doesn't fix this on this
>particular machine?
>
>The level of interaction you're looking for just isn't
possible with the
>public beta. You can bet that given the number of folks
out here reporting
>these errors, they are not having trouble replicating
them.
>--
>FAQ for Microsoft Antispyware:
>http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>
>"Bill-R" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed)
om...
>> Back when MSAS first came out, I had an Error 1904 on
installation and an
>> error 101 when I attempted to run MSAS on one of the
five installations
>> that I did. Other people also had the error and there
was a lot of
>> discussion and suggestions in the newsgroup.
>>
>> I tried ALL the suggested solutions to get MSAS to
install on the
>> computer. With no luck. I eventually gave up and
uninstalled MSAS
>> including the files the uninstall program misses.
>>
>> I had hoped that build 509 would fix the problem. It
does not.
>>
>> The initial installation and upgrade worked on the
other four systems.
>>
>> Is there a way of submitting a real "bug/issue report"
to the developers
>> on this problem with backup data and logs?
>>
>> Bill Rankin
>>
>
>
>.
>

Bill,

I do not know what you mean by verify.

I tried to install build 509 and got exactly the same results I got with
501. The attempt to update also failed. The 101 error is not really the
problem. The real problem is that MSAS never completes the install. During
installation (and Update) I get the following error:

Error 1904 Module C:\Windows\System 32\hashlib.dll failed to register.
HResult - 2147220473.
Contact your support personnel.

That is, all install attempts fail and an attempt to use MSAS results in the
expected 101. This was on the system with 501 uninstalled. I tried several
accounts on this system.

I am of two opinions (that means I have no real evidence):

1. that the problem involves the configuration of options of the two active
administrator-level user accounts on this system (not counting the
administrator account). The argument against this opinion is I have MSAS
installed on a different system with three user accounts and do not have a
problem.

2. that the uninstall program has not removed something that is blocking
the reinstall. I uninstalled, rebooted, then removed all the MSAS files
that uninstall did not remove. That did not help, but there may be more
files I missed.

Hopefully this issue is being worked,
Bill Rankin

"Bill Sanderson" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> The known issues section of the help in build .509 has the standard
> prescription for what do do about 101 errors.
>
> Can you verify that doing a change, update, still doesn't fix this on this
> particular machine?
>
> The level of interaction you're looking for just isn't possible with the
> public beta. You can bet that given the number of folks out here
> reporting these errors, they are not having trouble replicating them.
> --
> FAQ for Microsoft Antispyware:
> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>
> "Bill-R" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Back when MSAS first came out, I had an Error 1904 on installation and an
>> error 101 when I attempted to run MSAS on one of the five installations
>> that I did. Other people also had the error and there was a lot of
>> discussion and suggestions in the newsgroup.
>>
>> I tried ALL the suggested solutions to get MSAS to install on the
>> computer. With no luck. I eventually gave up and uninstalled MSAS
>> including the files the uninstall program misses.
>>
>> I had hoped that build 509 would fix the problem. It does not.
>>
>> The initial installation and upgrade worked on the other four systems.
>>
>> Is there a way of submitting a real "bug/issue report" to the developers
>> on this problem with backup data and logs?
>>
>> Bill Rankin

Bill--it isn't clear from your message whether you tried the update route,
rather than remove and reinstall.

However, rather than mess with this further, I'd recommend the following:

Send an email to as-(E-Mail Removed)

Jeff Dillon is looking into the 103/110 errors, and is interested in the
errors.log files from such systems. I'm not sure he wants those files
immediately, but if your file is small, you might zip it up and add it to
the email.



--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

"Bill-R" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Bill,
>
> I do not know what you mean by verify.
>
> I tried to install build 509 and got exactly the same results I got with
> 501. The attempt to update also failed. The 101 error is not really the
> problem. The real problem is that MSAS never completes the install.
> During installation (and Update) I get the following error:
>
> Error 1904 Module C:\Windows\System 32\hashlib.dll failed to register.
> HResult - 2147220473.
> Contact your support personnel.
>
> That is, all install attempts fail and an attempt to use MSAS results in
> the expected 101. This was on the system with 501 uninstalled. I tried
> several accounts on this system.
>
> I am of two opinions (that means I have no real evidence):
>
> 1. that the problem involves the configuration of options of the two
> active administrator-level user accounts on this system (not counting the
> administrator account). The argument against this opinion is I have MSAS
> installed on a different system with three user accounts and do not have a
> problem.
>
> 2. that the uninstall program has not removed something that is blocking
> the reinstall. I uninstalled, rebooted, then removed all the MSAS files
> that uninstall did not remove. That did not help, but there may be more
> files I missed.
>
> Hopefully this issue is being worked,
> Bill Rankin
>
> "Bill Sanderson" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> The known issues section of the help in build .509 has the standard
>> prescription for what do do about 101 errors.
>>
>> Can you verify that doing a change, update, still doesn't fix this on
>> this particular machine?
>>
>> The level of interaction you're looking for just isn't possible with the
>> public beta. You can bet that given the number of folks out here
>> reporting these errors, they are not having trouble replicating them.
>> --
>> FAQ for Microsoft Antispyware:
>> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>>
>> "Bill-R" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Back when MSAS first came out, I had an Error 1904 on installation and
>>> an error 101 when I attempted to run MSAS on one of the five
>>> installations that I did. Other people also had the error and there was
>>> a lot of discussion and suggestions in the newsgroup.
>>>
>>> I tried ALL the suggested solutions to get MSAS to install on the
>>> computer. With no luck. I eventually gave up and uninstalled MSAS
>>> including the files the uninstall program misses.
>>>
>>> I had hoped that build 509 would fix the problem. It does not.
>>>
>>> The initial installation and upgrade worked on the other four systems.
>>>
>>> Is there a way of submitting a real "bug/issue report" to the developers
>>> on this problem with backup data and logs?
>>>
>>> Bill Rankin
>
>

Yes, I tried update on a partial installation and it failed with a 1904
error without completing the update. Essentially it acted the same for both
an install and an update. It failed to install.

However, I went back and looked at the Windows\System 32 folder and the
hashlib.dll file was still there from an earlier install I attempted on 20
Mar. I deleted it and tried again. This time I got a good install for one
user.

Now I am only getting the 101 error for the other user on the system. Isn't
this a known error for computers with multiple users?

Bill Rankin


"Bill Sanderson" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Bill--it isn't clear from your message whether you tried the update route,
> rather than remove and reinstall.
>
> However, rather than mess with this further, I'd recommend the following:
>
> Send an email to as-(E-Mail Removed)
>
> Jeff Dillon is looking into the 103/110 errors, and is interested in the
> errors.log files from such systems. I'm not sure he wants those files
> immediately, but if your file is small, you might zip it up and add it to
> the email.
>
>
>
> --
> FAQ for Microsoft Antispyware:
> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>
> "Bill-R" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Bill,
>>
>> I do not know what you mean by verify.
>>
>> I tried to install build 509 and got exactly the same results I got with
>> 501. The attempt to update also failed. The 101 error is not really the
>> problem. The real problem is that MSAS never completes the install.
>> During installation (and Update) I get the following error:
>>
>> Error 1904 Module C:\Windows\System 32\hashlib.dll failed to register.
>> HResult - 2147220473.
>> Contact your support personnel.
>>
>> That is, all install attempts fail and an attempt to use MSAS results in
>> the expected 101. This was on the system with 501 uninstalled. I tried
>> several accounts on this system.
>>
>> I am of two opinions (that means I have no real evidence):
>>
>> 1. that the problem involves the configuration of options of the two
>> active administrator-level user accounts on this system (not counting the
>> administrator account). The argument against this opinion is I have MSAS
>> installed on a different system with three user accounts and do not have
>> a problem.
>>
>> 2. that the uninstall program has not removed something that is blocking
>> the reinstall. I uninstalled, rebooted, then removed all the MSAS files
>> that uninstall did not remove. That did not help, but there may be more
>> files I missed.
>>
>> Hopefully this issue is being worked,
>> Bill Rankin
>>
>> "Bill Sanderson" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> The known issues section of the help in build .509 has the standard
>>> prescription for what do do about 101 errors.
>>>
>>> Can you verify that doing a change, update, still doesn't fix this on
>>> this particular machine?
>>>
>>> The level of interaction you're looking for just isn't possible with the
>>> public beta. You can bet that given the number of folks out here
>>> reporting these errors, they are not having trouble replicating them.
>>> --
>>> FAQ for Microsoft Antispyware:
>>> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>>>
>>> "Bill-R" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> Back when MSAS first came out, I had an Error 1904 on installation and
>>>> an error 101 when I attempted to run MSAS on one of the five
>>>> installations that I did. Other people also had the error and there
>>>> was a lot of discussion and suggestions in the newsgroup.
>>>>
>>>> I tried ALL the suggested solutions to get MSAS to install on the
>>>> computer. With no luck. I eventually gave up and uninstalled MSAS
>>>> including the files the uninstall program misses.
>>>>
>>>> I had hoped that build 509 would fix the problem. It does not.
>>>>
>>>> The initial installation and upgrade worked on the other four systems.
>>>>
>>>> Is there a way of submitting a real "bug/issue report" to the
>>>> developers on this problem with backup data and logs?
>>>>
>>>> Bill Rankin
>>
>>
>
>

That's useful information--thanks. Surely the installer should be able to
replace that file, rather than just giving up in disgust.

I'd go ahead and send email, mentioning that you only get the error in the
multi-user context. I don't know the breadth of what Jeff Dillon is looking
for.

--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

"Bill-R" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Yes, I tried update on a partial installation and it failed with a 1904
> error without completing the update. Essentially it acted the same for
> both an install and an update. It failed to install.
>
> However, I went back and looked at the Windows\System 32 folder and the
> hashlib.dll file was still there from an earlier install I attempted on 20
> Mar. I deleted it and tried again. This time I got a good install for
> one user.
>
> Now I am only getting the 101 error for the other user on the system.
> Isn't this a known error for computers with multiple users?
>
> Bill Rankin
>
>
> "Bill Sanderson" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Bill--it isn't clear from your message whether you tried the update
>> route, rather than remove and reinstall.
>>
>> However, rather than mess with this further, I'd recommend the following:
>>
>> Send an email to as-(E-Mail Removed)
>>
>> Jeff Dillon is looking into the 103/110 errors, and is interested in the
>> errors.log files from such systems. I'm not sure he wants those files
>> immediately, but if your file is small, you might zip it up and add it to
>> the email.
>>
>>
>>
>> --
>> FAQ for Microsoft Antispyware:
>> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>>
>> "Bill-R" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Bill,
>>>
>>> I do not know what you mean by verify.
>>>
>>> I tried to install build 509 and got exactly the same results I got with
>>> 501. The attempt to update also failed. The 101 error is not really
>>> the problem. The real problem is that MSAS never completes the install.
>>> During installation (and Update) I get the following error:
>>>
>>> Error 1904 Module C:\Windows\System 32\hashlib.dll failed to register.
>>> HResult - 2147220473.
>>> Contact your support personnel.
>>>
>>> That is, all install attempts fail and an attempt to use MSAS results in
>>> the expected 101. This was on the system with 501 uninstalled. I tried
>>> several accounts on this system.
>>>
>>> I am of two opinions (that means I have no real evidence):
>>>
>>> 1. that the problem involves the configuration of options of the two
>>> active administrator-level user accounts on this system (not counting
>>> the administrator account). The argument against this opinion is I have
>>> MSAS installed on a different system with three user accounts and do not
>>> have a problem.
>>>
>>> 2. that the uninstall program has not removed something that is
>>> blocking the reinstall. I uninstalled, rebooted, then removed all the
>>> MSAS files that uninstall did not remove. That did not help, but there
>>> may be more files I missed.
>>>
>>> Hopefully this issue is being worked,
>>> Bill Rankin
>>>
>>> "Bill Sanderson" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> The known issues section of the help in build .509 has the standard
>>>> prescription for what do do about 101 errors.
>>>>
>>>> Can you verify that doing a change, update, still doesn't fix this on
>>>> this particular machine?
>>>>
>>>> The level of interaction you're looking for just isn't possible with
>>>> the public beta. You can bet that given the number of folks out here
>>>> reporting these errors, they are not having trouble replicating them.
>>>> --
>>>> FAQ for Microsoft Antispyware:
>>>> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>>>>
>>>> "Bill-R" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>> Back when MSAS first came out, I had an Error 1904 on installation and
>>>>> an error 101 when I attempted to run MSAS on one of the five
>>>>> installations that I did. Other people also had the error and there
>>>>> was a lot of discussion and suggestions in the newsgroup.
>>>>>
>>>>> I tried ALL the suggested solutions to get MSAS to install on the
>>>>> computer. With no luck. I eventually gave up and uninstalled MSAS
>>>>> including the files the uninstall program misses.
>>>>>
>>>>> I had hoped that build 509 would fix the problem. It does not.
>>>>>
>>>>> The initial installation and upgrade worked on the other four systems.
>>>>>
>>>>> Is there a way of submitting a real "bug/issue report" to the
>>>>> developers on this problem with backup data and logs?
>>>>>
>>>>> Bill Rankin
>>>
>>>
>>
>>
>
>

Bill,

My only guess is that the installation is configured not to replace existing
files. For your info, there are at least four system32 files that are not
uninstalled: GCCollection.dll, gcTypLibA.tbl, gcUnCompress.dll and
hashlib.dll.

I sent Jeff a more coherent version of the Issue and the errors.log file as
you suggested.

Thanks
Bill

"Bill Sanderson" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> That's useful information--thanks. Surely the installer should be able to
> replace that file, rather than just giving up in disgust.
>
> I'd go ahead and send email, mentioning that you only get the error in the
> multi-user context. I don't know the breadth of what Jeff Dillon is
> looking for.
>
> --
> FAQ for Microsoft Antispyware:
> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>
> "Bill-R" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Yes, I tried update on a partial installation and it failed with a 1904
>> error without completing the update. Essentially it acted the same for
>> both an install and an update. It failed to install.
>>
>> However, I went back and looked at the Windows\System 32 folder and the
>> hashlib.dll file was still there from an earlier install I attempted on
>> 20 Mar. I deleted it and tried again. This time I got a good install
>> for one user.
>>
>> Now I am only getting the 101 error for the other user on the system.
>> Isn't this a known error for computers with multiple users?
>>
>> Bill Rankin
>>
>>
>> "Bill Sanderson" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Bill--it isn't clear from your message whether you tried the update
>>> route, rather than remove and reinstall.
>>>
>>> However, rather than mess with this further, I'd recommend the
>>> following:
>>>
>>> Send an email to as-(E-Mail Removed)
>>>
>>> Jeff Dillon is looking into the 103/110 errors, and is interested in the
>>> errors.log files from such systems. I'm not sure he wants those files
>>> immediately, but if your file is small, you might zip it up and add it
>>> to the email.
>>>
>>>
>>>
>>> --
>>> FAQ for Microsoft Antispyware:
>>> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>>>
>>> "Bill-R" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> Bill,
>>>>
>>>> I do not know what you mean by verify.
>>>>
>>>> I tried to install build 509 and got exactly the same results I got
>>>> with 501. The attempt to update also failed. The 101 error is not
>>>> really the problem. The real problem is that MSAS never completes the
>>>> install. During installation (and Update) I get the following error:
>>>>
>>>> Error 1904 Module C:\Windows\System 32\hashlib.dll failed to register.
>>>> HResult - 2147220473.
>>>> Contact your support personnel.
>>>>
>>>> That is, all install attempts fail and an attempt to use MSAS results
>>>> in the expected 101. This was on the system with 501 uninstalled. I
>>>> tried several accounts on this system.
>>>>
>>>> I am of two opinions (that means I have no real evidence):
>>>>
>>>> 1. that the problem involves the configuration of options of the two
>>>> active administrator-level user accounts on this system (not counting
>>>> the administrator account). The argument against this opinion is I
>>>> have MSAS installed on a different system with three user accounts and
>>>> do not have a problem.
>>>>
>>>> 2. that the uninstall program has not removed something that is
>>>> blocking the reinstall. I uninstalled, rebooted, then removed all the
>>>> MSAS files that uninstall did not remove. That did not help, but there
>>>> may be more files I missed.
>>>>
>>>> Hopefully this issue is being worked,
>>>> Bill Rankin
>>>>
>>>> "Bill Sanderson" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>> The known issues section of the help in build .509 has the standard
>>>>> prescription for what do do about 101 errors.
>>>>>
>>>>> Can you verify that doing a change, update, still doesn't fix this on
>>>>> this particular machine?
>>>>>
>>>>> The level of interaction you're looking for just isn't possible with
>>>>> the public beta. You can bet that given the number of folks out here
>>>>> reporting these errors, they are not having trouble replicating them.
>>>>> --
>>>>> FAQ for Microsoft Antispyware:
>>>>> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>>>>>
>>>>> "Bill-R" <(E-Mail Removed)> wrote in message
>>>>> news:(E-Mail Removed)...
>>>>>> Back when MSAS first came out, I had an Error 1904 on installation
>>>>>> and an error 101 when I attempted to run MSAS on one of the five
>>>>>> installations that I did. Other people also had the error and there
>>>>>> was a lot of discussion and suggestions in the newsgroup.
>>>>>>
>>>>>> I tried ALL the suggested solutions to get MSAS to install on the
>>>>>> computer. With no luck. I eventually gave up and uninstalled MSAS
>>>>>> including the files the uninstall program misses.
>>>>>>
>>>>>> I had hoped that build 509 would fix the problem. It does not.
>>>>>>
>>>>>> The initial installation and upgrade worked on the other four
>>>>>> systems.
>>>>>>
>>>>>> Is there a way of submitting a real "bug/issue report" to the
>>>>>> developers on this problem with backup data and logs?
>>>>>>
>>>>>> Bill Rankin
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Thanks. There are enough installer issues seen that I hope a thorough rev
is happening in that area of the product.

--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

"Bill-R" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Bill,
>
> My only guess is that the installation is configured not to replace
> existing files. For your info, there are at least four system32 files
> that are not uninstalled: GCCollection.dll, gcTypLibA.tbl,
> gcUnCompress.dll and hashlib.dll.
>
> I sent Jeff a more coherent version of the Issue and the errors.log file
> as you suggested.
>
> Thanks
> Bill
>
> "Bill Sanderson" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> That's useful information--thanks. Surely the installer should be able
>> to replace that file, rather than just giving up in disgust.
>>
>> I'd go ahead and send email, mentioning that you only get the error in
>> the multi-user context. I don't know the breadth of what Jeff Dillon is
>> looking for.
>>
>> --
>> FAQ for Microsoft Antispyware:
>> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>>
>> "Bill-R" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> Yes, I tried update on a partial installation and it failed with a 1904
>>> error without completing the update. Essentially it acted the same for
>>> both an install and an update. It failed to install.
>>>
>>> However, I went back and looked at the Windows\System 32 folder and the
>>> hashlib.dll file was still there from an earlier install I attempted on
>>> 20 Mar. I deleted it and tried again. This time I got a good install
>>> for one user.
>>>
>>> Now I am only getting the 101 error for the other user on the system.
>>> Isn't this a known error for computers with multiple users?
>>>
>>> Bill Rankin
>>>
>>>
>>> "Bill Sanderson" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> Bill--it isn't clear from your message whether you tried the update
>>>> route, rather than remove and reinstall.
>>>>
>>>> However, rather than mess with this further, I'd recommend the
>>>> following:
>>>>
>>>> Send an email to as-(E-Mail Removed)
>>>>
>>>> Jeff Dillon is looking into the 103/110 errors, and is interested in
>>>> the errors.log files from such systems. I'm not sure he wants those
>>>> files immediately, but if your file is small, you might zip it up and
>>>> add it to the email.
>>>>
>>>>
>>>>
>>>> --
>>>> FAQ for Microsoft Antispyware:
>>>> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>>>>
>>>> "Bill-R" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>> Bill,
>>>>>
>>>>> I do not know what you mean by verify.
>>>>>
>>>>> I tried to install build 509 and got exactly the same results I got
>>>>> with 501. The attempt to update also failed. The 101 error is not
>>>>> really the problem. The real problem is that MSAS never completes the
>>>>> install. During installation (and Update) I get the following error:
>>>>>
>>>>> Error 1904 Module C:\Windows\System 32\hashlib.dll failed to
>>>>> register.
>>>>> HResult - 2147220473.
>>>>> Contact your support personnel.
>>>>>
>>>>> That is, all install attempts fail and an attempt to use MSAS results
>>>>> in the expected 101. This was on the system with 501 uninstalled. I
>>>>> tried several accounts on this system.
>>>>>
>>>>> I am of two opinions (that means I have no real evidence):
>>>>>
>>>>> 1. that the problem involves the configuration of options of the two
>>>>> active administrator-level user accounts on this system (not counting
>>>>> the administrator account). The argument against this opinion is I
>>>>> have MSAS installed on a different system with three user accounts and
>>>>> do not have a problem.
>>>>>
>>>>> 2. that the uninstall program has not removed something that is
>>>>> blocking the reinstall. I uninstalled, rebooted, then removed all the
>>>>> MSAS files that uninstall did not remove. That did not help, but
>>>>> there may be more files I missed.
>>>>>
>>>>> Hopefully this issue is being worked,
>>>>> Bill Rankin
>>>>>
>>>>> "Bill Sanderson" <(E-Mail Removed)> wrote in message
>>>>> news:(E-Mail Removed)...
>>>>>> The known issues section of the help in build .509 has the standard
>>>>>> prescription for what do do about 101 errors.
>>>>>>
>>>>>> Can you verify that doing a change, update, still doesn't fix this on
>>>>>> this particular machine?
>>>>>>
>>>>>> The level of interaction you're looking for just isn't possible with
>>>>>> the public beta. You can bet that given the number of folks out here
>>>>>> reporting these errors, they are not having trouble replicating them.
>>>>>> --
>>>>>> FAQ for Microsoft Antispyware:
>>>>>> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>>>>>>
>>>>>> "Bill-R" <(E-Mail Removed)> wrote in message
>>>>>> news:(E-Mail Removed)...
>>>>>>> Back when MSAS first came out, I had an Error 1904 on installation
>>>>>>> and an error 101 when I attempted to run MSAS on one of the five
>>>>>>> installations that I did. Other people also had the error and there
>>>>>>> was a lot of discussion and suggestions in the newsgroup.
>>>>>>>
>>>>>>> I tried ALL the suggested solutions to get MSAS to install on the
>>>>>>> computer. With no luck. I eventually gave up and uninstalled MSAS
>>>>>>> including the files the uninstall program misses.
>>>>>>>
>>>>>>> I had hoped that build 509 would fix the problem. It does not.
>>>>>>>
>>>>>>> The initial installation and upgrade worked on the other four
>>>>>>> systems.
>>>>>>>
>>>>>>> Is there a way of submitting a real "bug/issue report" to the
>>>>>>> developers on this problem with backup data and logs?
>>>>>>>
>>>>>>> Bill Rankin
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Bill,

Build 1.0.614 does not correct the 1904 error. The message is "Error 1904
Module C:/Windows/.../hashlib.dll failed to register. HResult 2147220473"

It looks as if a rev for the installer area did not happen.

Bill-R

"Bill Sanderson" <(E-Mail Removed)> wrote in message
news:e0$(E-Mail Removed)...
> Thanks. There are enough installer issues seen that I hope a thorough rev
> is happening in that area of the product.
>
> --
> FAQ for Microsoft Antispyware:
> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>
> "Bill-R" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Bill,
>>
>> My only guess is that the installation is configured not to replace
>> existing files. For your info, there are at least four system32 files
>> that are not uninstalled: GCCollection.dll, gcTypLibA.tbl,
>> gcUnCompress.dll and hashlib.dll.
>>
>> I sent Jeff a more coherent version of the Issue and the errors.log file
>> as you suggested.
>>
>> Thanks
>> Bill
>>
>> "Bill Sanderson" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> That's useful information--thanks. Surely the installer should be able
>>> to replace that file, rather than just giving up in disgust.
>>>
>>> I'd go ahead and send email, mentioning that you only get the error in
>>> the multi-user context. I don't know the breadth of what Jeff Dillon is
>>> looking for.
>>>
>>> --
>>> FAQ for Microsoft Antispyware:
>>> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>>>
>>> "Bill-R" <(E-Mail Removed)> wrote in message
>>> news:%(E-Mail Removed)...
>>>> Yes, I tried update on a partial installation and it failed with a 1904
>>>> error without completing the update. Essentially it acted the same for
>>>> both an install and an update. It failed to install.
>>>>
>>>> However, I went back and looked at the Windows\System 32 folder and
>>>> the hashlib.dll file was still there from an earlier install I
>>>> attempted on 20 Mar. I deleted it and tried again. This time I got a
>>>> good install for one user.
>>>>
>>>> Now I am only getting the 101 error for the other user on the system.
>>>> Isn't this a known error for computers with multiple users?
>>>>
>>>> Bill Rankin
>>>>
>>>>
>>>> "Bill Sanderson" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>> Bill--it isn't clear from your message whether you tried the update
>>>>> route, rather than remove and reinstall.
>>>>>
>>>>> However, rather than mess with this further, I'd recommend the
>>>>> following:
>>>>>
>>>>> Send an email to as-(E-Mail Removed)
>>>>>
>>>>> Jeff Dillon is looking into the 103/110 errors, and is interested in
>>>>> the errors.log files from such systems. I'm not sure he wants those
>>>>> files immediately, but if your file is small, you might zip it up and
>>>>> add it to the email.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> FAQ for Microsoft Antispyware:
>>>>> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>>>>>
>>>>> "Bill-R" <(E-Mail Removed)> wrote in message
>>>>> news:(E-Mail Removed)...
>>>>>> Bill,
>>>>>>
>>>>>> I do not know what you mean by verify.
>>>>>>
>>>>>> I tried to install build 509 and got exactly the same results I got
>>>>>> with 501. The attempt to update also failed. The 101 error is not
>>>>>> really the problem. The real problem is that MSAS never completes
>>>>>> the install. During installation (and Update) I get the following
>>>>>> error:
>>>>>>
>>>>>> Error 1904 Module C:\Windows\System 32\hashlib.dll failed to
>>>>>> register.
>>>>>> HResult - 2147220473.
>>>>>> Contact your support personnel.
>>>>>>
>>>>>> That is, all install attempts fail and an attempt to use MSAS results
>>>>>> in the expected 101. This was on the system with 501 uninstalled. I
>>>>>> tried several accounts on this system.
>>>>>>
>>>>>> I am of two opinions (that means I have no real evidence):
>>>>>>
>>>>>> 1. that the problem involves the configuration of options of the two
>>>>>> active administrator-level user accounts on this system (not counting
>>>>>> the administrator account). The argument against this opinion is I
>>>>>> have MSAS installed on a different system with three user accounts
>>>>>> and do not have a problem.
>>>>>>
>>>>>> 2. that the uninstall program has not removed something that is
>>>>>> blocking the reinstall. I uninstalled, rebooted, then removed all
>>>>>> the MSAS files that uninstall did not remove. That did not help, but
>>>>>> there may be more files I missed.
>>>>>>
>>>>>> Hopefully this issue is being worked,
>>>>>> Bill Rankin
>>>>>>
>>>>>> "Bill Sanderson" <(E-Mail Removed)> wrote in message
>>>>>> news:(E-Mail Removed)...
>>>>>>> The known issues section of the help in build .509 has the standard
>>>>>>> prescription for what do do about 101 errors.
>>>>>>>
>>>>>>> Can you verify that doing a change, update, still doesn't fix this
>>>>>>> on this particular machine?
>>>>>>>
>>>>>>> The level of interaction you're looking for just isn't possible with
>>>>>>> the public beta. You can bet that given the number of folks out
>>>>>>> here reporting these errors, they are not having trouble replicating
>>>>>>> them.
>>>>>>> --
>>>>>>> FAQ for Microsoft Antispyware:
>>>>>>> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>>>>>>>
>>>>>>> "Bill-R" <(E-Mail Removed)> wrote in message
>>>>>>> news:(E-Mail Removed)...
>>>>>>>> Back when MSAS first came out, I had an Error 1904 on installation
>>>>>>>> and an error 101 when I attempted to run MSAS on one of the five
>>>>>>>> installations that I did. Other people also had the error and
>>>>>>>> there was a lot of discussion and suggestions in the newsgroup.
>>>>>>>>
>>>>>>>> I tried ALL the suggested solutions to get MSAS to install on the
>>>>>>>> computer. With no luck. I eventually gave up and uninstalled MSAS
>>>>>>>> including the files the uninstall program misses.
>>>>>>>>
>>>>>>>> I had hoped that build 509 would fix the problem. It does not.
>>>>>>>>
>>>>>>>> The initial installation and upgrade worked on the other four
>>>>>>>> systems.
>>>>>>>>
>>>>>>>> Is there a way of submitting a real "bug/issue report" to the
>>>>>>>> developers on this problem with backup data and logs?
>>>>>>>>
>>>>>>>> Bill Rankin
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>