What version of the WiX toolset are you using?
On Tue, Mar 27, 2012 at 12:49 PM, Wesley Manning wrote:
> Hi,
>
> It's a very old laptop. I ran windows update on it and it listed 100
> updates. Note at this time my burn package (i.e. my program) was still
> installed. I installed the 100 update
Hi,
It's a very old laptop. I ran windows update on it and it listed 100 updates.
Note at this time my burn package (i.e. my program) was still installed. I
installed the 100 updates and rebooted the computer. I tried uninstalling my
program and it failed and this was in the log:
[0F24:0B6
I tried to enable a disabled feature in an msp using Wix 3.5 and Windows
Installer 4.5, and ran into two problems.
I created the disabled feature as a placeholder is an msi, and that msi has
already been delivered to customers. The purpose was so that the disabled
feature could be enabled late
Could you use he ActiveSetup registry key instead of the RunOnce key? Is
that monitored also?
http://blogs.flexerasoftware.com/installtalk/2011/11/using-active-setup-to-r
epair-user-settings.html
From: "Peter Hull"
Sent: Tuesday, March 27, 2012 9:31
This has been seen before and reported as a bug:
http://sourceforge.net/tracker/?func=detail&aid=3431068&group_id=105970&atid=642714
I believe it only affects Windows XP - is that what your customer has?
I don't think there is a workaround. According to Trend's documentation, signed
executabl
Ahh, yes. You can also right-click the .zip file after downloading it and
choose Properties then click the "Unblock" button at the bottom.
On Tue, Mar 27, 2012 at 6:13 AM, John L Krupka wrote:
> Finally got back into looking at this issue. The problem is related to
> using
> the files from the t
That's a standard part of any software installation (usually for handling
reboots). There were conversations earlier on this mailing list about Trend
Micro OfficeScan aggressively killing anything that tried to touch that
key. It apparently is a configuration setting in the virus checker to be
that
Strange, this is the first email I've seen on this topic.
On Tue, Mar 27, 2012 at 4:58 AM, stewarth wrote:
> I'm dont know if I'm posting correctly because no-one seems to look at my
> posts .
>
> Anyway - i resolved this issue. I needed to set the
> ResolveSourceEventArgs.Result to Result.Retr
Hey everyone!
I'm getting the following issue reported from a user:
> I tried to install the typesafe stack at work, but the virus checker
software we use (Trend Micro OfficeScan) blocked the installer.
> I think the problem is that the installer uses registry key
HKLM\SOFTWARE\Microsoft\Windows\
Finally got back into looking at this issue. The problem is related to using
the files from the the binaries download. After unzipping them to disk, the
files are locked since they were created on another machine. It would be
nice if the Windows Explorer visually indicated this similar to how is
I'm dont know if I'm posting correctly because no-one seems to look at my
posts .
Anyway - i resolved this issue. I needed to set the
ResolveSourceEventArgs.Result to Result.Retry.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Can-t-get-SetLocalS
Hi list,
I've got some trouble with msi's reboot mechanism:
The installer I'm currently developing sometimes requires a reboot.
Depending on whether a reboot is required or not, I want the
installer's UI to either launch a configuration utility or schedule it
in the RunOnce registry.
Both CustomA
12 matches
Mail list logo