Microsoft .Net Framework 3.5 SP1 KB951847

So, Microsoft Releases .Net 3.5 SP1 and you cant install it?

The .NET Setup Exe Required, Windows Installer 3.1  OR higher.
Recommended (as of now) is Windows installer 4.5 which is WindowsXP-KB942288-v3-x86.exe.
Make sure you select the correct windows installer EXE file.
"KB942288-v3" Is the third version of  Installer v4.5.

Keep reading if it wont install, because the solution is here !

The .NET 3.5 SP1 Downloads:
Microsoft .NET Framework 3.5 SP1 Full Redist x86 / x64 (complete developers package)  231.49mb
Microsoft .NET Framework 3.5 SP1 Client x86 (the for general windows users) 52.3mb
Microsoft .NET Framework 3.5 SP1 Client x64 (the for general windows users) 95.4mb 
Microsoft .NET Framework 3.5 SP1 Bootstrap Install x86 / x64 (online installer ) 2.8mb to  231.49mb

The green one is probably the one you want if your just trying to use game trainers or use slipstreaming tools or ATi drivers written in .NET.  Even if your on an x64 machine the x86 Client will normally do. I could do with an official MS link to the 52.3mb file,

However, the link provided is the correct file,  It's digital signature date is the ‎27 ‎February ‎2009 signed at 02:39:45.

Microsoft .NET Framework 3.5 Service Pack 1 Wont Install ?

Tried to install a .NET 3.5 SP1 AKA KB951847  and it fails ?

Error
EventType : visualstudio8setup     P1 : 35101    
P2 : 3.5.30729.01_orcas_x86_net     P3 : pr     P4 : inst     P5 : f    
P6 : gencomp209     P7 : baseret_failure     P8 : -     P9 : 1603     P10 : -

Tried the firewall off suggestion seen on some sites to no avail, avoided the permissions advice on sites (as you Don't wish to change the permissions on C to all Users lmao...)

System32\WMPhoto.dll  Is the problem here...
BUT every online solution you read removes it, downgrades it or worse tells you to remove all traces of all versions.. Screw that....

 So.. MY Tidy Quick Solution...

Click Start, Run, Type CMD, Hit Enter

type
cd c:\WINDOWS\system32

then type
regsvr32 /u WMPhoto.dll

This just Unloads the DLL from memory so its not in use

now type
makecab WMPhoto.dll

That compresses YOUR  WMPhoto.dll  into  WMPhoto.dl_  (stored just like an install CD)
due to makecab (xp drive compression isn't even required) yet it is compressed in-case you wish to keep a bk up permanently.


now type
del WMPhoto.dll

That then deletes the actual WMPhoto.dll  (but your WMPhoto.dl_ is backed up safe)

Now install .NET 3.5, Then after its installed, which it will..

type
cd c:\WINDOWS\system32

type
regsvr32 /u WMPhoto.dll

type
del WMPhoto.dll

that deletes the .Net 3.5 SP1 WMPhoto.dll version 6.0.5840.16388 that was just installed

type
expand WMPhoto.dl_ %SystemRoot%\system32\WMPhoto.dll

That restores your WMPhoto.dll version 6.0.6001.17009

then type 

del WMPhoto.dl_

to remove the backup

NOTE:
IF YOU CHECK MICROSOFT UPDATE IT'LL STILL OFFER YOU 3.5 SP1 AKA KB951847
BUT, if you look under it you'll see it now also lists the updates for 3.5
(so it knows 3.5 is their because needs updating)  even though it's still offering you KB951847.

Don't panic, that's just because the 3.0 part of the 3.5 didn't add the right registry branch and the KB for 3.5 is their best solution lol.

My solution to that is to "just install the actual updates"
DO NOT try to install 3.5 (AKA KB951847) again..
It IS IN, windows update just can't see all the registry branch yet!

Once the updates are in, the branch of the registry will then be complete and it'll know 3.5 is in  and then win update will no longer offer it.

THE REASON IT WAS STILL OFFERING IT?
Updates have [FileBranchInfo] and also [Strings] and i assume something differs in were 3.5 SP1 logs its self in the registry of  SP3. That QFE GDR crap no doubt.

THE SPECIFIC REASON IT WOULDN'T INSTALL?
When you run a .NET 3.5 Installer, it contains this exe installer file "wic_x86_enu.exe" under the 3.0 side.

if you extract the dotnetfx35  its located here from inside it
*:\dotnetfx35_x86\dotnetfx30\wic_x86_enu.exe

Inside that, when  "wic_x86_enu.exe" extracts, is a file called wmphoto.dll, It is Version 6.0.5840.16388

However, in your own actual system32 folder (running XP SP3)  you will no doubt have Version6.0.6001.17009.

This wic_x86_enu.exe fails to install because it doesn't wish to downgrade your current wmphoto.dll

Its simply an older version, and its for an older Version of windows

File Version:  6.0.5840.16388 versus 6.0.6001.17009
Build: 061024-1209 versus 070920-1905

I did a lot of research into this, including debugging Service packs of varied xp flavours.

The wmphoto.dll  file was implemented within Windows XP Service Pack 3. The dll file wasn't present within Windows Xp Home, Professional or MCE at any previous SP level.

Nor was it part of the later released Windows Fundamentals for Legacy PC's,  Though WINFLP was initially SP2 and as i stated it didn't turn up within windows its self until SP3.

So far i have found the file within KB951847,  KB936929  and  KB958255

If you wish to Bat this to run before setup, then auto pause during .net install then you un pause afterwards, you could use

cd c:\WINDOWS\system32
regsvr32 /u WMPhoto.dll
makecab WMPhoto.dll
del WMPhoto.dll

pause

cd c:\WINDOWS\system32
regsvr32 /u WMPhoto.dll
del WMPhoto.dll
expand WMPhoto.dl_ %SystemRoot%\system32\WMPhoto.dll
del WMPhoto.dl_
exit

You could bat up the .Net installer before the pause, then you could remove the pause if you start the installer with the /wait option


MISC INFO:

Microsoft .NET Framework 3.5 Service Pack 1
is a full cumulative update that contains many new features building incrementally upon .NET Framework 2.0, 3.0, 3.5, and includes cumulative servicing updates to the .NET Framework 2.0 and .NET Framework 3.0 subcomponents.

A such, you don't need 3.5 to install 3.5 SP1. So what updates are needed by .net 3.5 SP1 ?

UPDATES TO SATISFY .NET 3.5 SP1 - IN ORDER OF RELEASE / INSTALL DATE
========================================================================

NDP20sp2-kb958481-x86.exe = from 13th December 2008 (for silent) /q /norestart
NDP30sp2-kb958483-x86.exe = from 13th December 2008 (for silent) /q /norestart
NDP35sp1-kb958484-x86.exe = from 13th December 2008 (for silent) /q /norestart

NOTE - this ones an Xp update for printer issues caused by .NET, as such the switch differs
WindowsXP-KB961118-x86-ENU.exe = from January 2009 (for silent) needs /quiet /norestart

NDP35sp1-kb963707-x86.exe = from 20th March 2009 (for silent) /q /norestart
NDP30sp2-kb976570-x86.exe = from 27th October 2009 (for silent) /q /norestart
NDP20sp2-kb976569-x86.exe = from 28th October 2009 (for silent) /q /norestart
NDP20sp2-kb976576-x86.exe = from 9th November 2009 (for silent) /q /norestart
NDP20sp2-kb979909-x86.exe = from 25th February 2010 (for silent) /q /norestart
NDP30sp2-kb982168-x86.exe = from 26th April 2010 (for silent) /q /norestart
NDP30sp2-kb977354-v2-x86.exe = from 31st March 2010 (for silent) /q /norestart
NDP20sp2-kb2418241-x86.exe = from 23th September 2010 (for silent) /q /norestart
NDP35sp1-kb2416473-x86.exe = from 24th September 2010 (for silent) /q /norestart
NDP35sp1-kb2604111-x86.exe = from 23rd December 2011 (for silent) /q /norestart
NDP20sp2-kb2604092-x86.exe = from 4th January 2012 (for silent) /q /norestart
NDP20sp2-kb2729450-x86.exe = from 13th September 2012 (for silent) /q /norestart
NDP30sp2-kb2756918-x86.exe = from 28th September 2012 (for silent) /q /norestart
NDP20sp2-kb2742596-x86.exe = from 4th October 2012 (for silent) /q /norestart
NDP35sp1-kb2736416-x86.exe = from 16th October 2012 (for silent) /q /norestart
NDP20sp2-kb2789643-x86.exe = from 10th December 2012 (for silent) /q /norestart
NDP30sp2-kb2832411-x86.exe = from 25th April 2013 (for silent) /q /norestart
NDP35sp1-kb2836940-x86.exe = from 3rd May 2013 (for silent) /q /norestart
NDP35sp1-kb2840629-x86.exe = from 13th May 2013 (for silent) /q /norestart
NDP20sp2-kb2863239-x86.exe = from 4th July 2013 (for silent) /q /norestart
NDP35sp1-kb2861697-x86.exe = from 8th July 2013 (for silent) /q /norestart
NDP20sp2-kb2836941-v2-x86.exe = from 20th July 2013 (for silent) /q /norestart
NDP30sp2-kb2861189-x86.exe = from 22nd July 2013 (for silent) /q /norestart
NDP20sp2-kb2844285-v2-x86.exe = from 26th July 2013 (for silent) /q /norestart
NDP20sp2-kb2898856-x86.exe = from 24th October 2013 (for silent) /q /norestart
NDP20sp2-kb2901111-x86.exe = from 8th November 2013 (for silent) /q /norestart

UPDATES TO SATISFY .NET 3.5 SP1  "RELEASED TO EMBEDDED SYSTEMS" BY DATE WAS
=======================================================================

ndp20sp2-kb4040968-x86.exe = from 31 August 2017 (for silent) /Q /norestart
ndp30sp2-kb4055229-x86.exe = from 6 December 2017 (for silent) /Q /norestart
ndp20sp2-kb4054178-x86.exe = from 18 December 2017 (for silent) /Q /norestart
ndp20sp2-kb4095516-x86.exe = from 13 April 2018 (for silent) /Q /norestart
ndp30sp2-kb4338597-x86.exe = from 12 June 2018 (for silent) /Q /norestart
ndp20sp2-kb4338615-x86.exe = from 14 June 2018 (for silent) /Q /norestart
ndp20sp2-kb4344180-x86.exe = from 8 August 2018(for silent) /Q /norestart
ndp30sp2-kb4457058-x86.exe = from 14 August 2018 (for silent) /Q /norestart

=======================================================================

NOTE:
While i understand there was many other (100's) of random NDP20sp2, NDP30sp2 and NDP35sp1 "Updates" and also "Hotfixes" released for Microsoft .NET 3.5 SP1, You need to remember a few things.

Updates, often become superseeded, Example, two future updates that are needed (between the contents of those two) can actually replace sometimes two or more of the updates that came before them because those two contain newer versions of files in maybe 6 or 7 prior updates. As such, sometimes 50 odd updates can be narrowed down to 20 odd kinda thing.

Hotfixes, where generally system specific, Example, a .NET developer has issues on certain systems trying to compile diffrent code. As an "End Point User" tryna run your game trainer or ATi driver software the majority of hotfixes where irrelevent. Some hot fixes where also just that, a HotFix.. They were a real time running fix in the background for an issue that was sometimes never fully fixed.

So installing random hotfixes because you've found a Gigs worth of .Net updates is just going to bog your system and waste your time....

The list i have provided fully satisfys Microsoft Update for XP and Embedded x86 systems
and I compiled this list BEFORE they began to pull certain files that are no longer offered. As such (one day) this list like many of my other lists will be more accurate than what windows update offers and these winupdate file grabbers (and thats even if the windows update site will be around) Share my pages, Don't copy them!


REMEMBER:
ON THE OFF CHANCE YOU WISH TO ADD YOUR OWN CONSUMER SYSTEM HOTFIXES, THE SILENT SWITCHES DIFFER

/q = Totally Silent Install for NDP exe's
/quiet = Totally Silent Install for WindowsXP-KB exe's

/pasive = Shows Progress Bar for NDP and WindowsXP-KB exe's
/norestart = for NDP and WindowsXP-KB exe's

If you place a Consumer based Hotfix EXE into your root drive,
then click Start, Run and call to it with the /?  switch
it'll often list the silent install switches

EXAMPLE:
C:\NDP20sp2-kb2863239-x86.exe /?

If you think i have missed any x86 Required KB's, feel free to explain why in the comments....

While im sure this begs the question, what about x64 ?, can you use this same list as a guide ?
No idea, but be aware x86 sometimes has less updates because its less of a target, on the other hand sometimes x64 has lass updates because its more secure

IF you have an X64  XP  SP2 installed, give it a try & see what winupdate offers afterwards
don't leave it too long though, they are randomly removing updates

3.5 SP1 Supported Operating System

Windows Server 2003, Windows Server 2008, Windows Vista, Windows XP

• Processor: 400 MHz Pentium processor or equivalent (Minimum); 1GHz Pentium processor or equivalent (Recommended)
• RAM:96 MB (Minimum); 256 MB (Recommended)
• Hard Disk: Up to 500 MB of available space may be required
• CD or DVD Drive: Not required
• Display: 800 x 600, 256 colors (Minimum); 1024 x 768 high color, 32-bit (Recommended)

NOTE 2:
If you faced that 3.5 SP1 Error you'll no doubt also encounter an error for the 1.1 SP1 security update with Error Code: 65535.  Again i think this is registry branch related.

On .NET 1.1 SP1 ndp1.1sp1-kb2833941-x86.exe,  if it fails to install with Error Code: 65535

Have Winrar or 7Zip,  right click on it and extract to  ndp1.1sp1-kb2833941-x86
then go in the folder and run the  MSP  file inside  "NDP1.1sp1-KB2833941-X86.msp"

It will install, and you can make sure it has here, because it makes its own folde
C:\Windows\Microsoft.NET\Framework\v1.1.4322\Updates\M2833941

For other .NET Update issues theirs an in-depth post here.

I WRITE GUIDES FROM YEARS OF EXPERIENCE, MY WORK NOW CULMINATES ON THIS BLOG, DON'T STEAL IT (BECAUSE YOUR TO THICK TO UPDATE CHANGES)  AND / OR NOT EVEN SAVI ENOUGH TO CHECK BACK FOR MORE MODERN INFORMATION.

ALSO DO NOT JUST UNINSTALL EVERY .NET LIKE OTHER WEBSITES TELL YOU TO!
THAT ADVICE IS FRANKLY JUST INSANE.....

PAGE LAST UPDATED 5th JUNE 2017