Sometimes while trying to install or reinstall a program on your Windows 10 computer, most users experience an error such as "Fatal error, Installation ended prematurely because of an error".
Here at Outsource Path, as part of our Technical Support Services, we regularly help our customers to fix Windows related errors.
In this context, we shall look into the causes of this error and how to get rid of it easily.
This error is most likely caused by some files that may have been left behind by the previous installation of the program.
Each time a program is uninstalled, it leaves behind its files and if the uninstallation process wasn’t completed properly, then it would result to errors like “Fatal error, Installation ended prematurely because of an error”.
Additionally, this error is generic in nature and could occur when performing any software reinstallation or installation.
In order to fix this error, you can try to install or reinstall the program in a Clean Boot State or restart the Windows Installer Service.
You could also try to re-register the Windows Installer Service or re-register the VBScript.dll file.
Now let us see how to do this.
It is possible that there are some third-party applications in your computer that’s preventing the program from getting installed and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem.
In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs.
Note that you have to disable and enable one process at a time.
i. Log onto your PC as an administrator.
ii. Type in msconfig in the Start Search to open the System Configuration utility.
iii. From there, go to the General tab and click “Selective startup”.
iv. Clear the “Load Startup items” checkbox and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
v. Next, click the Services tab and select “Hide All Microsoft Services” checkbox.
vi. Click Disable all.
vii. Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And to configure Windows to use the usual startup, just simply undo the changes.)
viii. After you’ve set your computer into a Clean Boot State, make sure that you’re signed in as administrator and then try to install the program again.
The next thing you can do to fix the problem is to restart the Windows Installer Service.
To do this, follow these steps:
i. Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and then hit Enter to open the Windows Services Manager.
ii. Next, look for the Windows Installer service among the list of services shown.
iii. Once you found it, right-click on it and open its Properties.
iv. From there, click on the Stop button and then click on the Start button.
v. But if it isn’t running, then just click on the Start button.
To do this, follow the process below;
i. Tap the Win + R keys to open the Run dialog box.
ii. Then type the “msiexec /unregister” command and hit Enter to unregister the Windows Installer Module.
iii. Next, type the “msiexec /regserver” command and hit Enter to re-register the Windows Installer Module.
iv. Now restart your computer and see if un-registering and re-registering the Windows Installer Module fixed the problem or not.
You may have to re-register the vbscript.dll file using the regsvr32.exe before you can successfully install the program and fix the error. The Regsvr32 tool is a command-line utility that can be used to register and un-register the OLE controls as DLL and ActiveX (OCX) controls in the Windows operating system.
Follow the steps below to use it.
i. Open Command Prompt as admin from the WinX menu.
ii. Next, type regsvr32.exe vbscript.dll in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
iii. You should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.