Why the Vista's hotfixes are *.msu?

[Masterwill21]

Why the Vista's hotfixes are *.msu????? and why I cant install on Vista. I would like de final vLite will integrate the hotfixes

[anonymous_user]

to install them under Vista, u double-click them (like an executable).

Edited February 14, 2007 by anoymous_person

[RaGhul]

Hmm... this is interesting.

I've played with a few Vista betas, but never got to any hotfixes. I never knew the hotfixes were this ".msu" file. Must be Microsucks' new .msi (Great, another installer-type file to give us all headaches!! )

@anonymous,

to install them under Vista, u double-click them (like an executable).

Well, duh!! Tell us something we DON'T know!

Anyone got any information about this type of file?

PS:

It's interesting to note that Vista JUST got released, and already has Hotfixes for it. So much for improved security!

[TheTripleX]

I am not sure of how many of those fix any security holes, instead they add compatibility and improve stability.

[HeadHunter2]

The *.msu files are some kind of cab files.

They contain this, take KB929427:

a xml Windows6.0-KB929427-x86.xml:

<?xml version="1.0" encoding="utf-8"?>

<unattend xmlns="urn:schemas-microsoft-com:unattend">

<servicing>

<package action="install">

<assemblyIdentity name="Package_for_KB929427" version="6.0.1.10" language="neutral" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35"/>

<source location="%configsetroot%\Windows6.0-KB929427-x86.CAB" />

</package>

</servicing>

</unattend>

a Windows6.0-KB929427-x86.cab which contains new files and cats files for it.

a WSUSSCAN.cab caontains: package.cab -->seems to be a small installer

and the forth but least file is this one: Windows6.0-KB929427-x86-pkgProperties.txt:

Applies to="Windows 6.0"

Build Date="2007/01/26"

Company="Microsoft Corporation"

File Version="1"

Installation Type="FULL"

Installer Engine="Component Based Servicing - WUSA.exe"

Installer Version="6.0.0.0"

KB Article Number="929427"

Language="ALL"

Package Type="Update"

Processor Architecture="x86"

Product Name="Windows 6.0"

Support Link="http://support.microsoft.com?kbid=929427"

[Masterwill21]

to install them under Vista, u double-click them (like an executable).

I did double-click on the .msu like an executable but don't install anything

[nuhi]

Masterwill21, don't double post.

[vim]

Here is some more info on MSU packages:

http://www.mydigitallife.info/2007/02/15/e...-windows-vista/

[strotee76]

It's interesting to note that Vista JUST got released, and already has Hotfixes for it. So much for improved security!

Yes, if you consider November as JUST released. You realize Vista RTM'ed in November, hence no changes to the final code. So, 3.5 months later, here we sit.

[MAVERICKS CHOICE]

Why the Vista's hotfixes are *.msu????? and why I cant install on Vista. I would like de final vLite will integrate the hotfixes

I'm guessing Dino will get round to this shortly, given Vista has gone public now for such a small time. I too would like such a feature to pre integrate hotfixes in a ua Vista enviroment. Getting there slowly.

[taltamir]

MSU = Microsoft Update/s? Sounds to me like another gimmicky file format from microsoft...

[dexter.inside]

I think MSUs have full access to the TrustedInstaller process, unlike MSIs or MSPs. It may be a way to install drivers and install/remove services without restarting, but I think we will have to wait for Visual Studio 2007 to test it out.

Edited February 23, 2007 by dexter.inside

[ane]

Why the Vista's hotfixes are *.msu????? and why I cant install on Vista. I would like de final vLite will integrate the hotfixes

It's Simple, The "MS" stand for m$, "U" stand for Update .

[bledd]

imo its a good thing vista has its own update extentions, at least there's no way you could confuse a non vista hotfix with a vista one now