According to Microsoft, "You can think of the [.NET Framework ] as an agent that manages code at execution time, providing core services such as memory management, thread management, and remoting, while also enforcing strict type safety and other forms of code accuracy that promote security and robustness." This is a fundamental component of Windows and, when necessary, its components must be carefully replaced.
The .NET technology is evolving and Microsoft has released several interdependent versions and Service Packs for .NET over time. Errors can result when a revision, new version or service pack for .NET fails to install properly as part of routine Windows updates, or when Windows XP is not up-to-date with Service Pack 3 and .NET framework.
Errors such as
indicate that one or more of the Microsoft .NET Framework components in the Windows on your computer probably is corrupted or missing. Before following any suggestions on this webpage, see CTI's disclaimer of warranty (below) .
If you are using Windows XP, ensure that it is up-to-date (including Service Pack 3). To see which version of Windows and which Windows service pack (SP) is running on your computer, open the Windows Control Panel and select System. The latest installed Service Pack number is listed below the version of Windows.
To display the Windows Update History on this computer from the Control Panel's System screen:
Look for "Failed" or red X beside any updates that never completed successfully, especially any that include "NET Framework." If your latest update to Windows (any version) included a .NET component, and everything including CTI Navigator was working correctly before this Windows update, try restoring your Windows system files back to the date before the update was installed (see Restore Windows System files in the related articles below), and then update Windows again. Otherwise, to fix a Microsoft .NET Framework error requires removing/uninstalling the corrupted .NET component and then re-installing it and all of its associated components in the .NET Framework. To accomplish this, Microsoft recommends you use the Microsoft automated .NET Framework repair tool described below.
Microsoft provides a wizard-based .NET Framework Repair Tool that "detects and tries to fix some frequently occurring issues with the setup of or with updates to the Microsoft .NET Framework." To download and run this tool on your computer, click on "Microsoft .NET Framework Repair Tool" and follow Microsoft's instructions. To see more information about this tool, click on "Microsoft .NET Framework Repair Tool Description."
If Microsoft's automated repair tool fails to fix your error or you are not comfortable running this tool or trying to repair your Windows .NET Framework files yourself (see manual repair below for advanced users), CTI recommends that you have a local computer technician test and repair the Windows .NET Framework in your computer. Otherwise, for free "computer repair, service and support" (such as repairing Windows) Realtor® members can contact the www.TechnologyHotline.com. This tech hotline is funded by your state Association of Realtors® as a member benefit and can be reached by phone (Monday - Saturday) at
Repair Tool Version Note: The current version of the Microsoft's automated repair tool (dated 10-08-2012) supports repairing the .NET Framework 4, .NET 3.5 SP1 (includes .NET 3.0 SP2 and .NET 2.0 SP2) on Windows 7 and earlier (Vista, Server 2008, Server 2003, and XP).
Compatibility Note: Incorrectly setting CTI Navigator Desktop to run in a "Compatibility Mode" different from the version of Windows in which it is running can cause CTI Navigator to suddenly disappear whenever a CTI Navigator function (such as Login or Send) requests Internet access. To confirm or correct that CTI Navigator is not set to run in Compatibility Mode: open Windows Explorer > browse to C:\Program Files\CTI Navigator [in a 64-bit version of Windows browse to C:\Program Files (x86)\CTI Navigator]) > right-click on CTI Navigator.exe > select Properties > click the Compatibility tab > verify that "Run this program in compatibility mode for" is not checked.
By default, .NET Framework 4.5 is enabled in a new or clean installation of Windows 8, but .NET 3.5 is not included. The files for .NET 3.5 are available on the Windows 8 installation media as an optional feature. When an app requires .NET Framework 3.5 (or .NET 2.0), Windows 8 should automatically request permission to download the missing files from Windows Update. If this fails, users can enable .NET Framework through the Windows 8 Control Panel or from the system ISO image file.
To enable .NET Framework 3.5 (and earlier) in Windows 8 Control Panel (if needed by an app):
To enable .NET Framework 3.5 from a Windows 8 ISO image:
Note: Copying from the sources\SxS\ folder can be used but is not a Microsoft supported mechanism for normal distribution of .NET Framework 3.5. (see Windows 8 .NET Framework 4.5 is default and .NET Framework 3.5 is optional).
Always try Microsoft's automated repair tool first (see the preceding section). If you are an advanced computer user and Microsoft's automated repair tool fails to resolve the problem, you can attempt to manually repair .NET Framework yourself, contact the state association sponsored technology hotline for assistance, or have a local computer technician repair it for you.
To manually repair .NET, follow the steps in the prescribed order for the approach chosen below. Before you start, ensure that your Windows has the latest Service Pack and the latest security patches installed for your version of Windows. (Sometimes Microsoft's latest update includes a hot fix for the problem.) Beware that manual repair may take more than an hour, depending on your computer and which components are damaged or missing.
The sections below represent three approaches to rebuilding Microsoft .NET Framework:
▲ Back to the top of this webpage
To manually repair or rebuild Microsoft .NET, complete the following steps in order
as appropriate for your version of Windows:
.NET Framework 3.0, and 2.0 are
included as part of Windows Vista Operating System; and
.NET Framework 3.5, 3.0, and 2.0 are included as part of Windows 7
Operating System. To repair NET Framework 3.5, 3.0, and 2.0 in
Windows Vista or 7 1)
Start > All Programs > Accessories 2)
Right-click on Command Prompt > select "Run as
Administrator" > Continue 3)
Run "sfc /scannow" to automatically replace
incorrect/corrupt versions of system files if possible 4)
If SFC could not fix some files, follow Microsoft's instructions at "How
to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe)
program generates in Windows Vista" at http://support.microsoft.com/kb/928228;
and "Copy
Good DVD Files To Replace Corrupt OS Files"
at
http://www.vistax64.com/tutorials/86959-access-vista-install-dvd-files.html If
the problem is not resolved, proceed with the following steps. 1) Windows XP, 2000, Server 2003: 2.0 - dotNetfx.exe for 32-bit or
NetFx64.exe
for 64-bit Windows [redistributable] at 2.0
SP2 - Netfx20SP2_x86 exe
for 32-bit or Netfx20SP2_x64 exe for 64-bit Windows [w/
cumulative roll-up updates] at
3.0 - dotNetfx3.exe for 32-bit or
dotnet3_64.exe for 64-bit Windows at http://www.microsoft.com/downloads/details.aspx?FamilyID=10CC340B-F857-4A14-83F5-25634C3BF043 3.5
SP1 - dotNetFx35setup.exe to install only
components needed for that computer (recommended) at
3.5
SP1 - dotNetFx35setup.exe to install only
components needed for that computer (recommended) at
4.0 - dotNetFx40_Fullx86_x64.exe
optional standalone installer at http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=0a391abd-25c1-4fc0-919f-b21f31ab88b7
2) Windows 7 and Vista: download only
3.5 SP1
(because 2.0 and 3.0 are part of the Operating System).
3) dotNetFx_Cleanup_tool.zip at
http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog_Tools/dotnetfx_cleanup_tool.zip
Warning:
The .NET Framework Cleanup Tool should be used with caution. It not
only removes the selected version files, hotfixes and service packs to that
version, but it also removes files and registry keys shared with other
versions of the .NET Framework. All associated versions of .NET
Framework must be repaired or re-installed (in numeric sequence) after using
the Cleanup Tool.
Vista/7:
Programs and Features > .NET 3.5 SP1 >
Change/Remove > Repair.
If problem is not resolved
by an automated repair, proceed with the following steps.
Use the following procedure if the preceding standard repair and re-build (described above) does not succeed.
The .NET Framework 3.5 Service Pack 1 is a full cumulative update that "includes cumulative servicing updates to the .NET Framework 2.0 and .NET Framework 3.0 subcomponents." If .NET was working correctly until recently, you may only need to un-do and reinstall the 3.5 SP1 Update as follows.
▲ Back to the top of this webpage
Disclaimer of Warranty. All services are provided under the terms and conditions of CTI's license agreement accompanying CTI Navigator. Assistance in any form is provided only as a convenience to licensed users of CTI products. Problems and solutions may depend on the nature of your system environment and other parameters that are unknown to CTI. By requesting assistance, user agrees that actions and solutions described, suggested or implemented by CTI staff are entirely at the user's own risk and are provided without warranties of any kind. Under no circumstances, including negligence, shall CTI or any of its employees be liable for any direct, indirect, incidental, special, punitive, consequential or other damages, loss, cost or liability whatsoever that result from or are related to use of technical support provided by CTI.
Related articles and Internet links:
Links to Microsoft's Instructions for .NET Framework:
▲ Back to the top of this webpage
To go to CTI's menu of Instructions to Fix Errors, click here or use the back arrow at the top of your Internet browser.
To go directly to CTI's online Menu of Help and Tutorials, click here.
rev.
04.17.2013