That article notes that " This problem was first reported in August 2015 and these slow Windows Updates have become progressively worse over time.
There is currently a known issue where Windows Update will not run to completion on Vista SP2 computers - see the FAQ How to Fix Vista SP2 "Checking for Updates." Hangs and Slow Windows Updates pinned at the top of this board. I was able to find one example of a Windows Server 2008 installation where Control Panel | System and Maintenance | System showed that Service Pack 3 was installed (see the image posted by SC13Sonic in the spiceworks thread Has Anyone Seen a SP3 for Windows Server 2008 R2?) but the general consensus was that the incorrect Service Pack number was displayed because of a corrupted Windows registry entry.
Did you use Ex_Brit's ISO file to install Service Pack 1 and Service Pack 2 after reinstalling your Vista OS instead of downloading those service packs from the official Microsoft site and and applying them manually? Or were you attempting to repair a corrupted Vista SP2 installation with that ISO file? I'm not exactly clear from your post in that thread why you needed that ISO file or what you were planning to do it. I see you requested a Vista ISO file yesterday via a private message from Ex_Brit per post # 2,990 in the thread Vista ISO Download. This will ensure that you are not running an older version that could be causing conflicts with other software, etc.I've never heard of an official Service Pack 3 (SP3) released for Vista (or Windows Server 2008).
Method 5 – Install the latest Windows Installer versionįinally, you can do a search on Google for “Windows Installer” and download the latest version from Microsoft. This basically adds the required registry keys for the Installer service to work properly. Once you download it, unzip it and right-click on the. You can download the MSIServer package from WinHelpOnline. If that does not work, you can download the Windows Installer Service and re-install it! Kind of ironic eh!? Do this if you do not even see the service listed in the Services applet or if nothing else works. Method 4 – Reinstall Windows Installer Service Only change it to NT Authority\NetworkService if Local System Account does not work. Note that if it goes away when you chose Local System Account, just leave it at that setting.
The password will automatically be filled in for this account, so don’t change it.Īgain, restart your computer and see if the problem goes away. If that does not work, choose the This account: radio button and click Browse. Then restart your computer and see if the problem goes away. Now click on the Log On tab and under Log on as:, choose Local System Account and tick the Allow this service to interact with the desktop checkbox. Go to the Services section again like mentioned above (Start, Run, services.msc) and right-click on Remote Procedure Call (not the one that says RPC Locator) and choose Properties. Sometimes the issue can be caused by another service called Remote Procedure Call. Method 3 – Modify Remote Procedure Call Service Again, just go to Services and right click on Windows Installer and choose Restart. Once you rename it, then you can restart the Windows Installer service. If that is the case, then you should rename the extra msiexec file with a. By default, there should only be one msiexec.exe file in that directory, but sometimes another one gets created with no extension and a size of 0 KB. Method 2 – Delete MSIEXEC with no extensionĪnother strange thing that can happen is the creation of a second msiexec file in your C:\Windows\system32 directory. You can also start the service by going to Start, Run and type in net start MSIServer into the Run box.