This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: SILENT install WINDOWS with [press enter to close this window]???
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 22, 2008
06:11 PM
SILENT install WINDOWS with [press enter to close this window]???
I am receiving this message at the end of SILENT installation
"[press enter to close this window]"
I have seen this a couple times now and this not appropriate for a SILENT installation.
Does anyone know when or why this happens.
My WINDOWS installer in SILENT mode opens another Console window. However it is only recently i have seen it ask the user to click enter at the end. No user interaction should take place in SILENT mode. I thought maybe was ctrl key was held during install, for debug, but could not reproduce.
Any help would be appreciated.
Console:
Installation Complete.
SHUTDOWN REQUESTED
(X) commiting registry
REGISTRY ALREADY STORED!
(X) shutting down service manager
(X) cleaning up temporary directories
cleanUp()
calling cleanUpWin32()
Exiting with exit code: 0
[press enter to close this window]
"[press enter to close this window]"
I have seen this a couple times now and this not appropriate for a SILENT installation.
Does anyone know when or why this happens.
My WINDOWS installer in SILENT mode opens another Console window. However it is only recently i have seen it ask the user to click enter at the end. No user interaction should take place in SILENT mode. I thought maybe was ctrl key was held during install, for debug, but could not reproduce.
Any help would be appreciated.
Console:
Installation Complete.
SHUTDOWN REQUESTED
(X) commiting registry
REGISTRY ALREADY STORED!
(X) shutting down service manager
(X) cleaning up temporary directories
cleanUp()
calling cleanUpWin32()
Exiting with exit code: 0
[press enter to close this window]
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 22, 2008
06:21 PM
JWeinste wrote:
I am receiving this message at the end of SILENT installation
"[press enter to close this window]"
I have seen this a couple times now and this not appropriate for a SILENT installation.
Does anyone know when or why this happens.
My WINDOWS installer in SILENT mode opens another Console window. However it is only recently i have seen it ask the user to click enter at the end. No user interaction should take place in SILENT mode. I thought maybe was ctrl key was held during install, for debug, but could not reproduce.
Any help would be appreciated.
Console:
Installation Complete.
SHUTDOWN REQUESTED
(X) commiting registry
REGISTRY ALREADY STORED!
(X) shutting down service manager
(X) cleaning up temporary directories
cleanUp()
calling cleanUpWin32()
Exiting with exit code: 0
[press enter to close this window]
How are you launching the silent installer ? If you are launching it from Command Prompt try using the switch
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 22, 2008
07:28 PM
Thanks for your response, but not yet of help.
I am running the installer using the appropriate command line. I am not running in debug mode. I am directing stderr/out to "console" using the project properties.
I run this from ant.
cmd.exe /c Installer.exe -i silent -f test.properties
This has been working, without this glitch for a couple+ months now.
It happened to me once a couple days ago and then happened in our automated build system which a release engineer maintains. I haven't been able to reproduce since i saw it a couple days ago, but RE just complained as this issue basically halted the build at a preety inopportune time in our release cycle. As far as i am concerned it is a pretty severe issue. Hopefully there is an easy answer.
I am running the installer using the appropriate command line. I am not running in debug mode. I am directing stderr/out to "console" using the project properties.
I run this from ant.
cmd.exe /c Installer.exe -i silent -f test.properties
This has been working, without this glitch for a couple+ months now.
It happened to me once a couple days ago and then happened in our automated build system which a release engineer maintains. I haven't been able to reproduce since i saw it a couple days ago, but RE just complained as this issue basically halted the build at a preety inopportune time in our release cycle. As far as i am concerned it is a pretty severe issue. Hopefully there is an easy answer.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 22, 2008
09:13 PM
JWeinste wrote:
Thanks for your response, but not yet of help.
I am running the installer using the appropriate command line. I am not running in debug mode. I am directing stderr/out to "console" using the project properties.
I run this from ant.
cmd.exe /c Installer.exe -i silent -f test.properties
This has been working, without this glitch for a couple+ months now.
It happened to me once a couple days ago and then happened in our automated build system which a release engineer maintains. I haven't been able to reproduce since i saw it a couple days ago, but RE just complained as this issue basically halted the build at a preety inopportune time in our release cycle. As far as i am concerned it is a pretty severe issue. Hopefully there is an easy answer.
I haven't actually done silent installs on Windows, but I am actually doing one on Linux and it puts me back on the prompt after a silent install..so I am assuming it should work the same way on Windows too......
Did you try launching the installer from Windows Explorer ?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 24, 2008
07:00 AM
Have you added the first line in your properties file as:
INSTALLER_UI=silent
and then run:
Installer.exe -f test.properties
INSTALLER_UI=silent
and then run:
Installer.exe -f test.properties