Since Microsoft decidied it would be a good idea to prevent Windows Update from working in Audit mode i was wondering if there are a major issues with the workaround of creating a temprary user, runing all the updates and then going back to audit mode to delete temp user and continue with MDT Capture as usual ?

What is the adnavntage of using powershell workaround ?

Hi,

In my opinion, if you want to package Windows update into Windows image, there are many ways to achieve the goals instead of using the process you described. 

You can refer to the contents of the blog below for more reasonable method to package Windows update:

http://blogs.technet.com/b/mniehaus/archive/2011/05/16/creating-a-fully-patched-image-using-mdt-2010-lite-touch.aspx

For using powershell, what I know just is it's more helpful when applies a large amount of operations and management. For more assistance, you can access PowerShell forum.

From your link above

"Install all updates from Microsoft Update directly

This is the easy way, as long as you have good internet bandwidth (all updates are downloaded from the internet) and a direct path to these downloads, and always want to install all critical updates.

To use this method, all you need to do is search your task sequence for the following steps:

• Windows Update (Pre-Application Installation)
• Windows Update (Post-Application Installation)

Enable both of them, and then build a new image thats all there is to it."

From my understanding these 2 task will be running in Audit mode, and in Windows 8.1 will fail as Windows update isnt working in Win8.1 Audit mode.

This is what I do. I will sysprep the Windows 8.1 image and go through oobe. Then set Windows Updates to disable and click to check for updates. After it searches and shows you the list of available updates, search for each on the Catalog site. Download all you can find, then inject them into the WIM using DISM. Redeploy and re-check for updates.

Here is the catalog link, you need to use Internet Explorer:
https://catalog.update.microsoft.com/v7/site/Home.aspx

this can't be the optimal way of doing it,

This is sounds like a huge step backwards from Windows 7, where i would install Win7 from iso on a VM, then Ctrl+Shif+F3 to Audit mode, install Office, run Windows Updates, and after it installes about 4GB of updates (Win+Office) I would start LightTouch.vbs and in 40 min i would have a Custom WIM ready.

With method of manually "search for each on the Catalog site" sounds like housrs of work (Windows Updates aren't 5 or 10, its more like 180+ Updates.)

Surely MS hava way to do this properly.

The way I outlined is also how I do it for Windows 7. I left out the part that we do it this way to track exactly which packages are put into images. There is also the consideration that certain channels (OEM/SB) are not allowed to accept EULAs on updates. Those types of updates are not available for download from the catalog site anyways, which helps.

A downfall of that, however, is that some of the EULA updates are actually updates to the Windows Update itself. As a result, a fully patched Win7 or Win8 image may still show SP1 or Update 1 in the list of available updates.