Forum » Support and Bug Reports »

Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

Winstech

It was an upgrade. Thanks for the insight.
martin

Re: WinSCP v6.1.2 triggering reboot

Is it a new installation? Or upgrade?
The installer deploys a drag&drop shell extension. When upgrading, that usually requires a restart, as the old extension is loaded into Windows Explorer. The normal installer is optimized not to replace the extension, unless there's a new version of it. So the restart is needed rarely on upgrade. But the MSI installer probably does not have this optimization.
Winstech

Re: WinSCP v6.1.2 triggering reboot

Yes installed using MSI, and yes it happened only after installation.
martin

Re: WinSCP v6.1.2 triggering reboot

Did you install WinSCP using MSI? Is this happening (only) right after the installation?
Winstech

WinSCP v6.1.2 triggering reboot

Hi

I'm seeing that WinSCP v6.1.2 is triggering a reboot of machines it is deployed to. It returns error code 1641 on deployment, and in event viewer on a target machine I see the following:

The process msiexec.exe has initiated the restart of computer PC01 on behalf of user NT AUTHORITY\SYSTEM for the following reason: No title for this reason could be found
Reason Code: 0x80030002
Shutdown Type: restart
Comment: The Windows Installer initiated a system restart to complete or continue the configuration of 'WinSCP'.

Is this expected behaviour?

Documentation

Support

Associations

Follow Us