AutoPatcher Forum

wow.

dotNET updated for January.

+ = 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

dotNET updated for February.

+ = Added - = Removed @ = Updated
+KB2789642 +KB2789643 +KB2789645 +KB2789646 +KB2789648

DesertJerry, on 18 February 2013 - 05:27 AM, said:

Reported in Windows XP x64 thread.
One for you click-click

WAC, we talked about this before. The files and versions below pertain to KB958483

System.ServiceModel.dll	 3.0.4506.2254
Wpfgfx_v0300.dll	  3.0.6920.1500
PresentationFramework.dll 3.0.6920.1500

If 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.

I apologize for this..as you can see it was not me that reported it, I remember some of this from the PM's and unfortunately as you know I deleted them so was unable to look over the information you provided.

I quoted what DesertJerry had posted in Windows XP x64 thread so that you could provide the information.

No need for apologies. I do tend to sound grumpy sometimes. I'll point DJ here.

XP Pro x64 > AutoPatcher
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

As I said previously, "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". wpfgfx_v0300.dll = 3.0.6920.1500 is not new
Edited by click-click, 18 February 2013 - 11:04 PM.

Should this one be added? Hotfix rollup KB2803754

http://support.micro....com/kb/2803754

No. It's a hotfix that needs to be requested. We don't normally do hotfixes.
Edited by click-click, 05 March 2013 - 09:50 AM.

Was running autopatcher the other day and noticed the log file was larger than expected...upon investigation noticed this in the log..

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.

Might help a bit more if you said what you had in the modules dir with the .NET since some other things need that parent as well. Was this your AIO? If its just .NET then its probably something just for CC to fix otherwise there may be more then one problem.
Edited by ViroMan, 24 March 2013 - 07:43 PM.

I'm not sure if this is really an error - at least AP doesn't flag it that way. I see the same thing for DOTNET4_PARENT on Win7/Vista, but I think this has to do with 4.0 being suppressed if 4.5 is installed. If you only have 4.0 installed, you will not see these type of messages.

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.

Upon further investigation to this matter, this all relates to the AIO apup/ap I have, noticed that DotNET 1.1 was not displayed (OS is Windows XP x64), so shuffled the release dates of the the parent apms reran autopatcher and voila the errors disappeared, .NET 1.1 has also reappeared. It seems there is a clash somewhere with the All In One pertaining to the release dates of the parent apms...
Of course to my editing of the apms my ap now displays .NET as Unofficial...my problem..