.NET Framework Addon Pack
ViroMan
30 Apr 2012
How do you know it was superseded? I looked at the MS bulletins and it doesn't say it was replaced, doesn't mean it wasn't I just can't find anything that says it was.
I suppose since its a SP it should include all the previous fixes no? I guess that makes sense then.
Edited by ViroMan, 30 April 2012 - 02:21 AM.
I suppose since its a SP it should include all the previous fixes no? I guess that makes sense then.
Edited by ViroMan, 30 April 2012 - 02:21 AM.
Whatacrock
30 Apr 2012
The KB in question KB98216 is for a rollup update for the .NET Framework 3.5 Service Pack 1 and the .NET Framework 2.0 Service Pack on Windows XP and on Windows Server 2003 (976765 and 980773) dated June8, 2010
dated June8, 2010. This is not replaced by any other KB.
As for KB2418241 is an Security Update for the Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 2.0 Service Pack 2 on Windows Server 2003 and Windows XP.
Link for KB2418241 http://support.micro....com/kb/2418241
Link for KB98216 http://support.microsoft.com/kb/982167
Edited by Whatacrock, 30 April 2012 - 02:42 AM.
dated June8, 2010. This is not replaced by any other KB.
As for KB2418241 is an Security Update for the Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 2.0 Service Pack 2 on Windows Server 2003 and Windows XP.
Link for KB2418241 http://support.micro....com/kb/2418241
Link for KB98216 http://support.microsoft.com/kb/982167
Edited by Whatacrock, 30 April 2012 - 02:42 AM.
click-click
30 Apr 2012
According to MS11-100, KB2418241 in MS10-070 and KB982167 in Security Advisory 973811 were replaced by KB2656352, so I will remove KB982167 for clarity the next time I update dotNET.
ViroMan
30 Apr 2012
what did you use to find that out or did you go through each one? I would like to know, to make it easier to find information like that.
click-click
30 Apr 2012
It's usually hit and miss. I entered kb982167 and replaced as search arguments in Google. I wish it were easier. Your best bet is to keep up with the security bulletins. This seems like the only place where Microsoft talks about superseded files.
Edited by click-click, 30 April 2012 - 06:39 PM.
Edited by click-click, 30 April 2012 - 06:39 PM.
Whatacrock
01 May 2012
That would be typical of Microsoft and even then the security bulletins aren't always updated or the replacements aren't added to the current one.
Noticed this with some of the older bulletins whilst doing the WinXP x64 updates.Sometimes you end up going around in circles only to end up back where you started.
Noticed this with some of the older bulletins whilst doing the WinXP x64 updates.Sometimes you end up going around in circles only to end up back where you started.
Whatacrock
09 May 2012
May Updates for .NET Framework
http://technet.micro...lletin/ms12-034
Security Update for Microsoft .NET Framework 3.0 Service Pack 2 on Windows Server 2003 and Windows XP KB2656407
Security Update for Microsoft .NET Framework 4 on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 KB2656405
http://technet.micro...lletin/ms12-035
Security Update for Microsoft .NET Framework 3.0 Service Pack 2 on Windows Server 2003 and Windows XP KB2604110
Security Update for Microsoft .NET Framework 3.5 Service Pack 1 on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 KB2604111
Security Update for Microsoft .NET Framework 2.0 Service Pack 2 on Windows Server 2003 and Windows XP KB2604092
Edited by Whatacrock, 09 May 2012 - 08:42 AM.
http://technet.micro...lletin/ms12-034
Security Update for Microsoft .NET Framework 3.0 Service Pack 2 on Windows Server 2003 and Windows XP KB2656407
Security Update for Microsoft .NET Framework 4 on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 KB2656405
http://technet.micro...lletin/ms12-035
Security Update for Microsoft .NET Framework 3.0 Service Pack 2 on Windows Server 2003 and Windows XP KB2604110
Security Update for Microsoft .NET Framework 3.5 Service Pack 1 on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 KB2604111
Security Update for Microsoft .NET Framework 2.0 Service Pack 2 on Windows Server 2003 and Windows XP KB2604092
Spoiler
Edited by Whatacrock, 09 May 2012 - 08:42 AM.
Whatacrock
09 May 2012
JRosenfeld
11 May 2012
Unfortunately returning false in Autopatcher after downloading latest net framework (with Apup2 1.0.5.13), also still showing date as 12 April
ViroMan
11 May 2012
He made new rti files but, it seems he forgot to change the dates. no biggie there but, they are showing as unofficial to me. I will poke around.
Kinda weird... md5 shows as good. the only thing I can think of off the top of my head is that when he made the rti's something was off in some way. I have a way to deconstruct an rti I will see if I notice a difference between the md5 list and the rti.
We found the error and are fixing it now... shouldn't take a minute to do.
Edited by ViroMan, 11 May 2012 - 06:39 PM.
Kinda weird... md5 shows as good. the only thing I can think of off the top of my head is that when he made the rti's something was off in some way. I have a way to deconstruct an rti I will see if I notice a difference between the md5 list and the rti.
We found the error and are fixing it now... shouldn't take a minute to do.
Edited by ViroMan, 11 May 2012 - 06:39 PM.
click-click
11 May 2012
Small glitch folks. If you get unofficial, you can delete dotnet_x86.rti and dotnet_x64.rti or wait until I change the script.
Edited by click-click, 11 May 2012 - 07:11 PM.
Edited by click-click, 11 May 2012 - 07:11 PM.
click-click
11 May 2012
The scripts have been updated.
For those of you that have already downloaded the new dotNET, please delete dotnet_x86_20120508.rti and dotnet_x64_20120508.rti if present in the AP directory and rerun APUP. You should also delete the md5 files.
Edited by click-click, 11 May 2012 - 07:15 PM.
For those of you that have already downloaded the new dotNET, please delete dotnet_x86_20120508.rti and dotnet_x64_20120508.rti if present in the AP directory and rerun APUP. You should also delete the md5 files.
Edited by click-click, 11 May 2012 - 07:15 PM.
click-click
11 May 2012
In case anyone is wondering about KB2604044, MS12-035 has been revised. Here's the FAQ:
Frequently Asked Questions (FAQ) Related to This Security Update
Why was this bulletin revised on May 10, 2012?
Microsoft revised this bulletin to communicate that for all supported systems running Microsoft .NET Framework 1.1 Service Pack 1, except when installed on Windows Server 2003 Service Pack 2, the vulnerabilities described in this bulletin are addressed by security update KB2656353. Security update KB2656353 was previously offered in MS11-100, but also addresses the vulnerabilities described in this bulletin, CVE-2012-0160 and CVE-2012-0161.
Security update KB2656353 is available through all standard deployment channels, including Microsoft Update, Windows Update, and the Microsoft Download Center. There were no changes to the security update files. Customers who have successfully installed either KB2656353, from MS11-100, or KB2604044, previously offered through this bulletin, do not need to take any action. Customers running Microsoft .NET Framework 1.1 Service Pack 1 on all supported systems except Windows Server 2003 Service Pack 2, who have not installed either KB2656353 or KB2604044, should apply the KB2656353 update immediately using update management software, or by checking for updates using the Microsoft Update service.
Edited by click-click, 11 May 2012 - 08:17 PM.
Frequently Asked Questions (FAQ) Related to This Security Update
Why was this bulletin revised on May 10, 2012?
Microsoft revised this bulletin to communicate that for all supported systems running Microsoft .NET Framework 1.1 Service Pack 1, except when installed on Windows Server 2003 Service Pack 2, the vulnerabilities described in this bulletin are addressed by security update KB2656353. Security update KB2656353 was previously offered in MS11-100, but also addresses the vulnerabilities described in this bulletin, CVE-2012-0160 and CVE-2012-0161.
Security update KB2656353 is available through all standard deployment channels, including Microsoft Update, Windows Update, and the Microsoft Download Center. There were no changes to the security update files. Customers who have successfully installed either KB2656353, from MS11-100, or KB2604044, previously offered through this bulletin, do not need to take any action. Customers running Microsoft .NET Framework 1.1 Service Pack 1 on all supported systems except Windows Server 2003 Service Pack 2, who have not installed either KB2656353 or KB2604044, should apply the KB2656353 update immediately using update management software, or by checking for updates using the Microsoft Update service.
Edited by click-click, 11 May 2012 - 08:17 PM.
click-click
12 May 2012
Looks like MS removed KB2604044 as a download too. I will have to revert back to KB2656353. More reasons to wait a few days before updating 
Edited by click-click, 12 May 2012 - 11:21 AM.
404 - File or directory not found The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
Edited by click-click, 12 May 2012 - 11:21 AM.
Whatacrock
12 May 2012
@startrek-which APUPversion did you use version 1 or version 2 and what OS are you running?
If you used version 2 you will get this error as I did on my Vista x86 box(usually run version 1 on it especially for the .NET releases).This system is showing as unofficial and the .NET stating false.
Ran version 1 on XP received no errors and shown as official with the release stating true
I doubt that click-click changed anything other than the rti file which caused a problem before and now has been corrected.
@click-click- was too slow for my posting as was booting up vista again to check the apup log
Edited by Whatacrock, 12 May 2012 - 11:27 AM.
If you used version 2 you will get this error as I did on my Vista x86 box(usually run version 1 on it especially for the .NET releases).This system is showing as unofficial and the .NET stating false.
Ran version 1 on XP received no errors and shown as official with the release stating true
I doubt that click-click changed anything other than the rti file which caused a problem before and now has been corrected.
@click-click- was too slow for my posting as was booting up vista again to check the apup log
Edited by Whatacrock, 12 May 2012 - 11:27 AM.
Whatacrock
12 May 2012
You were correct MS in its wisdom has pulled the file, just reran on vista got the one or more files failed verification, here is the end of the apup log
Did some further reading and from this bulletin clicked on the download link it sends you here http://go.microsoft..../?LinkId=226977
NDP1.1sp1-KB2656353-X86.exe
Edited by Whatacrock, 12 May 2012 - 11:42 AM.
Spoiler
Did some further reading and from this bulletin clicked on the download link it sends you here http://go.microsoft..../?LinkId=226977
NDP1.1sp1-KB2656353-X86.exe
Edited by Whatacrock, 12 May 2012 - 11:42 AM.
ViroMan
12 May 2012
@Whatacrock is it true that .net doesn't work for you if you use apup2 but, its fine with apup1? If so I need to look into this because no one else has complained. It seems to work for me though. Have you tried using the supplied MD5 files to cross check for extra or missing files?
Whatacrock
12 May 2012
Just retried it on the vista machine and get the same file error so it is working, its just I use version 1 for doing the .NET releases. I run APUP on each version twice to double check all is good.
Sorry for not wording my posting correctly, just been in front of this thing all afternoon doing the script, fingers run ahead of the brain
Sorry for not wording my posting correctly, just been in front of this thing all afternoon doing the script, fingers run ahead of the brain
