Desktop: Windows Nextcloud client installer restarts computer without prompt or warning

[Normonator]

Expected behaviour

Installation prompts to restart computer allowing user to save any ongoing work.

Actual behaviour

Installer restarts immediately after displaying Run Nextcloud prompt and does not allow clicking on finish before restarting.

Steps to reproduce

1. Have older version of Visual C++ Redistributable (prompting vc installer to reboot if not suppressed)
2. Install nextcloud client
3. Computer restarts immediately, resulting possibly in lost work.

Client configuration

Client version:
2.5
Operating system:
Windows 10 1809 Build 17763.55 (up to date)
OS language:
English US
Installation path of client:
C:\Program Files (x86)\Nextcloud

Logs

Event Viewer entry:
The process C:\Program Files (x86)\Nextcloud\i18n\vcredist_x64.exe (COMPUTERNAME) has initiated the restart of computer COMPUTERNAME on behalf of user USERNAME for the following reason: Application: Installation (Planned)
Reason Code: 0x80040002
Shutdown Type: restart
Comment:

[RiSK1979]

I experienced the same issue on two different Windows 10 computers.

[hillebr]

...same here on two different Windows 10 computers.

[JarbyDev]

Same Here, I tried on Windows 10 Computer and Windows Server 2016.

[pfeiferocks]

Same here on 2 Windows 10 Computers and i will not try it on Windows Server 2016.

[gr4ssi]

Wow, this sucks big time. Just had that too. Reason is, vcredist_x64.exe requests reboot without asking.

Vom Prozess "C:\Program Files (x86)\Nextcloud\i18n\vcredist_x64.exe (NB-xxx)" wurde auf Anforderung des Benutzers "NB-xxx\abc" das Ereignis "Neustart" für den Computer "NB-xxx" aus folgendem Grund initiiert: "Anwendung: Installiert (geplant)"
Ursachencode: "0x80040002"
Herunterfahrtyp: "Neustart"

This is definitely not expected behaviour for a desktop client. I almost put that on our server. :-(

[toms1342]

vcredist_x64.exe ignores/overwrites the "/norestart" switch of theNC 2.5.0 .msi client installer.

A fix of this behavior is highly appreciated for every admin how plans a rollout of the new client on productive machines.
Unfortunately we did not find a way to work around this.
Any help is welcome!

[Marcwa19197]

i have exactly the same issue on two windows 10 computers, really annoying.

[stephanhendl]

Same here with a couple of Windows 10 clients.

[Siedlerchr]

I can confirm this bug with the latest release 2.5.1 on Windows 10 x64 .

[hillebr]

I can confirm this bug on a fresh installation with recent stable installer (2.5.1) on Win10 x64
An update from 2.5.0 to 2.5.1 won't restart the machine maybe because it rebooted on 2.5.0 installation and updating doesn`t change the vcredist_x64.exe.

HTH

René

[mioiox]

I can confirm the issue stays with the current version (2.5.1) of NC client (fresh install, Windows 10 1809 x64). Really annoying. Here is the event message from the System event log in English:

The process C:\Program Files (x86)\Nextcloud\i18n\vcredist_x64.exe (Computername) has initiated the restart of computer Computername on behalf of user Domain\Username for the following reason: Application: Installation (Planned)
Reason Code: 0x80040002
Shutdown Type: restart
Comment:

[Shorty-KS]

Ich habe zwar keine Lösung, aber einen funktionierenden Workaround:

Wie hier schon berichtet wurde, liegt das Problem an der Installation der vcredist_x64.exe, die den harten Neustart macht (Beim Nextcloud-2.5.1-setup wird automatisch die Version 14.14.26405.0 der der vcredist_x64 installiert). Installiert man aber vor dem Nextcloud-2.5.1-setup eine aktuellere Version der vcredist_x64.exe, erfolgt kein Neustart!

Eine neuere Version (14.16.27012.6) findet man z.B. hier:
https://support.microsoft.com/de-de/help/2977003/the-latest-supported-visual-c-downloads

Wenn man das ganze, so wie ich, per PowerShell App Deployment Toolkit macht, wäre die Reihenfolge also ungefähr so:

If ($ENV:PROCESSOR_ARCHITECTURE -eq "AMD64") {Execute-Process -Path 'VC_redist.x64.exe' -Parameters '/S /norestart'}

If ($ENV:PROCESSOR_ARCHITECTURE -eq "AMD64") {$ReturnCode = Execute-Process -Path 'Nextcloud-2.5.1-setup.exe' -Parameters '/S /norestart' -IgnoreExitCodes ‘1223’ -PassThru}

[chapb]

Same problem here.

[jellykells]

Same issue on Windows 7 x64 SP1.

[oligu]

Also experienced that issue.
Found out that when the Integration for Windows Explorer is deselected in the installer, there is no reboot.

[moorsey]

Duplicates of this #496 and #1040

[camilasan]

Hi All!
Please, try this installer: https://download.nextcloud.com/desktop/daily/Windows/Nextcloud-2.5.1.5037-daily-20190125.exe
Let me know if it works for you!
Thanks @gr4ssi for the help!

[camilasan]

Yet, it needs to reboot before for the Windows Explorer integration to work!

[gr4ssi]

Works for me on nearly naked Win7 DE 64Bit Prof. Thanks for updating the client. :-)

[Dennis360ict]

Same with the technical preview. Maybe you should update that

On Windows 2016 and Windows 10.

[Fortyseven]

Thankfully, VirtualBox actually saved it's state before the reboot could finish, otherwise I might have lost some work this morning, in addition to the disruption. This is _awful_ behavior.

[jellykells]

Hi All!
Please, try this installer: https://download.nextcloud.com/desktop/daily/Windows/Nextcloud-2.5.1.5037-daily-20190125.exe
Let me know if it works for you!
Thanks @gr4ssi for the help!

Works for me :-)

[burner-]

I just take installer from https://nextcloud.com/install/#install-clients for fresh install. And it restarted computer without any warning.
"The process C:\Program Files (x86)\Nextcloud\i18n\vcredist_x64.exe (PC2) has initiated the restart of computer PC2 on behalf of user PC2\user for the following reason: Application: Installation (Planned)"

[xrammit]

A new client version (2.5.2) was released but the Nextcloud website havn't been updated yet.
@camilasan Can you please ask the website maintainer to update the link to point to the new version?

[affinityv]

@xrammit 2.5.1 is the latest actual release. There is a newer tag for 2.5.2, but it isn't released yet.

https://github.com/nextcloud/desktop/releases

[xrammit]

@xrammit 2.5.1 is the latest actual release. There is a newer tag for 2.5.2, but it isn't released yet.

No, in my opinion version 2.5.2 was already released as there are (stable) binaries available on nextcloud.com for all platforms [1] and the new version was also published on the stable Nextcloud desktop client PPA [2].

[1] https://download.nextcloud.com/desktop/releases/
[2] https://launchpad.net/~nextcloud-devs/+archive/ubuntu/client

[e-alfred]

Yet, it needs to reboot before for the Windows Explorer integration to work!

Is a reboot really needed? Couldn't it be done by killing/restarting the Explore.exe process to enable the integration into the Windows Explorer instead of a sudden reboot?

[Dennis360ict]

Is a reboot really needed? Couldn't it be done by killing/restarting the Explore.exe process to enable the integration into the Windows Explorer instead of a sudden reboot?

The shell of windows is dependent on explorer.exe. Or actually explorer starts the shell (windows desktop) as you know it. So restarting explorer restarts your shell, which can gives weird issues as not all running apps can handle that.

Its also the reason bad explorer plugins could take down whole windows shell.

At least, this is how its been since windows 95, some of the newer builds of win10 might handle stuff differently, although i doubt it.

Anyway, a reboot for explorer integration isn’t that bad in my opinion. Windows needs lots of restarts anyway so one more isnt that bad in my opinion.

[jernejs]

I know several programs that simply restart explorer.exe to get the shell extensions to load, and AFAIK, WinRAR uses some method to reload the extensions without doing anything visible to Explorer at all.

Windows needs lots of restarts anyway so one more isnt that bad in my opinion.

What? This hasn't been true at all for years. Except for the updates, there's no need to reboot Windows nowadays at all.

[jancborchardt]

Was confirmed above to be fixed, by @jellykells at https://github.com/nextcloud/desktop/issues/831#issuecomment-465544601 → closing hence. :)