We have an issue in our product installation in XP OS with Windows Installer 4.5 & it’s Hot Fix 981669. The installation is prematurely ending.
Error 1719: The Windows Installer Service could not be accessed.
Without that Hot Fix we are able to install the application.
There are several pages on the web talking about problems with the Windows Installer, but no real answers as to how to solve the problem. For example, here, in method 2 they are asking to reinstall windows installer. I suggested this as a workaround for the issue.
The Windows Installer Hot Fix 981669, is replacing two DLLs: msi.dll & Msihnd.dll.
After Windows Installer Hot Fix 981669:
msi.dll [version 4.5.6002.22362]
Msihnd.dll [version 4.5.6002.22193]
Before it was:
msi.dll [version 4.5.6001.22159]
Msihnd.dll [version 4.5.6001.22159]
With original versions of Windows Installer 4.5 DLLs (msi.dll [version 4.5.6001.22159] and Msihnd.dll [version 4.5.6001.22159]) we are able to install the product without any issues.
We are using WIX (Votive-2.0.5805.0.msi) application to create the product MSI.
If you have any idea about this issue please help.
Related
I updated a vb windows forms application using visual studio 2015. I need to install this on a windows xp machine.
I updated my application to run using .net framework 4.0, the same as the one installed in the xp machine.
When I tried to install it the first time, it asked me to restart the machine, which I did. after restarting it gave me the error that installation is incomplete.
I have been researching all morning on how to fix it, i tried the dpca.dll solution, i tried restarting the windows installer service, i used msiexec to view the logs, and now it gives me the error that a dll required for this install to complete could not be run. I have no idea which dll, it doesn't say.
My application is fine. It builds and installs beautifully on windows 7 and above.
Please help me before I smash the windows xp machine into pieces.
I came across a comment that i can run the executable itself, just needed to copy all the dll files and put it in the same folder as the executable. So I just copied the whole folder and run the exe on the xp machine and it works.
I am putting together a WiX installer that includes silently installing DirectX 9:
dxsetup.exe /silent
How do I tell WiX how to un-install DirectX? Is there another switch on the command line?
I need to be able to configure the installer to un-install DirectX automatically, else users complain if they can't uninstall.
For the DirectX End-User Runtime (aka DirectSetup or DXSETUP), it has long been recommended that you don't even try to uninstall it.
In any case, on most versions of Windows you can't 'uninstall' DirectX and running DXSETUP doesn't actually "Install DirectX" either as it's built into the OS. It can only be updated by installing a new version of the OS, installing a Service Pack, or applying a Windows Update. This applies to all versions of Windows starting with Windows XP Service Pack 2, Windows Server 2003 Service Pack 1, and Windows XP x64 Edition.
DXSETUP is still useful for deploying stuff like legacy D3DX9, D3DX10, D3DX11, XACTEngine, XAudio 2.7, XInput 1.3, D3DCompile #43 or earlier, etc. It just doesn't ever install "DirectX".
See No So Direct Setup. If after reading this article you still think you need to run DXSETUP as part of your deployment, you should pick up the latest version of DXSETUP to avoid some potential issues, and trim it down to just those CABs you actually use in your application.
I'm trying to figure out why the simplest firebreath plugin wont install on a German Windows XP SP3. I'm running Windows XP as a virtual machine.
The event viewer in Windows XP tells me something about the Windows Installer aborting but not why. I'm logged in as the administrator.
The installer works on Windows 7.
For development I use Windows 7, Visual Studio 2010 and some one months old firebreath trunk.
Is this is known problem? What are the typical steps I could use to track down the issue?
Regards,
Christian
If you get an error saying module can't be found it means that you are missing a .dll file needed to make the plugin work. The most common if it works on most computers (or many) but not that one is that your .dll was compiled with a dynamic runtime, in which case you'll have to install the common runtime for whatever version of visual studio you compiled it with.
For example, the runtime distributable for vs2008 is at http://www.microsoft.com/en-us/download/details.aspx?id=29
Dependency Walker might help you to find out which dll is missing.
There is a limitation with LUA (non-administrative) patching an application on XP when the original installation was not done from removable media (when using Windows Installer 3). This limitation has apparently been removed in Windows Installer 4
For such an installed application, would upgrading Windows Installer to v4 permit me to LUA-patch the application? Or does the fact that the app was originally installed using Installer v3 limit me?
I tried to start developing for Microsoft Surface. For that I first installed Visual Studio 2008. Then I followed this guide:
http://msdn.microsoft.com/en-us/library/ee804897.aspx
However there it says that only Windows Vista is supported. I'm still running Windows XP on my laptop and old PC and I don't want to update if not absolutely necessary. So I wonder if it is really necessary to use Windows Vista or if it is just a recommendation.
I already tried to install it on Windows XP, but every time i start the Surace SDK installer, the following error message appears:
This installation package cannot be
installed by the Windows Installer
service. You must install a Windows
service pack that contains a newer
version of the Windows Installer
service.
So I was wondering if this is the problem because I don't use Windows Vista. And if not, how can I solve this problem?
Yep, probably.
You can try installing the latest version of Windows installer.
http://support.microsoft.com/kb/942288
Windows vista is definitely required. I can't tell you if this is an artificially imposed requirement, or a physical incompatibility, but vista has been a requirement to install the SDK since was first released to Microsoft partners.
surface has a number of hard Vista dependencies. DWM is the most obvious one