0x8024001E after many hours of parsing needed updates

[becomingcloser]

Hello!

I am troubleshooting updates on a Server 2008 (not R2) machine. I have turned off automatic updates and am trying to run the client portion of the offline updater. It will sit at "Listing ids of missing updates" for many hours, finally erroring with 0x8024001E. Any direction would be greatly appreciated.

Thanks,
Mike

[Dalai]

According to the Windows Update error code list the code means

0x8024001E WU_E_SERVICE_STOP Operation did not complete because the service or system was being shut down.

I'd start by finding out what causes the service to be stopped; might be some other (background) program running. A look into C:\Windows\WindowsUpdate.log might have some details about that.

Or it might have something to do with memory available. Since Windows Server 2008 is NT 6.0 it shares the same code with Vista which doesn't have an up-to-date Update Agent - this thing eats memory which might cause the system to begin killing processes/services. How much RAM does your system have?

Regards
Dalai

[becomingcloser]

I am taking a look into the windowsupdate.log file and will report back. This system has 8GB of memory and is currently sitting at 5GB used.

[becomingcloser]

The error mentioned seems to always come immediately after this:

WARNING: WU client failed Searching for update with error 0x8024000b
or
WARNING: Failed to filter search results, error = 0x8024000B

The server has 8GB of RAM and is currently using 5GB.

[aker]

32bit or 64bit?

(w2k8 is the last server version with x86)

[becomingcloser]

64 bit. Thanks!

[Dalai]

Code 0x8024000B is

WU_E_CALL_CANCELLED Operation was cancelled.

, which is quite logical when the service gets stopped. You might want to check the lines before this error code.

Does the 5 GB used RAM include the Windows Update Service? If not, it's quite likely that lack of free RAM is the culprit.

Regards
Dalai

[becomingcloser]

It does include the svchost which includes Windows Update.

WSUS Offline tool still checking after being started 12 hours ago.

[aker]

MS currently only fixes this issue for Windows 7, 8.1 and 10. I've found a working fix for Nov 2016. I'll update it with the most recent updates and post it here.

[becomingcloser]

Thanks, aker. I'll keep my eyes peeled for your reply. I appreciate the help this forum has provided.