Yes, I was looking at the same page you reference. The instructions are
unclear; you could assume that only folders with a copy of mscorlib.dll indicate
an installed version, or that the presence of one of the listed folders
indicates an installed version. Neither is correct!
The community content looks promising, particularly regarding the relevant
registry keys, but I haven't tried it.
Harry.
PA Bear [MS MVP] wrote:
> In short, I dunno. Win7 is NOT listed in the Applies To section of
> KB976982 or KB923100 but this wouldn't be the first time a KB article's
> not kept fully updated, Harry, but your installer argument is certainly
> a valid one.
> [Then again, if the OP (who hasn't posted any follow-up as of the reply)
> had upgraded to Win7 from Vista or WinXP, all bets are off.]
> As for your WinXP box, KB318785, and .NET 3.5 SP1:
> - KB318785 now points to
> http://msdn.microsoft.com/en-us/kb/kb00318785.aspx here (at least here &
> while signed-in to my Live ID)
> - KB00318785 suggests that the folder
> %systemroot%\Microsoft.NET\Framework\v3.5 would be present if .NET 3.5
> was installed; and...
> - KB00318785 includes some of that [censored] Community Content, any of
> which may prove helpful to you.
Harry Johnston [MVP] wrote:
> PA Bear,
>
> Is this procedure applicable to Windows 7? I'm thinking the .NET installers
> probably won't work, since they significantly predate W7, and since W7
> includes 3.5.1 as an OS component.
>
> I also note that the process in KB318785 doesn't work as documented, even on
> Windows XP; my machine has .NET 3.5 SP1 but only the v2.0.50727 folder
> contains a mscorlib.dll file. Admittedly the article claims to only apply
> to versions 1.0, 1.1 and 2.0. Do you know what the equivalent procedure is
for 3.x?
> PA Bear [MS MVP] wrote:
>> When installing updates using Windows update or Microsoft Update you may
>> receive Error 0x643 or 0x80070643 (23 Oct-09)
>>
http://support.microsoft.com/kb/976982 >>
>> =====================
>>
>> Step #1 => Before doing anything else, write down what .NET Framework
>> versions are currently installed:
>>
>> How to determine which versions of the .NET Framework are installed and
>> whether service packs have been applied
>>
http://support.microsoft.com/kb/318785 >>
>> Step #2 => Now see Resolution Method 2 in...
>>
>> When you try to install an update for the .NET Framework 1.0, 1.1, 2.0,
>> 3.0, or 3.5, you may receive Windows Update error code "0x643" or
>> Windows Installer error code "1603" (ignore the title, if need be)
>>
http://support.microsoft.com/kb/923100 >>
>> After running the appropriate/needed tool, (re)install all .NET
>> Framework versions (but only the ones you wrote down in #1 above)
>> manually using the download links on the page then run Windows Update
>> manually to install security updates for same.
>>
>> NB: If you remove .NET Framework 3.5 SP1 using the tool, reinstalling
>> .NET Framework 3.5 will also install .Net Framework 2.0 SP2 and 3.0 SP2;
>> then Windows Update will offer .NET Framework 3.5 SP1.
>>
>> IMPORTANT! => If you remove .NET Framework 3.5 SP1, reinstall your .NET
>> Framework versions in the following order:
>>
>> 1. .Net Framework 3.5, then...
>> 2. .Net Framework 1.1, then...
>> 3. .Net Framework 1.1 SP1
>>
>> NB: KB923100 references this page:
>>
http://blogs.msdn.com/astebner/archive/2006/05/30/611355.aspx. Please
>> read ALL of it as well as the related page
>>
http://blogs.msdn.com/astebner/pages/8904493.aspx before using the .NET
>> Framework Cleanup Tool.
>>
>> Step #3 => Check-in at Windows Update and install any critical security
>> updates offered.
|
