SEEYOU.SEEYOU version 2.0.2

[khaffner]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[microsoft-github-policy-service]

Hello @khaffner,

During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches?

This can also happen when a dependency is missing. You can test with https://github.com/microsoft/winget-pkgs#test-your-manifest.

Please investigate a fix and resubmit the Pull Request.

You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI, or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect them and the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress.

Template: msftbot/validationError/installation/unattended

[BrandonWanHuanSheng]

Configuring the installer...

[BrandonWanHuanSheng]

This is most likely like Fiddler Setup. I am going to get the silent switch.

[BrandonWanHuanSheng]

No silent switches, The installer type supposed nullsoft. I am going to check if there is any dependent services.

[khaffner]

/allusers /S

Might work

[BrandonWanHuanSheng]

I seeing a lot of cmd pop up while during uninstall.

[BrandonWanHuanSheng]

/allusers /S

Might work

Yes

[stephengillie]

Hi @khaffner,

The installation isn't unattended:

Is there an installer switch to bypass this and have it install without rebooting?

Edit: I tried both /S and /noreboot but neither prevented the prompt.

[BrandonWanHuanSheng]

I also noticed that one but norestart did not work. Normally the command is used when using updating cab and msu when trying to skip this dialog. It also use in exe application. Norestart usually suppresses automatic reboots and reboot prompts.

[BrandonWanHuanSheng]

I guess it might be NR. Still No Work.

[BrandonWanHuanSheng]

I found the help usage https://nsis.sourceforge.io/Docs/Chapter3.html

[BrandonWanHuanSheng]

@khaffner, I found the help file. https://nsis.sourceforge.io/Docs/Chapter3.html

[BrandonWanHuanSheng]

@stephengillie It look like the installer is not unattended. But I actually tried every command, the reboot dialog keep popping up. There is no ways to resolve.

[stephengillie]

@stephengillie It look like the installer is not unattended. But I actually tried every command, the reboot dialog keep popping up. There is no ways to resolve.

Pending:

• Settings for installer modes winget-cli#910

[microsoft-github-policy-service]

Hello @khaffner,

This package appears to require user interaction to install.

This PR is blocked until support for interactive installer search filtering is implemented in:

• Support for filtering packages on installer method winget-cli#823

Template: msftbot/blockingIssue/interactiveOnlyInstall

[BrandonWanHuanSheng]

Closed #101232

Result: Failure to interactive install because this installer does not accept NoRestart and NoReboot Command.

[microsoft-github-policy-service]

Hello @khaffner,

This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

Template: msftbot/noRecentActivity