Skip to content

New version: SerZhyAle.FastMediaSorter version 26.8.14.1510 - #417402

Merged
microsoft-github-policy-service[bot] merged 3 commits into
microsoft:masterfrom
SerZhyAle:SerZhyAle-FastMediaSorter-26.8.14.1510
Aug 14, 2026
Merged

New version: SerZhyAle.FastMediaSorter version 26.8.14.1510#417402
microsoft-github-policy-service[bot] merged 3 commits into
microsoft:masterfrom
SerZhyAle:SerZhyAle-FastMediaSorter-26.8.14.1510

Conversation

@SerZhyAle

@SerZhyAle Serhii Zhyhunenko (SerZhyAle) commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Description

Version update for SerZhyAle.FastMediaSorter (Fast Media Sorter for Windows, published as FastMediaSorter LITE): 26.8.14.1400 -> 26.8.14.1510.

Only PackageVersion, InstallerUrl, InstallerSha256 and ReleaseDate changed. The installer shape is unchanged from the manifest that passed validation previously: the Inno setup.exe is referenced directly (InstallerType: inno), with no Dependencies, no Scope and no NestedInstallerType.

What's new in this version (full text: CHANGELOG):

  • Setup's optional "turn folder sharing on" step is no longer withdrawn when the installation is not elevated. The firewall rule it writes is the only part that needs administrator rights, so instead of disabling the option, Setup now asks Windows for that single step at the end - one prompt, and the consent marker is written only once the rule really exists. This changes nothing for unattended installs: that page is never shown, the box stays unticked and no prompt can appear.
  • The options page no longer runs past the bottom edge of the wizard: the recommended companion project is a single link now instead of a heading, a paragraph and a bare command line that were cut off mid-sentence.
  • On a PC that also has the separate Server edition installed, uninstalling this package could offer to remove a Windows service it does not own. Both products stage their worker in the same machine folder, so ownership is now decided by the Server edition's absence rather than by that path.

Links:


  • Have you signed the Contributor License Agreement?
  • Have you checked that there aren't other open pull requests for the same manifest update/add?
  • 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.12 schema?
Microsoft Reviewers: Open in CodeFlow

@wingetvalidator-prod wingetvalidator-prod Bot added New-Manifest Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Completed Validation passed labels Aug 14, 2026
@microsoft-github-policy-service
microsoft-github-policy-service Bot enabled auto-merge (squash) August 14, 2026 14:12
@stephengillie Stephen Gillie (stephengillie) added the Moderator-Approved One of the Moderators has reviewed and approved this PR label Aug 14, 2026
@microsoft-github-policy-service
microsoft-github-policy-service Bot merged commit 437404d into microsoft:master Aug 14, 2026
80 of 83 checks passed
@wingetbot

Copy link
Copy Markdown
Collaborator

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Moderator-Approved One of the Moderators has reviewed and approved this PR New-Manifest Publish-Pipeline-Succeeded Validation-Completed Validation passed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants