http://www.microsoft.com/technet/security/bulletin/ms07-040.mspx?pubDate=2007-07-10
Frequently Asked Questions (FAQ) Related to This Security Update
" This security bulletin says that .NET Framework 3.0 is non-affected.
How does .NET Framework 3.0 relate to the previous versions that are
affected?
Microsoft .NET Framework 3.0 is a superset of .NET Framework 2.0.
Microsoft .NET Framework 3.0 listed as Non-Affected Software in this
security update refers to the four new technologies added as the
superset to the .NET Framework 2.0. These technologies are: Windows
Presentation Foundation (WPF), Windows Workflow Foundation (WF), Windows
Communication Foundation (WCF), and Windows CardSpace. The
vulnerabilities addressed in this security update do not affect any of
the four specific .NET Framework 3.0 technologies. Developers wishing to
learn more about the .NET Framework 3.0 and it’s relation to previous
version may refer to the following .NET Framework 3.0 Versioning and
Deployment MSDN article. Additional information for .NET Framework 3.0
may also be found in the following MSDN article.
http://msdn2.microsoft.com/en-us/netframework/aa663309.aspx
I only have .NET Framework 3.0 installed. Why am I being offered the
security update?
There is no security update targeting the WPF, WF, WCF, and CardSpace
technologies that together make up Microsoft .NET Framework 3.0 as they
are not affected by any of the vulnerabilities in this security update.
However, every installation of Microsoft .NET Framework 3.0 also
includes .NET Framework 2.0, which is an affected product in this
security update and as such this update is offered to all systems where
applicable. "
..NET 1.1 SP1 and KB928366 have ***nothing*** to do with the above.
End of discussion.
MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============
I repeat, a Security update for .NET Framework 1.1 is intended for
that specific runtime *only*. It does not matter if there are other
runtimes installed. Sec updates for those other runtimes are
*specific*, too.
*The* most common installation issue installing .NET Frameworks,
Service Packs, and Security updates for them are directly related to
the installed antivirus/security software.
MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============
If you have .net framework 2.0 or 3.0 installed you do not need
this update, you should have installed kb928365 already.
What Utter Nonsense. Security updates for a specific .NET Framework
have NOTHING to do with any other version of .NET Frameworks that
are installed.
If .NET Framework 1.1 is installed then one should install all
Security updates for it that are not superseded by any other
Security updates for it.
MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============
Thank you, Mow Green for your comments. I suggest that we attempt to
resolve our disagreement by asking the OP to install the Belarc
Advisor version 7.2t, available from this hyperlink :
http://www.belarc.com/free_download.html . It will show what MS
security updates are missing from his system. I am sure that you are
already familiar with this useful service, Mow Green. If the OP will
post back his result here it may assist us in helping him to resolve
this issue.
I would still like to know whether the OP has .Net Framework 2.0/3.0
installed in order to help him solve his problem.
Thank you again, Mow Green [MVP]. Here is the original security bulletin
:
http://www.microsoft.com/technet/security/bulletin/ms07-040.mspx?pubDate=2007-07-10
. It is the same security update and it only has to be installed once.
That is also why Belarc Advisor does not show that kb928366 is missing
on systems that have .Net Framework 2.0/3.0 installed, as long as
kb928365 is already installed. After all, you cannot install .Net
Framework 2.0 without already having .Net Framework 1.0/1.1 installed.
Since the OP has not posted back,I assume that he has solved his
problem, possibly as a result of our replies to his post. However, since
so many people have had problems with security updates to .Net Framework
since July, I am almost certain that he will not be the last.
