Error code 8024A008 when trying to check for updates

Anonymous
2013-10-18T15:07:22+00:00

Hey, I just upgraded my computer from windows 8 to windows 8.1. After the installation I tried to run the Windows update and after sever minutes of checking for updates the following error occurred "8024A008".  I tried several methods to solve this, first of all I restarted the computer but nothing changed, then I ran the "Windows Update Diagnostic" tool with no luck either. I'd appreciate any advice on how to solve this problem. Thanks a lot!

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2013-11-02T13:05:54+00:00

Look at the bottom of this thread:

http://social.technet.microsoft.com/Forums/windows/en-US/afc7f693-f742-402f-b513-063989b79c2f/windows-81-enterprise-windows-updates

http://gallery.technet.microsoft.com/scriptcenter/2d191bcd-3308-4edd-9de2-88dff796b0bc

1.)  Copy the whole module folder (after unzipping) to %WINDIR%\System32\WindowsPowerShell\v1.0\Modules

2.) Start up PowerShell ISE as admin from admin tools

3.) Set-ExecutionPolicy RemoteSigned

4.) Import-Module PSWindowsUpdate

5.) Get-WUInstall

6.) The rest should be automated with some prompts

After Reboot

follow the instructions to run the PowerShell script and it will force a Windows Update. Make sure you follow the instructions in the second relevant post:

This is a great solution! I just tested it and I only had one small issue. "Set-ExecutionPolicy RemoteSigned" was not sufficient in my case because the files were flagged as coming from another computer and were blocked when trying to import the module. Simple solution: copy the zip file locally and unblock the zip file BEFORE extracting the files, otherwise you have to unblock the files one by one. You can do that in the properties dialog of the file. You can also use "Set-ExecutionPolicy Unrestricted" but I do not suggest doing this.

If you want to execute without prompts, maybe to automate the process, you can execute:

Get-WUInstall -AcceptAll -IgnoreReboot

So great work by these Guys and a big thumbs down to Microsoft. I have run it successfully and it download 39 updates (including Office).

Many thanks to HenkelsGuy5

Was this answer helpful?

100+ people found this answer helpful.
0 comments

89 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2013-12-02T07:05:58+00:00

    Changes back to 1.

    Same as before.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-12-02T06:13:47+00:00

    Hey,

    Can you check the value of the Following key

    IsOOBEInProgress at the registry Location :

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update

    If the Value is 1 kindly change the value to 0, and restart the update Service and confirm if the value has remained the same.

    If it is, kindly check for updates.

    Thanks,

    Sam

    Exactly the same here, the value is 1, if I change it to 0, it changes after restart back to 1.

    No change in the update loop as-well.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-11-30T06:15:51+00:00

    Hey,

    Can you check the value of the Following key

    IsOOBEInProgress at the registry Location :

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update

    If the Value is 1 kindly change the value to 0, and restart the update Service and confirm if the value has remained the same.

    If it is, kindly check for updates.

    Thanks,

    Sam

    I tried this, it doesn't work - this key simply represents the state of the last OOBE check.

    I set it to zero as instructed above, and furthermore removed permissions from the registry key so it was read only.

    I then ran windows update; the logging indicated that - even though windows update could not write to this key, it still detected OOBE was running.

    So, the problem is not the value of this key - rather the value of this key indicates that the check for OOBE is returning true (and this key is then updated)...

    First there is the message in WindowsUpdate.log "OOBE is in progress, so cannot perform Accelerated Install" followed a couple of seconds late by "OOBE is still in progress. AU deferring detection", followed a few milliseconds later with "WARNING: RegSetDwordValue failed for IsOOBEInProgress, hr is 80070005" (which is permission denied).

    After this test (with permissions removed), IsOOBEInProgress was still 0, but windowsupdate.log still was reporting OOBE was in progress.

    In summary, this key doesn't specify that OOBE is in progress, but simply records if auto-update found that it was in progress last time it ran.

    So, in this test, auto-updates could not update the registry key, but it still failed.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-11-30T05:36:35+00:00

    Sam:  I also tried:

    1. Stopping the Windows Update service.
    2. Changing the IsOOBEInProgress key from 1 to 0.
    3. Restarting the Windows Update service.
    4. Manually checking for updates in the Control Panel.

    The check for updates still hangs.  And when I refreshed the RegEdit window, the IsOOBEInProgress key was back at 1.

    Was this answer helpful?

    0 comments