[Addon] Microsoft .NET Framework Family 3.5 SP1 - 20131008
- ricktendo64
- Posts: 3214
- Joined: Mon May 22, 2006 12:27 am
- Location: Honduras
Im trying to figure it out myself...first I thought that u_h had KB974065 same as me and thats why the update would fail.
But looks like the update will fail anyway...so I integrated the MU update into the msi then ran the MU update normally and it seems to install fine again even with KB974065 integrated (this is how I was able to finally get my regfix)
But looks like the update will fail anyway...so I integrated the MU update into the msi then ran the MU update normally and it seems to install fine again even with KB974065 integrated (this is how I was able to finally get my regfix)
- laddanator
- Posts: 131
- Joined: Thu Jan 17, 2008 9:26 pm
- Location: virginia
Error
Hey I used the 1.0.3 version on my last complete disc and now when I try to install KB974417 from microsoft it says None of the products that this update addresses is not installed on this pc but in add or remove I can see 2.0 sp2 is installed
"I'LL BE BACK"
Re: Error
Getting the same now too following the update on wednesday.laddanator wrote:Hey I used the 1.0.3 version on my last complete disc and now when I try to install KB974417 from microsoft it says None of the products that this update addresses is not installed on this pc but in add or remove I can see 2.0 sp2 is installed
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
compstuff wrote:I'm not having any luck at all but I will try the Beta and report back... thanks
some weirdness deffinately.
1.05 is fine but it seems MU still nags for KB974417.
although it is integrated into the main msi installer.
probably the same issue when we had to supress KB951847.
i am installing dotnet fully via MU and will check and see where the diff is.
i had to do the test on an old PIII800 so 3 hours later dotnet is still installing....holy cow !
issue will be found and solved.
- jamesbebby
- Posts: 161
- Joined: Fri Mar 13, 2009 10:32 am
- Kelsenellenelvian
- Moderator
- Posts: 4383
- Joined: Tue Nov 30, 2004 8:32 pm
- Location: Pocatello, ID
- Contact:
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
When I use your addon with driverpacks.net base I get some unexpected behavior. After windows installs and boots up for the first time I usually get the driverpacks.net finisher. Instead I see your installer. I never saw the finisher run. While your installer is running it says "Windows is now setting up the following items: Driverpacks.net finisher." This goes away when your installer finishes. I used method 2 for the finisher which uses runonceex. I'm sure I could fix this by using method 1 but then I won't get progress indicators and I like those.
Any suggestions?
Any suggestions?
- mr_smartepants
- Posts: 824
- Joined: Thu May 18, 2006 5:56 am
- Location: Cambridgeshire, UK
That's because this addon is conflicting with the DriverPacks ROE entry in cmdlines.txt.
Open your %source%\$OEM$\cmdlines.txt and %source%\I386\svcpack\add-NET-runonce.bat and compare the entries.
cmdlines.txt
"ROE.exe 100"
add-NET-runonce.bat
REG ADD %KEY%\100 /VE /D "Installing .NET All-In-One" /f
REG ADD %KEY%\100 /V 1 /D "%PP%\dotNet35SP1_1.03.exe -ai1" /f
Change the duplicate number (I used 100 as an example) in cmdlines.txt to a higher number (less than 999) than the .NET addon.
Open your %source%\$OEM$\cmdlines.txt and %source%\I386\svcpack\add-NET-runonce.bat and compare the entries.
cmdlines.txt
"ROE.exe 100"
add-NET-runonce.bat
REG ADD %KEY%\100 /VE /D "Installing .NET All-In-One" /f
REG ADD %KEY%\100 /V 1 /D "%PP%\dotNet35SP1_1.03.exe -ai1" /f
Change the duplicate number (I used 100 as an example) in cmdlines.txt to a higher number (less than 999) than the .NET addon.
Thanks I'll do that!mr_smartepants wrote:That's because this addon is conflicting with the DriverPacks ROE entry in cmdlines.txt.
Open your %source%\$OEM$\cmdlines.txt and %source%\I386\svcpack\add-NET-runonce.bat and compare the entries.
cmdlines.txt
"ROE.exe 100"
add-NET-runonce.bat
REG ADD %KEY%\100 /VE /D "Installing .NET All-In-One" /f
REG ADD %KEY%\100 /V 1 /D "%PP%\dotNet35SP1_1.03.exe -ai1" /f
Change the duplicate number (I used 100 as an example) in cmdlines.txt to a higher number (less than 999) than the .NET addon.
One more thing I noticed: You can't uninstall the framework. Is this intentional? Can updates still be applied without the installation source?
- DaRk MaDnEsS
- Posts: 168
- Joined: Fri Oct 10, 2008 4:15 pm
- Location: Port Said,Egypt
well if you extract the 7zip configRequi3m wrote:I didn't see that batch file in the svcpack folder. I think I'm just going to switch driverpacks back to GUIRunOnce and call it good.
you should be seeing that
but i think it's not recommended so the safe change the driver pack installer from 100 to something like 101 or 235 it would be hard to conflict then
the driverpacks one was set to 937. I doubt there was a conflict.DaRk MaDnEsS wrote:well if you extract the 7zip configRequi3m wrote:I didn't see that batch file in the svcpack folder. I think I'm just going to switch driverpacks back to GUIRunOnce and call it good.
you should be seeing that
but i think it's not recommended so the safe change the driver pack installer from 100 to something like 101 or 235 it would be hard to conflict then
I think I'm just going to use somebody else's .NET installer until user_hidden responds about the uninstallation thing. I already got owned by the last round of updates and I don't need it happening again. I couldn't apply the update, and I couldn't uninstall the framework to fix it either.
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
Requi3m wrote:I think I'm just going to use somebody else's .NET installer until user_hidden responds about the uninstallation thing. I already got owned by the last round of updates and I don't need it happening again. I couldn't apply the update, and I couldn't uninstall the framework to fix it either.
if you look at the first post of this thread at the end there are links i posted to some utilities by Aaron Stebner.
the first link is a .Net Cleanup Tool. to uinstall the .Net package use the tool
by uninstalling in this order: dotNet2.0SP2 > dotNet30SP2 > dotNet35SP1
i have tested the above MANY times.
- dumpydooby
- Posts: 530
- Joined: Sun Jan 15, 2006 6:09 am
- mr_smartepants
- Posts: 824
- Joined: Thu May 18, 2006 5:56 am
- Location: Cambridgeshire, UK
@user_hidden:user_hidden wrote:some weirdness deffinately.
1.05 is fine but it seems MU still nags for KB974417.
although it is integrated into the main msi installer.
probably the same issue when we had to supress KB951847.
i am installing dotnet fully via MU and will check and see where the diff is.
i had to do the test on an old PIII800 so 3 hours later dotnet is still installing....holy cow !
issue will be found and solved.
Have you had any time to follow up on the KB974417 issue - I have seen this arise as well - (LOL...like any of us have any time at all...

Thanks!
galileo
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
yup v1.06 in 1st post fixes KB974417 naggalileo wrote:
@user_hidden:
Have you had any time to follow up on the KB974417 issue - I have seen this arise as well - (LOL...like any of us have any time at all......)
Thanks!
galileo
if you used 1.05 and want the nag to go away just import the reg below:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\9E0DE89293FE9BB33898F24ED18CCF08]
"MSI3"=dword:00000001
"State"=dword:00000001
"LUAEnabled"=dword:00000000
"PatchType"=dword:00000000
"DisplayName"="KB974417"
"MoreInfoURL"="http://www.microsoft.com/"
I saw that I was just wondering if it was supposed to have the installer files or not. Why didn't the updates apply correctly and will they in the future?user_hidden wrote:Requi3m wrote:I think I'm just going to use somebody else's .NET installer until user_hidden responds about the uninstallation thing. I already got owned by the last round of updates and I don't need it happening again. I couldn't apply the update, and I couldn't uninstall the framework to fix it either.
if you look at the first post of this thread at the end there are links i posted to some utilities by Aaron Stebner.
the first link is a .Net Cleanup Tool. to uinstall the .Net package use the tool
by uninstalling in this order: dotNet2.0SP2 > dotNet30SP2 > dotNet35SP1
i have tested the above MANY times.
- laddanator
- Posts: 131
- Joined: Thu Jan 17, 2008 9:26 pm
- Location: virginia
Later updates
I really like this pack but my question is will this 1.0.6 effect future releases of the updated what I mean is every time a new framework update comes out I try to install it through WU and says the update does not apply because framewrok is not installed and I dont want to reload PC every time a new netframe work update comes out. Thanks for the addon just wondering.
"I'LL BE BACK"
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
i'll post the new version in the morning.compstuff wrote:Thats really great news user_hidden... your previous pack has been a basic requirement in all my CD's... thanks for all your work
i will also post a link in the 1st post to an EXE i made that will try and fix
versions pre 1.07 to enable the Uninstall via Add/Remove Programs.
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
- laddanator
- Posts: 131
- Joined: Thu Jan 17, 2008 9:26 pm
- Location: virginia
Future Updates
Will 1.0.7 allow future updates to install through MU and for kicks I am going to load this to virtual machine to see if KB974417 will reconize 2.0 SP2 being installed. Thanks for the release
"I'LL BE BACK"
- laddanator
- Posts: 131
- Joined: Thu Jan 17, 2008 9:26 pm
- Location: virginia
Good
Good deal glad to hear it I really like this packI just tried both in a VPC where I uninstalled all DOTNET and then installed 1.07 then checked MU... all seemed to work great. I will try a real system shortly
"I'LL BE BACK"
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
Re: Future Updates
YES even though KB974417 is integrated you can always install it again over itself. i tested after installing the full .net, i then downloaded KB974417 and ran the exe and it did the install and did recognize dotnet2 was there.laddanator wrote:Will 1.0.7 allow future updates to install through MU and for kicks I am going to load this to virtual machine to see if KB974417 will reconize 2.0 SP2 being installed. Thanks for the release
as for MU it works now but one can never forcast what snafus MS may serve up.
interested as well to know if the util i posted gave you access to uninstall the dotnet that you were locked out of before.
Tested the pack again on real hardware and it ran just great... one question:if you get nagged by MU/WU for KB961118 and/or KB971314 use my Post-SP3 update pack
or one that does include them. XPSP3_QFE_UpdatePack for Windows XP Post-SP3 (user_hidden)
I install KB971314 via runonceex at the end of my install but when I do a MU it shows KB961118 is needed. Is there any other way around this besides changing over to a different update pack OR using a 2nd step of nLite to slipstream it? THANKS
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
you need both updates to supress MU.compstuff wrote:Tested the pack again on real hardware and it ran just great... one question:if you get nagged by MU/WU for KB961118 and/or KB971314 use my Post-SP3 update pack
or one that does include them. XPSP3_QFE_UpdatePack for Windows XP Post-SP3 (user_hidden)
I install KB971314 via runonceex at the end of my install but when I do a MU it shows KB961118 is needed. Is there any other way around this besides changing over to a different update pack OR using a 2nd step of nLite to slipstream it? THANKS
my postSP3 update pack has both updates included.
if you don't want to use my update pack than nlite to run both at ROE would be your choice.
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
at least my update pack only includes KB971314 and it works well. don't know why you still need kb961118.user_hidden wrote:you need both updates to supress MU.compstuff wrote:Tested the pack again on real hardware and it ran just great... one question:if you get nagged by MU/WU for KB961118 and/or KB971314 use my Post-SP3 update pack
or one that does include them. XPSP3_QFE_UpdatePack for Windows XP Post-SP3 (user_hidden)
I install KB971314 via runonceex at the end of my install but when I do a MU it shows KB961118 is needed. Is there any other way around this besides changing over to a different update pack OR using a 2nd step of nLite to slipstream it? THANKS
my postSP3 update pack has both updates included.
if you don't want to use my update pack than nlite to run both at ROE would be your choice.
@imer
You probably integrated the 'switchless' installer (dotNet35SP1_1.07.exe) as a svcpack addon.
You should download/use the Addon_Microsoft.Net_Family.35SP1_ROE_1.07
You probably integrated the 'switchless' installer (dotNet35SP1_1.07.exe) as a svcpack addon.
You should download/use the Addon_Microsoft.Net_Family.35SP1_ROE_1.07
@Stefhan
here's my RVMI log..
here's my RVMI log..
Code: Select all
2009-11-02_19.12.01
Log Startup @ 19:12:01 local time, on November 02, 2009.
Running OS: WIN_VISTA X86
RVMIntegrator v1.6
"D:\RVMI\RVM_Integrator_1.6.exe"
19:12:14 - English - Windows XP Professional x86 - Corporate SP3 Found
19:13:21 -
19:13:21 - Source Drive = D:\GRTMPVOL_EN
19:13:21 - Destination Drive = D:\GRTMPVOL_EN
19:13:21 - Destination Size = 43.71 GB
19:13:21 - Working Directory = D:\GRTMPVOL_EN\I386
19:13:21 - Temp Directory = D:\GRTMPVOL_EN\I386\rvmtemp
19:13:21 -
19:13:21 - Starting Integration
19:13:21 -
19:13:21 - Checking Destination For OS Type.
19:13:21 - English - Windows XP Professional x86 - Corporate SP3 Found
19:13:21 -
19:13:21 - Extracting Addon_Microsoft.Net_Family.35SP1_ROE_1.07.7z
19:13:27 - MD5 Hash = fae4093a26b45d29c33ae18a49027d3d
19:13:27 - Clearing any Read Only Attributes.
19:13:27 -
19:13:27 - Gathering temp files
19:13:27 - Shifting Stuff Around
19:13:27 - 3 Files Moved in 0 Seconds
19:13:27 - Analyzing 1 Entry Files
19:13:27 - Processing Microsoft dotNet Family Framework 3.5 SP1 v3.5.30729.1-1.07 (-ai1 -> passive) Build Date: 10/20/2009
19:13:27 - Gathering Sysoc Entries
19:13:27 - Gathering Dosnet.inf [Files] Entries
19:13:27 - Gathering txtsetup.sif [SourceDisksFiles] and [WinntDirectories] Entries
19:13:28 -
19:13:28 - Preparing System Files...
19:13:28 - sysoc.inf
19:13:28 - svcpack.inf
19:13:28 - dosnet.inf
19:13:28 - txtsetup.sif
19:13:29 -
19:13:29 - Processing Sysoc.inf
19:13:29 - Adding Components
19:13:29 - Processing svcpack.inf
19:13:29 - Processing dosnet.inf
19:13:29 - Editing [Files]
19:13:30 - Processing txtsetup.sif
19:13:30 - Editing [SourceDisksFiles]
19:13:33 -
19:13:34 - Compressing Files ASMS...
19:13:41 -
19:13:41 -
19:13:41 - Entire .ini Processing Completed in 13 Seconds
19:13:41 -
19:13:41 - Compressing and Moving Edited Files
19:13:41 -
19:13:41 - Optimizing System Files.
19:13:42 - Combining dosnet.inf - [Files]
19:13:44 - Optimizing dosnet.inf - [Files]
19:13:45 - Combining dosnet.inf - [FloppyFiles.0]
19:13:46 - Optimizing dosnet.inf - [FloppyFiles.0]
19:13:47 - Combining dosnet.inf - [FloppyFiles.1]
19:13:48 - Optimizing dosnet.inf - [FloppyFiles.1]
19:13:49 - Combining dosnet.inf - [FloppyFiles.2]
19:13:49 - Optimizing dosnet.inf - [FloppyFiles.2]
19:13:50 - Combining dosnet.inf - [FloppyFiles.3]
19:13:51 - Optimizing dosnet.inf - [FloppyFiles.3]
19:13:52 - Combining dosnet.inf - [FloppyFiles.x]
19:13:53 - Optimizing dosnet.inf - [FloppyFiles.x]
19:13:54 - Combining txtsetup.sif - [SourceDisksFiles]
19:13:55 - Optimizing txtsetup.sif - [SourceDisksFiles]
19:13:57 - Combining txtsetup.sif - [SourceDisksFiles.ia64]
19:13:57 - Optimizing txtsetup.sif - [SourceDisksFiles.ia64]
19:13:58 - Combining txtsetup.sif - [SourceDisksFiles.amd64]
19:13:58 - Optimizing txtsetup.sif - [SourceDisksFiles.amd64]
19:13:59 - Combining txtsetup.sif - [SourceDisksFiles.x86]
19:14:00 - Optimizing txtsetup.sif - [SourceDisksFiles.x86]
19:14:01 - Optimizing txtsetup.sif - [WinntDirectories]
19:14:01 - Optimizing txtsetup.sif - [FileFlags]
19:14:02 -
19:14:02 - Scanning I386 for other files to compress...
19:14:32 - Compressing Files I386...
19:14:57 - Optimizing System Files Finished In: 75 Seconds.
19:14:57 -
19:14:57 - Cleaning Up.
19:14:58 - Integration Completed.
19:14:58 - Total Integration Time = 96 Seconds
19:14:58 - ==================================================================================
19:14:58 -
Log Shutdown @ 2009-11-02 19:15:55 local time.
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
this is my steps when integrating... please CMIIW :
- fresh image untouched winxp sp3 corporate
- using nlite, integrating xable updatepack, onepiece IE8 + WM11
- using RVMI integrating NET framework 3.5
- integrating driverpacks
- using RVMI to create ISO
tried to integrating driverpacks first then NET framework getting same error
BUT, it seems NET framework installation is OK...
- fresh image untouched winxp sp3 corporate
- using nlite, integrating xable updatepack, onepiece IE8 + WM11
- using RVMI integrating NET framework 3.5
- integrating driverpacks
- using RVMI to create ISO
tried to integrating driverpacks first then NET framework getting same error
BUT, it seems NET framework installation is OK...
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
driver pack MUST be installed LAST this may be part of your issueimer wrote:this is my steps when integrating... please CMIIW :
- fresh image untouched winxp sp3 corporate
- using nlite, integrating xable updatepack, onepiece IE8 + WM11
- using RVMI integrating NET framework 3.5
- integrating driverpacks
- using RVMI to create ISO
tried to integrating driverpacks first then NET framework getting same error
BUT, it seems NET framework installation is OK...
as it maybe conflicting with the ROE of the .net
mr. smatepants is the man for driver packs so if he sees this he can
explain more.
- dareckibmw
- Posts: 15
- Joined: Thu Apr 26, 2007 2:58 am
- Location: Chicago, Illinois
- mr_smartepants
- Posts: 824
- Joined: Thu May 18, 2006 5:56 am
- Location: Cambridgeshire, UK
I'm confused by your post, are you saying that by using the above steps, in that order, works? Or not?imer wrote:this is my steps when integrating... please CMIIW :
- fresh image untouched winxp sp3 corporate
- using nlite, integrating xable updatepack, onepiece IE8 + WM11
- using RVMI integrating NET framework 3.5
- integrating driverpacks
- using RVMI to create ISO
It's possible that Xable's updatepack is missing/modifying something that .NET is relying on. Try User_Hidden's updatepack.
Driverpacks should always be integrated last and here's why:
- Driverpacks BASE will backup core source files before modification (dosnet.inf, txtsetup.sif, winnt.sif, setup.exe, etc.)
- Driverpacks BASE will then modify those files to support the extraction/installation during XP setup (extraction before T-39, installation between T-37 & T-33.)
- If you decide to remove Driverpacks from your source, simply re-run BASE and uncheck all Driverpacks at the selection page. BASE will then clean up after itself and restore the backed-up core files to their original state.
If you integrate an addon AFTER Driverpacks, you run the risk of corrupting your source if you later remove Driverpacks.
That's why Driverpacks are last.
But there is my situation (I dont need driver pack removal):mr_smartepants wrote:Driverpacks should always be integrated last
1) all the integrations & removals
2) DP_BASE
3) clean up source from *.org files
4) integrate dummy (empty) addon or something harmless (for me its ENU_User BVProSvcDesc) via RVMi & Optimize system files = On
5) integrate ENU_User SpeedUp post DPMS with Optimize system files = Off