ISusInternal::BeginFindUpdates failed, hr=8024002E

[Jones@discussions.microsoft.com VS. Jones]

WHen I run Windows Update, I get this Message (From the Windows Update Log):

ISusInternal::BeginFindUpdates failed, hr=8024002E

I beleive my "C:\WINDOWS\SoftwareDistribution" folder was tampered with, and
I have System Restore turned off for the sake of HD space; and I hadn't
planned on anyone using my computer.

[Torgeir Bakken (MVP)]

VS. Jones wrote:

Hi,

Error 0x8024002E is

SUS_E_WU_DISABLED
non managed server access is disallowed

Try this:

Start/Run ==> regedit.exe

Under the registry key
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion
\Policies\Explorer

delete the value "NoWindowsUpdate" if it exist.

Under the registry key
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion
\Policies\Windows Update

delete the value "DisableWindowsUpdateAccess" if it exist.

Under the registry key
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion
\Group Policy Objects\LocalUser\Software\Microsoft\Windows\
CurrentVersion\Policies\Windows Update

delete the value "DisableWindowsUpdateAccess" if it exist.

--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter/default.mspx

[VC# Jones]

Nope, no such luck. I think the problem is an error happening before that is
causing WU to automatically disable itself. Here is a more detailed log:
(There are no Policy settings I've set for WU)
-----------------------------------------------------
2004-10-17 13:39:32-0400 1836 e54 AU will be disabled since
DisableWindowsUpdateAccesspolicy is set and a sus server doesnt exist
2004-10-17 13:39:32-0400 1836 e54 AU is forbidden; setting AU approval type
to 'disabled'.
2004-10-17 13:39:54-0400 872 49c WU client fails
CClientCallRecorder::BeginFindUpdates from WindowsUpdate with error 0x8024002e
2004-10-17 13:39:54-0400 1836 e54 ISusInternal::BeginFindUpdates failed,
hr=8024002E
2004-10-17 13:39:54-0400 1836 e54 Unable to initiate asynchronous search,
hr=8024002E
-----------------------------------------------------

[VC# Jones]

No such luck. I believe the problem is an error occuring before that is
making WU disable itself. There are no Group Policy settings against WU in
the CURRENT_USER or LOCAL_MACHINE hives. Here is a more detailed bit of my
log:

---
2004-10-17 13:39:32-0400 1836 e54 AU will be disabled since
DisableWindowsUpdateAccesspolicy is set and a sus server doesnt exist
2004-10-17 13:39:32-0400 1836 e54 AU is forbidden; setting AU approval type
to 'disabled'.
2004-10-17 13:39:54-0400 872 49c WU client fails
CClientCallRecorder::BeginFindUpdates from WindowsUpdate with error 0x8024002e
2004-10-17 13:39:54-0400 1836 e54 ISusInternal::BeginFindUpdates failed,
hr=8024002E
2004-10-17 13:39:54-0400 1836 e54 Unable to initiate asynchronous search,
hr=8024002E

2004-10-17 13:44:28-0400 3384 154 Out of proc datastore is shutting down
2004-10-17 13:44:29-0400 3384 154 Out of proc datastore is now inactive
----

DisableWindowsUpdateAccesspolicy is not set anywhere; not the registry, nor
GP.

[Torgeir Bakken (MVP)]

VC# Jones wrote:

> Nope, no such luck. I think the problem is an error happening before that
> is causing WU to automatically disable itself. Here is a more detailed log:
> (There are no Policy settings I've set for WU)
> -----------------------------------------------------
> 2004-10-17 13:39:32-0400 1836 e54 AU will be disabled since
> DisableWindowsUpdateAccesspolicy is set and a sus server doesnt exist
> 2004-10-17 13:39:32-0400 1836 e54 AU is forbidden; setting AU
> approval type to 'disabled'.
> 2004-10-17 13:39:54-0400 872 49c WU client fails
> CClientCallRecorder::BeginFindUpdates from WindowsUpdate with error 0x8024002e
> 2004-10-17 13:39:54-0400 1836 e54 ISusInternal::BeginFindUpdates
> failed, hr=8024002E
> 2004-10-17 13:39:54-0400 1836 e54 Unable to initiate asynchronous
> search, hr=8024002E
> -----------------------------------------------------

Hi

According to PolicySettings.xls available here:

Group Policy Settings Reference for Windows XP Professional Service Pack 2
http://www.microsoft.com/downloads/details.aspx?familyid=ef3a35c0-19b9-4acc-b5be-9b7dab13108e&displaylang=en

The DisableWindowsUpdateAccess policy can be set under the two
following registry keys:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion

\Policies\WindowsUpdate

both places as registry value with name DisableWindowsUpdateAccess.

Note that one is in the HKEY_LOCAL_MACHINE branch and the other is in
HKEY_CURRENT_USER.

(the HKEY_CURRENT_USER is almost the same as in my other post, but in
my first post it was a space in the \WindowsUpdate key).

I suggest that you in regedit.exe search for DisableWindowsUpdateAccess
(Edit/Find) from the top (by setting the "cursor" at "My Computer" in
regedit).

[Torgeir Bakken (MVP)]

VC# Jones wrote:

> No such luck. I believe the problem is an error occuring before that is
> making WU disable itself. There are no Group Policy settings against WU in
> the CURRENT_USER or LOCAL_MACHINE hives. Here is a more detailed bit of my
> log:
>
> ---
> 2004-10-17 13:39:32-0400 1836 e54 AU will be disabled since
> DisableWindowsUpdateAccesspolicy is set and a sus server doesnt exist
> 2004-10-17 13:39:32-0400 1836 e54 AU is forbidden; setting AU approval
> type to 'disabled'.
> 2004-10-17 13:39:54-0400 872 49c WU client fails
> CClientCallRecorder::BeginFindUpdates from WindowsUpdate with error 0x8024002e
> 2004-10-17 13:39:54-0400 1836 e54 ISusInternal::BeginFindUpdates failed,
> hr=8024002E
> 2004-10-17 13:39:54-0400 1836 e54 Unable to initiate asynchronous search,
> hr=8024002E
> 2004-10-17 13:44:28-0400 3384 154 Out of proc datastore is shutting down
> 2004-10-17 13:44:29-0400 3384 154 Out of proc datastore is now inactive
> ----
>
> DisableWindowsUpdateAccesspolicy is not set anywhere; not the registry, nor
> GP.

Hi

Plese see my response to you in your "parallell" post.

If you do a global registry search, search for DisableWindowsUpdateAccess
and not DisableWindowsUpdateAccesspolicy...

[VC# Jones]

I fixed my problem. Attaching a debugger to IE and the activeX Control, a
file it critiacally needs,
C:\WINDOWS\SoftwareDistribution\DataStore\Logs\ebd.chk was missing. After
looking carefully at the debug output, I made a file with the information it
was looking for. Worked fine after that.

[Torgeir Bakken (MVP)]

VC# Jones wrote:

Hi

This was a strange case. Thanks for the feedback :-)