Windows 8.1 Enterprise Windows Updates
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 HanModerator
Monday, September 30, 2013 12:35 PM
potential issue
September 26th, 2013 3:43pm
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
October 8th, 2013 1:39pm
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
October 29th, 2013 6:47pm
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
December 17th, 2013 4:46pm
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
December 17th, 2013 8:14pm
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.
March 11th, 2014 9:09pm
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.
-
Edited by
arnoldjonker
Thursday, May 22, 2014 7:31 AM
May 21st, 2014 12:59pm
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.
June 5th, 2014 4:36am
Thanks man,
this Module realy saved my day :D
June 16th, 2014 5:56pm
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.
July 8th, 2014 6:11am
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.
July 17th, 2014 8:46pm
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
July 31st, 2014 12:20pm
thanks it gone with Windows Server 2012 r2 Too
August 3rd, 2014 12:17pm
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
You should try running Windows PowerShell ISE from administrative tools, not the (x86) one.
October 27th, 2014 5:16pm
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.
Why?
If you're going to advise people not to do something a certain way, you need to elaborate as to why it's a bad idea.
"I just wouldn't do it that way..." doesn't really help anybody.
November 19th, 2014 9:42am
Hello everyone, I did the Power Shell process and works it fine, Windows get all the last updates.
But after I extracted the updated image install.wim (with dism) and put inside the .iso that I have the error, right after the wizard copy the installation files, on update process:
"Windows could not update registry data in the installation."
I'm trying to install on a Virtual Machine VirtualBOX, I use the WSIM and NTLite software to generate the autounattend file but both return that error. Also I tried without a autounattend file and I keep getting the error, someone knows what could
it be?
January 18th, 2015 11:17am
hihihi .... microsoft... yes i did step in shame s*** ... have installed all the software i needed in audit mode...
have installed Windows8.1-KB3000850-x64.msu too, before making snapshot... (stupid me...)
Admin account cannot be logged in no more cause... who knows why :)...
What is the right way to install damned updates to the image using windows update and keep in audit mode so i can build install dvd with all the software i need and the updates
Or... How do i get ti install updates in offline mode (with a way to check with WU for the needed updates, both windows and rest of Microsoft), i do not care since i can install the software in audit mode
April 9th, 2015 1:48pm