Thanks Phil,
i moved the post to wix users.
i set the upgrade code for the major upgrade(New Bundle) to be the same as
the upgrade code in the RTM(Old Bundle). Now it removes the entry of the Old
Bundle from the ARP (also from the registry) but the patch is not removed
from the "installed updates
Hello,
I'm currently modifying an existing bundle that I did not set up. I'm very new
at this and I'm having a bit of trouble getting what I assume to be a simple
thing up and running. The goal is to have a bootstrapper launch our own WPF
Try adding Secure="yes" on the Property. This means that "the Property can
be passed to the server side when doing a managed installation with elevated
privileges". I don't fully understand what "the server side" is, but I
think it has something to do with the "transactional" part of the
installa
Whether or not this is a true issue or not, the error still needs to
be looked into in order to minimize the possibility that it is
contributing to the error you asked about. Do you happen to have a
log from a "fresh install?"
Carter
Quoting Michael Ogilvie :
> Hello,
>
> I don't think th
Hello,
I don't think that is the issue.
If I install on a fresh install of Windows that has not seen our old
installer, the new Wix installer works perfect all drivers are installed
first time.
>From what I can tell, it does look like the drivers are added to the
driverstore just not copied over
See Also:
http://stackoverflow.com/questions/13345788/propertyref-to-require-combobox
Quoting Carter Young :
> Note 1: Error 2205:
> 2205
> Database: [2]. Table does not exist: [3].
>
> [2] = Install Database Name
> [3] = Table Name
>
> See http://msdn.microsoft.com/en-us/library/aa372835.aspx
>
Note 1: Error 2205:
2205
Database: [2]. Table does not exist: [3].
[2] = Install Database Name
[3] = Table Name
See http://msdn.microsoft.com/en-us/library/aa372835.aspx
If an Upgrade/Repair option always works, my hunch is that Table [3]
is created during the Repair, but not during a fresh in
Thanks Phill,
The Product\manufacture name and INF Manufacture name do match so that
is not the issue.
The two drivers that seem to have the issue are the USB and FW but as I
said the strange thing is, if I do a repair with the same install
everything installs fine.
Looking at the setupapi.dev.l
True, zero is returned on success. A non-zero return may indicate a failure,
or it may indicate 'no action taken' (0x8007015e), a reboot is needed (3010)
or some other condition.
http://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx
--
View this message in context:
http://windows-inst
Take a look at using Root="HKMU"
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Vary-registry-hive-at-runtime-based-on-InstallScope-tp7595160p7595169.html
Sent from the wix-users mailing list archive at Nabble.com.
---
>>>DIFXAPP: INFO: No matching devices found in INF
"C:\Windows\System32\DriverStore\FileRepository\pxlgevndis6.inf_amd64_ne
utral_fe3715a4af78ac12\PxLGevNdis6.inf" on the Machine.
I would configure the target system to generate a verbose setupapi log, and
study both (msi and setupapi.dev.log)
If I recall correctly, one can also get 3010, "restart required", which is sort
of intermediary between success and failure, but I am not an expert on these
matters.
Keith Douglas
Programmer Analyst | Programmeur analyste
Questionnaire Development Services - CAI Social | Services de développem
A client wants to run our (StdBA) installer silently from a batch file and
detect whether or not the installation was successful. Would I be right in
thinking the exit code will be zero on success and non-zero on failure? If
not, what's the best way to determine if the installation succeeded?
13 matches
Mail list logo