msiexec

Error 2203 while extracting msi

拜拜、爱过 提交于 2019-12-05 00:21:06
I am getting 2203 error while extracting msi with following command. msiexec /a "C:\Test\Installer.msi" /QB targetDIR="C:\Test\Eval" /LV* "C:\Test\INST_Logfile.log" Please consider following points while answering: Logged-in user and SYSTEM account has full access on %TEMP%,C:\Windows\Installer. msi is not marked as ReadOnly. Checked Windows installer service and it is working fine. Tried unregister and register msiexec MSIEXEC /UNREGISTER MSIEXEC /REGSERVER Restarted system Below is error captured in log: MSI (s) (88:A4) [14:09:27:551]: Executing op: DatabaseCopy(DatabasePath=C:\Test

Creating a silent installer for a MSI

与世无争的帅哥 提交于 2019-12-04 21:12:14
What is the best way to make a silent installer (or unattended) for a program that was already created and has a msi installer? At work I'm told to create an installer that is automated and does all the interaction with the user automatically so that the user essentially just hits one button and it runs through the msi installer of the program that was already developed. Also I have to make it replace a couple files in the directory. Is it possible to make a installer automate another installer? Can it be done using WIX in visual studios or NSIS? Do I need to be able to pull the already

Trying to find the MSI product code for Java 8 Update 25 in to work with WSUS Package Publisher

大憨熊 提交于 2019-12-04 21:06:37
I'm trying to create a 3rd party custom update through WSUS Package Publisher however I can't manage to get the MSI code for Java as there is no MSI installer to use MSIReader on. If anyone knows how I can find this code then it would be much appreciated. It's managing to make me look bad as a Sys Admin at work. Cheers, Glympse. Two solutions : Install the product and search in : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall Or to be aware that Oracle always used the same schema for these MSI Product code Java 8 : 26a24ae4-039d-4ca4-87b4-2f8 32 1 8 0 25 f0 = 32 Bit -

How to push MSI with parameter using SCCM server

≡放荡痞女 提交于 2019-12-04 07:14:40
问题 I want to push MSI installer with parameter using SCCM server. i.e. msiexec.exe /i "setup.msi" INSTALLFOLDER="SpecifiedInstallationLocation" CONFIGFILE="FileName" Can I use parameter name defined by me or I have to use specific parameter name in command line? Is any specific format to pass parameter? Can I able to pass parameter to MSI installer? If I use same command in batch file then it will works properly. 回答1: In general questions about SCCM or corporate deployment tools may be better

Why would a WiX installation create two entries in HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\

主宰稳场 提交于 2019-12-04 06:31:34
问题 I'm trying to uninstall an older version of our product which was installed using a WiX-built installer and after uninstalling it silently: msiexec /x{GUID} the program still appears in Control Panel. I've opened a separate item to explore that mystery, but another curious issue has popped up. I noticed that after running the install for this program, two entries (GUIDs) are added to HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall. One with the product GUID and one that I

What are the Python 3 os commands to establish “writable data files and C-Drive paths” for a typical Windows 10 Application

巧了我就是萌 提交于 2019-12-04 05:31:59
问题 What are the Python 3 os commands to establish "writable data files and C-Drive paths" for a typical Windows 10 Application. There are several parts to this question: My Python 3 program creates (multiple) data files as part of it's purpose. When my MSI installer installs into /Programs, my Python executable does not have permission to create and write data files. Thus, the first part of my question is: Do I need to change my Python 3 program to create data files in a specific directory

WiX .NET Bootstrapper - Feature Selection

陌路散爱 提交于 2019-12-04 05:26:05
We are trying to get a custom .NET Bootstrapper to selectively install features in an MSI package through our WiX installer. Having registered to the event PlanMsiFeature we thought that we would be able to access the features in our MSI and exclude certain features based upon preset conditions. The event, however, never appears to be invoked. Has anybody managed to use this event successfully? Many thanks. We solved this issue. There were a couple of key items missing. 1) In the Bundle that contains our application, the MSI Package was required the following attribute. EnableFeatureSelection=

MsiExec progress catch

与世无争的帅哥 提交于 2019-12-03 21:19:15
I'm writing a small app to install some product and uninstall some other in silent mode. Every product has its MSI file and nothing else and my app manifest states that it should be run with admin privileges. It's pretty easy to run msiexec with proper arguments to accomplish my task (just a bunch of code) and everything is working fine. Anyway some package takes a lot of time to finish and on some old pc user is asking if something is still going on in background or it's hang. So is it possible to "catch" msiexec progress and for example update a progressbar on my app? Sounds crazy, but I'm

Run MsiExec from PowerShell and get Return Code

99封情书 提交于 2019-12-03 05:38:06
问题 With BAT/CMD script I can simply use "msiexec /i <whatever.msi> /quiet /norestart" and then check %errorlevel% for the result. With VBScript , using the Wscript.Shell object Run() method, I can get the result like this: "result = oShell.Run("msiexec /i ...", 1, True)" How can I do this with PowerShell? 回答1: I would wrap that up in Start-Process and use the ExitCode property of the resulting process object. For example (Start-Process -FilePath "msiexec.exe" -ArgumentList "<<whatever>>" -Wait

Uninstalling an InstallShield Installscript MSI program using C# silently

こ雲淡風輕ζ 提交于 2019-12-02 21:10:42
问题 This is going to be very specific to InstallShield, so I doubt anyone has dealt with this before, but I wrote a batch file to uninstall prior versions of our product and it doesn't work. (We always uninstall prior versions prior to an install/upgrade since the Upgrades in InstallShield don't seem to work). Uninstalling Installscript MSI projects is very different from typical uninstalls in that you need to "record" an uninstall and store the results in a file i.e.: setup.exe /x /r /f1"C:\temp