westes
asked on
Cannot Upgrade Microsoft Installer on Windows 2000
I have a strange problem on a Windows 2000 SP4 server. It had version 3.01 of the Microsoft installer, located at:
c:\winnt\system32\msiexec. exe. I looked for duplicate files and there are none in the path. I tried to upgrade this to 3.1 and 3.1 V2, and both of these claim to install the new version. Yet when we go to the installer location - even after reboot - it remains at version 3.01.
Now it gets weird. I go to c:\winnt\system32 and manually disable the command msiexec.exe by renaming it. At command line I type "msiexec" and the command not only executes, but it repopulates itself on disk from a cache.
It appears that I have some feature turned on here that forbids update of this component and recreates it from a cached copy. How do I stop that and allow the upgrade of installer from the Microsoft setup file?
c:\winnt\system32\msiexec.
Now it gets weird. I go to c:\winnt\system32 and manually disable the command msiexec.exe by renaming it. At command line I type "msiexec" and the command not only executes, but it repopulates itself on disk from a cache.
It appears that I have some feature turned on here that forbids update of this component and recreates it from a cached copy. How do I stop that and allow the upgrade of installer from the Microsoft setup file?
did you try uninstalling the previous version first?
I don't believe that you can do that. Windows 2000 has been unsupported for years now. https://support.microsoft.com/en-us/lifecycle?C2=1131
More info about Released Versions of Windows Installer: https://msdn.microsoft.com/en-us/library/aa371185%28v=vs.85%29.aspx
I'm trying to boot up my Windows 2000 Pro system which has all the updates to see what version is on that computer. It's taking forever.
More info about Released Versions of Windows Installer: https://msdn.microsoft.com/en-us/library/aa371185%28v=vs.85%29.aspx
I'm trying to boot up my Windows 2000 Pro system which has all the updates to see what version is on that computer. It's taking forever.
ASKER
More weirdness. I see both Microsoft Installer 3.0 and Microsoft Installer .1 installed.
I uninstall 3.0, but typing MSIEXEC at command line still gives 3.01. I tried to also uninstall 3.1, but that uninstaller complains that about 20 Windows 2000 hotfixes will no longer work. Should I uninstall anyway, reboot, and then try to install 3.1 V2 again?
I uninstall 3.0, but typing MSIEXEC at command line still gives 3.01. I tried to also uninstall 3.1, but that uninstaller complains that about 20 Windows 2000 hotfixes will no longer work. Should I uninstall anyway, reboot, and then try to install 3.1 V2 again?
ASKER
Dave, I believe the "Windows File Protection" feature was enabled on that system. Something tells me that this is the component that may be restoring MSIEXEC from a cached copy.
John, how did you get that display window?
In Windows 2000, Start, Run, msiexec.exe and up came the window I showed above.
ASKER
John, after I confirm the uninstall, I get a modal error dialog:
"This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package."
I am thinking I already did uninstall it (see earlier post in this thread), and something is repopulating the EXE from a cache. When I run the uninstall again perhaps the uninstaller is missing and did not get repopulated.
"This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package."
I am thinking I already did uninstall it (see earlier post in this thread), and something is repopulating the EXE from a cache. When I run the uninstall again perhaps the uninstaller is missing and did not get repopulated.
Try running the Windows 2000 System File Checker.
https://support.microsoft.com/en-us/kb/222471
That might fix the error.
For Windows XP you need the XP install disk to run SFC. You may need the Windows 2000 install disk to run SFC on Windows 2000.
https://support.microsoft.com/en-us/kb/222471
That might fix the error.
For Windows XP you need the XP install disk to run SFC. You may need the Windows 2000 install disk to run SFC on Windows 2000.
ASKER
John, SFC is already active on the system. Wouldn't I need to actually disable SFC and then do the install of the new version of Installer?
I did not disable SFC. I am saying run SFC. This is standard repair step. It should NOT be running on its own - just there. If it is running, something has caused it not to stop. Stop it (Task Manage) and restart the system.
ASKER
I doubt we have the original Windows 2000 CD with SP4 slip streamed on it. I can try to run it with an older install CD.
My point was that SFC was already configured on this system to have a cache and use it to replace critical system files when they are overwritten in the wrong way.
I tried to uninstall 3.1 in Control Panel Add/Remove Programs and that claims the uninstall worked and rebooted. After reboot, 3.1 still shows as installed in Control Panel, and funnier still the command line still brings up 3.01.
I am thinking I should completely disable SFC through registry, reboot, then repeat the uninstall of 3.1 until that actually takes effect. Then reboot and reinstall 3.1
My point was that SFC was already configured on this system to have a cache and use it to replace critical system files when they are overwritten in the wrong way.
I tried to uninstall 3.1 in Control Panel Add/Remove Programs and that claims the uninstall worked and rebooted. After reboot, 3.1 still shows as installed in Control Panel, and funnier still the command line still brings up 3.01.
I am thinking I should completely disable SFC through registry, reboot, then repeat the uninstall of 3.1 until that actually takes effect. Then reboot and reinstall 3.1
I do not understand your point about SFC. It is standalone command that is not running and not a service. If it really is running, it should not be and you should stop it.
I get the same display as John showed above with version 3.01. This page is the download for version 2 of 3.1 : https://www.microsoft.com/en-us/download/details.aspx?id=25 It does say that Windows 2000 Service Pack 4 is supported.
I am a bit curious about what you think you will be installing with it.
I am a bit curious about what you think you will be installing with it.
ASKER
Well, it is staying weird. I uninstall 3.1 and reboot. Now the system shows version 2.0, so that looks like progress. I reinstall 3.1 and reboot. Now the system once again shows 3.01.4000.1823, the same release showing in John's post.
My real objective here is to install VMWare Converter 3.03 on the computer. That installer complains about that Microsoft installer being fed the wrong arguments, and Windows pops up the Installer help screen (the one in John's post).
I'm about ready to turn off SFC and try again.
My real objective here is to install VMWare Converter 3.03 on the computer. That installer complains about that Microsoft installer being fed the wrong arguments, and Windows pops up the Installer help screen (the one in John's post).
I'm about ready to turn off SFC and try again.
ASKER
Can someone else tell me what release of MSIEXEC reports on command line after you install 3.1 V2 from Microsoft's official download?
ASKER
John, the command to enable automatic background operation of SFC is SFC /ENABLE.
Unfortunately, I do not see an SFC /DISABLE. You have to set a registry key:
http://www.pctools.com/guides/registry/detail/790/
Unfortunately, I do not see an SFC /DISABLE. You have to set a registry key:
http://www.pctools.com/guides/registry/detail/790/
Are you sure VMware Converter is supported? It is NOT supported on my Windows 2000 machine. I tried to run it to enlarge the VMDK file and could not - not supported.
ASKER
VMWare Converter is the utility that turns the Windows 2000 install into a virtual machine. I have run 3.03 (an older release) on many Windows 2000 computers. I believe that is one of that last VMWare Converter releases to officially support Windows 2000.
I know what VMware Converter is and how it works. I have it here and used on Virtual Machines I have.
I confess I do not have V3.03 - just V4 and up.
I confess I do not have V3.03 - just V4 and up.
Did you try disabling SFC (Windows File Protection) as outline in the first section of the article you posted? I do not have SFC running and I cannot test this for you.
But if you can turn it off, do so and try upgrading the installer again.
I have not gone down your path. My Windows 2000 installer works for all I need and I can live with my disk allotment in VMware.
But if you can turn it off, do so and try upgrading the installer again.
I have not gone down your path. My Windows 2000 installer works for all I need and I can live with my disk allotment in VMware.
ASKER
John, as an aside, I would love to have VMWare Converter 4.3. Do you know of a legit download site for it?
No. VMware's policy is to withdraw software and not make it available. I did some looking around and could not find any legitimate sites with old versions.
ASKER
So I permanently disabled SFC and rebooted.
I then uninstalled Microsoft Installer 3.1 and rebooted. That left me with the default Installer 2.0
I tried to install VMWare Converter 3.0.3 and that failed with an installer error.
I then installed Installer 3.1 V2 and rebooted again.
I then tried to install VMWare Converter 3.0.3 and it fails again with bad syntax errors for Installer.
I can't get Installer 4.5 to install on a Windows 2000 SP4 system. So at this point I seem to have exhausted obvious options.
I then uninstalled Microsoft Installer 3.1 and rebooted. That left me with the default Installer 2.0
I tried to install VMWare Converter 3.0.3 and that failed with an installer error.
I then installed Installer 3.1 V2 and rebooted again.
I then tried to install VMWare Converter 3.0.3 and it fails again with bad syntax errors for Installer.
I can't get Installer 4.5 to install on a Windows 2000 SP4 system. So at this point I seem to have exhausted obvious options.
I have looked on your behalf and have nothing more to suggest at this point in terms of your existing server.
Is it feasible to build a VMware Workstation Guest and install Server 2000 as a guest machine. That will work as Server 2000 is a supported guest.
Is it feasible to build a VMware Workstation Guest and install Server 2000 as a guest machine. That will work as Server 2000 is a supported guest.
ASKER
John, if I have to build an OS from scratch, I would make it Windows Server 2012.
I'm just perplexed what is going on because I have installed VMWare Converter 3.0.3 on many Windows 2000 computers in the past.
I also tried to build the VMWare Converter 3.0.3 "cold clone" CD and booted that, but it clearly has device driver issues because it cannot see the installed OS on the server it boots from.
I'm just perplexed what is going on because I have installed VMWare Converter 3.0.3 on many Windows 2000 computers in the past.
I also tried to build the VMWare Converter 3.0.3 "cold clone" CD and booted that, but it clearly has device driver issues because it cannot see the installed OS on the server it boots from.
If you just need a server, then Server 2000 is long dead, so then yes, build a Server 2012.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Provided a step by step procedure for overcoming the limitation.