.NET Framework Addon Pack
Posted 28 January 2013 - 09:27 PM
+ = Added - = Removed @ = Updated +KB2742596 -KB2686828 -KB2656369 -KB979909 +KB2742595 -KB2686827 -KB2656368 +KB2756918 -KB976570 +KB2736416 -KB982306 +KB2736428 +KB2742597 -KB2698023 -KB2656370 +KB2742601 -KB2686833 -KB2656374 -KB979910 +KB2742613 -KB2729460 +KB2750147 +KB2756919 +KB2742599 -KB2686831 -KB2656373 -KB2633873 +KB2736422 +KB2756921 -KB2604092 (replaced by KB2729450/KB2742596) -KB988481 (replaced by KB2656362/KB2729453/KB2742601) -KB958483 replaced by KB2656409/KB2756919 on Vista) @KB2656356 @KB2656411 shorten names: @KB2742597 @KB2604111 @KB2657424 @KB2736416 @KB2737083 @KB2742613 @KB2750147
Posted 17 February 2013 - 12:42 PM
+ = Added - = Removed @ = Updated +KB2789642 +KB2789643 +KB2789645 +KB2789646 +KB2789648
Posted 18 February 2013 - 06:16 AM
Everything looked good except for:
Microsoft Windows - Updated Components > .Net Framework 3.0 SP2:
black with no check - Microsoft .NET *** (KB958483)
Selected item and it installed - restarted AutoPatcher - still black. Have no idea why - superseded by another update?
Reported in Windows XP x64 thread.
One for you click-click
Posted 18 February 2013 - 11:53 AM
System.ServiceModel.dll 3.0.4506.2254 Wpfgfx_v0300.dll 3.0.6920.1500 PresentationFramework.dll 3.0.6920.1500If you have newer versions then the files above, that means they were replaced by another fix. If not, then you are for some reason missing the registry entries for that fix. I did a test and deleted the KB958483 reg entries from my x86 system and manually executed KB958483 and it put back the detection reg entries that I deleted. AP shows KB958483 as blue. I can't say why these registry entires are missing in x64. They may have been incorrectly deleted during one of the WU .NET updates. I have seen WU do this at times for other .NET fixes.
KB958483 had 2 files replaced by KB2604110 and KB2756918, but one file (Wpfgfx_v0300.dll) was not replaced so this fix should still be valid.
Edited by click-click, 18 February 2013 - 11:57 AM.
Posted 18 February 2013 - 12:03 PM
I quoted what DesertJerry had posted in Windows XP x64 thread so that you could provide the information.
Posted 18 February 2013 - 12:08 PM
Posted 18 February 2013 - 10:24 PM
Searched my system and found the following newer versions:
System.ServiceModel.dll = 3.0.4506.4037
PresentationFramework.dll = 3.0.6920.4021
wpfgfx_v0300.dll = 3.0.6920.1500
Posted 18 February 2013 - 11:03 PM
Edited by click-click, 18 February 2013 - 11:04 PM.
Posted 05 March 2013 - 09:47 AM
Edited by click-click, 05 March 2013 - 09:50 AM.
Posted 24 March 2013 - 10:04 AM
Module '.Net Framework 1.1' (unique id: 'DOTNET1_PARENT') reports 'WINDOWS_COMPONENTS_PARENT' as its parent, but such module does not exist or is not loaded in the right order.
Module 'Microsoft .NET Framework Version 1.1 Redistributable Package' (unique id: 'dotnetfx') reports 'DOTNET1_PARENT' as its parent, but such module does not exist or is not loaded in the right order.
Module 'Microsoft .NET Framework 1.1 Service Pack 1 (KB867460)' (unique id: 'NDP1.1sp1-KB867460-X86') reports 'DOTNET1_PARENT' as its parent, but such module does not exist or is not loaded in the right order.
Module 'Security Update for Microsoft .NET Framework 1.1 SP1 on XP, Server 2003 (64-bit), Vista, and Server 2008 (KB2742597)' (unique id: 'NDP1.1sp1-KB2742597-X86') reports 'DOTNET1_PARENT' as its parent, but such module does not exist or is not loaded in the right order.
Though I would bring it to your attention.
Posted 24 March 2013 - 07:42 PM
Edited by ViroMan, 24 March 2013 - 07:43 PM.
Posted 24 March 2013 - 11:10 PM
On Vista, I have dotNET1.1 installed and do not see any messages related to it, so I don't know why WAC is seeing those.
Edited by click-click, 24 March 2013 - 11:13 PM.
Posted 25 March 2013 - 06:10 AM
Of course to my editing of the apms my ap now displays .NET as Unofficial...my problem..
Posted 28 May 2013 - 08:40 PM
channels such as Windows Update or the Microsoft Download Center for dotNET updates for
the time being. Thanks for understanding.
Posted 22 July 2013 - 12:42 PM
dotNET has been refreshed to include updates from May, June, July
+ = Added - = Removed @ = Updated May - June +KB2804576 +KB2804577 +KB2804579 +KB2804580 +KB2804582 (+KB2805221 +KB2805226 -KB2750147 -KB2789648 -KB2804582) +KB2836939 +KB2836940 +KB2836941 +KB2836942 +KB2836943 @KB2656411 @KB2729452 @KB2736422 @KB2750147 July @KB2836942 +KB2832407 +KB2832411 -KB2604110 -KB2656407 +KB2832412 +KB2832414 +KB2833940 +KB2833941 -KB2742597 +KB2833946 +KB2833947 +KB2833957 +KB2835393 +KB2835622 +KB2840628 +KB2840629 +KB2840631 +KB2840642 +KB2844285 +KB2844286 +KB2844287
Posted 15 August 2013 - 07:58 AM
The scripts for these versions are no longer current and selecting them will not process anything since I moved them and they cannot be found. APUP will just say 'finished' without an error message, but if the scripts had been there and downloaded, they would have overwritten the users current Autopatcher dotNET.
This may not be the only addon that has been "broken" in that list, but I'll leave that to be determined by the person that updated it .
Edited by click-click, 15 August 2013 - 05:56 PM.
Posted 17 August 2013 - 09:17 AM
dotNET has been updated for August to include v2 updates.
+ = Added - = Removed @ = Updated @KB2836939 @KB2840628 @KB2840642 @KB2844285 @KB2844286 @KB2844287
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users