Bug 126838 - Install fails when silent and desktop shortcut creation is forbidden
Summary: Install fails when silent and desktop shortcut creation is forbidden
Status: RESOLVED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
6.3.0.4 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Installer-Windows
  Show dependency treegraph
 
Reported: 2019-08-11 20:42 UTC by Joda Stößer
Modified: 2019-11-03 15:01 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joda Stößer 2019-08-11 20:42:29 UTC
Description:
I use the Windows Defender Ransomware Protection which protects user folders by preventing access by not authorised apps, which typically includes all setups. Because of this creating desktop shortcuts is not possible on my system.
When using the silent flag to install LibreOffice, the installer throws and exception because of this, cancels and reverts the install.

Please fix the behaviour to resume install inspite of the error.

Steps to Reproduce:
1. Activate Windows Defender Ransomeware Protection
2. Install LibreOffice in silent mode

Actual Results:
Install throws error and cancels

Expected Results:
Install continues and logs the failed creation of the desktop shortcut as an error


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Oliver Brinzing 2019-08-12 06:26:07 UTC
(In reply to Joda Stößer from comment #0)
> Because of this creating desktop shortcuts is not possible on my system.
> When using the silent flag to install LibreOffice, the installer throws and
> exception because of this, cancels and reverts the install.

What does your msiexec command line look like?

Please try to add property CREATEDESKTOPLINK=0

https://wiki.documentfoundation.org/Deployment_and_Migration
Comment 2 Joda Stößer 2019-08-17 01:07:13 UTC
I am using AppGet to install LibreOffice: https://github.com/appget/appget.packages/blob/450c3c3f12a2f8e736471d6cc30b8c0102ce236e/manifests/libreoffice/libreoffice.yaml
I don't know the exact way the silent install is performed.
Comment 3 Oliver Brinzing 2019-08-17 16:13:04 UTC
does it work if you double click "LibreOffice_6.3.0_Win_x64.msi" and disable the create desktop link option within install wizard?
Comment 4 Joda Stößer 2019-11-03 13:04:10 UTC
I tested using the msi and graphical installer:
+ If I leave the "Create Desktop shortcut" box ticked, the installer runs in to an error and reverts the whole installation. If the installation was an update from a previous version, I am left without any installation at all.
+ If I uncheck the "Create Desktop shortcut" box, the installer runs through without a problem.
Comment 5 Oliver Brinzing 2019-11-03 14:54:00 UTC
(In reply to Joda Stößer from comment #4)
> I tested using the msi and graphical installer:
> + If I leave the "Create Desktop shortcut" box ticked, the installer runs in
> to an error and reverts the whole installation. If the installation was an
> update from a previous version, I am left without any installation at all.
> + If I uncheck the "Create Desktop shortcut" box, the installer runs through
> without a problem.

I tend to say this is not an LO issue.
If a third party software prevents desktop shortcut creation and you tell LO msi to create a shortcut during install it will fail with an error.

To prevent desktop shortcut creation you can add parameter: CREATEDESKTOPLINK=0
Comment 6 Mike Kaganski 2019-11-03 15:01:01 UTC
This is mentioned in our FAQ [1].

Of course, it's wrong to alter installer to continue when failed to perform one of the things selected for installation. This is absolutely incorrect, and will not be done. The parameter Oliver have mentioned in comment 5 is the correct thing to do if you cannot disable AV interfering with installation.

Closing NOTOURBUG (an antivirus should not prevent installing icons by MSI running with elevated permissions).

[1] https://wiki.documentfoundation.org/Faq/General/General_Installation_Issues_(Windows)