Install Microsoft .NET Framework 1.1 on Windows Vista – Fix RegSvcs.exe Fails Error
Windows Vista and Windows 7 comes packaged with Microsoft .NET Framework 2.0 and 3.0, but not version 1.1, which may still required by some applications such as QuickBooks 7, GFI Report Packs, VS.NET 2003, InstallShield 11.5, and many other developed software. However, when trying to install Microsoft .NET Framework 1.1 (dotnetfx.exe) on Windows Vista or Windows 7, one or more error messages similar to one of the following text will appear, and stop or prevent setup installation of .NET Framework 1.1 from continuing successfully.
RegSvcs.exe – Common Language Runtime Debugging Services
Application has generated an exception that could not be handled.
Process id=0xe50 (3664), Thread id=0xd44 (3396).Click OK to terminate the application.
Click CANCEL to debug the application.
If user click “OK’, the installation of .NET 1.1 will be cancelled, while clicking “CANCEL” produces another error message similar to below:
RegSvcs.exe – No debugger found
Registered JIT debugger is not available. An attempt to launch a JIT debugger with the following command resulted in an error code of 0×2 (s). Please check computer settings.
cardbg.exe !a 9×8e
In Even Viewer of Vista or Windows 7, the following log or similar can be seen:
Source: MsiInstaller
Event ID: 1030
Description:
Product: Microsoft .NET Framework 1.1. The application tried to install a more recent version of the protected Windows file C:\Windows\Microsoft.NET\Framework\sbs_wminet_utils.dll. You may need to update your operating system for this application to work correctly. (Package Version: 1.0.0.0, Operating System Protected Version: 1.0.0.0).
Source: MsiInstaller
Event ID: 1030
Description:
Product: Microsoft .NET Framework 1.1. The application tried to install a more recent version of the protected Windows file C:\Windows\Microsoft.NET\Framework\sbs_system.enterpriseservices.dll. You may need to update your operating system for this application to work correctly. (Package Version: 1.0.0.0, Operating System Protected Version: 1.0.0.0).
The error pops up in the end of .NET Framework 1.1 setup when it’s almost finished, and is registering “System.EnterpriseServices.dll” when the error occurs, time remaining for the installatin process shows 0 seconds.
Why exactly the error occurs when installing Microsoft .NET Framework 1.1 in Windows Vista or Windows 7 is not known, as the issue happens randomly. It may affect both 32-bit and 64-bit Vista or Windows 7 system, but not all system will have the issue. But one thing is for sure. Microsoft .NET Framework 1.1 SP1 (Service Pack 1) has resolved the issue. However, Microsoft does not provide download to standalone .NET Framework 1.1 installer that integrated with SP1.
Thus, the workaround to fix the Microsoft.NET Framework 1.1. installation error on Vista is to slipstream .NET Framework 1.1 SP1 into .NET Framework 1.1 installer, so that both the .NET Framework and the Service Pack can be installed at the same time.
To slipstream .NET 1.1 SP1 into .NET Framework setup package to have a integrated .NET Framework 1.1 SP1 installer, follow steps in this trick:
- Create a new folder named DotNet in C:\ drive (C:\DotNet is used in this guide, you can change to any folder you prefer, but ensure that you use correct path in the following steps).
- Download Microsoft .NET Framework 1.1 Redistributable Package (dotnetfx.exe). Make sure the setup file is saved as dotnetfx.exe.
- Download Microsoft .NET Framework 1.1 Service Pack 1 (NDP1.1sp1-KB867460-X86.exe). Make sure that the file is renamed and saved as dotnetfxsp1.exe, so that the rest of the steps can be followed easily.
- Move both installation files into the same directory (i.e. C:\DotNet), if you’re not saving them together.
- Open command prompt as Administrator.
- Change to the directory where the two installation setup files for .NET 1.1 are saved (i.e. C:\DotNet).
- Run the following commands one by one, press Enter after each one.
dotnetfx.exe /c:"msiexec.exe /a netfx.msi TARGETDIR=C:\DotNet"If you’re not using C:\DotNet directory, change the target to your path accordingly.
Then click on “Yes” when prompted to answer “would you like to install Microsoft .NET Framework 1.1. Package?”Wait for the uncompression, extraction and setup to complete with the display of the following dialog which says installation complete.
dotnetfxsp1.exe /Xp:C:\DotNet\netfxsp.mspNo status message for this step.
msiexec.exe /a c:\DotNet\netfx.msi /p c:\DotNet\netfxsp.msp
Wait for Windows Installer for Microsoft .NET Framework 1.1 to finish and disappear automatically.
- Install Microsoft .Net Framework 1.1 with slipstreamed/integrated Service Pack 1 by running netfx.msi created in the working folder.
Related Articles
- Fix Windows 7 KB974431 Fails to Install With C004F050 Error
- Visual Studio 2008 Fails to Install (Fix Can’t Unpackaged Not Cabinet Error)
- Internal Error 2739 Error in Vista (32 or 64-bit) When Install Adobe Photoshop CS3 and Reflector Related Programs
- Workaround to Install Microsoft AppLocale Utility in Windows Vista
- 1722 Error When Install Kaspersky Internet Security and Anti-Virus in Vista
- Download Microsoft .NET Framework 3.5 SP1 Standalone Full Redistributable Setup Installer
- Download and Install Windows Vista SP2 Beta Symbols (6002.16497) via Microsoft Windows Update Registry Hack
- Workaround to Change System Display Language When Vista MUI Install Tool Fails
- Microsoft Money 2007 Unable to Connect to Internet to Sign In Online in Windows Vista Error
- Windows 7 Installation Fails and Hangs At 62% When Upgrade from Vista
Entries (RSS)
December 7th, 2009 08:08
CAN ANYONE TYPE IN THE CMD COMMANDS EXACTLY AS YOU DID.BECAUSE IM TOTALLY CONFUSED AND HAS GOT STUCK IN STEP 7
WHEN I TYPED THE FULL COMMAND THE CONFORMATION BOX CAME BUT WHEN I PRESSED YES IT TELLS THAT IT CANT FIND THE SPECIFIED FILE.
PLEAASE HELP ME.I REALLY NEED TO MAKE THIS WORK.
(I HAVE KEPT BOTH THE EXE FILES IN C:/DOTNET
I HAVE RENAMED THEM AS DOTNETFX AND DOTNETFXSP1)
December 6th, 2009 14:06
thanks! cool tips man! works fine!
guys if you’re getting errors pls check ur syntax in the cmd probably u missed the commas or slashes
again, many thanks!
December 3rd, 2009 22:08
you are the best! very good instructions!
would help if you mentioned to use “cd..” to get to directory, and “cd DotNet” to change directorys, but with a little research, my problem is all solved =D
December 3rd, 2009 19:49
“This patch package could not be opened.
Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.”
I m getting dis problem as well..can anyone send me the solution to this problem please?i followed every single steps exactly until this error pops out. Thanks a lot.
December 2nd, 2009 22:45
Hi i’m gettin this prob too …
“This patch package could not be opened.
Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.”
and i kno i’m correctly following the processes .. if possible can anyone plz upload the netfx.msi u get aftr the 3rd step … or even better give a solution to this problem … thanks
December 1st, 2009 03:06
The last command does not work.
It tells me the following:
“This patch package could not be opened.
Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.”
I’m not computer illiterate, I know that I’m doing everything correctly.
Still for some reason I can’t figure this out.
I extracted both executables to see if I could find “netfxsp.msp”, but it doesn’t exist.
Perhaps this could be the culprit?
I’d be grateful if someone with a greater knowledge could share their thoughts.
November 23rd, 2009 14:01
Hi, the commands work fine and all, but when it comes to running netfx.msi it rolls back at the end anyway so I am kinda stuck at the moment…
Is there any other way too do this ?
still its a great tutorial..
November 17th, 2009 01:18
can anyone please help me write to robvandamlaimiss@gmial.com and tell me what to do now here is my issue on step 8 i do everything but and error comes up error 1500.another instalation is in progress.before continuing this one?? what do i do and nothing else is being installed is it because i didnt do step 6??because i dont know what to do in step 6 please help me someone asap
November 9th, 2009 11:35
hey dude, im not sure if this might work for you but try shift + right click in your DotNet folder to run as administrator..then type the codes…hope it works for you
THANKS A MILLION FOR THIS BTW
November 8th, 2009 16:59
I can’t get this, i get to the commands and when i try to input them i get this message:
Error Creating Process
Reason: The system cannot find the file specified.
November 2nd, 2009 18:44
[...] Installing .NET 1.1 for Vista Essentially the steps are as follows … [...]
November 1st, 2009 00:25
thanks a ton!!!now i can play NBA 2K10 on my laptop!!!
October 19th, 2009 13:45
Thanks for this guide! Has saved me quite a few times already.
October 17th, 2009 10:53
I used this on Windows 7.
To change the directory in cmd: c:\DotNet
After running the commands given above, go into your DotNet folder located in C:/ and run netfx which is the installer application you just created.
Finally! It took me 6 hours to figure this out.
October 14th, 2009 21:35
you sir are all sorts of awesome! thanks for this!
October 6th, 2009 14:03
Well I’ve tried many solutions and I finally tried yours, unfortunately, still nothing works. I can’t get .net framework 1.1 to install. I’m using Vista Home Premium, 32bit.
October 5th, 2009 17:36
Awsome, thank for the fix. Now I can use my outdated software that comes with my Omron BP monitor and pedometer… Hoo-rah!
October 3rd, 2009 01:31
It shows errors in the form of compatibility warnings in Windows 7 64bit but seems to still allow the required application to operate, but it might effect some services associated with IIS on the box (according to the warning) The application I was running works like a charm now. I’m curious now if once the new MSI is created it’s portable so you don’t have to redo this and can just make this a part of an install procedure for workstations that require the old .net version.