Discussion:
Win7 warning using Iexpress installer created on WinXP
(too old to reply)
Big Slim
2012-11-06 15:39:14 UTC
Permalink
I created a simple executable ("exe") file using Iexpress in Windows
XP. It contains two files I want to distribute to users. It runs fine
on Windows XP, but it results in a warning message on Windows 7 that
reads, "This program might not have installed correctly." However, the
files unpack correctly and are usable.

Originally, I thought the error might be the result of a BAT file
included with the installer that moved the files to a specific user
directory. However, I get the warning message even when I don't bundle
the BAT file.

Interestingly, the files were still placed correctly in the user
directory I specified when I included the BAT file. The warning appears
to be trivial, but it is annoying.

Has anyone here had the same experience? If there is no fix, could
there be an easier way to accomplish what I'm trying to do? Is there a
better group I should approach with this question? I'm a UNIX person,
so I'm not very familiar with all the Microsoft Usenet groups.

The goal is to distribute branded PowerPoint templates to a large
office. The BAT file ensures the files get put in the proper directory
no matter what version of Office the end user has installed.

Thanks in advance.
JJ
2012-11-06 20:07:24 UTC
Permalink
Big Slim <***@bones.com> wrote:
[snip]
Post by Big Slim
Has anyone here had the same experience? If there is no fix, could
there be an easier way to accomplish what I'm trying to do? Is there a
better group I should approach with this question? I'm a UNIX person,
so I'm not very familiar with all the Microsoft Usenet groups.
Blame it on Windows 7:

http://gnoted.com/disable-this-program-might-not-have-installed-correctly-
windows-7/
Big Slim
2012-11-07 16:54:09 UTC
Permalink
Post by JJ
[snip]
Post by Big Slim
Has anyone here had the same experience? If there is no fix, could
there be an easier way to accomplish what I'm trying to do? Is there a
better group I should approach with this question? I'm a UNIX person,
so I'm not very familiar with all the Microsoft Usenet groups.
http://gnoted.com/disable-this-program-might-not-have-installed-correctly-
windows-7/
Interesting. Thank you for sharing this link. I wonder if this happens
anytime you run an installer on Windows 7. If not, I wonder what steps
(if any) can be taken to prevent it. Should I just give up on trying to
fix this issue?
Michael Bednarek
2012-11-08 08:06:34 UTC
Permalink
On Wed, 07 Nov 2012 10:54:09 -0600, Big Slim wrote in
Post by Big Slim
Post by JJ
[snip]
Post by Big Slim
Has anyone here had the same experience? If there is no fix, could
there be an easier way to accomplish what I'm trying to do? Is there a
better group I should approach with this question? I'm a UNIX person,
so I'm not very familiar with all the Microsoft Usenet groups.
http://gnoted.com/disable-this-program-might-not-have-installed-correctly-windows-7/
Interesting. Thank you for sharing this link. I wonder if this happens
anytime you run an installer on Windows 7. If not, I wonder what steps
(if any) can be taken to prevent it. Should I just give up on trying to
fix this issue?
You could try to start your batch file with
SC stop PcaSvc
--
Michael Bednarek "ONWARD"
Big Slim
2012-11-08 14:27:33 UTC
Permalink
Post by Michael Bednarek
On Wed, 07 Nov 2012 10:54:09 -0600, Big Slim wrote in
Post by Big Slim
Post by JJ
[snip]
Post by Big Slim
Has anyone here had the same experience? If there is no fix, could
there be an easier way to accomplish what I'm trying to do? Is there a
better group I should approach with this question? I'm a UNIX person,
so I'm not very familiar with all the Microsoft Usenet groups.
http://gnoted.com/disable-this-program-might-not-have-installed-correctly-w
indows-7/
Interesting. Thank you for sharing this link. I wonder if this happens
anytime you run an installer on Windows 7. If not, I wonder what steps
(if any) can be taken to prevent it. Should I just give up on trying to
fix this issue?
You could try to start your batch file with
SC stop PcaSvc
The problem is not the batch file. The problem is the warning message
thrown by the EXE file. I was able to determine this by simply
including a file in the Iexpress setup wizard (without adding the batch
file). Even though the file gets "installed" correctly, Windows 7 still
complains that "this program might not have installed correctly."
Spalls Hurgenson
2012-11-09 14:50:39 UTC
Permalink
Post by Big Slim
I created a simple executable ("exe") file using Iexpress in Windows
XP. It contains two files I want to distribute to users. It runs fine
on Windows XP, but it results in a warning message on Windows 7 that
reads, "This program might not have installed correctly." However, the
files unpack correctly and are usable.
Originally, I thought the error might be the result of a BAT file
included with the installer that moved the files to a specific user
directory. However, I get the warning message even when I don't bundle
the BAT file.
Interestingly, the files were still placed correctly in the user
directory I specified when I included the BAT file. The warning appears
to be trivial, but it is annoying.
Has anyone here had the same experience? If there is no fix, could
there be an easier way to accomplish what I'm trying to do? Is there a
better group I should approach with this question? I'm a UNIX person,
so I'm not very familiar with all the Microsoft Usenet groups.
The goal is to distribute branded PowerPoint templates to a large
office. The BAT file ensures the files get put in the proper directory
no matter what version of Office the end user has installed.
Thanks in advance.
See http://msdn.microsoft.com/en-us/library/bb756937.aspx for the
logic used by the PCA

Things it checks
1) did the installation program create a registry entry for add/remove
programs?
2) does the program trigger UAC, either by requiring it be run as
administrator, create/copy a file into "Program Files"
3) use deprecated Windows components
4) uses unsigned drivers
5) creates control-panel applets that require administrator access

According to Microsoft, "the best option to exclude a program from PCA
is to include, with the program, an application manifest with run
level (either Administrator or as limited users) marking for UAC. This
marking means the program is tested to work under UAC (and Windows
Vista and Windows Server 2008). PCA checks for this manifest and will
exclude the program. This process applies for both installer and
regular programs. "
Big Slim
2012-11-09 22:07:22 UTC
Permalink
Post by Spalls Hurgenson
Post by Big Slim
I created a simple executable ("exe") file using Iexpress in Windows
XP. It contains two files I want to distribute to users. It runs fine
on Windows XP, but it results in a warning message on Windows 7 that
reads, "This program might not have installed correctly." However, the
files unpack correctly and are usable.
Originally, I thought the error might be the result of a BAT file
included with the installer that moved the files to a specific user
directory. However, I get the warning message even when I don't bundle
the BAT file.
Interestingly, the files were still placed correctly in the user
directory I specified when I included the BAT file. The warning appears
to be trivial, but it is annoying.
Has anyone here had the same experience? If there is no fix, could
there be an easier way to accomplish what I'm trying to do? Is there a
better group I should approach with this question? I'm a UNIX person,
so I'm not very familiar with all the Microsoft Usenet groups.
The goal is to distribute branded PowerPoint templates to a large
office. The BAT file ensures the files get put in the proper directory
no matter what version of Office the end user has installed.
Thanks in advance.
See http://msdn.microsoft.com/en-us/library/bb756937.aspx for the
logic used by the PCA
Things it checks
1) did the installation program create a registry entry for add/remove
programs?
2) does the program trigger UAC, either by requiring it be run as
administrator, create/copy a file into "Program Files"
3) use deprecated Windows components
4) uses unsigned drivers
5) creates control-panel applets that require administrator access
According to Microsoft, "the best option to exclude a program from PCA
is to include, with the program, an application manifest with run
level (either Administrator or as limited users) marking for UAC. This
marking means the program is tested to work under UAC (and Windows
Vista and Windows Server 2008). PCA checks for this manifest and will
exclude the program. This process applies for both installer and
regular programs. "
The problem is resolved when the EXE file is created using Iexpress on
Win7. I believe the warning in this case was thrown by the 32-bit
emulator in Windows 7, which is probably just a safety measure.

Loading...