New year answers...

re: New year answers...

joscon [Microsoft] — Thu, 17 Feb 2011 23:55:08 GMT

Nothing that would be really interesting to anyone outside of MSFT. It keeps a couple of other things used during processing.

re: New year answers...

Drewfus — Thu, 17 Feb 2011 23:44:09 GMT

Is the MSU wrapper technology interesting itself? For example, why not just put the underlying cabinet files in a zip file? What does the MSU technology provide that a zip file wouldn't, for example? Is it at all like the WIM format?

re: New year answers...

joscon [Microsoft] — Thu, 14 Jan 2010 18:34:02 GMT

Well an MSU is nothing more than the cabiner file in a wrapper. That's why you can always use the EXPAND command against the MSU to get the underlying cabinet files for the fix.

re: New year answers...

someone — Wed, 13 Jan 2010 19:31:50 GMT

Not what I wanted to hear but Vista is gone anyways. Here's hoping that less updates/hotfixes will be distributed as cab files in the Windows 7 era and all of them as MSUs.

re: New year answers...

joscon [Microsoft] — Tue, 12 Jan 2010 16:28:43 GMT

No WUSA cannot install .cab files, you would need DISM or PKGMGR for that. Why not build an image with the Ultimate Extras you want and then deploy it without the need for the script?

re: New year answers...

someone — Mon, 11 Jan 2010 17:08:57 GMT

But can WUSA install .cab updates? I thought we need Pkgmgr for installing .cab update like Ultimate Extras as WUSA only support .MSU updates. That's where I see this behavior but if I install the same updates using Windows Update, they all install without any issues. I don't want to download Ultimate Extras for every machine I update, and I don't want to use WSUS. A simple script should work to install all downloaded .CAB Ultimate Extras in a row one after the other but it doesn't as only pkgmgr supports .cab updates and it produces this above weird behavior if installing more than one update sequentially.