0x80240020 FIX FOUND

This was for a Windows 2000 Pro box. I have another laptop that is able to
do the Windows Updates fine. I took that SensLogon, exported it and then
imported it into the broken computer. The fix WORKS, it is installing
everything as we speak!!!!!!!

So you just exported the whole Senslogon Folder from a working 2000 machine
and merged the file on the broken one?

I will give this a shot - unfortunatley I have installed all updates
manually so there is nothing for me to install to test this. Thanks for the
update Nocturnal!

"Nocturnal" wrote:

> This was for a Windows 2000 Pro box. I have another laptop that is able to
> do the Windows Updates fine. I took that SensLogon, exported it and then
> imported it into the broken computer. The fix WORKS, it is installing
> everything as we speak!!!!!!!
>
>
>

Correct! Let me know if this works!
"Tbenson81" <> wrote in message
news:B2D4E51D-9C1B-49A6-B123-...
> So you just exported the whole Senslogon Folder from a working 2000
> machine
> and merged the file on the broken one?
>
> I will give this a shot - unfortunatley I have installed all updates
> manually so there is nothing for me to install to test this. Thanks for
> the
> update Nocturnal!
>
> "Nocturnal" wrote:
>
>> This was for a Windows 2000 Pro box. I have another laptop that is able
>> to
>> do the Windows Updates fine. I took that SensLogon, exported it and then
>> imported it into the broken computer. The fix WORKS, it is installing
>> everything as we speak!!!!!!!
>>
>>
>>

Hi Nocturnal,

Since this error code seems to be gaining in popularity, and I like to keep
notes of fixes for popular errors, I'd like to ask you this.......

In your response to my posting in Tbenson81's "Nocturnal" thread, you stated
that you had already tried the "importing the Senslogn key fix", and that it
did not work. Was there a difference in the Senslogn key that you previously
tried that didn't work, and the one that you mention in this current thread?
The only Senslogn key information that I currently have is for WINXP, the
same information that was provided in davidrrm's post that I referenced, and
I was wondering if you had tried the WINXP-based registry key information
and if that was what did not work.

I thank you in advance for any information that you can provide, as then I
can update the notes that I saved for fixing that particular error message.



Regards,

--
Patti MacLeod
Microsoft MVP - Windows Shell/User

"Nocturnal" <> wrote in message
news:...
> This was for a Windows 2000 Pro box. I have another laptop that is able
> to do the Windows Updates fine. I took that SensLogon, exported it and
> then imported it into the broken computer. The fix WORKS, it is
> installing everything as we speak!!!!!!!
>

Yes, I actually just copied the key from an XP Home installation thus not
having it work properly. I finally got a chance to use a working Windows
2000 Pro SP4 machine and I exported the key and imported it to the bad
machine.

It worked!!
"Patti MacLeod" <> wrote in message
news:...
> Hi Nocturnal,
>
> Since this error code seems to be gaining in popularity, and I like to
> keep notes of fixes for popular errors, I'd like to ask you this.......
>
> In your response to my posting in Tbenson81's "Nocturnal" thread, you
> stated that you had already tried the "importing the Senslogn key fix",
> and that it did not work. Was there a difference in the Senslogn key that
> you previously tried that didn't work, and the one that you mention in
> this current thread? The only Senslogn key information that I currently
> have is for WINXP, the same information that was provided in davidrrm's
> post that I referenced, and I was wondering if you had tried the
> WINXP-based registry key information and if that was what did not work.
>
> I thank you in advance for any information that you can provide, as then I
> can update the notes that I saved for fixing that particular error
> message.
>
>
>
> Regards,
>
> --
> Patti MacLeod
> Microsoft MVP - Windows Shell/User
>
> "Nocturnal" <> wrote in message
> news:...
>> This was for a Windows 2000 Pro box. I have another laptop that is able
>> to do the Windows Updates fine. I took that SensLogon, exported it and
>> then imported it into the broken computer. The fix WORKS, it is
>> installing everything as we speak!!!!!!!
>>
>
>

I guess I will have to wait for another update to be released so I can test
this fix. I am a little worried because I compared all the keys in the
senslogon folder from a working 2000 machine with mine thats not working and
all the keys are exactly the same! I am still going to copy over anways but
do you think it will make a difference if all the keys are already exactly
the same?

"Nocturnal" wrote:

> Yes, I actually just copied the key from an XP Home installation thus not
> having it work properly. I finally got a chance to use a working Windows
> 2000 Pro SP4 machine and I exported the key and imported it to the bad
> machine.
>
> It worked!!
> "Patti MacLeod" <> wrote in message
> news:...
> > Hi Nocturnal,
> >
> > Since this error code seems to be gaining in popularity, and I like to
> > keep notes of fixes for popular errors, I'd like to ask you this.......
> >
> > In your response to my posting in Tbenson81's "Nocturnal" thread, you
> > stated that you had already tried the "importing the Senslogn key fix",
> > and that it did not work. Was there a difference in the Senslogn key that
> > you previously tried that didn't work, and the one that you mention in
> > this current thread? The only Senslogn key information that I currently
> > have is for WINXP, the same information that was provided in davidrrm's
> > post that I referenced, and I was wondering if you had tried the
> > WINXP-based registry key information and if that was what did not work.
> >
> > I thank you in advance for any information that you can provide, as then I
> > can update the notes that I saved for fixing that particular error
> > message.
> >
> >
> >
> > Regards,
> >
> > --
> > Patti MacLeod
> > Microsoft MVP - Windows Shell/User
> >
> > "Nocturnal" <> wrote in message
> > news:...
> >> This was for a Windows 2000 Pro box. I have another laptop that is able
> >> to do the Windows Updates fine. I took that SensLogon, exported it and
> >> then imported it into the broken computer. The fix WORKS, it is
> >> installing everything as we speak!!!!!!!
> >>
> >
> >
>
>
>

Thanks for the response, Nocturnal, as now I can update my notes about that
error :-)



Regards,

--
Patti MacLeod
Microsoft MVP - Windows Shell/User

"Nocturnal" <> wrote in message
news:eTu$...
> Yes, I actually just copied the key from an XP Home installation thus not
> having it work properly. I finally got a chance to use a working Windows
> 2000 Pro SP4 machine and I exported the key and imported it to the bad
> machine.
>
> It worked!!
> "Patti MacLeod" <> wrote in message
> news:...
> > Hi Nocturnal,
> >
> > Since this error code seems to be gaining in popularity, and I like to
> > keep notes of fixes for popular errors, I'd like to ask you this.......
> >
> > In your response to my posting in Tbenson81's "Nocturnal" thread, you
> > stated that you had already tried the "importing the Senslogn key fix",
> > and that it did not work. Was there a difference in the Senslogn key
that
> > you previously tried that didn't work, and the one that you mention in
> > this current thread? The only Senslogn key information that I currently
> > have is for WINXP, the same information that was provided in davidrrm's
> > post that I referenced, and I was wondering if you had tried the
> > WINXP-based registry key information and if that was what did not work.
> >
> > I thank you in advance for any information that you can provide, as then
I
> > can update the notes that I saved for fixing that particular error
> > message.
> >
> >
> >
> > Regards,
> >
> > --
> > Patti MacLeod
> > Microsoft MVP - Windows Shell/User
> >
> > "Nocturnal" <> wrote in message
> > news:...
> >> This was for a Windows 2000 Pro box. I have another laptop that is
able
> >> to do the Windows Updates fine. I took that SensLogon, exported it and
> >> then imported it into the broken computer. The fix WORKS, it is
> >> installing everything as we speak!!!!!!!
> >>
> >
> >
>
>

Hi Tbenson81,

If you don't want to wait for another update to be released, you can do as I
did when I wanted to test out the SensLogn thingie on my XP rigs and
uninstall one of the most recent updates via Add/Remove Programs (take note
of the KB# for the update that you're uninstalling, just in case.....) then
try installing it again via Windows Update.

When you navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\Cu rrentVersion\Winlogon is
there a Notify_Disabled subkey there? If so, delete the Notify_Disabled
subkey.



Regards,

--
Patti MacLeod
Microsoft MVP - Windows Shell/User

"Tbenson81" <> wrote in message
news:657973B3-60AF-439D-B56F-...
> I guess I will have to wait for another update to be released so I can
test
> this fix. I am a little worried because I compared all the keys in the
> senslogon folder from a working 2000 machine with mine thats not working
and
> all the keys are exactly the same! I am still going to copy over anways
but
> do you think it will make a difference if all the keys are already exactly
> the same?
>
> "Nocturnal" wrote:
>
> > Yes, I actually just copied the key from an XP Home installation thus
not
> > having it work properly. I finally got a chance to use a working
Windows
> > 2000 Pro SP4 machine and I exported the key and imported it to the bad
> > machine.
> >
> > It worked!!
> > "Patti MacLeod" <> wrote in message
> > news:...
> > > Hi Nocturnal,
> > >
> > > Since this error code seems to be gaining in popularity, and I like to
> > > keep notes of fixes for popular errors, I'd like to ask you
this.......
> > >
> > > In your response to my posting in Tbenson81's "Nocturnal" thread, you
> > > stated that you had already tried the "importing the Senslogn key
fix",
> > > and that it did not work. Was there a difference in the Senslogn key
that
> > > you previously tried that didn't work, and the one that you mention in
> > > this current thread? The only Senslogn key information that I
currently
> > > have is for WINXP, the same information that was provided in
davidrrm's
> > > post that I referenced, and I was wondering if you had tried the
> > > WINXP-based registry key information and if that was what did not
work.
> > >
> > > I thank you in advance for any information that you can provide, as
then I
> > > can update the notes that I saved for fixing that particular error
> > > message.
> > >
> > >
> > >
> > > Regards,
> > >
> > > --
> > > Patti MacLeod
> > > Microsoft MVP - Windows Shell/User
> > >
> > > "Nocturnal" <> wrote in message
> > > news:...
> > >> This was for a Windows 2000 Pro box. I have another laptop that is
able
> > >> to do the Windows Updates fine. I took that SensLogon, exported it
and
> > >> then imported it into the broken computer. The fix WORKS, it is
> > >> installing everything as we speak!!!!!!!
> > >>
> > >
> > >
> >
> >
> >

If that doesn't work try and download and install the Microsoft MSXML 3
Service Pack 4 and see if that resolves it. I spoke to someone who was
getting the dreaded error and he said that resolved it.

--
Nocturnal


"Tbenson81" <> wrote in message
news:657973B3-60AF-439D-B56F-...
>I guess I will have to wait for another update to be released so I can test
> this fix. I am a little worried because I compared all the keys in the
> senslogon folder from a working 2000 machine with mine thats not working
> and
> all the keys are exactly the same! I am still going to copy over anways
> but
> do you think it will make a difference if all the keys are already exactly
> the same?
>
> "Nocturnal" wrote:
>
>> Yes, I actually just copied the key from an XP Home installation thus not
>> having it work properly. I finally got a chance to use a working Windows
>> 2000 Pro SP4 machine and I exported the key and imported it to the bad
>> machine.
>>
>> It worked!!
>> "Patti MacLeod" <> wrote in message
>> news:...
>> > Hi Nocturnal,
>> >
>> > Since this error code seems to be gaining in popularity, and I like to
>> > keep notes of fixes for popular errors, I'd like to ask you this.......
>> >
>> > In your response to my posting in Tbenson81's "Nocturnal" thread, you
>> > stated that you had already tried the "importing the Senslogn key fix",
>> > and that it did not work. Was there a difference in the Senslogn key
>> > that
>> > you previously tried that didn't work, and the one that you mention in
>> > this current thread? The only Senslogn key information that I currently
>> > have is for WINXP, the same information that was provided in davidrrm's
>> > post that I referenced, and I was wondering if you had tried the
>> > WINXP-based registry key information and if that was what did not work.
>> >
>> > I thank you in advance for any information that you can provide, as
>> > then I
>> > can update the notes that I saved for fixing that particular error
>> > message.
>> >
>> >
>> >
>> > Regards,
>> >
>> > --
>> > Patti MacLeod
>> > Microsoft MVP - Windows Shell/User
>> >
>> > "Nocturnal" <> wrote in message
>> > news:...
>> >> This was for a Windows 2000 Pro box. I have another laptop that is
>> >> able
>> >> to do the Windows Updates fine. I took that SensLogon, exported it
>> >> and
>> >> then imported it into the broken computer. The fix WORKS, it is
>> >> installing everything as we speak!!!!!!!
>> >>
>> >
>> >
>>
>>
>>