8024a008 ошибка обновления windows server 2012 r2

Well, Windows Updates deliver crucial updates for the services. Windows Updates not only help us to keep the Windows along with the latest patches for security along with newer versions of the Windows components. However, also help keep the firmware, software, hardware, etc in the computer up to date. If the Windows Updates effect through any kind of errors, it will then affect the entire Windows platform. And cause Windows, Internet browsers, and any applications install on the PC to malfunction. Net updates and ALSO new versions are too delivered via these Updates. Office 2016, Office 2013, Office 2010, Office 2007, Office 365 are also updated through Windows Updates. In this article, we are going to talk about How to Fix Windows Update Error Code 8024a008. Let’s begin!

Windows could not search for new updates

There was a problem checking for updates.

Error Code 8024A008

Windows Update ran into a problem.

As you guys can see, it was actually the error code 8024A008 that entertained us. But, you might get a different error code along with this same issue.

• First of all, you have to download the Windows Update PowerShell Module.

The module is actually in ZIP format, so you guys can easily extract it via decompression software. Such as 7-zip so that you guys will get the PSWindowsUpdate folder.

• Now press Windows+ R and type this into the Run dialog box and tap Enter key and click on OK:

%WINDIR%\System32\WindowsPowerShell\v1.0\Modules

• Then copy the extracted ZIP folder named as PSWindowsUpdate from the first step to Modules folder so opened from the 2nd step:
• Now, head to Start Screen, press Windows + I, then tap on Tiles and set the slider to Yes for Show administrative tools. From administrative tools so pinned in order to Start Screen now, you have to open the administrative Windows PowerShell ISE. And then execute the following commands one by one after tapping Enter key:

Set-ExecutionPolicy RemoteSigned

Import-Module PSWindowsUpdate

Get-WUInstall

regsvr32 c:\windows\system32\vbscript.dll /s
regsvr32 c:\windows\system32\mshtml.dll /s
regsvr32 c:\windows\system32\msjava.dll /s
regsvr32 c:\windows\system32\jscript.dll /s
regsvr32 c:\windows\system32\msxml.dll /s
regsvr32 c:\windows\system32\actxprxy.dll /s
regsvr32 c:\windows\system32\shdocvw.dll /s
regsvr32 wuapi.dll /s
regsvr32 wuaueng1.dll /s
regsvr32 wuaueng.dll /s
regsvr32 wucltui.dll /s
regsvr32 wups2.dll /s
regsvr32 wups.dll /s
regsvr32 wuweb.dll /s
regsvr32 Softpub.dll /s
regsvr32 Mssip32.dll /s
regsvr32 Initpki.dll /s
regsvr32 softpub.dll /s
regsvr32 wintrust.dll /s
regsvr32 initpki.dll /s
regsvr32 dssenh.dll /s
regsvr32 rsaenh.dll /s
regsvr32 gpkcsp.dll /s
regsvr32 sccbase.dll /s
regsvr32 slbcsp.dll /s
regsvr32 cryptdlg.dll /s
regsvr32 Urlmon.dll /s
regsvr32 Shdocvw.dll /s
regsvr32 Msjava.dll /s
regsvr32 Actxprxy.dll /s
regsvr32 Oleaut32.dll /s
regsvr32 Mshtml.dll /s
regsvr32 msxml.dll /s
regsvr32 msxml2.dll /s
regsvr32 msxml3.dll /s
regsvr32 Browseui.dll /s
regsvr32 shell32.dll /s
regsvr32 wuapi.dll /s
regsvr32 wuaueng.dll /s
regsvr32 wuaueng1.dll /s
regsvr32 wucltui.dll /s
regsvr32 wups.dll /s
regsvr32 wuweb.dll /s
regsvr32 jscript.dll /s
regsvr32 atl.dll /s
regsvr32 Mssip32.dll /s

• Now, just tap on the File menu and choose the Save as an option.
• Then on the next screen, select a suitable location and then save the file as WindowsUpdate.bat. By the way, you guys can also change the file name as per your need. However, the extension of the file name must be a batch file actually.
• When you guys create the batch file, then double-tap on it. And whenever UAC prompts on the screen, then tap on the Yes button.
• Now after that, reboot your device and when it starts up, then check if the error code 8024A000 still persists or not. If it is, then just move down to the next effective workaround actually.

Conclusion

Alright, That was all Folks! I hope you guys like this “8024a008” article and also find it helpful to you. Give us your feedback on it. Also if you guys have further queries and issues related to this article. Then let us know in the comments section below. We will get back to you shortly.

Have a Great Day!

Also See: How to View Print History on Windows – Tutorial

Not long after we started adding Windows Server 2012R2 servers earlier this year we noticed a problem with Windows Update. Our Server Group policy settings were set to automatically download updates, but we would have to manually install these updates to plan for downtime. In a 24-hour operation like a jail, we can’t necessarily schedule a time to boot users off of vital servers for restarts.

What I started to see was that on some of our servers the updates were not making it from our Windows Server Update Services server to the clients (ironically, our new WSUS server was one of these that wouldn’t get updates). In fact, these servers had never updated. After investigating I determined that the servers that were affected had one thing in common; they were never updated before they had a WSUS policy applied to them.

Digging for information I found a blog that highlights the issue. When you install a new Server, or a new Desktop OS for that matter, Windows runs through the Out-Of-Box-Experience, or OOBE. You’re familiar with this even if you never knew what it was called; it’s the part of the installation where Windows asks what you want your user and computer name to be, where you choose how you will handle updates, and where you choose your time zone.

Server 2012 has a short OOBE with a hidden step; run Windows Update. The OOBE will not end until Windows connects to Windows Update. And according to the above blog this issue also affects Windows 8.1.

You will know you have this issue if you navigate to C:/Windows/WindowsUpdate.log, the Windows Update log, and you find the following:
Windows OOBE is still in progress. AU deferring detection
WARNING: BeginDetection failed, hr:0x8024a008
All AU searches complete.
# WARNING: Failed to find updates with error code 8024a008
AU setting next detection timeout to 2014-10-22 12:44:24
OOBE is in progress, so cannot perform Accelerated Install

So how do you fix this? The blog quoted above shows a PowerShell module that can be downloaded and used to access Windows Update (As an aside, how is there not an official Microsoft PowerShell built-in module for Windows Update?). This works well for updating the machine but it still doesn’t solve the actual problem; it doesn’t manage to force an end to the OOBE. And while updating is definitely a good thing, I also want to return the system to its full functionality so that I don’t have to remember that these are the three machines that need to be update in some  special way.

After a few months of searching I finally found the answer, accidentally, as it were. I was examining the registry values for Windows Update in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update when I came across this:

IsOOBEInProgress : 1
PSPath           : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Win
dowsUpdate\Auto Update

I few tests later and I determined that this registry d-word value, when set to 1, means that the Out Of Box Experience is currently running. When set to 0, Windows Update thinks that the OOBE is completed. Sure enough, this change fixed all of the issues we had with server updates.

So to make this change yourself, open a PowerShell prompt as an administrator (Right-click and select “Run As Administrator”) and type the following command:

set-itemproperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\' -Name IsOOBEInProgress -Value 0

After a restart, you should be able to run Windows Update without any problems.