883 replies to this topic

[Erik Ramey]

I've confirmed the same as Cristiano . Hate when MS does this

[James]

It seems 4NNuN4kI was right after all.
As I found yesterday, it took 48 hours or so for Microsoft's servers, ISP caches etc to all be updated reliably.

The script has now been updated by Erik.

See Here (posts #3 through #6) if you want to know the details.

--

[Cristiano]

> it took 48 hours
lucky yours. so far, the only one thing that has changed into my language is the release date

[]s

[James]

In amongst the 11 Security Bulletins yesterday (MS08-041 through MS08-051) Microsoft issued one with no bulletin number, as an Advisory:
"Microsoft Security Advisory (953839) Cumulative Security Update of ActiveX Kill Bits"

Download links flow from This KB article

Details are as follows:

Quote

Deployment: Windows Update, Microsoft Update, Important/Automatic Updates, WSUS, and Catalog
Classification: High Priority, Non-Security, Update Rollups
Supersedes: MS08-032 (KB950760) on Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP, and Microsoft Windows 2000
Target platforms: Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP, and Microsoft Windows 2000

No MSFT bulletin number is probably because the new kill bits are for non-Microsoft products (Aurigma Image Uploader + HP Instant Support).

--

Edited by James, 13 August 2008 - 07:35 AM.

[Cristiano]

James, topic merged with hotfix depot, since is related to that

[]s

edit: i'm not sure about yours, but sounds annoying to me that something changes his version and don't change his detection. this appears to be true with .net 3.5 sp1. if we keep that, those that already have .net 3.5 will see it also an already installed update, that isn't true, since there's an sp1 that they may not have yet. so, it's time to change that detection and i've saw a couple of options. at registry, we have this:

RegistryPath=HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5
KeyName=Version
KeyValue=3.5.30729.01

the version isn't he same, so, it will works. also, this may works too:

RegistryPath=HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5
KeyName=SP
KeyValue=1

but i didn't tested this one. also, you may detect this update by .cat file too. msxpsdrv.cat is related to that and also mxdwdrv.dll, xpssvcs.dll , but just .reg detections shall suffice.

also, the new updates that ms bring to us are this ones:
kb953839
kb890830 - 08/2008
kb951066
kb952954
kb953838
kb950934
kb952287

all those critical

edit2: obsolete from this last wave: KB950759 (IE7) and KB950759 (IE6), KB950760

[]s

[DesertJerry]

New version, messenger.msi, released 12 Aug - AutoPatcher needs updating.

[Cristiano]

@DesertJerry: confirmed. pt-br script updated. thanks

by the way: topic merged, due content related with hotfix depot

[]s

[Erik Ramey]

There's a lot of updates this patch cycle so this is going to take awhile to do all the packs

@Cristiano - I think you might have downloaded the .net 3.5 modules when I was first uploading them the other day. If you download them again, you should notice the SP1 tag that you aleady mentioned being used

@DesertJerry - Do I need to say anything? <wink> P.S WOW! You used a new smiley face! <another wink>

@James - I believe you are right about the Kill Bits article. I'm glade that Microsoft is now encouraging 3rd party's when they need to "Kill" a bad ActiveX.

[James]

Erik Ramey, on Aug 14 2008, 04:12 AM, said:

There's a lot of updates this patch cycle so this is going to take awhile to do all the packs

No kidding! I'm drowning in patches on my own network right now!

Apart from the 11 bulletins (23 Office patches alone!), the killbit update and .NET 3.5 SP1 there's also a new version of WindowsUpdateAgent:

WindowsUpdateAgent version 7.2.6001.784. See KB946928 for file details and download links.

Also, for MS08-050, the new version of Windows Messenger (=5.1.0.715) is if you have version 5.1 installed. If you still have version 4.7 installed, it's a regular security patch (=KB946648).

Version 5.1 can be installed on other platforms as well:

Quote

Supported Operating Systems: Windows 2000 Service Pack 4; Windows Server 2003; Windows Server 2003 Service Pack 1; Windows XP 64-bit; Windows XP Service Pack 1; Windows XP Service Pack 2; Windows XP Tablet PC Edition

Also, KB936782 = MS07-047 = WMP 9/10/11 has been officially updated to detect on XP SP3 (as well as SP2).

--


--

[James]

@Cristiano + Erik

.NET detection is quite a bit more complicated than that. For example:

Quote

On 64-bit system while checking registry for 32-bit version of .NET Framework you should check under:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v3.5
rather than default:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5

See:
.NET Framework 3.5 Deployment Guide for Application Developers (Microsoft)

.NET Framework 3.5 Deployment Guide for Administrators (Microsoft)

How .NET Framework 3.5 setup checks for its prerequisites behind the scenes (Aaron Stebner)

Start with the Aaron Stebner link, it should tell you more than you ever wanted to know...

Now you all know where I get my .NET information from!

--

[Cristiano]

> Now you all know where I get my .NET information from
by the way: you already readed something about that 9mb that .net 3.5 (any sp) tries to download if you are installing it online?

[]s

[James]

Cristiano, on Aug 14 2008, 12:34 PM, said:

... you already readed something about that 9mb that .net 3.5 (any sp) tries to download if you are installing it online?

Yes: if you install .NET 3.5 on a non-english OS it will try to download the language pack from the internet. As usual Aaron Stebner has the full answer and the details:
Scenarios where .NET Framework 3.5 setup tries to connect to the Internet and how to avoid them

In your case, .NET will be trying to download dotnetfx35langpack_x86pt-BR.exe. Read the link I have given. Under Case 2 - Installing the .NET Framework 3.5 on a non-English OS there are then links to other articles, which lead to the Microsoft download pages. For example:

Quote

Descrição Resumida
Os Pacotes de Idiomas do Microsoft .NET Framework 3.5 contêm textos traduzidos, como as mensagens de erro, para cada idioma.
...
Detalhes Rápidos
Versão: 3.5
Data de Publicação: 6/3/2008
Idioma: Português (Brasil)
Tamanho do Download: 8.1 MB - 32.5 MB

The easiest is probably to install the .NET 3.5 framework using the /lang:ENU option, then install the language pack. This is just one of the alternatives that Aaron Stebner explains.

--


Edit: corrected spelling

Edited by James, 14 August 2008 - 02:17 PM.

[Cristiano]

> /lang:ENU
that will be done, at least, in my module to that. really, it's an pain install it if you forget that you are online. i don't know arround the globe, but in here, most people doesn't have real broadband

thanks

off: now, i must bring my brand new bike to home. i will fix this issue later

[]s

[Erik Ramey]

I must say that these articles are all good readings. I'm thinking that we are going to have to implement a lot of these suggestions that are presented in this blog.

[DesertJerry]

Erik Ramey, on Aug 14 2008, 04:12 AM, said:

@DesertJerry - Do I need to say anything? <wink> P.S WOW! You used a new smiley face! <another wink>

I was a day late though - was watching the girls Olympic beach volleyball - and got carried away.

[Cristiano]

> Also, KB936782 = MS07-047 = WMP 9/10/11 has been officially updated to detect on XP SP3 (as well as SP2)
they just have updated the description, right? the md5 for WindowsMedia11-KB936782-x86-PTB.exe is still the same. date for enu too

@James: thanks. that /lang:ENU worked like a charm. i've added the transtation pack as well, but seems that the translation pack for sp1 isn't out yet. but what i'm complaining? the new build of wmp11 isn't translated yet

[]s

[James]

Cristiano, on Aug 15 2008, 05:13 PM, said:

... they just have updated the description, right? the md5 for WindowsMedia11-KB936782-x86-PTB.exe is still the same. date for enu too ...

Yes, they only updated the "detection logic" so that it will (1) show as missing if not installed; and (2) will also install on SP3.

It is taking Microsoft a long time -- months and months -- to find all the updates which apply to XP-SP3 as well as SP2.

--

[James]

Just when you thought it was nearly all over following Patch Tuesday...

KB951072 has been upped to v2
KB951618 has been upped to v2

Also SyncToy v2 has been out a few days.

More to follow...

--

[Cristiano]

> KB951072v2
great. do you remember that issue that you talked about this kb don't install over an previews version, that only applies to Iran?

http://img178.images...951072v2te6.gif

you may now add Brazil into that list...

thanks

[James]

Cristiano, on Aug 21 2008, 04:40 PM, said:

... do you remember that issue that you talked about this kb don't install over an previews version, that only applies to Iran? ...

That's not really what I meant. I was saying two things:

1) version 2 will not install over the top of version 1;

2) the difference between version 2 and version 1 is that the time data for Iran is different.

--