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
    2014-02-03T07:24:02+00:00

    This issue can be resolved by re-running OOBE with sysprep then repairing Windows Update using the Fix-It utility.

    1. Open a command prompt window and run the following command:

    %systemroot%\System32\Sysprep\sysprep.exe /oobe

    If the command is successful your computer will shut down when done, goto step 2. If the command fails, proceed to step 1b.

    1b. Open regedit and navigate to:

    HKEY_LOCAL_MACHINE\SYSTEM\Setup

    If there is a dword named "Upgrade" delete it. Note, there is also a subkey named "Upgrade" DO NOT delete it. In my case the "RollbackActive" dword was set to "1" so I changed it to "0". Reboot and try step 1 again.

    2. Startup your computer and complete OOBE. Unlike the upgrade OOBE you will not be able to select an existing user account to use. Instead, create a throwaway account you can delete later.

    3. Once you reach the desktop, navigate to:

    Control Panel\All Control Panel Items\Troubleshooting\All Categories

    Right click on "Windows Update" and select "Run as administrator". Reboot when the Fix-It is finished.

    Windows Update should now function normally.

    Went thru step 1b, completed the OOBE with creating user and Error message, that it could not complete installation. OK button to reboot. After reboot, Windows Update still checking endlessly.

    Any more ideas?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-02-03T07:05:13+00:00

    Tried it step by step, with all the reboots.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-02-03T06:58:00+00:00

    Check the referenced log file. Look for any line that begins with an error message or warning:

    2014-02-01 13:52:04, Error      [0x0f0036] SYSPRP spopk.dll:: Sysprep will not run on an upgraded OS. You can only run Sysprep on a custom (clean) install version of Windows.

    Feel free to post the log if you need further help.

    Hello, here is the log file - I am getting the same error, as mentioned above(screenshot)

    2014-02-03 07:53:06, Info                  SYSPRP ========================================================

    2014-02-03 07:53:06, Info                  SYSPRP ===          Beginning of a new sysprep run          ===

    2014-02-03 07:53:06, Info                  SYSPRP ========================================================

    2014-02-03 07:53:06, Info       [0x0f004d] SYSPRP The time is now 2014-02-03 07:53:06

    2014-02-03 07:53:06, Info       [0x0f004e] SYSPRP Initialized SysPrep log at C:\WINDOWS\System32\Sysprep\Panther

    2014-02-03 07:53:06, Info       [0x0f0054] SYSPRP ValidateUser:User has required privileges to sysprep machine

    2014-02-03 07:53:06, Info       [0x0f007c] SYSPRP FCreateTagFile:Successfully deleted tag file C:\WINDOWS\System32\Sysprep\Sysprep_succeeded.tag

    2014-02-03 07:53:06, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'OOBE'

    2014-02-03 07:53:06, Info       [0x0f00d7] SYSPRP WinMain:Pre-validing 'cleanup' internal providers.

    2014-02-03 07:53:06, Info                  SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 3

    2014-02-03 07:53:06, Info       [0x0f00ba] SYSPRP SysprepSession::CreateSession: Successfully created instance with mount path C:, action file C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml, and mode <null>

    2014-02-03 07:53:06, Info                  SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml

    2014-02-03 07:53:06, Info                  SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep

    2014-02-03 07:53:06, Info                  SYSPRP ActionPlatform::GetValue: Getting value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep

    2014-02-03 07:53:06, Warning               SYSPRP ActionPlatform::GetValue: Error from RegQueryValueEx on value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep; dwRet = 0x2

    2014-02-03 07:53:06, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>

    2014-02-03 07:53:06, Info                  SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

    2014-02-03 07:53:06, Info                  SYSPRP ActionPlatform::GetValue: Getting value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

    2014-02-03 07:53:06, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64

    2014-02-03 07:53:06, Info       [0x0f0080] SYSPRP ActionPlatform::LaunchModule: Found 'Sysprep_Clean_Validate_Opk' in C:\Windows\System32\spopk.dll; executing it

    2014-02-03 07:53:06, Error      [0x0f0036] SYSPRP spopk.dll:: Sysprep will not run on an upgraded OS. You can only run Sysprep on a custom (clean) install version of Windows.

    2014-02-03 07:53:06, Error      [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll; dwRet = 0x139f

    2014-02-03 07:53:06, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml; dwRet = 0x139f

    2014-02-03 07:53:06, Error                 SYSPRP RunPlatformActions:Failed while validating SysprepSession actions; dwRet = 0x139f

    2014-02-03 07:53:06, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x139f

    2014-02-03 07:53:06, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep cleanup internal providers; hr = 0x8007139f

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-02-02T20:39:35+00:00

    Check the referenced log file. Look for any line that begins with an error message or warning:

    2014-02-01 13:52:04, Error      [0x0f0036] SYSPRP spopk.dll:: Sysprep will not run on an upgraded OS. You can only run Sysprep on a custom (clean) install version of Windows.

    Feel free to post the log if you need further help.

    Was this answer helpful?

    0 comments