Hi,

I was just about to create my custom image, so booted Windows 8.1 Enterprise into Audit Mode (CTRL+SHIFT+F3) but now it never does any Windows Updates.

WindowsUpdate.log shows the following:

Windows OOBE is still in progress.  AU deferring detection.

#WARNING: Failed to find updates with error code 8024a008

OOBE is in progress, so cannot perform Accelerated Install.

Help please.  Windows 8 allowed me to do this..

• Changed type Niki HanMicrosoft contingent staff, Moderator Monday, September 30, 2013 12:35 PM potential issue

That is not true. I have 8.1 running at home and I am getting updates there.

The issue described by the parent is specific to running Windows Update while in Audit Mode. I am experiencing the same problem.

I have the same problem as I posted about it here 2 days ago. http://social.technet.microsoft.com/Forums/en-US/80ea7f39-c8f4-4547-940a-f87a1790f4ed/windows-81-wont-get-updates-in-audit-mode

I have this problem when using core and pro versions of windows 8.1 as well. The update screen just shows "Checking for updates..." forever. If I continue through OOBE and create a user account and let windows start normally then updates will work fine.

I have opened an MSDN Support issue on this.  Will keep you posted.

I wouldn't recommend that workaround myself. Instead I'd recommend Install Windows 8.1, go through OOBE, create the temp user, install updates... BUT.

Instead go into the View Installed Updates, make note of all of them. Download those updates from the Microsoft Catalog.

Then reinstall Windows to Audit Mode, sysprep and capture image. Then inject those updates with DISM you downloaded from the catalog into your image.

I wouldn't recommend that workaround myself. Instead I'd recommend Install Windows 8.1, go through OOBE, create the temp user, install updates... BUT.

Instead go into the View Installed Updates, make note of all of them. Download those updates from the Microsoft Catalog.

Then reinstall Windows to Audit Mode, sysprep and capture image. Then inject those updates with DISM you downloaded from the catalog into your image.

On the plus side, this means that OEMs can better ensure that only the updates they want on their machines get installed in the factory floor image, even if they enable automatic updating in the image.

I wouldn't recommend that workaround myself. Instead I'd recommend Install Windows 8.1, go through OOBE, create the temp user, install updates... BUT.

Instead go into the View Installed Updates, make note of all of them. Download those updates from the Microsoft Catalog.

Then reinstall Windows to Audit Mode, sysprep and capture image. Then inject those updates with DISM you downloaded from the catalog into your image.

Hmm, well this article from Microsoft regarding creating a Windows 7 image seems to think its the way to do it.

http://technet.microsoft.com/en-us/library/ee523217(v=ws.10).aspx

I've tested and deployed my new 8.1 image using this method and it worked perfectly.

• Edited by alanplum Tuesday, October 08, 2013 1:41 PM

I was under the impression that we are no longer able to inject updates via DISM (since Windows 8's release). Has this since changed?

Hmm, well this article from Microsoft regarding creating a Windows 7 image seems to think its the way to do it.

http://technet.microsoft.com/en-us/library/ee523217(v=ws.10).aspx

I've tested and deployed my new 8.1 image using this method and it worked perfectly.

Microsoft has not released any Windows 8.1 system updates as of this date.  They will become available after General Availability (GA) of Windows 8.1 (after O

Any solution?

I upgraded my Windows 8 yo 8.1 from store and im getting the same message in the Windows Update log file

Isianfas,

This is completely different.  If you have "upgraded" from 8 to 8.1 then all should be good.

The only possible reason you could get this is if your machine has dropped back into OOBE mode after your upgrade, which I find hard to believe, as this thread is about admin mode.

Isianfas,

This is completely different.  If you have "upgraded" from 8 to 8.1 then all should be good.

The only possible reason you could get this is if your machine has dropped back into OOBE mode after your upgrade, which I find hard to believe, as this thread is about admin mode.

I think my machine has dropped back to OOBE.

Im not the only one with this issue after upgrading

http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-code-8024a008-when-trying-to-check-for/c1cc5a2f-9821-4072-bfcc-3b41c1717f6d?rtAction=1382172522816

The change is an absolute disaster!

After completing OOBE (creating local user `user` ) and installing updates, we reboot into Audit mode, delete the user account using windows UI app, 'cause standard computer management won't allow to edit users anymore, and perform sysprep /generalize /shutdown.

Guess what...USER PERSISTS and after deployment you will have  a user `user` sitting there.

Whoever decided to make that change should get -100500 to their karma

Hello,

I think I may have found a easy workaround.

The old System Builder Bypass Tool seems to work fine in Windows 8.1!

You can download it from here;

http://www.microsoft.com/oem/en-gb/installation/downloads/Pages/system_builder_bypass.aspx#fbid=0en0pM4ljU_

It was originally designed for bypassing the Windows Genuine Advantage in XP so you could still do updates before activation.

PLEASE NOTE:
This software was not designed for this purpose, I have only run some initial tests confirm that it works. There may be unknown future issues.

I have been fighting the same issue as everyone else.

I believe I found a work around that seems to be working for me. I installed a PowerShell module that does 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

• Edited by HenkelsGuy5 Tuesday, October 29, 2013 7:46 PM Spelling

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

Let's hope nobody at Microsoft decides to block this solution on some falacious statement!

Many thanks to HenkelsGuy5.

Great work - a manual update of 39 downloads (including Office).

Many thanks to HenkelsGuy5

I found this 2 weeks before.

This is a little too complicated and does not fix the issue. It's easier to use wuinstall.exe /scan /install rather than this powershell thing.

But still no fix to this problem, so we can use windows updates normally.

• Edited by mtarggart 19 hours 0 minutes ago

This does help!!

I'm new to PowerShell, so it took me a few minutes to figure out where to type the commands mentioned, but once I figured it out, it worked like a charm.

Is there a way to see the description of the update before accepting or rejecting it, besides looking it up? I'd rather not look up 30-100+ updates the next time I go to update my base image. I'll continue to look and see if I can figure this out more.

This does help!!

I'm new to PowerShell, so it took me a few minutes to figure out where to type the commands mentioned, but once I figured it out, it worked like a charm.

Is there a way to see the description of the update before accepting or rejecting it, besides looking it up? I'd rather not look up 30-100+ updates the next time I go to update my base image. I'll continue to look and see if I can figure this out more.

Sure!

Get-WUList

• Edited by Louis Phil 15 hours 32 minutes ago

Thanks, it did helped me to install the updates.

But Windows Update still hangs forever on "Checking for updates"...