MS06-061 KB925672 command line issue if windows installer 2 installed.

MS06-061 KB925672 command line issue if windows installer 2 installed.

I have this issue when I install KB925672
MS write in MS06-061 use command line /quiet /norestart
to deploy with SMS

but on computers WIN2K without windows installer 3.0 or more.
Windows installer return "Incorrect command line Parameters"

very bad to not write need Windows Installer 3.1.

I not sure if I can use /q and this doesn't restart computer when
msxml4.dll is in use by user.

or maybe use /q REBOOT=ReallySuppress

for now i'm waiting for the best solution by MS

maybe deploy windows installer 3.1 v2 before deploy last updates.

Hi,

i have the same problem with the patch KB925672.
The MS Hotline wants to open a call for that, but I think it's a program
failure from the developer of this patch.

Anyway...teh listed parameters in the KB-article are only correct when
Windows Installer 3.x is installed. This information is not found in the
article!

Many systems of our environment have installed the Windows Installer 2.0 yet.
So, this problem is really bad, because we cannot use SUFP with the
documentated parameters in our environment.
The security problem cannot be fixed immediately.

Can anyone from MS can fixed the patch?

Thörsti



"jstrecko" wrote:

> MS06-061 KB925672 command line issue if windows installer 2 installed.
>
> I have this issue when I install KB925672
> MS write in MS06-061 use command line /quiet /norestart
> to deploy with SMS
>
> but on computers WIN2K without windows installer 3.0 or more.
> Windows installer return "Incorrect command line Parameters"
>
> very bad to not write need Windows Installer 3.1.
>
> I not sure if I can use /q and this doesn't restart computer when
> msxml4.dll is in use by user.
>
> or maybe use /q REBOOT=ReallySuppress
>
> for now i'm waiting for the best solution by MS
>
> maybe deploy windows installer 3.1 v2 before deploy last updates.
>
>

Hi,

i have detected another problem.

With MBSA 1.2.1 the patch KB925672 is detected as applicable.
(file version lower than expected.
[\\client1\C$\WINDOWS\system32\msxml4.dll, 4.20.9818.0 < 4.20.9839.0])

With MBSA 2.0 the patch is NOT applicable.

At the moment the MBSA 1.2.1 detected more as the MBSA 2.0.

Very funny...;-<<<<

Bad thing!!!!



"Thörsti" wrote:

> Hi,
>
> i have the same problem with the patch KB925672.
> The MS Hotline wants to open a call for that, but I think it's a program
> failure from the developer of this patch.
>
> Anyway...teh listed parameters in the KB-article are only correct when
> Windows Installer 3.x is installed. This information is not found in the
> article!
>
> Many systems of our environment have installed the Windows Installer 2.0 yet.
> So, this problem is really bad, because we cannot use SUFP with the
> documentated parameters in our environment.
> The security problem cannot be fixed immediately.
>
> Can anyone from MS can fixed the patch?
>
> Thörsti
>
>
>
> "jstrecko" wrote:
>
> > MS06-061 KB925672 command line issue if windows installer 2 installed.
> >
> > I have this issue when I install KB925672
> > MS write in MS06-061 use command line /quiet /norestart
> > to deploy with SMS
> >
> > but on computers WIN2K without windows installer 3.0 or more.
> > Windows installer return "Incorrect command line Parameters"
> >
> > very bad to not write need Windows Installer 3.1.
> >
> > I not sure if I can use /q and this doesn't restart computer when
> > msxml4.dll is in use by user.
> >
> > or maybe use /q REBOOT=ReallySuppress
> >
> > for now i'm waiting for the best solution by MS
> >
> > maybe deploy windows installer 3.1 v2 before deploy last updates.
> >
> >

Hi again,

I have detected another problem with the patch MS06-061 KB925672.

With MBSA 1.2.1 the patch will be detected as applicable. That's OK.
(Result: file version lower than expected.
[\\client-pc1\C$\WINDOWS\system32\msxml4.dll, 4.20.9818.0 < 4.20.9839.0]

But with MBSA 2.0 the patch will not be detected as applicable.


Therfore the information in the article from Microsoft is not right!
There is given the information that MBSA 1.2.1 AND MBSA 2.0 can be used to
determine if the patch is required!!!
At the moment the MBSA 1.2.1 detected more than the MBSA 2.0.

Very funny;-<<<<<

Bad thing!!!!

"Thörsti" wrote:

> Hi,
>
> i have the same problem with the patch KB925672.
> The MS Hotline wants to open a call for that, but I think it's a program
> failure from the developer of this patch.
>
> Anyway...teh listed parameters in the KB-article are only correct when
> Windows Installer 3.x is installed. This information is not found in the
> article!
>
> Many systems of our environment have installed the Windows Installer 2.0 yet.
> So, this problem is really bad, because we cannot use SUFP with the
> documentated parameters in our environment.
> The security problem cannot be fixed immediately.
>
> Can anyone from MS can fixed the patch?
>
> Thörsti
>
>
>
> "jstrecko" wrote:
>
> > MS06-061 KB925672 command line issue if windows installer 2 installed.
> >
> > I have this issue when I install KB925672
> > MS write in MS06-061 use command line /quiet /norestart
> > to deploy with SMS
> >
> > but on computers WIN2K without windows installer 3.0 or more.
> > Windows installer return "Incorrect command line Parameters"
> >
> > very bad to not write need Windows Installer 3.1.
> >
> > I not sure if I can use /q and this doesn't restart computer when
> > msxml4.dll is in use by user.
> >
> > or maybe use /q REBOOT=ReallySuppress
> >
> > for now i'm waiting for the best solution by MS
> >
> > maybe deploy windows installer 3.1 v2 before deploy last updates.
> >
> >

Hi,

I have the same problem. (in more 70 pc's and server's)

The mbsa 2.0 (Microsoft Update, ITMU, MBSA 2.0) reported MS06-061
(924191, 924424) and was not required (925672). and
MBSA 1.2.1 reported MS06-061 (924191, 925672) but the Windows Update
reported only 924191.

any idea what to do?


"Thörsti" wrote:

> Hi again,
>
> I have detected another problem with the patch MS06-061 KB925672.
>
> With MBSA 1.2.1 the patch will be detected as applicable. That's OK.
> (Result: file version lower than expected.
> [\\client-pc1\C$\WINDOWS\system32\msxml4.dll, 4.20.9818.0 < 4.20.9839.0]
>
> But with MBSA 2.0 the patch will not be detected as applicable.
>
>
> Therfore the information in the article from Microsoft is not right!
> There is given the information that MBSA 1.2.1 AND MBSA 2.0 can be used to
> determine if the patch is required!!!
> At the moment the MBSA 1.2.1 detected more than the MBSA 2.0.
>
> Very funny;-<<<<<
>
> Bad thing!!!!
>
> "Thörsti" wrote:
>
> > Hi,
> >
> > i have the same problem with the patch KB925672.
> > The MS Hotline wants to open a call for that, but I think it's a program
> > failure from the developer of this patch.
> >
> > Anyway...teh listed parameters in the KB-article are only correct when
> > Windows Installer 3.x is installed. This information is not found in the
> > article!
> >
> > Many systems of our environment have installed the Windows Installer 2.0 yet.
> > So, this problem is really bad, because we cannot use SUFP with the
> > documentated parameters in our environment.
> > The security problem cannot be fixed immediately.
> >
> > Can anyone from MS can fixed the patch?
> >
> > Thörsti
> >
> >
> >
> > "jstrecko" wrote:
> >
> > > MS06-061 KB925672 command line issue if windows installer 2 installed.
> > >
> > > I have this issue when I install KB925672
> > > MS write in MS06-061 use command line /quiet /norestart
> > > to deploy with SMS
> > >
> > > but on computers WIN2K without windows installer 3.0 or more.
> > > Windows installer return "Incorrect command line Parameters"
> > >
> > > very bad to not write need Windows Installer 3.1.
> > >
> > > I not sure if I can use /q and this doesn't restart computer when
> > > msxml4.dll is in use by user.
> > >
> > > or maybe use /q REBOOT=ReallySuppress
> > >
> > > for now i'm waiting for the best solution by MS
> > >
> > > maybe deploy windows installer 3.1 v2 before deploy last updates.
> > >
> > >