none
Windows 8.1 Enterprise Windows Updates

    General discussion

  • 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..

    Thursday, September 26, 2013 3:43 PM

All replies

  • From what I understand, Updates for 8.1 won't become available (on Windows Update) until the OS hits General Availability.
    Friday, September 27, 2013 2:59 PM
  • 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.

    Friday, September 27, 2013 6:00 PM
  • I asked Microsoft and during OOBE WU is not working. But in audit mode it should work. Phone the MSDN/Technet Support about this.

    "A programmer is just a tool which converts caffeine into code"

    Friday, September 27, 2013 7:17 PM
  • 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.

    Friday, September 27, 2013 10:24 PM
  • I have opened an MSDN Support issue on this.  Will keep you posted.
    Tuesday, October 01, 2013 9:17 AM
  • I have opened an MSDN Support issue on this.  Will keep you posted.

    ok, thanks :)

    "A programmer is just a tool which converts caffeine into code"

    Tuesday, October 01, 2013 5:25 PM
  • OMG. You are not going to believe the response from Microsoft!!!!!!! See below. Thank You for sharing the logs. I was able to reproduce the issue in my virtual environment. To understand more about this behavior, I engaged the Product Group and I have been informed that this behavior is By Design. WU uses the OOBEComplete() Windows API call to determine whether OOBE is in progress or not, and if so, it will not perform automatic or UI update searches. HRESULT code 0x8024a008 is the WU error code WU_E_AU_OOBE_IN_PROGRESS. WU automatic and UI updates won’t run while Setup reports that OOBE is still in progress. This is to prevent automatic updates from causing a system reboot during OOBE, which is – needless to say – a Very Bad Thing. This problem has always existed. Unfortunately, when the computer is in Sysprep audit mode, Setup will report to WU that OOBE is in progress even though it might not actually be so. This is the reason that updates from WU UIs are blocked in audit mode. 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.
    Wednesday, October 02, 2013 8:43 PM
  • Needless to say I have replied in 2 forms. 1. Why did Windows 8.0 allow it 2. Your going to have a lot of unhappy customers
    Wednesday, October 02, 2013 8:44 PM
  • Unfortunately, when the computer is in Sysprep audit mode, Setup will report to WU that OOBE is in progress even though it might not actually be so. This is the reason that updates from WU UIs are blocked in audit mode. 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.
    ok, this is the reason. So this was changed between 8 and 8.1.

    "A programmer is just a tool which converts caffeine into code"

    Thursday, October 03, 2013 6:01 AM
  • Well, Microsoft have closed the case now, adamant it's by design.

    I've found a workaround though.

    Install 8.1 and GO THROUGH OOBE, and create a temp user.  This will allow you to do all the Windows Updates and install your software.  When done, run sysprep /audit.

    This will boot the machine back to audit mode (Where WU wont work, but it doesn't matter as we did them above).  Delete the temporary user above, and set up the image as you like before sysprep /generalize /oobe

    Monday, October 07, 2013 2:56 PM
  • 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.

    Monday, October 07, 2013 4:29 PM
  • 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 was under the impression that we are no longer able to inject updates via DISM (since Windows 8's release). Has this since changed?
    Tuesday, October 08, 2013 7:47 AM
  • 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.
    How can we better ensure that only the updates we want are on there if we can't get any updates at all during Audit mode?
    Tuesday, October 08, 2013 7:51 AM
  • 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
    Tuesday, October 08, 2013 1:39 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?
    You can inject updates into Windows 8 no problem with Win7's AIK or Win8 RTM ADK. However if you want to service Windows 8.1, you will need the updated ADK.
    Tuesday, October 08, 2013 3:57 PM
  • 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.


    Those instructions are for VLK media. It also specifically mentions the guide is for SMBs inexperienced with Windows Deployment. While the guide may work for you, it presents a lot of uneccesary work to me. :)
    Tuesday, October 08, 2013 4:02 PM
  • 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 Oct. 18th).

    Carey Frisch

    Sunday, October 13, 2013 4:12 PM
  • 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 Oct. 18th).

    Carey Frisch

    Carey,

    I don't know where you get your information from, but you are just plain wrong.

    If you install Windows 8.1 fresh and go to Windows Update, you will find that there are a few available and have been since 8.1 RTM'd.

    Try it if you don't believe me.

    AFAIK, there was a flash player update, and a few others.

    Tuesday, October 15, 2013 8:58 AM
  • Any solution?

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

    Friday, October 18, 2013 5:28 PM
  • 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.

    Friday, October 18, 2013 11:12 PM
  • 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

    Saturday, October 19, 2013 8:57 AM
  • 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

    Friday, October 25, 2013 5:00 PM
  • 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.

    Tuesday, October 29, 2013 1:56 AM
  • 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

    Hope this helps.
    • Edited by HenkelsGuy5 Tuesday, October 29, 2013 7:46 PM Spelling
    Tuesday, October 29, 2013 6:47 PM
  • 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.

    Wednesday, October 30, 2013 1:20 PM
  • Great work - a manual update of 39 downloads (including Office).

    Many thanks to HenkelsGuy5

    Saturday, November 02, 2013 1:07 PM
  • I had to put the module in SysWow64 instead of System32 for this to work.
    Friday, November 08, 2013 2:34 PM
  • awesome! works like a charm... or actually better than the charms lol
    Wednesday, December 04, 2013 8:58 PM
  • 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.

    Friday, December 13, 2013 4:58 AM
  • I tried the System Builder Bypass Tool and it does not work in Audit Mode. It gives an error that says "Sbbypass.exe can only be used during the Factory mode of the Windows preinstallation process."

    • Edited by mtarggart Wednesday, December 18, 2013 5:48 PM
    Tuesday, December 17, 2013 4:46 PM
  • 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.

    Tuesday, December 17, 2013 5:38 PM
  • 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 Tuesday, December 17, 2013 8:15 PM
    Tuesday, December 17, 2013 8:14 PM
  • Thanks, it did helped me to install the updates.

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

    Wednesday, December 18, 2013 4:14 AM
  • One option to workaround the problem is to use an offline updater

    http://download.wsusoffline.net/

    Monday, February 03, 2014 6:56 AM
  • does not work for everyone, use Set-ExecutionPolicy Unrestricted

    Friday, March 07, 2014 9:24 PM
  • We were recently hit with this issue... we found that one of the programs in our task sequence was not exiting with a response code that SCCM was expecting and therefore even though the computer imaged successfully and the software worked, there were registry settings set to indicate we were still in audit mode.

    In our case, it was K-Lite codec pack / media player.  We removed it from the task sequence and added VLC.  Windows Updates worked correctly in every image after.

    Tuesday, March 11, 2014 9:09 PM
  • Thanks! Works perfectly now.

    Just repeat the steps 2,4 and 5 in order to get all updates.

    Run Sysprep
    And made an image.

    Thanks a million.

    BUT.... now 1 day later it seems that the image wont deploy on new machines. It says that Windows Installation has failed. While the boot logo appears on my screen.

    Tired of reinstalling Windows over and over again to get this fixed.

    Wednesday, May 21, 2014 12:59 PM
  • I tried it works just fine...install, create "Temp" user, choose home network, do updates and global (all users)machine program installations. Sysprep /audit, reboot into bultin disabled administrator account, go to user profiles and delete "Temp", go to computer management /users and delete the "Temp" user. Now sysprep /oobe /generalize /shutdown. Now boot off line and capture the partition for a distribution share. If on a large network you will need a vlk/kms server on your network. Or you can push it locally to each machine one at a time if small business network.
    Thursday, June 05, 2014 4:36 AM
  • Thanks man,

    this Module realy saved my day :D

    Monday, June 16, 2014 5:56 PM
  • Verified, this solution works!!! Be sure to go into user profiles and delete the orphaned profile for that temp user created after deleting it in local users and groups.
    Tuesday, July 08, 2014 6:11 AM
  • But this will cause any unattend using "Copy Profile" to fail.  Copy profile requires only one admin account guid in the registry or it fails, not knowing which account to use.  So Microsoft knowingly destroyed part of it's WAIK feature set in 8.1 is what I'm reading.
    Thursday, July 17, 2014 8:46 PM
  • I had to put the module in SysWow64 instead of System32 for this to work.

    Me too, Get-WUInstall didn't returned me any results while in the System32 folder. Running it now inside the SysWow64 folder.

    Machine: Windows 8.1 Pro

    Thursday, July 31, 2014 12:20 PM