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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-01-18T01:44:36+00:00

    Found this article which seems to point the finger at OOBE too:

    https://dannymccaslin.wordpress.com/2015/09/25/oobe-problems-with-windows-server-2012r2-updates/

    Basically check the following key:

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

    Locate the "IsOOBEInProgress" DWORD entry and if it's a 1 change it to a 0

    However, I found that the registry change would revert as soon as I clicked "Check for Updates" in Control panel

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-11-05T10:58:44+00:00

    Running sysprep.exe /OOBE reboot was the only way I was able to fix this issue on already deployed Windows 2012 R2 servers.

    Each Windows 2012 R2 server I rolled out via SCCM was having this issue. At the end I was able to pin point this issue to the VMware Tools package which I deployed during the Task Sequence.

    I used the following command line to install the WMware tools package:

    setup64.exe /S /v/qn

    When I changed the command line as follows the problem was solved:

    setup64.exe /S /v"/qn REBOOT=ReallySuppress"

    So this tells me that any installation package which is not closed properly could leave Windows in the OOBE state.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-09-13T14:48:13+00:00

    Круто !!!! Спасибо - это сработало !

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-09-05T15:19:52+00:00

    Well, you can do all that amazing Powershell, bluescreen, filedownload, diagnostic tool stuff.   And reboot your computer a bunch of times. 

    Or you can restart Windows Update in Services and try again.   Not as much fun, but quicker.

    Was this answer helpful?

    0 comments