Net Framework Initialization Error Mscorwks Dll Could Not Be Loaded
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 21 Oct 2016 01:59:31 GMT by s_wx1196 (squid/3.5.20)
on Windows Vista ★★★★★★★★★★★★★★★ Aaron StebnerMarch 26, 2007227 Share 0 0 NOTE - this blog post was originally written for the .NET Framework 2.0 and 3.0 on Windows Vista. Since then, Windows 7 has shipped, and it includes the .NET Framework 2.0, 3.0 and 3.5 as OS components. The steps in this blog post apply equally to Windows 7 as well. Since the Windows Vista public launch in January 2007, I have been receiving questions about how to repairthe .NET Framework 2.0 and 3.0 to try to resolve various bugs. As I previously described here, the 2.0 http://answers.microsoft.com/en-us/windows/forum/windows_vista-update/net-framework-v2050727-mscorwksdll-could-not-be/62c22a30-3f31-4f93-8241-b79898c31d73 and 3.0 versions are installed as OS components on Windows Vista and do not appear in the Programs and Features (formerly known as Add/Remove Programs) control panel. Many of the customers I have heard from have tried to use the .NET Framework cleanup tool, but it does not list the .NET Framework 2.0 as a valid removal option when it is run on Windows Vista. This is by design https://blogs.msdn.microsoft.com/astebner/2007/03/26/how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista/ - the cleanup tool does not offer the option to remove any version of the .NET Framework that is an OS component on the OS it is being run on. Windows Vista OS files and registry information (including those that are a part of the .NET Framework 2.0 and 3.0) are protected by Windows Resource Protection (WRP) in Windows Vista. This means that only the OS installer service (named TrustedInstaller) has permission to modify/remove these files or registry keys unless you specifically take ownership of the files/keys and add additional user accounts to the access permission list (which you should not need to do except in extraordinary circumstances). If you run into problemsusing .NET Framework applications on Windows Vista, and you suspect that files or registry entries that are a part of the .NET Framework 2.0 or 3.0 are corrupt, you can use the instructions listed below to attempt to repair them. Repairing .NET Framework 2.0/3.0 files on Windows Vista You can use the following steps to repair the files that are a part of the .NET Framework 2.0 and 3.0 on Windows Vista and Windows Server 2008: Click on the Start menu, choose All Programs, then Accessories, then right-click on the Comma
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer https://www.veritas.com/support/en_US/article.000035811 Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Windows update causes Backup Exec not to launch and gives the error message "c:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll net framework could not be loaded Article:000035811 Publish: Article URL:http://www.veritas.com/docs/000035811 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In net framework initialization Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Windows update causes Backup Exec not to launch and gives the error message "c:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll could not be loaded Error Message .NET framework Initialization Error Solution Cause: This issue can be caused by a damaged .NET Framework component. Windows update upgraded the version of .NET to SP2 and corrupted some components for .NET framework. Resolution: 1. Re-register the DLL shown in the error, if still unresolved follow the below steps. 2. Run a repair of .NET Framework and attempt to restart the Backup Exec services. 3. If the issue persists, uninstall .NET Framework and reinstall it after rebooting. http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-translated.