Addons All dotNet Frameworks NL (2014-02)
- bartgrefte
- Posts: 153
- Joined: Thu May 18, 2006 3:43 pm
I just switched to the addon without v4.
Let's start with that KB2539631 (for v2) does not seem to be in there, is the addon without v4 on hold as well like the one with v4?
Now something new about v4: it installs just fine through MSU, including those pain in the *** updates
. Plus they did not stay visible on MSU anymore as if they where never installed, that was the case before.
So... have the updates been fixed by MS or is there something else that solved it? The only thing I did was switch to the addon without v4 in it.
Not sure if it helps, but went like this:
I installed Microsoft.Net_1.1SP1+3.5SP1_NL_Addon_20110724 with a batch after XP was installed and completely booted up for the 1st time, after the addon was installed the batch did a reboot.
Then I ran MSU three times without reboots in between.
(edit: Just now tried it again, didn't had the IE8 pack slipstreamed yet, now MSU says rebooting is required, weird. Everything still goes okay though.)
1st MSU scan for new updates:
KB982670 (FW4 installer)
2nd MSU scan for new updates:
KB2478663
KB2518870
KB2533523
KB2468871
3rd MSU scan for new updates:
KB2539636
Done, everything installed just fine and no more FW4 updates on MSU.
Screenshot of history: http://www.ravenslair.nl/plaatjes/fw4-updates.jpg
Let's start with that KB2539631 (for v2) does not seem to be in there, is the addon without v4 on hold as well like the one with v4?

Now something new about v4: it installs just fine through MSU, including those pain in the *** updates

So... have the updates been fixed by MS or is there something else that solved it? The only thing I did was switch to the addon without v4 in it.
Not sure if it helps, but went like this:
I installed Microsoft.Net_1.1SP1+3.5SP1_NL_Addon_20110724 with a batch after XP was installed and completely booted up for the 1st time, after the addon was installed the batch did a reboot.
Then I ran MSU three times without reboots in between.
(edit: Just now tried it again, didn't had the IE8 pack slipstreamed yet, now MSU says rebooting is required, weird. Everything still goes okay though.)
1st MSU scan for new updates:
KB982670 (FW4 installer)
2nd MSU scan for new updates:
KB2478663
KB2518870
KB2533523
KB2468871
3rd MSU scan for new updates:
KB2539636
Done, everything installed just fine and no more FW4 updates on MSU.
Screenshot of history: http://www.ravenslair.nl/plaatjes/fw4-updates.jpg
bartgrefte,
Nothing new; still exactly the issue explained in the thread of my Sep. 04 post.
The AIO_Addon with dotNET4 is full patched; only detection by MSU isn't working.
The most weird is that the faulty detection is triggered by the langpack and that
even more weird these updates DO NOT apply to the langpack.
You can see this if you install the DNF4Core (from the SFX) without langpack.
But using the AIO_Addon will install full patched Frameworks (dNET4 aswell).
You can hide the returning updates in MSU.
Nothing new; still exactly the issue explained in the thread of my Sep. 04 post.
The AIO_Addon with dotNET4 is full patched; only detection by MSU isn't working.
The most weird is that the faulty detection is triggered by the langpack and that
even more weird these updates DO NOT apply to the langpack.
You can see this if you install the DNF4Core (from the SFX) without langpack.
But using the AIO_Addon will install full patched Frameworks (dNET4 aswell).
You can hide the returning updates in MSU.
- bartgrefte
- Posts: 153
- Joined: Thu May 18, 2006 3:43 pm
Weird indeed.
But why does a clean install of v4 (incl updates) install without problems and does not have the faulty detection?
.... KB2539636 has a 4th version according to http://www.microsoft.com/downloads/nl-n ... bba12827c8 , is this one a newer one than you've integrated in the pack?
edit: kb982670 (fw4 installer) has had a recent update according to MS Catalog, http://catalog.update.microsoft.com/v7/ ... 82670%20xp , last modification/update 26-9-2011.
And the rest:
KB2478663: 12-7-2011
KB2518870: 18-7-2011
KB2533523: 12-9-2011
KB2468871: 12-9-2011
KB2539636: 22-9-2011
ps. why is Microsoft.Net_1.1SP1+3.5SP2_NL_Addon_20110819.cab not in the startpost? Is there something wrong with that one as well? I thought only v4 had issues.
But why does a clean install of v4 (incl updates) install without problems and does not have the faulty detection?
.... KB2539636 has a 4th version according to http://www.microsoft.com/downloads/nl-n ... bba12827c8 , is this one a newer one than you've integrated in the pack?
edit: kb982670 (fw4 installer) has had a recent update according to MS Catalog, http://catalog.update.microsoft.com/v7/ ... 82670%20xp , last modification/update 26-9-2011.
And the rest:
KB2478663: 12-7-2011
KB2518870: 18-7-2011
KB2533523: 12-9-2011
KB2468871: 12-9-2011
KB2539636: 22-9-2011
ps. why is Microsoft.Net_1.1SP1+3.5SP2_NL_Addon_20110819.cab not in the startpost? Is there something wrong with that one as well? I thought only v4 had issues.
There is no newer KB2539636 version untill now; only MS changed detection in MSU.
But this is still not solving XP detection for admin install group policy mode.
This is the way these addons are compiled (=same as WSUS enterprise deployment)
Same goes for the other updates...
But as explained before, the issue is triggered by the langpack; without it no probs.
So there must be somewhere some reg.entries changed in the langpack by the updates.
(This because Framework+langpack is supposed to be installed before the patches.)
I'll be looking into it again later (whenever I find some freetime)
No issues with Microsoft.Net_1.1SP1+3.5SP2_NL_Addon_20110819.cab.
Just wanted to post both addons together to first post.
But this is still not solving XP detection for admin install group policy mode.
This is the way these addons are compiled (=same as WSUS enterprise deployment)
Same goes for the other updates...
But as explained before, the issue is triggered by the langpack; without it no probs.
So there must be somewhere some reg.entries changed in the langpack by the updates.
(This because Framework+langpack is supposed to be installed before the patches.)
I'll be looking into it again later (whenever I find some freetime)
No issues with Microsoft.Net_1.1SP1+3.5SP2_NL_Addon_20110819.cab.
Just wanted to post both addons together to first post.
Back in June DN4langpack needed KB2478663 and admin patch worked.yumeyao wrote:That's because language pack needs those (problematic) updates too. So you may need to add registry (like I do in .NET 2.0) to satisfy WU.
Now with the August hotfixes I get the message that they don't apply.
I will download them again from the webpage of Dutch hotfixes and see.
(I thought they are language independant, as was KB2478663 in June)
- bartgrefte
- Posts: 153
- Joined: Thu May 18, 2006 3:43 pm
Was updated a LONG time ago: see post of april 02, 2011Pegasos wrote:Can you please update VC2008 to sp1
and already patched twice for current addon versions.
Latest Addons patched: Microsoft Security Bulletin MS11-078 - Critical Vulnerability
in .NET Framework and Microsoft Silverlight Could Allow Remote Code Execution
Microsoft.Net_Framework.AIO_NL_Addon_20111030.cab
Microsoft.Net_1.1SP1+3.5SP2_NL_Addon_20111023.cab
posted on oct. 23, 2011
Last edited by jaynbe on Sat May 12, 2012 1:04 pm, edited 1 time in total.
I dont know what the problem is but try to install MediaPortal http://www.team-mediaportal.com/ it will tell you it's not.
Was updated a LONG time ago: see post of april 02, 2011
and already patched twice for current addon versions.
Maybe Mediaportal requires this specific older version.Pegasos wrote:
I dont know what the problem is but try to install MediaPortal http://www.team-mediaportal.com/ it will tell you it's not.
Here you can download an addon for this VC89+ATL that
can be integrated side by side with the newer versions:
http://www.mediafire.com/download.php?wg59tnwcw5a0p65
There is even an addon for Mediaportal here:
http://www.ryanvm.net/forum/viewtopic.php?t=8735
Addons for .NET and VC89++ have to be integrated FIRST.
Thanks jaynbe, I will try the older version and report later.jaynbe wrote:
Maybe Mediaportal requires this specific older version.
Here you can download an addon for this VC89+ATL that
can be integrated side by side with the newer versions:
http://www.mediafire.com/download.php?wg59tnwcw5a0p65
There is even an addon for Mediaportal here:
http://www.ryanvm.net/forum/viewtopic.php?t=8735
Addons for .NET and VC89++ have to be integrated FIRST.
Microsoft.Net All Frameworks in one
After integrating the "Microsoft.Net All Frameworks in one" pack 23-10-2011 i still get this update: KB2533523 this is released 13-9-2011 or this one: KB2539636 released 23-8-2011.
Maybe i'm doing something wrong but i tried it several times.
Maybe i'm doing something wrong but i tried it several times.
- bartgrefte
- Posts: 153
- Joined: Thu May 18, 2006 3:43 pm
I can confirm the above report, also seeing those updates, plus some new ones released after last FW addon.
edit: In addition to that, after letting MS Update do it's job, a bunch of updates remain visible even though they have been installed.
These are all updates available after using the last addon:
*KB2539636: Security update for Microsoft .NET Framework 4
*KB2533523: Update for Microsoft .NET Framework 4
*KB2572078: Security update for Microsoft .NET Framework 4
**KB2518870: Security update for Microsoft .NET Framework 4
*KB2656351: Security update for Microsoft .NET Framework 4
*KB2657424: Security update for Microsoft .NET Framework 3.5 SP1
KB2656353: Security update for Microsoft .NET Framework 1.1 SP1
KB2656352: Security update for Microsoft .NET Framework 2.0 SP2
The ones with a * are the updates that remain visible after succesfully (or so MS Update claims) installing them. The one with ** failed to install, code 0x66A.
And to make things weird, all of those (including the one that failed to install from MSU) are shown as installed in XP's add/remove programs/updates list.
edit: In addition to that, after letting MS Update do it's job, a bunch of updates remain visible even though they have been installed.
These are all updates available after using the last addon:
*KB2539636: Security update for Microsoft .NET Framework 4
*KB2533523: Update for Microsoft .NET Framework 4
*KB2572078: Security update for Microsoft .NET Framework 4
**KB2518870: Security update for Microsoft .NET Framework 4
*KB2656351: Security update for Microsoft .NET Framework 4
*KB2657424: Security update for Microsoft .NET Framework 3.5 SP1
KB2656353: Security update for Microsoft .NET Framework 1.1 SP1
KB2656352: Security update for Microsoft .NET Framework 2.0 SP2
The ones with a * are the updates that remain visible after succesfully (or so MS Update claims) installing them. The one with ** failed to install, code 0x66A.
And to make things weird, all of those (including the one that failed to install from MSU) are shown as installed in XP's add/remove programs/updates list.
bartgrefte,
The last 4 are new updates posted 20111231 and not yet included in the addons.
The first 4 are older updates included in the addons, but not detected by MU.
Microsoft changed last august detection schemes for dotNET by checking regfiles.
Each time a new update is installed this causes overwriting regfiles and also
newer regfiles missing for detection. (and somethimes missing in the update)
This has already been explained and posted several times above.
When the last 4 updates are installed the dotNET Frameworks are fully updated.
You can hide (or ignore) the remaining (false) MU nags.
For KB2657424 you can add following regfile to correct the missing reg:
Microsoft.Net_1.1SP1+3.5SP1_NL_Addon_20120207.cab
The last 4 are new updates posted 20111231 and not yet included in the addons.
The first 4 are older updates included in the addons, but not detected by MU.
Microsoft changed last august detection schemes for dotNET by checking regfiles.
Each time a new update is installed this causes overwriting regfiles and also
newer regfiles missing for detection. (and somethimes missing in the update)
This has already been explained and posted several times above.
When the last 4 updates are installed the dotNET Frameworks are fully updated.
You can hide (or ignore) the remaining (false) MU nags.
For KB2657424 you can add following regfile to correct the missing reg:
Code: Select all
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 SP1\SP1\KB2657424]
"ReleaseType"="Security Update"
"PublishingGroup"="Developer Division"
"Publisher"="Microsoft Corporation"
"PackageVersion"="1"
"PackageName"="Security Update for Microsoft .NET Framework 3.5 Service Pack 1 (KB2657424)"
"InstallerVersion"="4.05"
"InstallerName"="Windows Installer"
"BuildLab"="LDR"
"ThisVersionInstalled"="Y"
Microsoft.Net_1.1SP1+3.5SP1_NL_Addon_20120207.cab
Last edited by jaynbe on Sat May 12, 2012 1:03 pm, edited 1 time in total.
- bartgrefte
- Posts: 153
- Joined: Thu May 18, 2006 3:43 pm
Okay, so this is the same problem as before, didn't think of that
Well, since someone requested an uptodate XP disc and I didn't want him to wait I did it differently. I've downloaded all .NET Framework updates that MSU offers and made a batch that silently installs everything. This made the XP installation disc about 400MB larger, but it already didn't fit on a cd anymore so this is not a problem.
Just out of curiosity, will this problem return with every new .NET Framework update if the addon is used?

Well, since someone requested an uptodate XP disc and I didn't want him to wait I did it differently. I've downloaded all .NET Framework updates that MSU offers and made a batch that silently installs everything. This made the XP installation disc about 400MB larger, but it already didn't fit on a cd anymore so this is not a problem.
Just out of curiosity, will this problem return with every new .NET Framework update if the addon is used?
Quote Microsoft to answer your question:
Deployment Information for Windows XP
Registry Key Verification:
These registry keys may not contain a complete list of installed files. Also, these
registry keys may not be created correctly when an administrator or an OEM integrates
or slipstreams this security update into the Windows installation source files.
- bartgrefte
- Posts: 153
- Joined: Thu May 18, 2006 3:43 pm
- alsyundawy
- Posts: 99
- Joined: Mon Jun 28, 2010 5:47 pm
Updated dotNET Frameworks with 05-2012 security hotfixes.
For updating older dotNET Addons in running systems add this reg.
Same issue with update KB2604111 as previously with KB2657424:
The update installs correctly, but MU doesn't detect it as installed:
For updating older dotNET Addons in running systems add this reg.
Same issue with update KB2604111 as previously with KB2657424:
The update installs correctly, but MU doesn't detect it as installed:
Code: Select all
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 SP1\SP1\KB2657424]
"ReleaseType"="Security Update"
"PublishingGroup"="Developer Division"
"Publisher"="Microsoft Corporation"
"PackageVersion"="1"
"PackageName"="Security Update for Microsoft .NET Framework 3.5 Service Pack 1 (KB2657424)"
"InstallerVersion"="4.05"
"InstallerName"="Windows Installer"
"BuildLab"="LDR"
"ThisVersionInstalled"="Y"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 SP1\SP1\2604111]
"ReleaseType"="Security Update"
"PublishingGroup"="Developer Division"
"Publisher"="Microsoft Corporation"
"PackageVersion"="1"
"PackageName"="Security Update for Microsoft .NET Framework 3.5 Service Pack 1 (2604111)"
"InstallerVersion"="4.05"
"InstallerName"="Windows Installer"
"BuildLab"="LDR"
"ThisVersionInstalled"="Y"
Re: Addons All dotNet Frameworks NL (2012-06)
Updated dotNET Frameworks with 06-2012 security hotfixes.
Fixed MU security updates detection for dNET4.
DNF11-KB2656370v2 - Vulnerability in .NET Framework Could Allow Remote Code Execution
DNF20-KB2656369v2 - Vulnerability in .NET Framework Could Allow Remote Code Execution
DNF20-KB2686828 - Vulnerability in .NET Framework Could Allow Remote Code Execution
DNF40-KB2656368v2 - Vulnerability in .NET Framework Could Allow Remote Code Execution
DNF40-KB2686827 - Vulnerability in .NET Framework Could Allow Remote Code Execution
Fixed MU security updates detection for dNET4.
DNF11-KB2656370v2 - Vulnerability in .NET Framework Could Allow Remote Code Execution
DNF20-KB2656369v2 - Vulnerability in .NET Framework Could Allow Remote Code Execution
DNF20-KB2686828 - Vulnerability in .NET Framework Could Allow Remote Code Execution
DNF40-KB2656368v2 - Vulnerability in .NET Framework Could Allow Remote Code Execution
DNF40-KB2686827 - Vulnerability in .NET Framework Could Allow Remote Code Execution
Updated dotNET Frameworks with MS12-074 security hotfixes.
Fixed MU security updates detection for dNET4.
NDP1.1sp1-KB2698023 - Vulnerability in .NET Framework Could Allow Remote Code Execution
NDP20SP2-KB2729450 - Vulnerability in .NET Framework Could Allow Remote Code Execution
NDP40-KB2729449 - Vulnerability in .NET Framework Could Allow Remote Code Execution
NDP40-KB2737019 - Vulnerability in .NET Framework Could Allow Remote Code Execution
Fixed MU security updates detection for dNET4.
NDP1.1sp1-KB2698023 - Vulnerability in .NET Framework Could Allow Remote Code Execution
NDP20SP2-KB2729450 - Vulnerability in .NET Framework Could Allow Remote Code Execution
NDP40-KB2729449 - Vulnerability in .NET Framework Could Allow Remote Code Execution
NDP40-KB2737019 - Vulnerability in .NET Framework Could Allow Remote Code Execution
Download Url. removed for Microsoft.Net_Framework.AIO_NL_Addon_20121117.cab
See: http://www.ryanvm.net/forum/viewtopic.php?t=9901
EDIT: Renamed and reuploaded to GE.TT:
Microsoft.Net_Framework.5IO_NL_Addon_20121117.cab
See: http://www.ryanvm.net/forum/viewtopic.php?t=9901
EDIT: Renamed and reuploaded to GE.TT:
Microsoft.Net_Framework.5IO_NL_Addon_20121117.cab
- Atari800xl
- Posts: 345
- Joined: Sun Dec 30, 2012 5:46 pm
- Location: NL
Thank you very much!!! I only recently learned how to make my own updated XP iso, and this new pack is very much appreciated!! I'm building my latest XP iso now (if I'm doing something wrong/ stupid, please give me some tips):
- Use RyanVMi on MSDN-XPSP3, add latest Dutch update pack, add noError IE8 and this new dotNet1.1-3.5
- Use nLite to remove (only a few) components and add latest hotfixes (kb2758694, kb2761465, kb2727528, kb2753842, kb2757638, kb2758857, kb2770660, kb2779030, kb2779562)
- Use DPBase to add MassStorage drivers
- Use Ultraiso to add i386 and $oem$\$1 to a "base" bootable XP.iso and remove i386\lang folder
- Use WinNTSetup to install from WinPE_SE USB (also has w7 and w8 setup), select appropriate WINNT.SIF.
Thank you everybody for teaching me about this wonderful stuff!!! I never thought I would learn how to do this!
(OK, so I'm a little late to this game, but better late than never)
- Use RyanVMi on MSDN-XPSP3, add latest Dutch update pack, add noError IE8 and this new dotNet1.1-3.5
- Use nLite to remove (only a few) components and add latest hotfixes (kb2758694, kb2761465, kb2727528, kb2753842, kb2757638, kb2758857, kb2770660, kb2779030, kb2779562)
- Use DPBase to add MassStorage drivers
- Use Ultraiso to add i386 and $oem$\$1 to a "base" bootable XP.iso and remove i386\lang folder
- Use WinNTSetup to install from WinPE_SE USB (also has w7 and w8 setup), select appropriate WINNT.SIF.
Thank you everybody for teaching me about this wonderful stuff!!! I never thought I would learn how to do this!
(OK, so I'm a little late to this game, but better late than never)
-
- Posts: 9
- Joined: Fri Nov 06, 2009 1:01 pm
First of all, thanks for the new releases of the .net updatepacks.
I have used ryan's integrator to integrate the .net all in one pack but after installing windows I still get 4 .net 4 updates. These updates fail
I only integrated the latest post sp3 spack, the No error IE8 pack and the .net AIO. What can I do?
I have used ryan's integrator to integrate the .net all in one pack but after installing windows I still get 4 .net 4 updates. These updates fail
