windows update doesn't work in audit mode with windows 8.1. just google it or look into your windowsupdate.log file, where it says, that because OOBE is not finished, the search for updates will not be carried out. another stupid change by MS. -andy-
Thanks for that, no need to wait any longer then... Kinda strange that there's no warning or something, it's just sitting there.. EDIT: So I did some research, turns out there's two possible workarounds: - Install 8.1 in the normal way (create a user). Let it update, then enter auditmode afterwards (sysprep /audit, the system will reboot). Remove the user, sysprep /generalize /oobe and capture image. - Download the updates yourself and inject offline with DISM (well, that's a wellknown method of course). Not a very good change if you ask me... On the other hand, maybe I stuck with it for too long and will have to go with the offline DISM method. Might actually save a lot of time, when I think about it...
Tried to integrate GA Rollup using DISM - worked, as expected. But 'DISM /Image:XXX /Cleanup-Image /StartComponentCleanup /ResetBase' doesn't work on image ('Err 0x800f0806 = pending operation' - check if pending.xml is created in WinSxS, if yes - it will block any /Cleanup-Image stuff) So Image will contain backup of updated files(unlike GA distros). Can be cleaned after install using Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase
Indeed. Just tested it. 2883200 rollup sets pending values and blocks resetbase. Code: Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\Windows\system32>dism /mount-wim /wimfile:c:\win81x86\sources\install.wim /in dex:1 /mountdir:d:\mount Deployment Image Servicing and Management tool Version: 6.3.9600.16384 Mounting image [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>dism /image:d:\mount /add-package /packagepath:e:\win81slips tream\kbfiles\x86\Windows8.1-KB2883200-x86.msu Deployment Image Servicing and Management tool Version: 6.3.9600.16384 Image Version: 6.3.9600.16384 Processing 1 of 1 - Adding package e:\win81slipstream\kbfiles\x86\Windows8.1-KB2 883200-x86.msu [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>dism /image:d:\mount /cleanup-image /startcomponentcleanup / resetbase Deployment Image Servicing and Management tool Version: 6.3.9600.16384 Image Version: 6.3.9600.16384 Error: 0x800f0806 The operation could not be completed due to pending operations. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log C:\Windows\system32>
Actually, everything creates a pending.xml. You have to look at the contents of it to see if it will block a cleanup (I forgot exactly what section to look at, as it's been a while since I last investigated the issue). KB2883200 definitely does. So does enabling .NET 3.5, which isn't even a MSU update.
So updating in audit mode doesn't work anymore, and using the DISM method is quite a bit of work (figuring out which update sets the "pending" flag, checking which updates to add, etc.). I guess I'll give the "other" alternative a go, just to see how that goes: So that's installing w8.1 normally (with autounattend, but letting it create a user), letting it update, then enter audit mode (reset), removing the user (not sure yet how to do that), then generalize/ shutdown system and capture. I hope this method can produce a halfway decent updated .wim. (Oh, and I should add that my "normal" w8.1 wim used for a clean install already has NetFX3 added, and most AppX packages removed with DISM.)
I'm going to play with audit-mode. Even with non-audit-mode, you could script a /resetbase during setupcomplete.cmd It's just a pain in the rear since it takes up the extra 200+megs plus change for every index.
Could you please tell me which KB number that is? I didn't see one in my RSS feed for Visual Studio KBs... Nah, it won't be obsolete. With 8.0, there was an rollup each month. But none of the rollups were cumulative with previous rollups. So you'd have to install several different rollups. I think what they mean by "rollup" is "several different issues in one MSU" instead of "cumulative collection of fixes". So if 8.0 is anything to go by, the November rollup will need to be applied on top of KB2883200 instead of fully superseding it.
And it'll be a pending update, right? And the next new ones. It's just a matter of time. So why so hype?
It seems as if they purposefully blocked Windows Update from working in Audit-Mode. Perhaps there's some issues with installing that way. A work-around would be to: Create a user account in OOBE mode Run Windows Update. Run "SYSPREP /AUDIT" While in Audit-Mode, delete the temp account Run the Sysprep again to finalize and reboot/shutdown Delete the temp user folder and Administrator folder Capture image
Sorry, what takes up extra megs? Could you explain a bit more? I've done a first test with entering auditmode *after* a normal setup (w/ NetFX, NoAppx, autounattend) and updaterun. In the article mentioned before, they were talking about removing the temporary user you created during setup, but I didn't need that, as I use an autounattend with autologin for the administrator. So with no user to delete, I just reset into audit mode (using the commandline of course, as we've been told not to use the gui anymore), generalize/ shutdown and capture image. This doesn't look too bad after all! So let us know how you're doing with /resetbase etc please! [EDIT: sorry, was typing this while you posted you're message of 10m ago)
Yah you go back into audit-mode *after* setting everything up instead of before... You were probably supposed to do that in 8.0, but most of us didn't. Just go into control panel when in audit mode, user accts, remove yer temp acct. You can manually delete the administrator users folder before capturing to save more megs
I've finished my tests. Conclusion: I'll stick with auditmode... I'm using this install.wim as starting point: Windows 8.1 32bit Enterprise. With DISM, add NetFX3, remove most Appx packages. This is the "base" wim. From this I create two test wims: (1): Add the current 5 updates to the wim (offline) with DISM. (2): Install the "bare" .wim to a test PC using an autounattend.xml which automates everything (incl. creating a user with admin rights, with autologin). After setup, let it update (5 found, no drivers etc). Then, run "sysprep /audit". After reboot, run sysprep generalize, oobe, shutdown system. Capture the new image. Install from (1) Takes 11m30s (tested from after apply finished and system is rebooted). Install from (2) Takes 5m15s. Quite a big difference... Does this have anything to do with the "pending" status of the updates in wim (1)? The "preparing..." stage takes a lot longer! As I said before, doing this updaterun once in a while actually saves me a lot of time, for one thing I don't need to keep up with all the details of every single new update. But this is just a little follow-up to my previous post, so I'm curious how this is working for others...