none
Deleted RRS feed

Alle Antworten

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

    Freitag, 27. September 2013 18:00
  • 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"

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

    Freitag, 27. September 2013 22:24
  • Deleted
    Dienstag, 1. Oktober 2013 09:17
  • 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"

    Dienstag, 1. Oktober 2013 17:25
  • Deleted
    Mittwoch, 2. Oktober 2013 20:43
  • Deleted
    Mittwoch, 2. Oktober 2013 20:44
  • 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"

    Donnerstag, 3. Oktober 2013 06:01
  • Deleted
    Montag, 7. Oktober 2013 14:56
  • 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.

    Montag, 7. Oktober 2013 16:29
  • 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?
    Dienstag, 8. Oktober 2013 07:47
  • 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?
    Dienstag, 8. Oktober 2013 07:51
  • Deleted
    Dienstag, 8. Oktober 2013 13:39
  • 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.
    Dienstag, 8. Oktober 2013 15:57
  • 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. :)
    Dienstag, 8. Oktober 2013 16:02
  • 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

    Sonntag, 13. Oktober 2013 16:12
  • Deleted
    Dienstag, 15. Oktober 2013 08:58
  • Any solution?

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

    Freitag, 18. Oktober 2013 17:28
  • Deleted
    Freitag, 18. Oktober 2013 23:12
  • 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

    Samstag, 19. Oktober 2013 08:57
  • 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

    Freitag, 25. Oktober 2013 17:00
  • 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.

    Dienstag, 29. Oktober 2013 01:56
  • 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.
    • Bearbeitet HenkelsGuy5 Dienstag, 29. Oktober 2013 19:46 Spelling
    Dienstag, 29. Oktober 2013 18:47
  • 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.

    Mittwoch, 30. Oktober 2013 13:20
  • Great work - a manual update of 39 downloads (including Office).

    Many thanks to HenkelsGuy5

    Samstag, 2. November 2013 13:07
  • I had to put the module in SysWow64 instead of System32 for this to work.
    Freitag, 8. November 2013 14:34
  • awesome! works like a charm... or actually better than the charms lol
    Mittwoch, 4. Dezember 2013 20:58
  • 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.

    Freitag, 13. Dezember 2013 04:58
  • 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."

    • Bearbeitet mtarggart Mittwoch, 18. Dezember 2013 17:48
    Dienstag, 17. Dezember 2013 16:46
  • 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.

    Dienstag, 17. Dezember 2013 17:38
  • 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


    • Bearbeitet Louis Phil Dienstag, 17. Dezember 2013 20:15
    Dienstag, 17. Dezember 2013 20:14
  • Thanks, it did helped me to install the updates.

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

    Mittwoch, 18. Dezember 2013 04:14
  • One option to workaround the problem is to use an offline updater

    http://download.wsusoffline.net/

    Montag, 3. Februar 2014 06:56
  • does not work for everyone, use Set-ExecutionPolicy Unrestricted

    Freitag, 7. März 2014 21:24
  • 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.

    Dienstag, 11. März 2014 21:09
  • 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.

    Mittwoch, 21. Mai 2014 12:59
  • 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.
    Donnerstag, 5. Juni 2014 04:36
  • Thanks man,

    this Module realy saved my day :D

    Montag, 16. Juni 2014 17:56
  • 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.
    Dienstag, 8. Juli 2014 06:11
  • 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.
    Donnerstag, 17. Juli 2014 20:46
  • 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

    Donnerstag, 31. Juli 2014 12:20
  • thanks it gone with Windows Server 2012 r2 Too
    Sonntag, 3. August 2014 12:17
  • 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.
    Montag, 27. Oktober 2014 17:16
  • 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.

    Mittwoch, 19. November 2014 09:42
  • 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?

    Sonntag, 18. Januar 2015 11:17
  • 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

    Donnerstag, 9. April 2015 17:46
  • I am unable to run this it dosen't automated with some prompts.

    Sonntag, 27. September 2015 03:04
  • What is OOBE?

    Mittwoch, 3. Februar 2016 01:47
  • The zip file is empty... No extraction possible. Any suggestions?
    Samstag, 7. Januar 2017 23:51
  • 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

    Out-freaking-standing!!!

    Dienstag, 31. Januar 2017 17:42
  • Processing of this module, as for today, seems to stop at the very beginnig : "Connecting to Windows Update server. please wait...'

    I suppose, this nice script may need to get verified by some programmer with a lot more skills than me ;p
    Samstag, 12. Januar 2019 22:32