setup-x86_64.exe --quiet-mode issues using Management Tools

setup-x86_64.exe --quiet-mode issues using Management Tools

[Paul Isaacson]

Hello Cygwin Support,

I am trying to install Cygwin silently  through a management tool like SCCM (called Bigfix). I went through the FAQ on your website to see what commands/switches existed. I would like to install silently without any user interaction and so I attempted to use setup-x86_64.exe --quiet-mode and I get into an infinite loop for the installation. Bigfix tells me that the installation is waiting for user response and will not continue. It gets stuck and can't start/finish the installation. Is there any suggestions on what I can try? I also want to install a bunch of packages during the installation but thought I would try to start at a completely silent installation firsts. 

I have also checked forums as well online to see if anyone else had issues. I found a one forum where someone is having the same issue with no resolution found here: https://www.itninja.com/question/cygwin-realy-silent-installation-no-progress-window-with-option-to-counsel


Thanks,
Paul
 
___________________________________________________________________
 
For IT support, please E-mail: fsmhelp@northwestern.edu | Phone: 847-491-HELP
 
Paul Isaacson
Senior Technical Support Specialist, Client Management
Northwestern University
Feinberg School of Medicine
Information Technology
710 N. Lake Shore Drive, 7th Floor
Chicago, Illinois 60611
312.503.6159 office
paul_isaacson@northwestern.edu
feinberg.northwestern.edu/it
 

 

RE: setup-x86_64.exe --quiet-mode issues using Management Tools

[KAVALAGIOS Panagiotis (EEAS-EXT)]

> From: Cygwin <cygwin-bounces@cygwin.com> On Behalf Of Paul Isaacson
> Hello Cygwin Support,
> 
> I am trying to install Cygwin silently  through a management tool like SCCM
> (called Bigfix). I went through the FAQ on your website to see what
> commands/switches existed. I would like to install silently without any user
> interaction and so I attempted to use setup-x86_64.exe --quiet-mode and I
> get into an infinite loop for the installation. Bigfix tells me that the installation
> is waiting for user response and will not continue. It gets stuck and can't
> start/finish the installation. Is there any suggestions on what I can try? I also
> want to install a bunch of packages during the installation but thought I would
> try to start at a completely silent installation firsts.
> 
> I have also checked forums as well online to see if anyone else had issues. I
> found a one forum where someone is having the same issue with no
> resolution found here: https://www.itninja.com/question/cygwin-realy-
> silent-installation-no-progress-window-with-option-to-counsel

Welcome to the club. Unfortunately, Cygwin setup is not friendly for Software Managers. After a lot of research, I have ended up to the following command:

----------------
@echo off
@echo Starting Cygwin installation

"%cd%\setup-x86_64.exe" -q -A -L -l "%cd%\cygwin-repo" -R "C:\Program Files\Cygwin" -P autoconf,automake,bash-completion,binutils,curl,emacs,git,git-svn,gnupg2,inetutils,konsole,mc,openssh,patchutils,perl,python2,python3,rsync,ruby,subversion,tcsh,tmux,unzip,vim,vim-common,wget,xinit,xlaunch,xorg-server,xorg-server-common,xorg-server-xorg,xorg-x11-fonts-dpi100,xorg-x11-fonts-dpi75,xorg-x11-fonts-Type1,xorg-x11-fonts-misc,xterm,zip
----------------

wrapped in a nice "setup-x86_64.bat" that is executed by the installation Powershell script. That command is still popping up a progress window, but it was removed by our Landesk configuration. You may check if yours having the same option not to allow any GUI to be displayed by the installation program.

I have already requested a feature to totally remove any GUI from silent installation:

https://www.mail-archive.com/cygwin@cygwin.com/msg162887.html

Panos

Re: setup-x86_64.exe --quiet-mode issues using Management Tools

[Bill Stewart]

On Wed, Apr 15, 2020 at 9:03 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:

> wrapped in a nice "setup-x86_64.bat" that is executed by the
> installation Powershell script. That command is still popping up a
> progress window, but it was removed by our Landesk configuration.
> You may check if yours having the same option not to allow any GUI
> to be displayed by the installation program.
>
> I have already requested a feature to totally remove any GUI from
> silent installation:
>
> https://www.mail-archive.com/cygwin@cygwin.com/msg162887.html

Just curious: Why does it matter whether a GUI appears or not, as long
as it doesn't block (stop for input)?

Bill

RE: setup-x86_64.exe --quiet-mode issues using Management Tools

[KAVALAGIOS Panagiotis (EEAS-EXT)]

> From: Cygwin On Behalf Of Bill Stewart
> On Wed, Apr 15, 2020 at 9:03 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
> 
> > I have already requested a feature to totally remove any GUI from
> > silent installation:
> >
> > https://www.mail-archive.com/cygwin@cygwin.com/msg162887.html
> 
> Just curious: Why does it matter whether a GUI appears or not, as long as it
> doesn't block (stop for input)?

Because the package can be sent to your machine when you are working and we don't wish to disturb the users. Everything is performed in the background. Annoying popups are not welcomed. Silent installation is supposed to be silent without any horns shouting in the foreground.

Panos

Re: setup-x86_64.exe --quiet-mode issues using Management Tools

[Bill Stewart]

On Thu, Apr 16, 2020 at 2:25 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:

> > From: Cygwin On Behalf Of Bill Stewart
> > On Wed, Apr 15, 2020 at 9:03 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
> >
> > > I have already requested a feature to totally remove any GUI from
> > > silent installation:
> > >
> > > https://www.mail-archive.com/cygwin@cygwin.com/msg162887.html
> >
> > Just curious: Why does it matter whether a GUI appears or not, as long as it
> > doesn't block (stop for input)?
>
> Because the package can be sent to your machine when you are working
> and we don't wish to disturb the users. Everything is performed in the
> background. Annoying popups are not welcomed. Silent installation is
> supposed to be silent without any horns shouting in the foreground.

If the install doesn't occur as the current user (and it shouldn't),
the installation won't be visible anyway.

I for one am against installers that run completely invisibly.

Bill

RE: setup-x86_64.exe --quiet-mode issues using Management Tools

[KAVALAGIOS Panagiotis (EEAS-EXT)]

> -----Original Message-----
> From: Cygwin <cygwin-bounces@cygwin.com> On Behalf Of Bill Stewart
> 
> On Thu, Apr 16, 2020 at 2:25 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
> 
> > Because the package can be sent to your machine when you are working
> > and we don't wish to disturb the users. Everything is performed in the
> > background. Annoying popups are not welcomed. Silent installation is
> > supposed to be silent without any horns shouting in the foreground.
> 
> If the install doesn't occur as the current user (and it shouldn't), the
> installation won't be visible anyway.
> 
> I for one am against installers that run completely invisibly.

I personally don't like stealth modifications to my system either. We are describing a different scenario and different needs. The users don't have admin rights in their machines and they have asked Cygwin to be included in the list of their development software. All the provided developer software so far includes silent installation apart from Cygwin, which you cannot call it 100% silent. We could also use a zip distribution for Cygwin, in fact that was our old deployment method, but half of the programs were able to run due to broken links. I know that there is a script to fix the links, but I would trust the setup itself better to avoid any possible issues on the users' machines.

This is the way that we are pushing the packages currently to end users is through software managers with silent installation. Of course, it would be far better to set up something like Windows Store, where the user can select Cygwin, launch its installation and have full control over it.

Kind regards,

Panos Kavalagios

Application Architect
CONSULIAT (under contract with the EEAS)
BA.BS.3.IS
_____________________________________
Office: EEAS B100 Floor 5 Area 048
Rue Belliard 100, 1000 Brussels
Phone: +32 2 584 6017

Re: setup-x86_64.exe --quiet-mode issues using Management Tools

[Andrey Repin]

Greetings, Bill Stewart!

> On Thu, Apr 16, 2020 at 2:25 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:

>> > From: Cygwin On Behalf Of Bill Stewart
>> > On Wed, Apr 15, 2020 at 9:03 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>> >
>> > > I have already requested a feature to totally remove any GUI from
>> > > silent installation:
>> > >
>> > > https://www.mail-archive.com/cygwin@cygwin.com/msg162887.html
>> >
>> > Just curious: Why does it matter whether a GUI appears or not, as long as it
>> > doesn't block (stop for input)?
>>
>> Because the package can be sent to your machine when you are working
>> and we don't wish to disturb the users.

Since you install it as administrator, install it as a system application.
This way it is easier to integrate it with users' workflow AND your
infrastructure, and you could more easily control this integration as well as
protect it from accidental changes.

>> Everything is performed in the
>> background. Annoying popups are not welcomed. Silent installation is
>> supposed to be silent without any horns shouting in the foreground.

> If the install doesn't occur as the current user (and it shouldn't),
> the installation won't be visible anyway.

> I for one am against installers that run completely invisibly.

The problem is not the interface itself, the problem is that a user who see
a random program popped up on their screen could interrupt the installation,
intentionally or not.


-- 
With best regards,
Andrey Repin
Friday, April 17, 2020 12:59:54

Sorry for my terrible english...

Re: setup-x86_64.exe --quiet-mode issues using Management Tools

[Bill Stewart]

On Fri, Apr 17, 2020 at 1:01 AM KAVALAGIOS Panagiotis (EEAS-EXT)  wrote:

> This is the way that we are pushing the packages currently to
> end users is through software managers with silent
> installation.

My point is that "silent" doesn't mean "no visible GUI." It generally
means "the installer doesn't block" (i.e., the installation completes
without user input).

For example, the popular Inno Setup install builder
(https://www.jrsoftware.org/isinfo.php) has a "/SILENT" command line
parameter, which (if the installer is designed correctly) causes the
created installer to install the package without user input. If run in
the user's session, a GUI is still visible; it just doesn't stop to
ask for any input. If you install using a software management tool,
this usually installs in a separate session, so it doesn't matter if
there's a GUI as long as no input is required.

Bill

Re: setup-x86_64.exe --quiet-mode issues using Management Tools

[Jon Turney]

On 15/04/2020 16:02, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>> From: Cygwin <cygwin-bounces@cygwin.com> On Behalf Of Paul Isaacson
>> Hello Cygwin Support,
>>
>> I am trying to install Cygwin silently  through a management tool like SCCM
>> (called Bigfix). I went through the FAQ on your website to see what
>> commands/switches existed. I would like to install silently without any user
>> interaction and so I attempted to use setup-x86_64.exe --quiet-mode and I
>> get into an infinite loop for the installation. Bigfix tells me that the installation
>> is waiting for user response and will not continue. It gets stuck and can't
>> start/finish the installation. Is there any suggestions on what I can try? I also
>> want to install a bunch of packages during the installation but thought I would
>> try to start at a completely silent installation firsts.

It's possible that there are bugs in setup which cause quiet-mode to get 
stuck on some error conditions.

Unfortunately, there's not enough information provided to know if that's 
the case here, or fix it if it is.

>> I have also checked forums as well online to see if anyone else had issues. I
>> found a one forum where someone is having the same issue with no
>> resolution found here: https://www.itninja.com/question/cygwin-realy-
>> silent-installation-no-progress-window-with-option-to-counsel
> 
> Welcome to the club. Unfortunately, Cygwin setup is not friendly for Software Managers. After a lot of research, I have ended up to the following command:
> 
> ----------------
> @echo off
> @echo Starting Cygwin installation
> 
> "%cd%\setup-x86_64.exe" -q -A -L -l "%cd%\cygwin-repo" -R "C:\Program Files\Cygwin" -P autoconf,automake,bash-completion,binutils,curl,emacs,git,git-svn,gnupg2,inetutils,konsole,mc,openssh,patchutils,perl,python2,python3,rsync,ruby,subversion,tcsh,tmux,unzip,vim,vim-common,wget,xinit,xlaunch,xorg-server,xorg-server-common,xorg-server-xorg,xorg-x11-fonts-dpi100,xorg-x11-fonts-dpi75,xorg-x11-fonts-Type1,xorg-x11-fonts-misc,xterm,zip
> ----------------
> 
> wrapped in a nice "setup-x86_64.bat" that is executed by the installation Powershell script. That command is still popping up a progress window, but it was removed by our Landesk configuration. You may check if yours having the same option not to allow any GUI to be displayed by the installation program.
> 
> I have already requested a feature to totally remove any GUI from silent installation:
> 
> https://www.mail-archive.com/cygwin@cygwin.com/msg162887.html
> 

Yeah, about that...

If you want to see a feature added to setup, by far the best way is to 
provide a patch to add it.

RE: setup-x86_64.exe --quiet-mode issues using Management Tools

[KAVALAGIOS Panagiotis (EEAS-EXT)]

> -----Original Message-----
> From: Cygwin <cygwin-bounces@cygwin.com> On Behalf Of Bill Stewart
> 
> On Fri, Apr 17, 2020 at 1:01 AM KAVALAGIOS Panagiotis (EEAS-EXT)  wrote:
> 
> > This is the way that we are pushing the packages currently to end
> > users is through software managers with silent installation.
> 
> My point is that "silent" doesn't mean "no visible GUI." It generally means
> "the installer doesn't block" (i.e., the installation completes without user
> input).
> 
> For example, the popular Inno Setup install builder
> (https://www.jrsoftware.org/isinfo.php) has a "/SILENT" command line
> parameter, which (if the installer is designed correctly) causes the created
> installer to install the package without user input. If run in the user's session,
> a GUI is still visible; it just doesn't stop to ask for any input. If you install using
> a software management tool, this usually installs in a separate session, so it
> doesn't matter if there's a GUI as long as no input is required.

s/silent/verysilent/g

-----------
/SILENT, /VERYSILENT
Instructs Setup to be silent or very silent. When Setup is silent the wizard and the background window are not displayed but the installation progress window is. When a setup is very silent this installation progress window is not displayed. Everything else is normal so for example error messages during installation are displayed and the startup prompt is (if you haven't disabled it with DisableStartupPrompt or the '/SP-' command line option explained above).
-----------
 
Cygwin setup supports does not support very silent installation. That is our major issue describing in this thread.

Regards,

Panos Kavalagios

Application Architect
CONSULIAT (under contract with the EEAS)
BA.BS.3.IS
_____________________________________
Office: EEAS B100 Floor 5 Area 048
Rue Belliard 100, 1000 Brussels
Phone: +32 2 584 6017

RE: setup-x86_64.exe --quiet-mode issues using Management Tools

[KAVALAGIOS Panagiotis (EEAS-EXT)]

> -----Original Message-----
> From: Cygwin <cygwin-bounces@cygwin.com> On Behalf Of Jon Turney
> 
> It's possible that there are bugs in setup which cause quiet-mode to get stuck
> on some error conditions.
> 
> Unfortunately, there's not enough information provided to know if that's the
> case here, or fix it if it is.

That's fine. We do a testing with local repository, so usually the behaviour should be the same on all machines. Famous last words!

> > I have already requested a feature to totally remove any GUI from silent
> installation:
> >
> > https://www.mail-archive.com/cygwin@cygwin.com/msg162887.html
> >
> 
> Yeah, about that...
> 
> If you want to see a feature added to setup, by far the best way is to provide
> a patch to add it.

Do you accept patches in Java? :) My C skills are pure academic in the university several years ago.

Regards,

Panos Kavalagios

Application Architect
CONSULIAT (under contract with the EEAS)
BA.BS.3.IS
_____________________________________
Office: EEAS B100 Floor 5 Area 048
Rue Belliard 100, 1000 Brussels
Phone: +32 2 584 6017

Re: setup-x86_64.exe --quiet-mode issues using Management Tools

[Bill Stewart]

On Tue, Apr 21, 2020 at 2:08 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:

> s/silent/verysilent/g>
> -----------
> /SILENT, /VERYSILENT Instructs Setup to be silent or very silent.
> When Setup is silent the wizard and the background window are not
> displayed but the installation progress window is. When a setup is
> very silent this installation progress window is not displayed.
> Everything else is normal so for example error messages during
> installation are displayed and the startup prompt is (if you haven't
> disabled it with DisableStartupPrompt or the '/SP-' command line
> option explained above).
> -----------
>
> Cygwin setup supports does not support very silent installation.
> That is our major issue describing in this thread.

My point is that "very silent" is not necessary for automation. All
you need is for the installer not to stop for input.

Whether a GUI appears or not is irrelevant, as long as it doesn't
block (stop for input).

Bill

RE: setup-x86_64.exe --quiet-mode issues using Management Tools

[KAVALAGIOS Panagiotis (EEAS-EXT)]

> -----Original Message-----
> From: Cygwin <cygwin-bounces@cygwin.com> On Behalf Of Bill Stewart
> 
> On Tue, Apr 21, 2020 at 2:08 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
> 
> > s/silent/verysilent/g>
> > -----------
> > /SILENT, /VERYSILENT Instructs Setup to be silent or very silent.
> > When Setup is silent the wizard and the background window are not
> > displayed but the installation progress window is. When a setup is
> > very silent this installation progress window is not displayed.
> > Everything else is normal so for example error messages during
> > installation are displayed and the startup prompt is (if you haven't
> > disabled it with DisableStartupPrompt or the '/SP-' command line
> > option explained above).
> > -----------
> >
> > Cygwin setup supports does not support very silent installation.
> > That is our major issue describing in this thread.
> 
> My point is that "very silent" is not necessary for automation. All you need is
> for the installer not to stop for input.
> 
> Whether a GUI appears or not is irrelevant, as long as it doesn't block (stop
> for input).

Are you sure that a setup that is automated with a silent installation, but it still displays a progress popup, it cannot fail if it is not able to display that window when there is no user logged in? I am not, hence I would prefer that setup could ensure a real background operation.

An exception displaying the progress window could lead to the interruption of the installation process. That is a blocking condition as well, even though no input is required by the user.

Regards,

Panos Kavalagios

Application Architect
CONSULIAT (under contract with the EEAS)
BA.BS.3.IS
_____________________________________
Office: EEAS B100 Floor 5 Area 048
Rue Belliard 100, 1000 Brussels
Phone: +32 2 584 6017

Re: setup-x86_64.exe --quiet-mode issues using Management Tools

[Bill Stewart]

On Tue, Apr 21, 2020 at 7:56 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:

> Are you sure that a setup that is automated with a silent
> installation, but it still displays a progress popup, it cannot fail
> if it is not able to display that window when there is no user
> logged in? I am not, hence I would prefer that setup could ensure a
> real background operation.
>
> An exception displaying the progress window could lead to the
> interruption of the installation process. That is a blocking
> condition as well, even though no input is required by the user.

An exception during the installation would only block if it prevents
the process from closing (i.e., if it displays a message box). That
could happen in an installation even if the installer isn't displaying
a GUI.

What I am saying is what's important about automated installation is
that it not block (even in the case of an exception). Whether the
installer displays a GUI or not is really irrelevant, particularly if
the installation isn't running as the current user (in which case the
current user doesn't see the GUI anyway).

Bill

Re: setup-x86_64.exe --quiet-mode issues using Management Tools

[Brian Inglis]

On 2020-04-21 02:14, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>> From: Jon Turney
>> It's possible that there are bugs in setup which cause quiet-mode to get stuck
>> on some error conditions.
>> Unfortunately, there's not enough information provided to know if that's the
>> case here, or fix it if it is.

> That's fine. We do a testing with local repository, so usually the behaviour 
> should be the same on all machines. Famous last words!

>>> I have already requested a feature to totally remove any GUI from silent 
>>> installation:
>>> https://www.mail-archive.com/cygwin@cygwin.com/msg162887.html
>> Yeah, about that...
>> If you want to see a feature added to setup, by far the best way is to provide
>> a patch to add it.

> Do you accept patches in Java? :) My C skills are pure academic in the
> university several years ago.
It's Windows C++ built with Cygwin ports of a GNU toolchain:

	https://cygwin.com/git?p=cygwin-apps/setup.git	view
	git://cygwin.com/git/cygwin-apps/setup.git	clone

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

Re: setup-x86_64.exe --quiet-mode issues using Management Tools

[Brian Inglis]

On 2020-04-21 08:17, Bill Stewart wrote:
> On Tue, Apr 21, 2020 at 7:56 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>> Are you sure that a setup that is automated with a silent installation, but
>> it still displays a progress popup, it cannot fail if it is not able to
>> display that window when there is no user logged in? I am not, hence I
>> would prefer that setup could ensure a real background operation.
>>
>> An exception displaying the progress window could lead to the interruption
>> of the installation process. That is a blocking condition as well, even
>> though no input is required by the user.

> An exception during the installation would only block if it prevents the
> process from closing (i.e., if it displays a message box). That could happen
> in an installation even if the installer isn't displaying a GUI.
> 
> What I am saying is what's important about automated installation is that it
> not block (even in the case of an exception). Whether the installer displays
> a GUI or not is really irrelevant, particularly if the installation isn't
> running as the current user (in which case the current user doesn't see the
> GUI anyway).

One issue with the -M, --package-manager semi- and -q, --quiet-mode unattended
installs are that any errors are logged only in /var/log/setup.log.full, which
is overwritten by the next run, with only a summary log remaining at the end of
the cumulative /var/log/setup.log, and not all error or warning messages are
significant.

The is especially likely if *any* Cygwin processes are running when setup
starts, so you need to kill off any processes running any commands or using any
DLLs under the Cygwin root, before running setup.

You will have to manage the processes and error logs with your network install
wrapper, although some work could be delegated to permanent postinstall
[0z]p_...sh scripts in /etc/postinstall/.

The order of running postinstall script is alpha order, I believe under the
default/POSIX/C locale, with 0p_...sh scripts run before and zp_...sh scripts
run after all others.

It is *essential* that /etc/postinstall/0p_000_autorebase.dash always run first
and to completion without errors, as otherwise Cygwin DLLs could overlap,
especially under Cygwin 32 installs, and any program could fail, with a variety
of possible errors.

As part of my Cygwin profile, I check for any remaining files matching
	/etc/postinstall/[!0z][!pqrst][!_]*.*sh
or
	/{,usr/}{,*86*/**/}{*bin,lib}/*.{dll,exe}.new
as new exes and DLLs should replace the old files before postinstall scripts
run, and non-permanent package postinstall scripts should be renamed with .done
suffixed after execution, otherwise setup needs to be rerun with no Cygwin
processes running, or the system needs to be restarted, as Cygwin may have
created a Windows post-install script to complete the replacements.

You will also have to manage upgrades with -g, --upgrade-also to handle
upgrading to get security and other urgent regular base package maintenance
patches applied, for example Windows release support in Cygwin, and crypto,
ca-certificates, openssl, tzdata package upgrades.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.