More detailed troubleshooting ideas for .NET Framework 1.0 SP3 and 1.1 SP1 failures

re: More detailed troubleshooting ideas for .NET Framework 1.0 SP3 and 1.1 SP1 failures

Aaron Stebner — Fri, 08 Mar 2013 07:03:20 GMT

Hi Jim Vance - The "feature you are trying to use is on a network resource that is unavailable" error message means that there is something wrong with the base version of the .NET Framework 1.0 that is on your computer and it needs to be repaired before you can install 1.0 SP3. The easiest way to do that is to use the steps and the cleanup tool described at blogs.msdn.com/.../8108332.aspx to fully remove all versions of the .NET Framework, then re-install them.

re: More detailed troubleshooting ideas for .NET Framework 1.0 SP3 and 1.1 SP1 failures

Jim Vance — Thu, 07 Mar 2013 17:46:34 GMT

Hi, Aaron -- I tried to post something last night but again got a system error message and it doesn't appear this morning, so I'll reprise it this morning. I've uninstalled both the .NET Framework 4 Client and Extended without any issues, rebooted and then attempted to install the .NET Framework 1.0 SP3 patch without success. I tried it two different ways -- first the direct route using the downloaded installation file, but as before (which was described in that earlier Part 1/2 posting that evaporated) this generates an intermediate notice that it cannot find 'netfx.msi' in a temporary folder at the default subdirectory C:\Documents and Settings\Administrator\Local Settings\Temp. The specific message is: "The feature you are trying to use is on a network resource that is unavailable." When I manually try and navigate to the default location in Windows Explorer, that temporary folder doesn't exist If I bypass the default location in the notice and attempt to manually browse to a different location where I have previously extracted this netfx.msi file (per the instructions in another of your blog postings), the message changes to "Accessing the feature" for awhile and then changes back to the one about the network resource being unavailable. Nothing seems to work, so canceling out reverts the installation progress bar and that box disappears.

If I run Windows Update instead and deselect anything other than the .NET Framework 1.0 SP3 patch (the .NET Framework 4 Client is listed as an optional item, and perhaps an MSE definitions update), allowing it to proceed onward fails with the same 0x643 error code as has typically been the case since this issue first arose months ago.

Any other ideas?

re: More detailed troubleshooting ideas for .NET Framework 1.0 SP3 and 1.1 SP1 failures

Aaron Stebner — Wed, 06 Mar 2013 06:31:27 GMT

Hi Jim Vance - You've got the .NET Framework 4 installed on your computer. The .NET Framework 4 installs a registry key that prevents the .NET Framework 1.0 from being installed or repaired. When you try to install the .NET Framework 1.0 SP3, it triggers a repair of the .NET Framework 1.0 as part of the service pack installation process, and that in turn sees the registry key created by .NET Framework 4 setup and blocks the install.

In order to resolve this issue, you'll need to uninstall the .NET Framework 4 (both the Client Profile and Extended), install the .NET Framework 1.0 SP3, then re-install the .NET Framework 4.

Please let me know if that doesn't end up resolving this issue.

re: More detailed troubleshooting ideas for .NET Framework 1.0 SP3 and 1.1 SP1 failures

Jim Vance — Tue, 05 Mar 2013 03:12:36 GMT

Hi, Aaron -- If I've done everything properly, you should be able to access 2 files: 1) the vslogs.cab file and 2) the setupverifier text file at the following link:

http://sdrv.ms/XmDtNS

Please let me know if I somehow screwed up with either of those, and once again many thanks for your time and efforts to help me resolve this particular gremlin.

re: More detailed troubleshooting ideas for .NET Framework 1.0 SP3 and 1.1 SP1 failures

Jim Vance — Sun, 03 Mar 2013 01:49:47 GMT

Aaron, many thanks for the reply despite the failure of part 1 of the message to post. I discovered that fact late yesterday afternoon and attempted to summarize it with an additional post, but the system came back with a message that there was some problem and the administrators have been notified; since that message didn't post either, I just quit for the evening.

Hopefully, this one will go through so I'll try to summarize briefly again. The machine in question is running XP Pro SP3, and the problem lies with installation of the .NET Framework 1.0 SP3 (KB867461) patch which fails with this message: "This install cannot continue because this version of the .NET Framework is incompatible with a previously installed one. For more information, see..." a MS KB article URL reference (Q312500) which no longer exists. The URL reference leads to some troubleshooting options, and I've allowed the various Fixit tools which are offered to run, but while they claim to have repaired certain things (Windows Installer and .NET), it hasn't produced any difference in terms of an outcome. Although my primary browser is Firefox, for all of that online troubleshooting I was using IE (v8.0.6001.18702).

I've downloaded and run offline the latest Windows Installer just to make sure nothing was somehow getting blocked. I have tried running offline the .NET repair tool, and have used the cleanup tool twice to remove all .NET versions, then went laboriously through the process of running Windows Update repeatedly, rebooting between in order to reinstall all the .NET versions offered -- the 2nd time I used separately downloaded versions of the installation patches rather than running through the Windows Update shell, but all were completely unsuccessful in the end and that .NET 1.0 SP3 patch simply will not install. So, posting something on this blog was really the last shot because I plan to replace that desktop with a Win7 machine in another month, then recycle the old machine's hardware components after wiping everything on the hard drives following a complete backup and transfer with PC Mover to the new machine. Ultimately, I decided if I can't get this patch to go through, I'll just ignore it for the remainder of its functional life.

I have not run the verification tool which your other post referenced, though it appears I have done everything else -- I'll download the verification tool and run that tomorrow morning, then collect the setup log files and upload them to the server and provide a follow-up post here where they can be found.

re: More detailed troubleshooting ideas for .NET Framework 1.0 SP3 and 1.1 SP1 failures

Aaron Stebner — Fri, 01 Mar 2013 19:43:34 GMT

Hi Jim Vance - I'm sorry for the hassles that this issue is causing for you. The first part of your comment didn't post correctly, so I'm not sure what version of Windows you are running. The steps that I normally suggest for this type of .NET Framework installation problem are listed at blogs.msdn.com/.../8108332.aspx. If you haven't yet, I'd suggest trying those steps to see if they help resolve these issues.

If you're still seeing .NET Framework installation issues after trying those steps, can you please use the tool described at blogs.msdn.com/.../6458047.aspx to collect all of your setup log files, upload the file named %temp%\vslogs.cab that this tool will create to a file server (such as http://skydrive.live.com), and then reply back here and provide a link that I can use to download your log files and take a closer look?

re: More detailed troubleshooting ideas for .NET Framework 1.0 SP3 and 1.1 SP1 failures

Jim Vance — Thu, 28 Feb 2013 02:24:50 GMT

Part 2/2:

The versions of .NET which are installed on this desktop according to the list in the Windows\Microsoft .NET\Framework subdirectory are 1.0.3705 (mscorlib.dll version 1.0.3705.0), 1.1.4322 (1.1.4322.2502), 2.0.50727 (2.0.50727.3643), 3.0 (no mscorlib.dll), 3.5 (no mscorlib.dll, but has successfully been updated with SP1 and various security updates), 4.0.30319 (4.0.30319.296), and VJSharp (no mscorlib.dll). This machine had a problem installing a different .NET patch several months ago, and in the process of getting that resolved I used the cleanup tool to remove all the versions and rebuilt them from the ground up. When this SP3 patch wouldn't go, I went through that process a 2nd time, but KB867461 simply won't install no matter what -- I've allowed all the various FixIt tools that have been offered in following the "Windows Update won't install" options to run, and while they always seem to find something to repair the outcome produces no success.

I use MSE as my primary AV and Windows Firewall for that purpose, and run weekly manual scans with several other malware detection agents (Malwarebytes, Super AntiSpyware, Kaspersky TDSS rootkiller, Panda Cloud AV), plus use CCleaner on a monthly basis to remove temporary files, cookies and such. Nothing more than cookies have been found since long before this problem arose. I've tried shutting down the MSE functions and services before attempting the installation of this patch with no difference in success. I've used online scans from other AV vendors (ESET, AVG F-Protect) to verify there's really nothing in the way of malware lurking to block this installation.

I'm reasonably competent with computers from being a civil engineer who's personally dealt with them from 1970s mainframes onward through the era of PCs as both a user and a self-taught IT administrator for hardware repairs and OS reccovery when needed, but this particular problem has me stumped at this point and I've expended far too much time and effort in attempting to resolve it. I intend to replace this machine in another month or so and aren't inclined to do a repair installation or a wipe-and-rebuild at this point, so if there are no viable approaches which might be suggested in response to this post I'll just live with the foible and ignore that patch while I accelerate the replacement process a bit.

re: More detailed troubleshooting ideas for .NET Framework 1.0 SP3 and 1.1 SP1 failures

Aaron Stebner — Sun, 25 Nov 2012 22:07:50 GMT

Hi Kenneth Wolfson - What are you doing when you see this error? If you are trying to run an application, which application is it, and what version of Windows are you running on your computer?

If you haven't yet, I'd suggest trying to install the .NET Framework 4, or uninstall it and re-install it if it is already installed. You can find instructions describing how to do this at blogs.msdn.com/.../8108332.aspx.

re: More detailed troubleshooting ideas for .NET Framework 1.0 SP3 and 1.1 SP1 failures

Kenneth Wolfson — Sun, 25 Nov 2012 20:29:21 GMT

Have error stating not having net 4.0 or there is a problem with net 4.0. Do you have any thoughts on how to fix this please. Thank you

re: More detailed troubleshooting ideas for .NET Framework 1.0 SP3 and 1.1 SP1 failures

Aaron Stebner — Sat, 19 Feb 2011 23:08:55 GMT

Hi Sergio - I'd suggest trying to install the .NET Framework 3.5 SP1 from www.microsoft.com/.../details.aspx and then try again to install the .NET Framework 1.1.

If the .NET Framework 1.1 still fails after that, then please use the steps listed at blogs.msdn.com/.../help-me-help-you-if-you-have-setup-bugs.aspx to enable verbose logging, reproduce the failure, then upload your log file to http://skydrive.live.com and reply here with a link I can use to download the log file and take a further look.