Files
PowerToys/NOTICE.md
Gleb Khmyznikov a5b9cc77ec Squashed commit of the following:
commit 73e379238b
Author: leileizhang <leilzh@microsoft.com>
Date:   Tue Dec 9 10:13:48 2025 +0800

    Add FancyZones CLI for command-line layout management (#44078)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    Adds a new command-line interface (CLI) tool for FancyZones, enabling
    users and automation scripts to manage window layouts without the GUI.

    **Commands:**
    | Command | Aliases | Description |
    |---------|---------|-------------|
    | `help` | | Displays general help information for all commands |
    | `open-editor` | `editor`, `e` | Launch FancyZones layout editor |
    | `get-monitors` | `monitors`, `m` | List all monitors and their
    properties |
    | `get-layouts` | `layouts`, `ls` | List all available layouts with
    ASCII art preview |
    | `get-active-layout` | `active`, `a` | Show currently active layout |
    | `set-layout <uuid>` | `set`, `s` | Apply layout by UUID or template
    name |
    | `open-settings` | `settings` | Open FancyZones settings page |
    | `get-hotkeys` | `hotkeys`, `hk` | List all layout hotkeys |
    | `set-hotkey <key> <uuid>` | `shk` | Assign hotkey (0-9) to custom
    layout |
    | `remove-hotkey <key>` | `rhk` | Remove hotkey assignment |

    **Key Capabilities:**
    - ASCII art visualization of layouts (grid, focus, priority-grid,
    canvas)
    - Support for both template layouts and custom layouts
    - Monitor-specific layout targeting (`--monitor N` or `--all`)
    - Real-time notification to FancyZones via Windows messages
    - Native AOT compilation support for fast startup

    ### Example Usage

    ```bash
    # List all layouts with visual previews
    FancyZonesCLI.exe ls

    # Apply "columns" template to all monitors
    FancyZonesCLI.exe s columns --all

    # Set custom layout on monitor 2
    FancyZonesCLI.exe s {uuid} --monitor 2

    # Assign hotkey Win+Ctrl+Alt+3 to a layout
    FancyZonesCLI.exe shk 3 {uuid}
    ```

    https://github.com/user-attachments/assets/2b141399-a4ca-4f64-8750-f123b7e0fea7

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 4710b816b4
Author: Dave Rayment <dave.rayment@gmail.com>
Date:   Mon Dec 8 21:01:56 2025 +0000

    [CmdPal] Optimise MainListPage's results display by merging already-sorted lists (#44126)

    ## Summary of the Pull Request
    This PR replaces the current LINQ-based results compilation query of
    combining, sorting and filtering the four result sources with a 3-way
    merge operation plus a final append. It provides a performance increase
    as well as a significant reduction in allocations.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [x] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments
    The existing code:
    1. Limits the number of apps returned to a pre-defined maximum.
    2. Sorts the apps list.
    3. Appends filtered items, scored fallback items and the apps list
    together.
    4. Sorts the three lists based on their score.
    5. Appends the non-scored fallback items, with empty items excluded.
    6. Selects just the `Item` from each.
    7. Creates an array from the enumerable.

    ```csharp
        if (_filteredApps?.Count > 0)
        {
            limitedApps = _filteredApps.OrderByDescending(s => s.Score).Take(_appResultLimit).ToList();
        }

        var items = Enumerable.Empty<Scored<IListItem>>()
                              .Concat(_filteredItems is not null ? _filteredItems : [])
                              .Concat(_scoredFallbackItems is not null ? _scoredFallbackItems : [])
                              .Concat(limitedApps)
                              .OrderByDescending(o => o.Score)

                              // Add fallback items post-sort so they are always at the end of the list
                              // and eventually ordered based on user preference
                              .Concat(_fallbackItems is not null ? _fallbackItems.Where(w => !string.IsNullOrEmpty(w.Item.Title)) : [])
                              .Select(s => s.Item)
                              .ToArray();
    ```

    We can exploit the fact that each of the three 'scored' lists are
    pre-ordered, and replace the query with a 3-way merge and final append
    of the non-scored fallback items.

    By pre-sizing the results array we can avoid all the extra allocations
    of the LINQ-based solution.

    ### Proof of pre-ordering
    In `UpdateSearchText`, each of the lists is defined by calling
    `ListHelpers.FilterListWithScores`:

    ```csharp
        // Produce a list of everything that matches the current filter.
        _filteredItems = [.. ListHelpers.FilterListWithScores<IListItem>(newFilteredItems ?? [], SearchText, scoreItem)];
    ```

    ```csharp
        _scoredFallbackItems = ListHelpers.FilterListWithScores<IListItem>(newFallbacksForScoring ?? [], SearchText, scoreItem);
    ```

    ```csharp
        var scoredApps = ListHelpers.FilterListWithScores<IListItem>(newApps, SearchText, scoreItem);

    ...

        _filteredApps = [.. scoredApps];
    ```

    In `FilterListWithScores`, the results are ordered by score:

    ```csharp
       var scores = items
            .Select(li => new Scored<T>() { Item = li, Score = scoreFunction(query, li) })
            .Where(score => score.Score > 0)
            .OrderByDescending(score => score.Score);
    ```

    (This also makes the existing `OrderByDescending()` for `_filteredApps`
    before the LINQ query redundant.)

    ### K-way merge
    Since the results are pre-sorted, we can do a direct merge in linear
    time. This is what the new `MainListPageResultFactory`'s `Create`
    achieves. As the lists may be different sizes, the routine does a 3-way
    merge, followed by a 2-way merge and a single list drain to finish. Each
    element is only visited once.

    ### Benchmarks
    A separate benchmark project is
    [here](https://github.com/daverayment/MainListBench), written with
    Benchmark.net.

    The project compares the current LINQ-based solution against:
    1. An Array-based algorithm which pre-assigns a results array and still
    sorts the 3 scored sets of results. This shows a naive non-LINQ solution
    which is still _O(n log n)_ because of the sort.
    2. The k-way merge, which is described above. _O(n)_ for both time and
    space complexity.
    3. A heap merge algorithm, which uses a priority queue instead of
    tracking each of the lists separately. (This is _O(n log k)_ in terms of
    time complexity and _O(n + k)_ for space.)

    Care is taken to ensure stable sorting of items. When preparing the
    benchmark data, items with identical scores are assigned to confirm each
    algorithm performs identically to the LINQ `OrderBy` approach, which
    performs a stable sort.

    Results show that the merge performs best in terms of both runtime
    performance and allocations, sometimes by a significant margin. Compared
    to the LINQ approach, merge runs 400%+ faster and with at most ~20% of
    the allocations:

    <img width="1135" height="556" alt="image"
    src="https://github.com/user-attachments/assets/9f9d3932-1592-49d6-8a07-4ea3ba7a0cc5"
    />

    <img width="1149" height="553" alt="image"
    src="https://github.com/user-attachments/assets/ae9e9e0a-b255-4c1a-af4b-e791dea80fa4"
    />

    See here for all charts and raw stats from the run:
    https://docs.google.com/spreadsheets/d/1y2mmWe8dfpbLxF_eqPbEGvaItmqp6HLfSp-rw99hzWg/edit?usp=sharing

    ### Cons

    1. Existing performance is not currently an issue. This could be seen as
    a premature optimisation.
    2. The new code introduces an inherent contract between the results
    compilation routine and the lists, i.e. that they must be sorted.

    This PR was really for research and learning more about CmdPal (and a
    bit of algorithm practice because it's Advent of Code time), so please
    feel free to reject if you feel the cons outweigh the pros.

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed
    - Added unit tests to exercise the new code, which confirm that the
    specific ordering is preserved, and the filtering and pre-trimming of
    the apps list is performed as before.
    - Existing non-UI unit tests run. NB: I _could not_ run any UI Tests on
    my system and just got an early bail-out each time.
    - Manual testing in (non-AOT) Release mode.

commit b8a0163419
Author: Sam Rueby <samrueby@gmail.com>
Date:   Mon Dec 8 13:13:33 2025 -0500

    CmdPal: Arrow keys move logical grid pages (#43870)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [X] Closes: #41939
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [X] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed
    Before

    ![Before](https://github.com/user-attachments/assets/49853e8d-9113-425c-8230-e49fb9b8d640)

    After

    ![After](https://github.com/user-attachments/assets/a4597fe6-6503-4502-99cf-350425f5ef51)

    I noticed the double "active" line around the items when the ListPage is
    focused. I was unable to find where that is defined. Ideally, the
    black-border would go away.

    I tested with AOT turned on.

    The behavior accounts for suggestions. If the SearchBar is focused and
    there is a suggestion, right-arrow will [continue] to complete the
    suggestion.

commit 06fcbdac40
Author: Gordon Lam <73506701+yeelam-gordon@users.noreply.github.com>
Date:   Mon Dec 8 18:52:33 2025 +0800

    Update WinAppSDK to 1.8.3 (#44146)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    This pull request updates several dependencies to newer versions in the
    `Directory.Packages.props` file. The main focus is on upgrading the
    Microsoft Windows App SDK packages to ensure the project uses the latest
    features and bug fixes.

    Dependency version updates:

    * Upgraded `Microsoft.WindowsAppSDK`,
    `Microsoft.WindowsAppSDK.Foundation`, `Microsoft.WindowsAppSDK.AI`, and
    `Microsoft.WindowsAppSDK.Runtime` to their latest respective versions,
    replacing previous 1.8.25* releases with newer builds.
    <!-- Please review the items on the PR checklist before submitting-->

commit d515c67def
Author: leileizhang <leilzh@microsoft.com>
Date:   Mon Dec 8 13:34:33 2025 +0800

    Improve install scope detection to prevent mixed user/machine installations (#43931)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    The old implementation checked
    `HKLM\Software\Classes\powertoys\InstallScope` first. If this key
    existed (even as a remnant from incomplete uninstall), it would
    immediately return `PerMachine` without validating the actual
    installation.

    ### Fix
    - Uses Windows standard Uninstall registry (most reliable source of
    truth)
    - Identifies PowerToys Bundle by exact `BundleUpgradeCode` GUID match
    - MSI component entries (always in HKLM) are automatically ignored since
    they don't have `BundleUpgradeCode`
    - Checks HKCU first, then HKLM, properly handling the fact that Bundle
    location reflects true install scope

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43696
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 9439b6df41
Author: Noraa Junker <noraa.junker@outlook.com>
Date:   Mon Dec 8 04:55:51 2025 +0100

    [Settings] Create a global static instance of SettingsUtils (#44064)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    SettingsUtils is initialized multiple times over the whole solution.
    This creates one singeltone instance (with the default settings), so it
    only has to be initialized once (and improve performance a bit with
    that)

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit a37add8f08
Author: 舰队的偶像-岛风酱! <frg2089@outlook.com>
Date:   Mon Dec 8 11:14:00 2025 +0800

    feat(cmdpal): add pinyin support for Chinese input method (#39354)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    - Add ToolGood.Words.Pinyin package to support pinyin conversion
    - Implement pinyin matching in StringMatcher class
    - Update project dependencies and Directory.Packages.props

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] **Closes:** #38417 #39343
    - [ ] **Communication:** I've discussed this with core contributors
    already. If work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end user facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    I've completed a rough implementation of pinyin support, but since I'm
    currently unsure where to add the toggle for pinyin support, this
    feature is enabled by default for now.

    https://github.com/user-attachments/assets/59df0180-05ad-4b4a-a858-29aa15e40fd2

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

    ---------

    Signed-off-by: 舰队的偶像-岛风酱! <frg2089@outlook.com>
    Co-authored-by: Yu Leng <yuleng@microsoft.com>

commit 60deec6815
Author: Gordon Lam <73506701+yeelam-gordon@users.noreply.github.com>
Date:   Mon Dec 8 09:52:55 2025 +0800

    Using centralized package management for vcxproj (#43920)

    ## Summary of the Pull Request
    This pull request updates the build system for several native and
    managed projects, modernizing NuGet package management and improving
    code analysis configuration. The main changes involve switching from
    legacy `packages.config` and manual `.props`/`.targets` imports to
    PackageReference style for native projects, updating package versions,
    and streamlining code analysis settings.

    **Build system modernization and package management:**

    * Migrated native projects (`PowerToys.MeasureToolCore.vcxproj`,
    `FindMyMouse.vcxproj`) from legacy `packages.config` and manual
    `.props`/`.targets` imports to NuGet PackageReference style, simplifying
    dependency management and build configuration. This includes removing
    the `packages.config` file and related import/error logic, and
    introducing `PackageReference` items for required packages.
    [[1]](diffhunk://#diff-76320b3a74a9241df46edb536ba0f817d7150ddf76bb0fe677e2b276f8bae95aL3-R18)
    [[2]](diffhunk://#diff-76320b3a74a9241df46edb536ba0f817d7150ddf76bb0fe677e2b276f8bae95aR41-L41)
    [[3]](diffhunk://#diff-76320b3a74a9241df46edb536ba0f817d7150ddf76bb0fe677e2b276f8bae95aL145-R153)
    [[4]](diffhunk://#diff-d3a7d80ebbca915b42727633451e769ed2306b418ef3d82b3b04fd5f79560f17L1-L17)
    [[5]](diffhunk://#diff-0f27869c4e90c8fd2c81f5688c58da99afcc9e5767e69ef7938265dbb6928e0fL3-R13)
    * Updated the centralized package versions in
    `Directory.Packages.props`, adding new entries for `boost`,
    `boost_regex-vc143`, `Microsoft.Windows.ImplementationLibrary`, and
    `Microsoft.WindowsAppSDK.Foundation` to support the new build system and
    dependencies.
    [[1]](diffhunk://#diff-5baf5f9e448ad54ab25a091adee0da05d4d228481c9200518fcb1b53a65d4156R10-R11)
    [[2]](diffhunk://#diff-5baf5f9e448ad54ab25a091adee0da05d4d228481c9200518fcb1b53a65d4156R74-R77)

    **Code analysis improvements:**

    * Added configuration to both native and managed projects
    (`PowerToys.MeasureToolCore.vcxproj`, `MeasureToolUI.csproj`) to
    suppress specific warnings (81010002) and exclude NuGet cache files from
    code analysis, reducing noise and improving build performance.
    [[1]](diffhunk://#diff-76320b3a74a9241df46edb536ba0f817d7150ddf76bb0fe677e2b276f8bae95aL3-R18)
    [[2]](diffhunk://#diff-4f2b49a1a5cc7da36ee6d5044792ef681fd0ea5bea12db9ebd4c3090680d4b07R6-R11)

    **Project reference and output handling:**

    * Updated the managed project (`MeasureToolUI.csproj`) to handle native
    project outputs more robustly, ensuring the WinMD and DLL files are
    available at runtime and configuring the project reference to avoid
    assembly reference issues.

    **Compiler configuration:**

    * Enhanced C++ compiler settings in `Cpp.Build.props` to treat
    angle-bracket includes as external, disable warnings and analysis for
    external headers, and optimize build performance.

commit 7e791f2815
Author: Dave Rayment <dave.rayment@gmail.com>
Date:   Mon Dec 8 01:45:46 2025 +0000

    [ImageResizer] Fix Fill mode not cropping image when Shrink Only was engaged and scale was 1 (#43855)

    ## Summary of the Pull Request
    This PR fixes an Image Resizer issue where **Fill** mode operations were
    silently aborted when **Shrink Only** was enabled (the default) and
    scale was 1.0 on one dimension, resulting in files that were renamed
    according to the intended target size but which actually contained the
    original, unmodified image.

    This also fixes a latent bug regarding square images and the **Ignore
    Orientation** setting, and improves the readability of the core
    `Transform` method.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43772
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments
    ### Fix **Shrink Only** logic preventing the correct cropping of images
    **Issue:**
    When using **Fill** mode, the scaling factor is calculated based on the
    larger dimension to ensure the image fills the target box. In scenarios
    where one dimension matches the target and the other overflows (e.g.
    shrinking a 100x100 pixel image to 50x100), the calculated scale factor
    is `1.0`.

    The previous `ShrinkOnly` logic included this:

    ```csharp
    if (_settings.ShrinkOnly
            && _settings.SelectedSize.Unit != ResizeUnit.Percent
            && (scaleX >= 1 || scaleY >= 1))
        {
            return source;
        }
    ```

    This correctly prevents `ShrinkOnly` operations from returning upscaled
    result images, but it also exits too early for cases where the user is
    cropping the image across one dimension only, leaving the other at scale
    1. Effectively, the later cropping code is never run and instead of
    returning the cropped image, the original is returned. The _intended_
    target dimensions are correct, which results in the filename parts not
    matching the resulting image size.

    **Fix:**
    The logic has been split between upscaling and cropping, so:

    1. If the scale on either dimension is > `1.0`, return the source
    (explicitly preventing upscaling for **Shrink Only** mode).
    2. If the scale is <= `1.0` then check if the original dimensions exceed
    the target dimensions. If a crop is required, proceed with it even if
    the scale is exactly `1.0`.

    ### Fix for square images triggering orientation swap
    **Issue:**
    The "Ignore Orientation" check in the original code used a compound
    boolean check:

    ```csharp
    (originalWidth < originalHeight != width < height)
    ```

    This clever but less than readable statement detects orientation
    mismatches. The section also includes a logic issue. When the original
    image was square, `originalWidth < originalHeight` evaluated to `false`,
    treating it as Landscape. If the target dimensions were Portrait, the
    logic detected a mismatch and swapped the target dimensions incorrectly,
    which would crop the height instead of the width.

    'Fortunately' this bug was masked by the first bug, as the crop code
    would never be reached anyway.

    **Fix:**
    The orientation detection routine was refactored to explicitly check for
    Landscape vs. Portrait states. Square images are now naturally excluded,
    as they have neither Landscape nor Portrait orientations. This now
    prevents the dimensions from being swapped.

    ### Refactoring/readability
    The main `Transform` method has been cleaned up:

    - Replaced widespread use of `var` with `double` and `int` for dimension
    and scale calculations.
    - Replaced the non-obvious XOR orientation check (`a < b != c < d`) with
    named booleans (`isInputLandscape`, `isTargetPortrait` etc.) to make the
    intent more self-documenting.
    - New and expanded comments throughout.

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed
    Three new unit tests have been added to `ResizeOperationTests.cs` to
    cover the **Fill** mode edge cases:

    1. `TransformHonorsFillWithShrinkOnlyWhenCropRequired`: Verifies than an
    image requiring a crop but no scaling is processed correctly (tests that
    the original bug report is resolved).
    2. `TransformHonorsFillWithShrinkOnlyWhenUpscaleAttempted`: Confirms
    that when `ShrinkOnly` is set, any upscaling operations are still
    blocked.
    3. `TransformHonorsFillWithShrinkOnlyWhenNoChangeRequired`: Verifies
    that the system returns the source if neither scaling nor cropping is
    required.

    I also manually verified the bug fix with a test 4000 x 6000 pixel
    source file with 1920 x `Auto` **Fill** mode and **Shrink Only**
    settings, mirroring the original user's settings, and their source and
    target dimensions.

commit 2b0ecc2979
Author: Noraa Junker <noraa.junker@outlook.com>
Date:   Sun Dec 7 19:36:05 2025 +0100

    Quick accent character set fixes (#43504)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    * Fix double uppercase theta character
    * Fix some redundant special symbols

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43457 #43137 #41570
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

commit 45cf3de15d
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Sun Dec 7 10:18:02 2025 +0100

    CmdPal: Fix a line-break in RDC extension error toasts (#44129)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    This PR fixes a line break in the RDC extension toast message, replacing
    unescaped \r with a new line (\r in the XML is not recognized as a new
    line escape sequence).

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit bf8c548501
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Sun Dec 7 10:10:45 2025 +0100

    CmdPal: Make text of text Settings button on Command Bar localizable (#44128)

    ## Summary of the Pull Request

    See title

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #44108
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 121c6c0712
Author: Carlos Rafael Ramirez <crramirez@users.noreply.github.com>
Date:   Sun Dec 7 02:54:10 2025 +0100

    Add RGB hex color preview to Advanced Paste clipboard history (#43990)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    This pull request adds support for recognizing and displaying clipboard
    items that are valid RGB hex color codes (such as `#FFBFAB` or `#abc`)
    in the Advanced Paste module. It introduces logic to detect hex color
    strings, converts them to color values, and updates the UI to show a
    color preview for these items. The changes also include comprehensive
    unit tests for the new functionality.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43538
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [x] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [x] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    **Clipboard color detection and conversion:**

    * Added `ClipboardItemHelper.IsRgbHexColor` method using a compiled
    regex to identify valid hex color strings in clipboard text.
    [[1]](diffhunk://#diff-7429196ad30cd0bce57b102669da4dc13d43a09579e99ceac7cc0f7dc101cd2bR62-R86)
    [[2]](diffhunk://#diff-7429196ad30cd0bce57b102669da4dc13d43a09579e99ceac7cc0f7dc101cd2bR112-R114)
    * Introduced `HexColorConverterHelper.ConvertHexColorToRgb` utility to
    convert hex color strings to `Windows.UI.Color`, handling both 3-digit
    and 6-digit formats.

    **UI enhancements for color previews:**

    * Updated `ClipboardHistoryItemPreviewControl` to include a color
    preview grid that displays an ellipse filled with the detected color and
    the color code as text, using the new `HexColorToBrushConverter`.
    [[1]](diffhunk://#diff-2ed6014d4c17037b9cd0ab397e40b9069b1e7fe47a700673f34e8217d78124d5R29-R48)
    [[2]](diffhunk://#diff-2ed6014d4c17037b9cd0ab397e40b9069b1e7fe47a700673f34e8217d78124d5R14)
    [[3]](diffhunk://#diff-0c26c92697f6bb38fa40160fc8b18f0876ddc8d828a510034411001aa2e05063R1-R28)
    * Modified logic in `ClipboardHistoryItemPreviewControl.xaml.cs` to
    ensure color previews are shown only for detected color items and to
    adjust visibility of text and glyph previews accordingly.

    **Unit tests for color detection and conversion:**

    * Added unit tests for hex color conversion
    (`HexColorToColorConverterTests.cs`) and color detection logic
    (`ClipboardItemHelperTests.cs`) to verify correct behavior for valid,
    invalid, and edge-case inputs.
    [[1]](diffhunk://#diff-d81d997d5fb414f1563c31c38681113aaa9c847ef05bb77662d30bd1310d6b8eR1-R61)
    [[2]](diffhunk://#diff-185e8954ca6f061bf5d60d0c61ac6cfd87bd1a48ebda11a8172e3496a050fe85R1-R36)

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed
    * Copied to the clipboard a color encoded text like: #FFBFAB
    * Opened Advanced Paste and noticed the color:

    <img width="467" height="309" alt="image"
    src="https://github.com/user-attachments/assets/6cedce89-9833-4efb-abf9-3cfe8e8f32f0"
    />

    ---------

    Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
    Co-authored-by: crramirez <8397379+crramirez@users.noreply.github.com>
    Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

commit e68526b8d8
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Fri Dec 5 23:32:24 2025 +0100

    CmdPal: Add configuration option for Escape key behavior (#43354)

    ## Summary of the Pull Request

    This PR adds a new option to the **General** page in **Settings**:

    Escape key behavior — a dropdown with the following choices:

    - Clear search first, then go back
      - Current behavior.
      - If the search box contains text, it is cleared; otherwise goes back.
      - On the home page, CmdPal is dismissed.

    - Go back
      - Leaves the search text intact.
    - If the page is not transient, the search text reappears when
    returning.
      - On the home page, CmdPal is dismissed.

    - Hide window and go home (Always dismiss)
      - Immediately dismisses CmdPal and navigates to the home page.
      - Ignores the **Go home when activated** setting.
      - Search text is cleared.

    - Hide window
      - Just hides the window.
      - Intended to be used with #43355.

    This implementation preserves existing behavior, except for **Always
    dismiss**, which always forces navigation to the home page.

    ## Pictures? Pictures!

    <img width="1305" height="892" alt="image"
    src="https://github.com/user-attachments/assets/562e5604-1da6-4fc6-8358-5053df9c573d"
    />

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #38311
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 995a699de7
Author: ruslanlap <106077551+ruslanlap@users.noreply.github.com>
Date:   Fri Dec 5 18:21:01 2025 +0200

    [PowerToysRun][Docs] Add QuickAI plugin to third-party plugins list (#43238)

    Adds QuickAI plugin to the third-party plugins documentation.

    QuickAI is an AI-powered assistance plugin that provides instant, smart
    responses from multiple providers (Groq, Together, Fireworks,
    OpenRouter, Cohere) directly in PowerToys Run.

    Repository: https://github.com/ruslanlap/PowerToysRun-QuickAi

    ---------

    Co-authored-by: Niels Laute <niels.laute@live.nl>

commit 5f6df35d8d
Author: Copilot <198982749+Copilot@users.noreply.github.com>
Date:   Fri Dec 5 10:20:33 2025 -0600

    Add semantic headings to Dashboard page for accessibility (#42438)

    ## Summary

    Fixes #37668 by adding proper semantic heading structure to the
    Dashboard (Home) page, enabling screen reader users to navigate the page
    efficiently using heading shortcuts.

    ## Problem

    The Dashboard page lacked semantic heading elements, making it difficult
    for users of assistive technologies to understand the page structure and
    navigate between sections. When using screen readers with heading
    navigation (H key in scan mode), no headings were announced, violating
    WCAG 2.2 Success Criterion 1.3.1 (Info and Relationships).

    ## Solution

    Added `AutomationProperties.HeadingLevel` attributes to provide proper
    heading hierarchy:

    1. **Dashboard Title** - Marked as Level 1 (H1) heading
    - Added `AutomationProperties.HeadingLevel="1"` to the "Home" page title
       - Follows the same pattern as `SettingsPageControl.xaml`

    2. **Card Titles** - Marked as Level 2 (H2) headings
    - Added `AutomationProperties.HeadingLevel="Level2"` to the Card
    component
    - Applies to all card sections: "Quick Access", "Shortcuts Overview",
    and "Utilities"
       - Follows the same pattern as `SettingsGroup.xaml`

    ## Resulting Structure

    ```
    H1: Home (Dashboard Title)
    ├─ H2: Quick Access
    ├─ H2: Shortcuts Overview
    └─ H2: Utilities
    ```

    ## Impact

    - Screen reader users can now use heading navigation (H key) to jump
    between sections on the Dashboard page
    - Provides proper document structure that follows WCAG 2.2 Level A
    guidelines
    - No visual or functional changes - only accessibility metadata added
    - Consistent with existing accessibility patterns used throughout the
    Settings UI

    ## Testing

    - Changes follow existing patterns in `SettingsPageControl.xaml` (Level
    1) and `SettingsGroup.xaml` (Level 2)
    - Only XAML accessibility attributes added - no code logic changes
    - Minimal, surgical changes: 2 lines across 2 files

    ## References

    - Issue: #37668
    - WCAG 2.2: [Success Criterion 1.3.1 - Info and
    Relationships](https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships)

    <!-- START COPILOT CODING AGENT SUFFIX -->

    <details>

    <summary>Original prompt</summary>

    >
    > ----
    >
    > *This section details on the original issue you should resolve*
    >
    > <issue_title>No Heading Defined on the Home Page.</issue_title>
    > <issue_description>### Microsoft PowerToys version
    >
    > v0.94.2
    >
    > ### Installation method
    >
    > PowerToys auto-update
    >
    > ### Area(s) with issue?
    >
    > New+
    >
    > ### Steps to reproduce
    >
    > **Repro Steps:**
    >
    > 1. Open the Power Toys.
    > 2. Now Select Home from the left navigation pane.
    > 3. Now Turn on narrator and turn on scan mode.
    > 4. Now use Quick navigation H key for headings.
    > 5. Observe the issue.
    >
    > ### ✔️ Expected Behavior
    >
    > The home page should contain at least one semantic heading (typically
    an <h1>) that describes the main topic or purpose of the page.
    >
    > ###  Actual Behavior
    >
    > The home page does not contain any semantic heading tags (e.g., <h1>,
    <h2>, etc.). While text may be visually styled to look like headings, no
    actual heading elements are present in the page’s HTML structure.
    >
    > ### Additional Information
    >
    > **User Impact:**
    > Users of screen readers and other assistive technologies rely on
    headings to understand the structure of the page and navigate
    efficiently.
    >
    > **WCAG Reference:**
    > https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships
    >
    > **Attachments:**
    >
    >
    https://github.com/user-attachments/assets/5140b50c-67fc-40d5-bf80-40e2a2bb7782
    >
    > ### Other Software
    >
    > _No response_</issue_description>
    >
    > ## Comments on the Issue (you are @copilot in this section)
    >
    > <comments>
    > </comments>
    >

    </details>

    Fixes microsoft/PowerToys#42421

    <!-- START COPILOT CODING AGENT TIPS -->
    ---

    💡 You can make Copilot smarter by setting up custom instructions,
    customizing its development environment and configuring Model Context
    Protocol (MCP) servers. Learn more [Copilot coding agent
    tips](https://gh.io/copilot-coding-agent-tips) in the docs.

    ---------

    Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
    Co-authored-by: niels9001 <9866362+niels9001@users.noreply.github.com>
    Co-authored-by: Niels Laute <niels.laute@live.nl>

commit cffdecbc1b
Author: Noraa Junker <aaron.junker@outlook.com>
Date:   Fri Dec 5 14:55:45 2025 +0100

    Add documentation of bot commands and fix some devdocs (#43399)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    * Fixes location of `style.md` file
    * Deletes duplicated `localization.md` file
    * Adds documentation about the bot commands.
    * Adds links to aka.ms link docs and the new document

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [x] **Dev docs:** Added/updated

commit a4d8405957
Author: Noraa Junker <aaron.junker@outlook.com>
Date:   Fri Dec 5 14:54:13 2025 +0100

    Fix dpi issues in Quick Accent (#43314)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #40865
    - [x] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit cdf66a70e9
Author: Niels Laute <niels.laute@live.nl>
Date:   Fri Dec 5 14:33:59 2025 +0100

    [AdvancedPaste] Fix outdated string in Settings (#44099)

    Updating and removing outdated strings.

    Updated string:

    <img width="1565" height="323" alt="image"
    src="https://github.com/user-attachments/assets/3dcad3b9-7ba9-4d87-ab36-405a8e1705db"
    />

commit 9dcddfd4b8
Author: Valentin Arthur Thomas <64769541+warquys@users.noreply.github.com>
Date:   Fri Dec 5 11:57:01 2025 +0100

    Quotation mark (#30481)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Add Quotation mark
    Add local quotation based on ~~VK_OEM_7(0xDE)~~ VK_OEM_COMMA(0xBC) key.
    Not all quotes have been added, only `‟ „ ” « » ‚ , ‘ ’ › ‹ '「 」 《 》 『
    』〈 〉″ ‴ ⁗`
    Why not added :
    - ` ⹂ ⌜ ⌝ ❛ ❜ ❝ ❞ 🙶 🙷 🙸 ' 「 」 ` its redundant and would make too much
    and not readable.
    - ` ﹁ ﹂ ﹃ ﹄ `  I did not put them because there use for horizontal text

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: https://github.com/microsoft/PowerToys/issues/29371
    https://github.com/microsoft/PowerToys/issues/24832
    - [ ] **Communication:** I've discussed this with core contributors
    already. If work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end user facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places (None)
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed
    or any additional comments/features here -->
    This PR is currently a draft, I still need to know if adding
    language-related keyboard management is a good idea or specifying the
    use of a gobal key to make it easier to manage all the keyboards in one.
    Some languages ​​can use different keyboards, I think this would become
    problematic if the keyboard does not match the key used by default.
    However, using a universal key can also pose an issue to finding the
    key. that remains to be discussed
    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 503bcbdf2d
Author: Copilot <198982749+Copilot@users.noreply.github.com>
Date:   Fri Dec 5 07:33:37 2025 +0100

    Restore missing "Quick access" menu item in tray icon context menu (#42676)

    ## Summary
    Restores the "Quick access" menu item that was accidentally removed from
    the PowerToys tray icon context menu.

    ## Issue
    Fixes #[issue_number]

    The "Quick access" menu item was missing from the tray icon's
    right-click context menu, preventing users from accessing this feature
    via the tray menu.

    **Expected menu:**

    ![Expected
    menu](https://github.com/user-attachments/assets/805b1436-5a08-42e7-a34d-b9848fd9a235)

    **Actual menu (before this fix):**

    ![Actual
    menu](https://github.com/user-attachments/assets/7584035d-e893-4f73-acc3-84d789e31e81)

    ## Changes
    - Added the missing `MENUITEM "Quick access\tLeft-click",
    ID_QUICK_ACCESS_MENU_COMMAND` entry as the first menu item in the
    `ID_TRAY_MENU` definition in `src/runner/runner.base.rc`

    ## Details
    The menu item was accidentally removed in commit
    f5797a065a. This PR restores it to its
    correct position as the first item in the tray menu.

    All supporting code was already in place:
    - The resource ID `ID_QUICK_ACCESS_MENU_COMMAND` (40006) is defined in
    `resource.base.h`
    - The resource string `QUICK_ACCESS_MENU_TEXT` is defined in
    `Resources.resx`
    - The menu command handler in `tray_icon.cpp` opens the Quick Access
    flyout window
    - The localization code updates the menu text at runtime

    ## Testing
    -  Verified the menu item syntax is correct and matches existing
    patterns
    -  Confirmed all supporting resource IDs and handler code exist
    -  CI build verification pending

    After this fix, the tray menu will correctly display:
    1. Quick access (Left-click)
    2. Settings (Double-click)
    3. Documentation
    4. Report Bug
    5. Close

    <!-- START COPILOT CODING AGENT SUFFIX -->

    <details>

    <summary>Original prompt</summary>

    >
    > ----
    >
    > *This section details on the original issue you should resolve*
    >
    > <issue_title>Quick Access missing in tray menu</issue_title>
    > <issue_description>### Microsoft PowerToys version
    >
    > 0.95.0
    >
    > ### Installation method
    >
    > PowerToys auto-update
    >
    > ### Area(s) with issue?
    >
    > System tray interaction
    >
    > ### Steps to reproduce
    >
    > 1. Right click the tray icon
    > 2. Look at the list of items which can be selected
    > 3. Notice that the "Quick access" is missing
    >
    > Expected menu ("Exit" is now "Close" I took this image from initial
    implementation):
    >
    > <img width="234" height="127" alt="Image"
    src="https://github.com/user-attachments/assets/805b1436-5a08-42e7-a34d-b9848fd9a235"
    />
    >
    > Actual menu right now:
    >
    > <img width="239" height="105" alt="Image"
    src="https://github.com/user-attachments/assets/7584035d-e893-4f73-acc3-84d789e31e81"
    />
    >
    > ### ✔️ Expected Behavior
    >
    > The "Quick access" menu item should be there
    >
    > ###  Actual Behavior
    >
    > The menu item is missing
    >
    > ### Additional Information
    >
    > Windows 10 Pro 22H2 19045.6332
    >
    > (Also it is the same on my other computers)
    >
    > ### Other Software
    >
    > _No response_</issue_description>
    >
    > <agent_instructions>restore
    >
    > MENUITEM "Quick access\tLeft-click", ID_QUICK_ACCESS_MENU_COMMAND
    >
    > as first menu item of ID_TRAY_MENU MENU in
    src/runner/runner.base.rc</agent_instructions>
    >
    > ## Comments on the Issue (you are @copilot in this section)
    >
    > <comments>
    > <comment_new><author>@niels9001</author><body>
    > @davidegiacometti is this a regression from the PR where we updated
    the string names?</body></comment_new>
    > <comment_new><author>@davidegiacometti</author><body>
    > Hi @niels9001
    > I just realized that the menu was missing in
    https://github.com/microsoft/PowerToys/pull/40714 screenshots, but the
    regression was caused by
    f5797a065a.
    > Unfortunately, many of the `.rc` files in the PT codebase have
    UTF16-LE encoding and GitHub doesn't show diff.</body></comment_new>
    > </comments>
    >

    </details>

    Fixes microsoft/PowerToys#42618

    <!-- START COPILOT CODING AGENT TIPS -->
    ---

    💬 Share your feedback on Copilot coding agent for the chance to win a
    $200 gift card! Click
    [here](https://survey3.medallia.com/?EAHeSx-AP01bZqG0Ld9QLQ) to start
    the survey.

    ---------

    Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
    Co-authored-by: davidegiacometti <25966642+davidegiacometti@users.noreply.github.com>

commit 52f2561937
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Wed Dec 3 17:16:25 2025 +0100

    CmdPal: Find app for WinGet package (#43943)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    This PR introduces a bit of dark magic to resolve the correct installed
    app for a given WinGet package:

    - Packaged apps: matched using their package family name.
    - Everything else: matched using the product code (GUID) and heuristic
    registry lookup.
    - The registry rarely stores the executable path directly, so the logic
    compares install locations with known apps.
      - It attempts to pick the best candidate while avoiding uninstallers.
      - It’s not science — let’s call it `#666666` magic.
    - MSI API support was removed because it's too slow for this scenario.
    - If no reliable match is found, the command is skipped for now. The
    future plan is to redirect the user to the list of installed apps and
    search by display name, but that needs some supporting infrastructure
    first.
    - The command order for WinGet list entries was updated: **Install /
    Uninstall** is now the primary action, ensuring a stable UI since this
    command is always available.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43671
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit dc30f3fd8e
Author: Dustin L. Howett <duhowett@microsoft.com>
Date:   Wed Dec 3 03:59:46 2025 -0600

    build: move main and setup to SLNX (#43478)

    Closes #37100

    This does not migrate the rest of the solutions (why do we have so
    many?)

    Not migrated:

    - TemplateCmdPalExtension.sln
    - FancyZonesEditor.sln
    - BugReportTool.sln
    - CleanUp_tool.sln
    - FancyZones_DrawLayoutTest.sln
    - FancyZones_zonable_tester.sln
    - FancyZone_HitTest.sln
    - MonitorReportTool.sln
    - PowerToyTemplate.sln
    - StylesReportTool.sln

    ---------

    Co-authored-by: vanzue <vanzue@outlook.com>

commit 8f9a2c32cc
Author: Jessica Dene Earley-Cha <12740421+chatasweetie@users.noreply.github.com>
Date:   Tue Dec 2 09:59:57 2025 -0800

    add missing powertoys events (#44016)

    ## Summary of the Pull Request
    This added missing telemetry events from modules that were not listed in
    DATA_AND_PRIVACY

    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [x] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected

commit bcd1583bb7
Author: moooyo <42196638+moooyo@users.noreply.github.com>
Date:   Tue Dec 2 16:31:02 2025 +0800

    [AOT] Refactor SettingsLib/SettingsUI for Native AOT compatibility (#42644)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    Key Changes:

    1. Settings.UI.Library:
    - Added SettingsSerializationContext.cs with comprehensive
    JsonSerializable attributes for all settings types
    - Updated BasePTModuleSettings.ToJsonString() to use AOT-compatible
    serialization
    - Updated SettingsUtils.GetFile<T>() to use AOT-compatible
    deserialization
    - Modified all ToString() methods in Properties classes to use
    SettingsSerializationContext
    - Converted struct fields to properties in SunTimes and
    MouseWithoutBordersProperties for serialization compatibility

    2. Settings.UI:
    - Fixed namespace alias in SourceGenerationContextContext.cs to avoid
    conflicts

    For any future developers who discover incorrect settings resolution,
    please follow up my changes to add your setting type into
    JsonSerilizerContext.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

    Co-authored-by: Yu Leng <yuleng@microsoft.com>

commit b075a021df
Author: Carlos Zamora <carlos.zamora@microsoft.com>
Date:   Mon Dec 1 22:09:08 2025 -0800

    Bump our telemetry package version (#44015)

    Data collection is still hard.

    This just makes it so that the build pipeline uses the updated PowerToys
    telemetry NuGet package. The updated package switches us over to use a
    diagnostic data provider group for compliance with some new regulations
    (i.e. DMA and EU Data Act).

commit 9e43c23216
Author: Michael Clayton <mike@kingslandconsulting.co.uk>
Date:   Tue Dec 2 02:43:08 2025 +0000

    Ready for Review - [Mouse Without Borders] - refactoring "Common" classes (Part 6 of 7)  (#43208)

    ## Summary of the Pull Request

    **Part 6** of a [slow-running 7-part
    refactor](https://github.com/microsoft/PowerToys/issues/35155#issuecomment-2583334110)
    of the giant "Common" class in Mouse Without Borders into individual
    classes with tighter private scope.

    In this PR:

    * Extract the "Common" code from the following files:
      * ```Common.Encryption.cs```-> ```Core/Encryption.cs```
      * ```Common.Package.cs``` -> ```Core/<multiple files>.cs```
    * ```Common.ShutdownWithPowerToys.cs``` ->
    ```Core/ShutdownWithPowerToys.cs```
      * ```Common.VK.cs``` -> ```Core/VK.cs```, ```Core/WM.cs```
      * ```Common.WinAPI.cs``` -> ```Core/WinAPI.cs```
    * Update references to the types in the new locations
    * Update unit test to verify functionality has only changed in an
    expected way

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x]      Partially addresses #35155
    - [x] **Communication:** I've discussed this with core contributors
    already. If work hasn't been agreed, this work might be rejected
    - [x]     **Tests:** Added/updated and all pass
    - [x]     **Localization:** All end user facing strings can be localized
       - no changes in this PR
    - [x]     **Dev docs:** Added/updated
       - no changes in this PR
    - [x]     **New binaries:** Added on the required places
       - no changes in this PR
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [x] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx
       - no changes in this PR

    <!-- Provide a more detailed description of the PR, other things fixed
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

    ### Run manual tests from [Test Checklist
    Template](5bc7201ae2/doc/releases/tests-checklist-template.md (mouse-without-borders)):

    * Install PowerToys on two PCs in the same local network:
       - [x]     Verify that PowerToys is properly installed on both PCs.
       - [x]     Configure Windows Firewall Rules
    - ```netsh advfirewall firewall add rule
    name="PowerToys.MouseWithoutBorders - mc" dir=in action=allow
    program="C:\src\mc\PowerToys\x64\Debug\PowerToys.exe" enable=yes
    remoteip=any profile=any protocol=tcp```

     * Setup Connection:
    - [x] Open MWB's settings on the first PC and click the "New Key"
    button. Verify that a new security key is generated.
    - [x] Copy the generated security key and paste it in the corresponding
    input field in the settings of MWB on the second PC. Also enter the name
    of the first PC in the required field.
    - [x] Press "Connect" and verify that the machine layout now includes
    two PC tiles, each displaying their respective PC names.

     * Verify Connection Status:
    - [x] Ensure that the border of the remote PC turns green, indicating a
    successful connection.
    - [x] Enter an incorrect security key and verify that the border of the
    remote PC turns red, indicating a failed connection.

     * Test Remote Mouse/Keyboard Control:
    - [x] With the PCs connected, test the mouse/keyboard control from one
    PC to another. Verify that the mouse/keyboard inputs are correctly
    registered on the other PC.
    - [ ] Test remote mouse/keyboard control across all four PCs, if
    available. Verify that inputs are correctly registered on each connected
    PC when the mouse is active there.
         - unable to test - only 2 machines available

     * Test Remote Control with Elevated Apps:
    - note - the main PowerToys.exe must be running as a **non**-admin for
    these tests
    - [x] Open an elevated app on one of the PCs. Verify that without "Use
    Service" enabled, PowerToys does not control the elevated app.
    - [x] Enable "Use Service" in MWB's settings (need to run PowerToys.exe
    as admin to enable "Use Service", then restart PowerToys.exe as
    non-admin). Verify that PowerToys can now control the elevated app
    remotely. Verify that MWB processes are running as LocalSystem, while
    the MWB helper process is running non-elevated.
    - ```get-process -Name "PowerToys.MouseWithoutBorders*" -IncludeUserName
    | format-table Id, ProcessName, UserName```
    - [x] Process: ```PowerToys.MouseWithoutBorders.exe``` - running as
    ```SYSTEM```
    - [x] Process: ```PowerToys.MouseWithoutBorders.Helper.exe``` - running
    as current user
    - ```get-service -Name "PowerToys.*" | ft Status, Name, UserName;
    get-ciminstance -Class "Win32_Service" -Filter "Name like 'PowerToys%'"
    | ft ProcessId, Name```
    - [x] Service: ```PowerToys.MWB.Service``` - running as ```Local
    System```
    - [x] Toggle "Use Service" again, verify that each time you do that, the
    MWB processes are restarted.
    - [x] Run PowerToys elevated on one of the machines, verify that you can
    control elevated apps remotely now on that machine.

    * Test Module Enable Status:
    - [x] For all combinations of "Use Service"/"Run PowerToys as admin",
    try enabling/disabling MWB module and verify that it's indeed being
    toggled using task manager.

     * Test Disconnection/Reconnection:
    - [x] Disconnect one of the PCs from network. Verify that the machine
    layout updates to reflect the disconnection.
       - [x]     Do the same, but now by exiting PowerToys.
       - [ ]     Start PowerToys again, verify that the PCs are reconnected.

     * Test Various Local Network Conditions:
    - [ ] Test MWB performance under various network conditions (e.g., low
    bandwidth, high latency). Verify that the tool maintains a stable
    connection and functions correctly.

     * Clipboard Sharing:
    - [x] Copy some text on one PC and verify that the same text can be
    pasted on another PC.
    - [x] Use the screenshot key and Win+Shift+S to take a screenshot on one
    PC and verify that the screenshot can be pasted on another PC.
    - [x] Copy a file in Windows Explorer and verify that the file can be
    pasted on another PC. Make sure the file size is below 100MB.
    - [x] Try to copy multiple files and directories and verify that it's
    not possible (only the first selected file is being copied).

     * Drag and Drop:
    - [ ] Drag a file from Windows Explorer on one PC, cross the screen
    border onto another PC, and release it there. Verify that the file is
    copied to the other PC. Make sure the file size is below 100MB.
    - [ ] While dragging the file, verify that a corresponding icon is
    displayed under the mouse cursor.
    - [ ] Without moving the mouse from one PC to the target PC, press
    CTRL+ALT+F1/2/3/4 hotkey to switch to the target PC directly and verify
    that file sharing/dropping is not working.

     * Lock and Unlock with "Use Service" Enabled:
       - [x]     Enable "Use Service" in MWB's settings.
    - [x] Lock a remote PC using Win+L, move the mouse to it remotely, and
    try to unlock it. Verify that you can unlock the remote PC.
    - [x] Disable "Use Service" in MWB's settings, lock the remote PC, move
    the mouse to it remotely, and try to unlock it. Verify that you can't
    unlock the remote PC.

     * Test Settings:
    - [ ] Change the rest of available settings on MWB page and verify that
    each setting works as described.

    ### Group Policy Tests

    See https://learn.microsoft.com/en-us/windows/powertoys/grouppolicy

    - [ ] Install *.admx / *.adml and check settings behave as expected
      - [ ] I'll expand the list of settings here when I get this far :-)
    - [ ] HKEY_LOCAL_MACHINE\SOFTWARE\Policies\PowerToys
      - [x]     ConfigureEnabledUtilityMouseWithoutBorders
    - [x] ```[missing]``` - "Activation -> Enable Mouse Without Borders"
    enabled, with GPO warning hidden
    - ```reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Policies\PowerToys /v
    ConfigureEnabledUtilityMouseWithoutBorders /f```
    - [x] ```0``` - "Activation -> Enable Mouse Without Borders" set to
    "off" and disabled, with GPO warning visible
    - ```reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\PowerToys /v
    ConfigureEnabledUtilityMouseWithoutBorders /t REG_DWORD /d 0 /f```
    - [x] ```1``` - "Activation -> Enable Mouse Without Borders" set to "on"
    and disabled, with GPO warning visible
    - ```reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\PowerToys /v
    ConfigureEnabledUtilityMouseWithoutBorders /t REG_DWORD /d 1 /f```
      - [ ] MwbClipboardSharingEnabled
      - [ ] MwbFileTransferEnabled
      - [ ] MwbUseOriginalUserInterface
      - [ ] MwbDisallowBlockingScreensaver
      - [ ] MwbSameSubnetOnly
      - [ ] MwbValidateRemoteIp
      - [x]     MwbDisableUserDefinedIpMappingRules
    - [x] ```[missing]``` - "Advanced Settings -> IP address mapping"
    enabled, with GPO warning hidden
    - ```reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Policies\PowerToys /v
    MwbDisableUserDefinedIpMappingRules /f```
    - [x] ```0``` - "Advanced Settings -> IP address mapping" enabled, with
    GPO warning hidden
    - ```reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\PowerToys /v
    MwbDisableUserDefinedIpMappingRules /t REG_DWORD /d 0 /f```
    - [x] ```1``` - "Advanced Settings -> IP address mapping" disabled, with
    GPO warning visible
    - ```reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\PowerToys /v
    MwbDisableUserDefinedIpMappingRules /t REG_DWORD /d 1 /f```
      - [x]     MwbPolicyDefinedIpMappingRules
    - [x] ```[missing]``` - "Advanced Settings -> IP address mapping"
    enabled, with GPO warning and GPO values hidden
    - ```reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Policies\PowerToys /v
    MwbPolicyDefinedIpMappingRules /f```
    - [x] ```[empty value]``` - "Advanced Settings -> IP address mapping"
    enabled, with GPO warning hidden and GPO values hidden
    - ```reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\PowerToys /v
    MwbPolicyDefinedIpMappingRules /t REG_MULTI_SZ /d "" /f```
    - [x] ```[non-empty value]``` - "Advanced Settings -> IP address
    mapping" enabled, with GPO warning visible and GPO values visible
    - ```reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\PowerToys /v
    MwbPolicyDefinedIpMappingRules /t REG_MULTI_SZ /d "aaa 10.0.0.1\0bbb
    10.0.0.2" /f```

commit bece9c9217
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Tue Dec 2 03:25:38 2025 +0100

    CmdPal: Adds a back button to Settings window (#44013)

    ## Summary of the Pull Request

    This PR introduces proper navigation support in the Settings window.
    - Enables the Go back button in the title bar.
    - Adds support for Alt + Left Arrow, mouse X1 button, and the Go back
    button.
    - Fixes breadcrumb updates and localization issues to prevent them from
    breaking during navigation.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #44011
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 32c13cead4
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Mon Dec 1 20:24:54 2025 +0100

    CmdPal: Remove fallbacks from the home page when there's no query (#44005)

    ## Summary of the Pull Request

    This PR stops fallback commands from showing on the homepage when
    there’s no query, with the reasons detailed in the linked issue.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #44004
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 33808fdb9c
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Mon Dec 1 20:23:48 2025 +0100

    CmdPal: Hide RDC fallback item by default (#43994)

    ## Summary of the Pull Request

    This fixes few nits with RDC extension:
    - hides the RDC fallback item from the home page when there’s no query;
    - fixes MSTSC process working directory (must physically exists or be an
    empty string)

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit f510be4c53
Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Date:   Mon Dec 1 22:29:21 2025 +0800

    Build(deps): Bump actions/checkout from 3 to 6 (#43838)

    Bumps [actions/checkout](https://github.com/actions/checkout) from 3 to
    6.
    <details>
    <summary>Release notes</summary>
    <p><em>Sourced from <a
    href="https://github.com/actions/checkout/releases">actions/checkout's
    releases</a>.</em></p>
    <blockquote>
    <h2>v6.0.0</h2>
    <h2>What's Changed</h2>
    <ul>
    <li>Update README to include Node.js 24 support details and requirements
    by <a href="https://github.com/salmanmkc"><code>@​salmanmkc</code></a>
    in <a
    href="https://redirect.github.com/actions/checkout/pull/2248">actions/checkout#2248</a></li>
    <li>Persist creds to a separate file by <a
    href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2286">actions/checkout#2286</a></li>
    <li>v6-beta by <a
    href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2298">actions/checkout#2298</a></li>
    <li>update readme/changelog for v6 by <a
    href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2311">actions/checkout#2311</a></li>
    </ul>
    <p><strong>Full Changelog</strong>: <a
    href="https://github.com/actions/checkout/compare/v5.0.0...v6.0.0">https://github.com/actions/checkout/compare/v5.0.0...v6.0.0</a></p>
    <h2>v6-beta</h2>
    <h2>What's Changed</h2>
    <p>Updated persist-credentials to store the credentials under
    <code>$RUNNER_TEMP</code> instead of directly in the local git
    config.</p>
    <p>This requires a minimum Actions Runner version of <a
    href="https://github.com/actions/runner/releases/tag/v2.329.0">v2.329.0</a>
    to access the persisted credentials for <a
    href="https://docs.github.com/en/actions/tutorials/use-containerized-services/create-a-docker-container-action">Docker
    container action</a> scenarios.</p>
    <h2>v5.0.1</h2>
    <h2>What's Changed</h2>
    <ul>
    <li>Port v6 cleanup to v5 by <a
    href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2301">actions/checkout#2301</a></li>
    </ul>
    <p><strong>Full Changelog</strong>: <a
    href="https://github.com/actions/checkout/compare/v5...v5.0.1">https://github.com/actions/checkout/compare/v5...v5.0.1</a></p>
    <h2>v5.0.0</h2>
    <h2>What's Changed</h2>
    <ul>
    <li>Update actions checkout to use node 24 by <a
    href="https://github.com/salmanmkc"><code>@​salmanmkc</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2226">actions/checkout#2226</a></li>
    <li>Prepare v5.0.0 release by <a
    href="https://github.com/salmanmkc"><code>@​salmanmkc</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2238">actions/checkout#2238</a></li>
    </ul>
    <h2>⚠️ Minimum Compatible Runner Version</h2>
    <p><strong>v2.327.1</strong><br />
    <a
    href="https://github.com/actions/runner/releases/tag/v2.327.1">Release
    Notes</a></p>
    <p>Make sure your runner is updated to this version or newer to use this
    release.</p>
    <p><strong>Full Changelog</strong>: <a
    href="https://github.com/actions/checkout/compare/v4...v5.0.0">https://github.com/actions/checkout/compare/v4...v5.0.0</a></p>
    <h2>v4.3.1</h2>
    <h2>What's Changed</h2>
    <ul>
    <li>Port v6 cleanup to v4 by <a
    href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2305">actions/checkout#2305</a></li>
    </ul>
    <p><strong>Full Changelog</strong>: <a
    href="https://github.com/actions/checkout/compare/v4...v4.3.1">https://github.com/actions/checkout/compare/v4...v4.3.1</a></p>
    <h2>v4.3.0</h2>
    <h2>What's Changed</h2>
    <ul>
    <li>docs: update README.md by <a
    href="https://github.com/motss"><code>@​motss</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/1971">actions/checkout#1971</a></li>
    <li>Add internal repos for checking out multiple repositories by <a
    href="https://github.com/mouismail"><code>@​mouismail</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/1977">actions/checkout#1977</a></li>
    <li>Documentation update - add recommended permissions to Readme by <a
    href="https://github.com/benwells"><code>@​benwells</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2043">actions/checkout#2043</a></li>
    </ul>
    <!-- raw HTML omitted -->
    </blockquote>
    <p>... (truncated)</p>
    </details>
    <details>
    <summary>Changelog</summary>
    <p><em>Sourced from <a
    href="https://github.com/actions/checkout/blob/main/CHANGELOG.md">actions/checkout's
    changelog</a>.</em></p>
    <blockquote>
    <h1>Changelog</h1>
    <h2>V6.0.0</h2>
    <ul>
    <li>Persist creds to a separate file by <a
    href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2286">actions/checkout#2286</a></li>
    <li>Update README to include Node.js 24 support details and requirements
    by <a href="https://github.com/salmanmkc"><code>@​salmanmkc</code></a>
    in <a
    href="https://redirect.github.com/actions/checkout/pull/2248">actions/checkout#2248</a></li>
    </ul>
    <h2>V5.0.1</h2>
    <ul>
    <li>Port v6 cleanup to v5 by <a
    href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2301">actions/checkout#2301</a></li>
    </ul>
    <h2>V5.0.0</h2>
    <ul>
    <li>Update actions checkout to use node 24 by <a
    href="https://github.com/salmanmkc"><code>@​salmanmkc</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2226">actions/checkout#2226</a></li>
    </ul>
    <h2>V4.3.1</h2>
    <ul>
    <li>Port v6 cleanup to v4 by <a
    href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2305">actions/checkout#2305</a></li>
    </ul>
    <h2>V4.3.0</h2>
    <ul>
    <li>docs: update README.md by <a
    href="https://github.com/motss"><code>@​motss</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/1971">actions/checkout#1971</a></li>
    <li>Add internal repos for checking out multiple repositories by <a
    href="https://github.com/mouismail"><code>@​mouismail</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/1977">actions/checkout#1977</a></li>
    <li>Documentation update - add recommended permissions to Readme by <a
    href="https://github.com/benwells"><code>@​benwells</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2043">actions/checkout#2043</a></li>
    <li>Adjust positioning of user email note and permissions heading by <a
    href="https://github.com/joshmgross"><code>@​joshmgross</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2044">actions/checkout#2044</a></li>
    <li>Update README.md by <a
    href="https://github.com/nebuk89"><code>@​nebuk89</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2194">actions/checkout#2194</a></li>
    <li>Update CODEOWNERS for actions by <a
    href="https://github.com/TingluoHuang"><code>@​TingluoHuang</code></a>
    in <a
    href="https://redirect.github.com/actions/checkout/pull/2224">actions/checkout#2224</a></li>
    <li>Update package dependencies by <a
    href="https://github.com/salmanmkc"><code>@​salmanmkc</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/2236">actions/checkout#2236</a></li>
    </ul>
    <h2>v4.2.2</h2>
    <ul>
    <li><code>url-helper.ts</code> now leverages well-known environment
    variables by <a href="https://github.com/jww3"><code>@​jww3</code></a>
    in <a
    href="https://redirect.github.com/actions/checkout/pull/1941">actions/checkout#1941</a></li>
    <li>Expand unit test coverage for <code>isGhes</code> by <a
    href="https://github.com/jww3"><code>@​jww3</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/1946">actions/checkout#1946</a></li>
    </ul>
    <h2>v4.2.1</h2>
    <ul>
    <li>Check out other refs/* by commit if provided, fall back to ref by <a
    href="https://github.com/orhantoy"><code>@​orhantoy</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/1924">actions/checkout#1924</a></li>
    </ul>
    <h2>v4.2.0</h2>
    <ul>
    <li>Add Ref and Commit outputs by <a
    href="https://github.com/lucacome"><code>@​lucacome</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/1180">actions/checkout#1180</a></li>
    <li>Dependency updates by <a
    href="https://github.com/dependabot"><code>@​dependabot</code></a>- <a
    href="https://redirect.github.com/actions/checkout/pull/1777">actions/checkout#1777</a>,
    <a
    href="https://redirect.github.com/actions/checkout/pull/1872">actions/checkout#1872</a></li>
    </ul>
    <h2>v4.1.7</h2>
    <ul>
    <li>Bump the minor-npm-dependencies group across 1 directory with 4
    updates by <a
    href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/1739">actions/checkout#1739</a></li>
    <li>Bump actions/checkout from 3 to 4 by <a
    href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/1697">actions/checkout#1697</a></li>
    <li>Check out other refs/* by commit by <a
    href="https://github.com/orhantoy"><code>@​orhantoy</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/1774">actions/checkout#1774</a></li>
    <li>Pin actions/checkout's own workflows to a known, good, stable
    version. by <a href="https://github.com/jww3"><code>@​jww3</code></a> in
    <a
    href="https://redirect.github.com/actions/checkout/pull/1776">actions/checkout#1776</a></li>
    </ul>
    <h2>v4.1.6</h2>
    <ul>
    <li>Check platform to set archive extension appropriately by <a
    href="https://github.com/cory-miller"><code>@​cory-miller</code></a> in
    <a
    href="https://redirect.github.com/actions/checkout/pull/1732">actions/checkout#1732</a></li>
    </ul>
    <h2>v4.1.5</h2>
    <ul>
    <li>Update NPM dependencies by <a
    href="https://github.com/cory-miller"><code>@​cory-miller</code></a> in
    <a
    href="https://redirect.github.com/actions/checkout/pull/1703">actions/checkout#1703</a></li>
    <li>Bump github/codeql-action from 2 to 3 by <a
    href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/1694">actions/checkout#1694</a></li>
    <li>Bump actions/setup-node from 1 to 4 by <a
    href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/1696">actions/checkout#1696</a></li>
    <li>Bump actions/upload-artifact from 2 to 4 by <a
    href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a
    href="https://redirect.github.com/actions/checkout/pull/1695">actions/checkout#1695</a></li>
    </ul>
    <!-- raw HTML omitted -->
    </blockquote>
    <p>... (truncated)</p>
    </details>
    <details>
    <summary>Commits</summary>
    <ul>
    <li><a
    href="1af3b93b68"><code>1af3b93</code></a>
    update readme/changelog for v6 (<a
    href="https://redirect.github.com/actions/checkout/issues/2311">#2311</a>)</li>
    <li><a
    href="71cf2267d8"><code>71cf226</code></a>
    v6-beta (<a
    href="https://redirect.github.com/actions/checkout/issues/2298">#2298</a>)</li>
    <li><a
    href="069c695914"><code>069c695</code></a>
    Persist creds to a separate file (<a
    href="https://redirect.github.com/actions/checkout/issues/2286">#2286</a>)</li>
    <li><a
    href="ff7abcd0c3"><code>ff7abcd</code></a>
    Update README to include Node.js 24 support details and requirements (<a
    href="https://redirect.github.com/actions/checkout/issues/2248">#2248</a>)</li>
    <li><a
    href="08c6903cd8"><code>08c6903</code></a>
    Prepare v5.0.0 release (<a
    href="https://redirect.github.com/actions/checkout/issues/2238">#2238</a>)</li>
    <li><a
    href="9f265659d3"><code>9f26565</code></a>
    Update actions checkout to use node 24 (<a
    href="https://redirect.github.com/actions/checkout/issues/2226">#2226</a>)</li>
    <li><a
    href="08eba0b27e"><code>08eba0b</code></a>
    Prepare release v4.3.0 (<a
    href="https://redirect.github.com/actions/checkout/issues/2237">#2237</a>)</li>
    <li><a
    href="631c7dc4f8"><code>631c7dc</code></a>
    Update package dependencies (<a
    href="https://redirect.github.com/actions/checkout/issues/2236">#2236</a>)</li>
    <li><a
    href="8edcb1bdb4"><code>8edcb1b</code></a>
    Update CODEOWNERS for actions (<a
    href="https://redirect.github.com/actions/checkout/issues/2224">#2224</a>)</li>
    <li><a
    href="09d2acae67"><code>09d2aca</code></a>
    Update README.md (<a
    href="https://redirect.github.com/actions/checkout/issues/2194">#2194</a>)</li>
    <li>Additional commits viewable in <a
    href="https://github.com/actions/checkout/compare/v3...v6">compare
    view</a></li>
    </ul>
    </details>
    <br />

    [![Dependabot compatibility
    score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=actions/checkout&package-manager=github_actions&previous-version=3&new-version=6)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

    Dependabot will resolve any conflicts with this PR as long as you don't
    alter it yourself. You can also trigger a rebase manually by commenting
    `@dependabot rebase`.

    [//]: # (dependabot-automerge-start)
    [//]: # (dependabot-automerge-end)

    ---

    <details>
    <summary>Dependabot commands and options</summary>
    <br />

    You can trigger Dependabot actions by commenting on this PR:
    - `@dependabot rebase` will rebase this PR
    - `@dependabot recreate` will recreate this PR, overwriting any edits
    that have been made to it
    - `@dependabot merge` will merge this PR after your CI passes on it
    - `@dependabot squash and merge` will squash and merge this PR after
    your CI passes on it
    - `@dependabot cancel merge` will cancel a previously requested merge
    and block automerging
    - `@dependabot reopen` will reopen this PR if it is closed
    - `@dependabot close` will close this PR and stop Dependabot recreating
    it. You can achieve the same result by closing it manually
    - `@dependabot show <dependency name> ignore conditions` will show all
    of the ignore conditions of the specified dependency
    - `@dependabot ignore this major version` will close this PR and stop
    Dependabot creating any more for this major version (unless you reopen
    the PR or upgrade to it yourself)
    - `@dependabot ignore this minor version` will close this PR and stop
    Dependabot creating any more for this minor version (unless you reopen
    the PR or upgrade to it yourself)
    - `@dependabot ignore this dependency` will close this PR and stop
    Dependabot creating any more for this dependency (unless you reopen the
    PR or upgrade to it yourself)

    </details>

    Signed-off-by: dependabot[bot] <support@github.com>
    Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

commit 4d3c223402
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Mon Dec 1 02:32:30 2025 +0100

    CmdPal: Fix grid views (#43991)

    ## Summary of the Pull Request

    This PR fixes the crash due to binding to a trimmed property. For this
    it converts runtime bindings on GridView to use `{x:Bind}` so this issue
    can't happen in the future.

    - Fixes a crash related to the `Visibility` property in gallery/grid
    views when trimmed during AOT builds.
    - Fixes ShowTitle and ShowSubtitle properties, they are now taken into
    account in a view.
    - Improves UI layout, removes some margins and maches the corner radius
    of the item contaienr with the item content in the gallery view.
    - Refactores gallery and grid views to move logic from the view to the
    view model so we can x:Bind to them.
    - Replaces `{Binding}` with `{x:Bind}` to improve performance and enable
    compile-time binding validation.
    - Properties related to grids are splatted on to the common
    `IGridPropertiesViewModel` interface. Subclassing would add extra
    overhead without substential benefit.
    - Adds new samples to showcase various grid view configurations.

    ## Pictures? Pictures!

    A) Gallery view (with title and subtitle)
    <img width="909" height="583" alt="image"
    src="https://github.com/user-attachments/assets/b807e7a8-412f-4817-8121-e3470c49e0c0"
    />

    B) Gallery view (only title)
    <img width="903" height="582" alt="image"
    src="https://github.com/user-attachments/assets/b619d63f-04d0-42f2-9207-de256dc5e481"
    />

    C) Gallery view (no title or subtitle)
    <img width="900" height="583" alt="image"
    src="https://github.com/user-attachments/assets/c48cd1fc-8f51-40c1-8bce-607916e9f742"
    />

    D) Small icons
    <img width="907" height="582" alt="image"
    src="https://github.com/user-attachments/assets/8327da0a-fa45-443f-b52c-f0f1edd7b861"
    />

    E) Medium icons (with labels)
    <img width="914" height="588" alt="image"
    src="https://github.com/user-attachments/assets/dee9fab1-54e8-45f8-96d7-502b121a6ac2"
    />

    F) Medium icons (no labels)
    <img width="915" height="588" alt="image"
    src="https://github.com/user-attachments/assets/a32e8af2-6cb1-4106-91db-ca396253c0a3"
    />

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43973
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 1ba5a258e9
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Sun Nov 30 01:59:58 2025 +0100

    CmdPal: Add custom search engine option to Web Search extension (#43941)

    ## Summary of the Pull Request

    This PR allows user to customize a search query in Command Palette's Web
    Search built-in extension. This will also solve a problem with some
    browser that doesn't handle argument in form "? <query>" as it will
    allow user to specify the complete URI.

    - Introduces a new text box in Web Search extension settings for
    specifying a custom search engine URI
    - If the text box is non-empty, the provided URI is used for queries
    - If left empty, the extension defaults to previous behavior, sending
    queries in the format "? query"

    ## Pictures? Pictures!

    <img width="825" height="566" alt="image"
    src="https://github.com/user-attachments/assets/fbf3d3a5-ebfe-4c16-a5f1-0d044b6f9047"
    />

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43940
    - [x] Closes: #42867
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 8aea589b01
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Sun Nov 30 00:36:55 2025 +0100

    CmdPal: Align spellchecker and naming to .NET guidelines (#43974)

    ## Summary of the Pull Request

    - Add command-line parameter value (icf)
    - Unify file and class name casing to match .NET naming conventions (RDP
    -> Rdp as Url, Dns, Xml) -- fixes IRDP spellchecking error
    - Rename IRdpConnectionManager to IRdpConnectionsManager (*s) to match
    the class name

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit afd9d4cc3c
Author: Clint Rutkas <clint@rutkas.com>
Date:   Sat Nov 29 15:11:17 2025 -0800

    Update PowerToys download links to version 0.96.1 (#43965)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit bc0a760aff
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Sat Nov 29 23:23:24 2025 +0100

    CmdPal: Add mini dev center (#43939)

    ## Summary of the Pull Request

    This PR introduces a small ribbon to the CmdPal for app developers. The
    dev ribbon is dynamically added to the main window in local (non-CI)
    builds. It shows the number of logged errors and warnings, the current
    build configuration (Debug or Release), and whether it’s built with AOT.

    The flyout shows the latest errors and warnings and lets you quickly
    access the logs.

    ## Pictures? Pictures!

    <img width="985" height="589" alt="image"
    src="https://github.com/user-attachments/assets/6528b02b-b4b4-4968-91bf-e67a29f86415"
    />

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43318
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 06afe09973
Author: Michael Jolley <mike@baldbeardedbuilder.com>
Date:   Sat Nov 29 13:07:19 2025 -0600

    CmdPal: New Remote Desktop built-in extension (#43090)

    This PR introduces a new built-in extension for Remote Desktop users.

    It allows you to view past RDP connections, save predefined connections,
    and connect to any of them. Or start a new RDP connection.

    https://github.com/user-attachments/assets/6a5041a6-5741-4df0-a305-da7166f962e1

    ### GitHub issue maintenance stuff

    Closes #38305

    ---------

    Co-authored-by: Niels Laute <niels.laute@live.nl>
    Co-authored-by: Jiří Polášek <me@jiripolasek.com>

commit 0de60445ea
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Thu Nov 27 16:31:10 2025 +0100

    CmdPal: Use Shell API to determine the default browser in WebSearch (#43339)

    ## Summary of the Pull Request

    This PR introduces a new method for determining the default browser
    using the Windows Shell API. The new provider selects the browser
    associated with the HTTPS protocol (falling back to HTTP if necessary).
    The original implementation is retained as a fallback for now, and the
    codebase is prepared for future extensions (e.g., manual default-browser
    selection).

    As a flyby, it also fixes an issue where commands continued showing the
    previous browser name if the user changed their default browser while
    the Command Palette was running.

    ## One-liner for change log

    Fixed default browser selection in the Web Search built-in extension.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #42343
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [x] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 47d4a65223
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Thu Nov 27 16:24:47 2025 +0100

    CmdPal: Add option to return to home automatically after a delay (#43551)

    ## Summary of the Pull Request

    This PR replaces the Go home when activated setting with a new
    Automatically return home option. This allows users to specify how long
    the Command Palette should wait after being dismissed before
    automatically returning to the home page. It also introduces migration
    logic to transition from the old setting to the new one.

    ## Pictures? Pictures!

    <img width="1337" height="762" alt="image"
    src="https://github.com/user-attachments/assets/c649ef03-b3ee-40ba-ac67-485bc40efa73"
    />

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43355
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 1b72c0b969
Author: Kai Tao <69313318+vanzue@users.noreply.github.com>
Date:   Thu Nov 27 17:22:59 2025 +0800

    Update check-spelling expect list (#43925)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

    Spell no complain

commit 9160c82fc2
Author: Pratyush Nalam <github@code.pratyushnalam.com>
Date:   Thu Nov 27 05:15:06 2025 +0530

    Update Command Palette's Learn More string to be consistent with other utilities (#43898)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    In the PowerToys "What's new" window, every utility has the text "Learn
    more about <utility name>" next to the "Settings" button. Examples
    below:

    <img width="247" height="38" alt="learnmore-fancyzones"
    src="https://github.com/user-attachments/assets/fecdeb4b-e01c-438d-8d11-c056e613768e"
    />
    <img width="258" height="40" alt="learnmore-textextractor"
    src="https://github.com/user-attachments/assets/ffb0c801-5b89-46d1-b493-b57287303e65"
    />

    The only exception is the Command Palette utility which just says "Learn
    more".

    <img width="152" height="32" alt="learnmore-cmdpal"
    src="https://github.com/user-attachments/assets/232c11cd-b621-46eb-87f1-d3fc708d6286"
    />

    This is an inconsistency and this PR fixes that string.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43897
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 452e0dcf51
Author: Mike Hall <mikehall@microsoft.com>
Date:   Wed Nov 26 14:08:34 2025 +0000

    Module Loader tool for rapid testing of modules (#43813)

    ## Summary of the Pull Request
    ModuleLoader tool, a stand-alone Win32 executable for testing of
    PowerToy modules without needing branch builds.

    sample output from running the tool is below:

    .\ModuleLoader.exe .\powertoys.cursorwrap.dll
    PowerToys Module Loader v1.0
    =============================

    Loading module: .\powertoys.cursorwrap.dll
    Detected module name: cursorwrap

    Loading settings...
    Trying settings path:
    C:\Users\mikehall\AppData\Local\Microsoft\PowerToys\cursorwrap\settings.json
    Settings file loaded (315 characters)
    Settings loaded successfully.

    Loading module DLL...
    Module instance created successfully
    Module DLL loaded successfully.
    Module key: CursorWrap
    Module name: CursorWrap

    Applying settings to module...
    Settings applied.

    Registering module hotkeys...
    Module reports 1 legacy hotkey(s)
      Registering hotkey 0: Win+Alt+U - OK
    Hotkeys registered: 1

    Enabling module...
    Module enabled.

    =============================
    Module is now running!
    =============================

    Module Status:
      - Name: CursorWrap
      - Key: CursorWrap
      - Enabled: Yes
      - Hotkeys: 1 registered

    Registered Hotkeys:
      Win+Alt+U

    Press Ctrl+C to exit.
    You can press the module's hotkey to toggle its functionality.

    Note that this doesn't integrate with Powertoys settings UI - this is
    purely to test Powertoys module functionality.

    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    ## Detailed Description of the Pull Request / Additional comments
    See details above.

    ## Validation Steps Performed
    ModuleLoader tested on Windows 11, Surface Laptop 7 Pro.

commit 2c9a9e9fca
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Mon Nov 24 23:57:10 2025 +0100

    CmdPal: Improve Command Palette behavior in "Last position" mode (#43543)

    ## Summary of the Pull Request

    This PR improves Command Palette behavior in “Last position” mode:
    - Correctly handles DPI changes between monitors.
    - Ensures the window is always visible — if it’s fully off-screen or has
    less than 100px visible on any axis, it is re-centered.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43398
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 09c8c1d79a
Author: leileizhang <leilzh@microsoft.com>
Date:   Mon Nov 24 10:42:35 2025 +0800

    [Hot Fix] Fix Image Resizer not working on Win10 (#43763)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    Windows 10 can’t launch the app using the Sparse Package. Remove the app
    manifest so that Image Resizer can start properly on Windows 10.

    We will figure out how to support Sparse Packages on Windows 10 in the
    next release.
    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43747 #43734 #43722 #43759
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 95c8a83f79
Author: leileizhang <leilzh@microsoft.com>
Date:   Mon Nov 24 10:08:12 2025 +0800

    [Hotfix] Remove the properties in Prompt Execution Settings for OpenAI (#43766)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    Remove the properties in Prompt Execution Settings for OpenAI, as the
    new models may not support them.

    Will try to expose them in the UI so users can add them on their own in
    the next release.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist
    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 2830ea919c
Author: Kai Tao <69313318+vanzue@users.noreply.github.com>
Date:   Mon Nov 24 09:51:27 2025 +0800

    Advanced Paste: Adjust model parameter to make the result longer (#43768)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    Adjust model parameter to make the result longer
    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 725ad21952
Author: Dave Rayment <dave.rayment@gmail.com>
Date:   Mon Nov 24 01:12:54 2025 +0000

    [Awake] Fix issue with timed mode not expiring correctly (#43785)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    Resolves an issue with the timed mode's expiry not completing correctly.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43775
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments
    This was because of my recent change to the timed mode. The `Subscribe`
    method on the `Observable` interval accidentally wired the completion
    logic to the **Error** handler instead of the **Completion** handler
    because of the use of a discard `_` instead of an empty parameter list
    `()`. As a result of the incorrect overload being called, Awake stayed
    in the Timed state despite the timer reaching zero.

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed
    Confirmed that the timed mode times out and exits upon expiry.

commit ebc3a139c5
Author: Erik Anderson <erik.anderson@microsoft.com>
Date:   Fri Nov 21 02:34:34 2025 -0800

    Fix typo in AI settings card description (#43757)

    ## Summary of the Pull Request
    The word "cloud" does not use a vowel sound, so the preceding word
    should be "A" instead of "An".

    ## PR Checklist

    - [X] Closes: #43756
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [X] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    Co-authored-by: Erik Anderson <erikan@ntdev.microsoft.com>

commit 28dba2633e
Author: Jaylyn Barbee <51131738+Jaylyn-Barbee@users.noreply.github.com>
Date:   Thu Nov 20 15:22:40 2025 -0800

    [Light Switch][Dev Docs] Clarify LightSwitchService and LightSwitchStateManager roles (#43748)

    Updated LightSwitch module documentation to clarify the role of
    LightSwitchService and LightSwitchStateManager.

    ---------

    Co-authored-by: Niels Laute <niels.laute@live.nl>

commit 9fbd3de3a2
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Thu Nov 20 16:23:42 2025 +0100

    CmdPal: Add native debugging launch profile to launchSettings.json (#43718)

    ## Summary of the Pull Request

    See title.

    I’m too lazy to open the dialog and then revert the change later.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 4a0d9912ae
Author: Kai Tao <69313318+vanzue@users.noreply.github.com>
Date:   Thu Nov 20 09:57:29 2025 +0800

    Advanced Paste:  No cache for foundry local model list  (#43716)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    Cache of the downloaded model will make the newly added model only work
    after running of powertoys, this disable the cache, so just downloaded
    model will take effect immediately

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed
    Validated locally

commit 15c79a0176
Author: Dave Rayment <dave.rayment@gmail.com>
Date:   Wed Nov 19 08:50:25 2025 +0000

    [Settings] Fix inconsistent description text for the mouse tools (#43651)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    Change some of the mouse utilities' descriptions from declarative to
    imperative, to match best practice and to be consistent with the other
    descriptions.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed
    - Confirmed the changed descriptions were updated in Settings.

commit 97d46efec2
Author: Dave Rayment <dave.rayment@gmail.com>
Date:   Wed Nov 19 08:49:40 2025 +0000

    [Settings] Fix Dashboard toggle glitches and sorting UI (#43626)

    ## Summary of the Pull Request
    Fixes two UI bugs in the Settings Dashboard: module list glitching when
    toggling modules, and incorrect sort menu checkmarks.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43624
    - [x] Closes: #43625
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    ### User-Facing Fixes

    #### 1. Module list glitching when toggling enabled state
    When enabling or disabling a module from the "Utilities" list, the
    entire list would flicker and redraw, causing other toggles to glitch.
    This made it appear as if multiple modules were being affected by a
    single change.

    **Root cause**
    The `AllModules` ObservableCollection was being completely cleared and
    re-populated on every change, forcing the UI to destroy and recreate all
    list items.

    **Fix**
    Refactored collection updates to modify items in-place:
    - Introduced `_moduleItems` master list, built once during
    initialization.
    - `RefreshModuleList()` now updates properties without clearing
    collections
    - `SortModuleList()` uses `ObservableCollection.Move()` instead of
    `Clear()`/`Add()`

    #### 2. Incorrect sort menu checkmark behaviour
    The checkmark in the "Sort by" menu would not update correctly when
    changing sort order, sometimes showing the incorrect item checked, or
    even both at once.

    **Root cause**
    The `IsChecked` prop on the `ToggleMenuFlyoutItem` is bound to
    `DashboardSortOrder`, but the binding was not updating because the
    ViewModel didn't raise a property change notification when the sort
    order was changed.

    **Fix**
    Added `OnPropertyChanged(nameof(DashboardSortOrder))` in
    `SortModuleList()`.

    ### Code quality improvements

    1. Renamed `GetShortcutModules()` to `RefreshShortcutModules()`. The
    original name implied a getter, but the routine actually affects state
    by rebuilding the shortcut and action lists, violating the Command-Query
    Separation principle.
    2. Added an `_isUpdatingFromUI` flag as a defensive measure against
    circular updates when a UI toggle is changed.
    3. Separation of concerns for operations on the modules list. Building,
    sorting and refreshing it are separated.
    4. Added comments and XML doc headers for new methods. Included brief
    description of GPO locking behaviour.

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed
    - Verified that toggling modules in the list no longer causes the list
    to flicker or for other toggles to glitch.
    - Confirmed that the sort order checkmarks update correctly and reflect
    the current sort order.
    - Tested GPO policy settings are still queried as before.
    - Checked sort behaviour is unaffected.

    ## Videos

    *Sorting UI*

    https://github.com/user-attachments/assets/3484bf63-2946-4460-83a5-361fa7e41c82

    *Toggle behaviour*

    https://github.com/user-attachments/assets/1fae5429-6fa3-4431-80f3-0907dab4f326

    ---------

    Co-authored-by: Gordon Lam (SH) <yeelam@microsoft.com>

commit 46242b384e
Author: Kai Tao <69313318+vanzue@users.noreply.github.com>
Date:   Wed Nov 19 16:25:52 2025 +0800

    96 release change log (#43330)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

    ---------

    Signed-off-by: Shawn Yuan (from Dev Box) <shuaiyuan@microsoft.com>
    Signed-off-by: Shawn Yuan <shuai.yuan.zju@gmail.com>
    Co-authored-by: Jiří Polášek <me@jiripolasek.com>
    Co-authored-by: Jaylyn Barbee <51131738+Jaylyn-Barbee@users.noreply.github.com>
    Co-authored-by: Jeremy Sinclair <4016293+snickler@users.noreply.github.com>
    Co-authored-by: leileizhang <leilzh@microsoft.com>
    Co-authored-by: Shawn Yuan <128874481+shuaiyuanxx@users.noreply.github.com>
    Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
    Co-authored-by: niels9001 <9866362+niels9001@users.noreply.github.com>
    Co-authored-by: Niels Laute <niels.laute@live.nl>
    Co-authored-by: Dave Rayment <dave.rayment@gmail.com>
    Co-authored-by: Gleb Khmyznikov <gleb.khmyznikov@gmail.com>
    Co-authored-by: Gordon Lam (SH) <yeelam@microsoft.com>
    Co-authored-by: Juju Anselum J <106316316+anselumjuju@users.noreply.github.com>
    Co-authored-by: Dustin L. Howett <duhowett@microsoft.com>
    Co-authored-by: Leon Zandman <leon@wirwar.com>
    Co-authored-by: Leon Zandman <lzandman@rdw.nl>
    Co-authored-by: moooyo <42196638+moooyo@users.noreply.github.com>
    Co-authored-by: Yu Leng <yuleng@microsoft.com>
    Co-authored-by: Mike Griese <migrie@microsoft.com>
    Co-authored-by: Michael Jolley <mike@baldbeardedbuilder.com>
    Co-authored-by: Mario Hewardt <marioh@microsoft.com>
    Co-authored-by: Alex Mihaiuc <69110671+foxmsft@users.noreply.github.com>
    Co-authored-by: Mike Hall <mikehall@microsoft.com>
    Co-authored-by: Trevor <ngo.trev.95@gmail.com>

commit 84be261581
Author: Niels Laute <niels.laute@live.nl>
Date:   Tue Nov 18 19:19:38 2025 -0800

    Logo change for Azure Inference (#43686)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 5a8095b704
Author: Niels Laute <niels.laute@live.nl>
Date:   Tue Nov 18 18:32:14 2025 -0800

    Loc bug (#43685)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 417c1a6b98
Author: Niels Laute <niels.laute@live.nl>
Date:   Tue Nov 18 16:21:14 2025 -0800

    Update FoundryLocal.svg (#43682)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 2593149d22
Author: leileizhang <leilzh@microsoft.com>
Date:   Tue Nov 18 14:22:03 2025 +0800

    Fix OOBE Mouse Utilities crash by correcting localization key (#43664)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    - The OOBE Mouse Utilities page crashed when selected because the
    TextBlock with x:Uid="Oobe_MouseUtils_MousePointerCrosshairs" tried to
    bind a Description property that doesn’t exist.
    - Updated Resources.resw so the string entry is named
    Oobe_MouseUtils_MousePointerCrosshairs_Description.Text, matching the
    markdown description control instead of the TextBlock.
    - With the correct resource key, the XAML loader no longer resolves an
    invalid property and navigation succeeds.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes:  #43663
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 0b50c38fe1
Author: Kai Tao <69313318+vanzue@users.noreply.github.com>
Date:   Tue Nov 18 12:59:52 2025 +0800

    Advanced Paste: Refresh environment if foundry is not present (#43662)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    As title
    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

    [12:55:29.6763496] [Info] FoundryClient.cs::CreateAsync::23
        [FoundryClient] First attempt failed, refreshing PATH and retrying
    [12:55:29.6766491] [Info] FoundryClient.cs::RefreshEnvironmentPath::225
        [FoundryClient] Refreshing PATH environment variable from system
    [12:55:29.6768710] [Info] FoundryClient.cs::RefreshEnvironmentPath::266
        [FoundryClient] Updating process PATH with latest system values
    [12:55:29.6769080] [Info] FoundryClient.cs::TryCreateClientAsync::33
        [FoundryClient] Creating Foundry Local client
    [12:55:29.6769312] [Info] FoundryClient.cs::TryCreateClientAsync::45
    [FoundryClient] Starting Foundry service using
    manager.StartServiceAsync()
    [12:55:29.9807668] [Info] FoundryClient.cs::TryCreateClientAsync::48
        [FoundryClient] Foundry service started successfully

    Verified, fist launch successfully

commit 840808b465
Author: Niels Laute <niels.laute@live.nl>
Date:   Tue Nov 18 03:28:40 2025 +0100

    [AP] Adding a single scrollviewer and fixing hidden tabstop (#43660)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43655
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit b50df36b70
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Tue Nov 18 03:00:37 2025 +0100

    Setup: Hide apps in PowerToys.SpareApps package from Start Menu (#43650)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    This PR updates the Appx manifest for PowerToys.SpareApps to hide the
    apps from the Start Menu, as they lack proper visual elements like icons
    and text.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [x] Closes: #43647
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit b94593ef73
Author: Jiří Polášek <me@jiripolasek.com>
Date:   Tue Nov 18 00:55:14 2025 +0100

    Settings: Add ScrollViewer to Command Palette page in PowerToys Settings (#43649)

commit 7a01d56179
Author: Mario Hewardt <marioh@microsoft.com>
Date:   Mon Nov 17 07:26:42 2025 -0800

    Updates version for standalone release (#43645)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    Updates the version for standalone release

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 130e9a0a68
Author: Kai Tao <69313318+vanzue@users.noreply.github.com>
Date:   Mon Nov 17 12:55:22 2025 +0800

    cmdpal: Fix launch by button in settings not work (#43634)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    Shell does not know it's a protocol, so add protocol to it.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed
    Locally verified

commit 34c37f2d38
Author: Kai Tao <69313318+vanzue@users.noreply.github.com>
Date:   Mon Nov 17 09:48:32 2025 +0800

    Add not signed dll (#43631)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    This dll is not signed, will fail the pipeline

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 47aed03c03
Author: Niels Laute <niels.laute@live.nl>
Date:   Sun Nov 16 15:13:40 2025 +0100

    [AP] Loc fix (#43617)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 6423c7693d
Author: Niels Laute <niels.laute@live.nl>
Date:   Sun Nov 16 15:02:38 2025 +0100

    [CmdPal] Settings page refresh (#43487)

    - Refreshed the CmdPal page.
    - CmdPal can now also be activated from this page by clicking a button
    - Added a Preview InfoBar for FL in AP

    <img width="1384" height="1067" alt="image"
    src="https://github.com/user-attachments/assets/f670e13b-5b4a-4f6a-bcb0-e1dc357afb1e"
    />

    ## Summary of the Pull Request

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

    ---------

    Co-authored-by: vanzue <vanzue@outlook.com>

commit 3e14d50f65
Author: Kai Tao <69313318+vanzue@users.noreply.github.com>
Date:   Sun Nov 16 15:26:05 2025 +0800

    Advanced paste: Add more error handle for foundry local (#43600)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    Foundry local sdk will not run models that is not in catalog, when
    catalog removes some, the old ones will fail executing,
    so add error hint for users to re-configure the models in settings.

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed
    <img width="864" height="216" alt="image"
    src="https://github.com/user-attachments/assets/654207b3-ff50-4888-a638-82136216de7b"
    />

commit db7c9e180e
Author: Jaylyn Barbee <51131738+Jaylyn-Barbee@users.noreply.github.com>
Date:   Sat Nov 15 08:08:20 2025 -0500

    [Light Switch] Removed logs from every tick, only logging key events. (#43572)

    Title

commit bcc3ded280
Author: Michael Jolley <mike@baldbeardedbuilder.com>
Date:   Sat Nov 15 07:07:52 2025 -0600

    CmdPal: Adding page Id to OpenPage telemetry event (#43584)

    @niels9001 requested this.

    As the name says

commit 24a3cdd486
Author: Mario Hewardt <marioh@microsoft.com>
Date:   Fri Nov 14 17:36:31 2025 -0800

    Fixes regressions introduced with GIF support (#43589)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Fixes regressions introduced with GIF support:
    - Switches default recording format back to MP4
    - Fixes framerate issues between the two formats
    - Fixes file path names

    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [x ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments
    - Switches default recording format back to MP4
    - Fixes framerate issues between the two formats
    - Fixes file path names
    -
    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed
    Manual testing

commit 1884e6abc1
Author: Shawn Yuan <128874481+shuaiyuanxx@users.noreply.github.com>
Date:   Fri Nov 14 16:56:23 2025 +0800

    Remove unused properties in AP (#43564)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    This pull request removes legacy provider configuration migration logic
    and associated data structures from the Advanced Paste AI provider
    settings. The changes simplify the codebase by eliminating support for
    legacy provider configuration snapshots and related migration methods,
    focusing configuration management on the current provider model.

    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

    ---------

    Signed-off-by: Shawn Yuan (from Dev Box) <shuaiyuan@microsoft.com>

commit ad4b553bb1
Author: leileizhang <leilzh@microsoft.com>
Date:   Fri Nov 14 16:15:15 2025 +0800

    Remove all AdvancedPaste stored keys during uninstall (#43563)

    <!-- Enter a brief description/summary of your PR here. What does it
    fix/what does it change/how was it tested (even manually, if necessary)?
    -->
    ## Summary of the Pull Request
    Remove all AdvancedPaste stored keys during uninstall
    <!-- Please review the items on the PR checklist before submitting-->
    ## PR Checklist

    - [ ] Closes: #xxx
    <!-- - [ ] Closes: #yyy (add separate lines for additional resolved
    issues) -->
    - [ ] **Communication:** I've discussed this with core contributors
    already. If the work hasn't been agreed, this work might be rejected
    - [ ] **Tests:** Added/updated and all pass
    - [ ] **Localization:** All end-user-facing strings can be localized
    - [ ] **Dev docs:** Added/updated
    - [ ] **New binaries:** Added on the required places
    - [ ] [JSON for
    signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
    for new binaries
    - [ ] [WXS for
    installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
    for new binaries and localization folder
    - [ ] [YML for CI
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
    for new test projects
    - [ ] [YML for signed
    pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
    - [ ] **Documentation updated:** If checked, please file a pull request
    on [our docs
    repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys)
    and link it here: #xxx

    <!-- Provide a more detailed description of the PR, other things fixed,
    or any additional comments/features here -->
    ## Detailed Description of the Pull Request / Additional comments

    <!-- Describe how you validated the behavior. Add automated tests
    wherever possible, but list manual validation steps taken as well -->
    ## Validation Steps Performed

commit 193d9aacbe
Author: Dustin L. Howett <duhowett@microsoft.com>
Date:   Thu Nov 13 17:59:21 2025 -0600

    BugReportTool: replace cziplib with tar.exe (#41127)

    BugReportTool is the last consumer in the PowerToys repo of cziplib, a
    library we use to produce ZIP files.

    This pull request replaces cziplib with a simple CreateProcess call that
    spawns `tar.exe`, which comes with Windows as of RS4 and can produce ZIP
    files!

    I've tested this by producing a bug report archive and attempting to
    open it with File Explorer. It works fine.

    We have taken every precaution to ensure that we do not allow any
    attacker-controlled input to tar's command line. We are *not* using
    `system()`, and we are not opening up a vector through which a nefarious
    caller can perform shell injection.

    We do not pass filenames to tar except that of the final archive. We do
    not pass directory names to tar; we rely on the current directory
    instead.
2025-12-08 18:41:48 -08:00

76 KiB

NOTICES AND INFORMATION

This software incorporates material from third parties.

  • Color Picker
  • Command Palette
  • File Explorer Add-ins
  • ImageResizer
  • PowerToys Run
  • Installer/Runner
  • Measure tool
  • Peek
  • Registry Preview

Utility: Color Picker

Martin Chrzan's Color Picker

Source: https://github.com/martinchrzan/ColorPicker

MIT License

Copyright (c) 2020 martinchrzan

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Utility: Command Palette

wyhash

We use the WyHash NuGet package for calculating stable hashes for strings.

Source: https://github.com/wangyi-fudan/wyhash

This is free and unencumbered software released into the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or
distribute this software, either in source code form or as a compiled
binary, for any purpose, commercial or non-commercial, and by any
means.

In jurisdictions that recognize copyright laws, the author or authors
of this software dedicate any and all copyright interest in the
software to the public domain. We make this dedication for the benefit
of the public at large and to the detriment of our heirs and
successors. We intend this dedication to be an overt act of
relinquishment in perpetuity of all present and future rights to this
software under copyright law.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.

For more information, please refer to <http://unlicense.org/>

ToolGood.Words.Pinyin

We use the ToolGood.Words.Pinyin NuGet package for converting Chinese characters to pinyin.

Source: https://github.com/toolgood/ToolGood.Words.Pinyin

MIT License

Copyright (c) 2020 ToolGood

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Utility: Command Palette Built-in Extensions

Calculator

exprtk

We use the exprtk library (exprtk.hpp) to evaluate mathematical expressions.

Source: https://github.com/ArashPartow/exprtk

MIT License

Copyright (c) 1999-2024 Arash Partow

https://www.partow.net/programming/exprtk/index.html

Permission is hereby granted, free of charge, to any person  obtaining
a  copy  of  this software  and  associated  documentation files  (the
"Software"), to  deal in  the Software  without restriction, including
without limitation the  rights to use,  copy, modify, merge,  publish,
distribute, sublicense,  and/or sell  copies of  the Software,  and to
permit persons to whom the Software is furnished to do so, subject  to
the following conditions:

The  above  copyright  notice  and  this  permission  notice  shall be
included in all copies or substantial portions of the Software.

THE  SOFTWARE  IS PROVIDED  "AS  IS", WITHOUT  WARRANTY  OF ANY  KIND,
EXPRESS OR  IMPLIED, INCLUDING  BUT NOT  LIMITED TO  THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS  OR COPYRIGHT HOLDERS BE LIABLE FOR  ANY
CLAIM, DAMAGES OR OTHER LIABILITY,  WHETHER IN AN ACTION OF  CONTRACT,
TORT OR  OTHERWISE, ARISING  FROM, OUT  OF OR  IN CONNECTION  WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Utility: PowerToys Run Built-in Extensions

Calculator

Mages

We use the Mages NuGet package for calculating the result of expression.

Source: https://github.com/FlorianRappl/Mages

The MIT License (MIT)

Copyright (c) 2016 - 2025 Florian Rappl

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Utility: File Explorer Add-ins

Monaco Editor

Source: https://github.com/Microsoft/monaco-editor

Additional third party notifications: https://github.com/microsoft/monaco-editor/blob/main/ThirdPartyNotices.txt

The MIT License (MIT)

Copyright (c) 2016 - present Microsoft Corporation

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

The Quite OK Image Format reference decoder

Source: https://github.com/phoboslab/qoi

Note: @pedrolamas translated and adapted the reference decoder code to C# that is in PowerToys from the original C++ implementation.

MIT License

Copyright (c) 2022 Dominic Szablewski

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

UTF Unknown

We use the UTF.Unknown NuGet package for detecting encoding in text/code files.

Source: https://github.com/CharsetDetector/UTF-unknown

                          MOZILLA PUBLIC LICENSE
                                Version 1.1

                              ---------------

1. Definitions.

     1.0.1. "Commercial Use" means distribution or otherwise making the
     Covered Code available to a third party.

     1.1. "Contributor" means each entity that creates or contributes to
     the creation of Modifications.

     1.2. "Contributor Version" means the combination of the Original
     Code, prior Modifications used by a Contributor, and the Modifications
     made by that particular Contributor.

     1.3. "Covered Code" means the Original Code or Modifications or the
     combination of the Original Code and Modifications, in each case
     including portions thereof.

     1.4. "Electronic Distribution Mechanism" means a mechanism generally
     accepted in the software development community for the electronic
     transfer of data.

     1.5. "Executable" means Covered Code in any form other than Source
     Code.

     1.6. "Initial Developer" means the individual or entity identified
     as the Initial Developer in the Source Code notice required by Exhibit
     A.

     1.7. "Larger Work" means a work which combines Covered Code or
     portions thereof with code not governed by the terms of this License.

     1.8. "License" means this document.

     1.8.1. "Licensable" means having the right to grant, to the maximum
     extent possible, whether at the time of the initial grant or
     subsequently acquired, any and all of the rights conveyed herein.

     1.9. "Modifications" means any addition to or deletion from the
     substance or structure of either the Original Code or any previous
     Modifications. When Covered Code is released as a series of files, a
     Modification is:
          A. Any addition to or deletion from the contents of a file
          containing Original Code or previous Modifications.

          B. Any new file that contains any part of the Original Code or
          previous Modifications.

     1.10. "Original Code" means Source Code of computer software code
     which is described in the Source Code notice required by Exhibit A as
     Original Code, and which, at the time of its release under this
     License is not already Covered Code governed by this License.

     1.10.1. "Patent Claims" means any patent claim(s), now owned or
     hereafter acquired, including without limitation,  method, process,
     and apparatus claims, in any patent Licensable by grantor.

     1.11. "Source Code" means the preferred form of the Covered Code for
     making modifications to it, including all modules it contains, plus
     any associated interface definition files, scripts used to control
     compilation and installation of an Executable, or source code
     differential comparisons against either the Original Code or another
     well known, available Covered Code of the Contributor's choice. The
     Source Code can be in a compressed or archival form, provided the
     appropriate decompression or de-archiving software is widely available
     for no charge.

     1.12. "You" (or "Your")  means an individual or a legal entity
     exercising rights under, and complying with all of the terms of, this
     License or a future version of this License issued under Section 6.1.
     For legal entities, "You" includes any entity which controls, is
     controlled by, or is under common control with You. For purposes of
     this definition, "control" means (a) the power, direct or indirect,
     to cause the direction or management of such entity, whether by
     contract or otherwise, or (b) ownership of more than fifty percent
     (50%) of the outstanding shares or beneficial ownership of such
     entity.

2. Source Code License.

     2.1. The Initial Developer Grant.
     The Initial Developer hereby grants You a world-wide, royalty-free,
     non-exclusive license, subject to third party intellectual property
     claims:
          (a)  under intellectual property rights (other than patent or
          trademark) Licensable by Initial Developer to use, reproduce,
          modify, display, perform, sublicense and distribute the Original
          Code (or portions thereof) with or without Modifications, and/or
          as part of a Larger Work; and

          (b) under Patents Claims infringed by the making, using or
          selling of Original Code, to make, have made, use, practice,
          sell, and offer for sale, and/or otherwise dispose of the
          Original Code (or portions thereof).

          (c) the licenses granted in this Section 2.1(a) and (b) are
          effective on the date Initial Developer first distributes
          Original Code under the terms of this License.

          (d) Notwithstanding Section 2.1(b) above, no patent license is
          granted: 1) for code that You delete from the Original Code; 2)
          separate from the Original Code;  or 3) for infringements caused
          by: i) the modification of the Original Code or ii) the
          combination of the Original Code with other software or devices.

     2.2. Contributor Grant.
     Subject to third party intellectual property claims, each Contributor
     hereby grants You a world-wide, royalty-free, non-exclusive license

          (a)  under intellectual property rights (other than patent or
          trademark) Licensable by Contributor, to use, reproduce, modify,
          display, perform, sublicense and distribute the Modifications
          created by such Contributor (or portions thereof) either on an
          unmodified basis, with other Modifications, as Covered Code
          and/or as part of a Larger Work; and

          (b) under Patent Claims infringed by the making, using, or
          selling of  Modifications made by that Contributor either alone
          and/or in combination with its Contributor Version (or portions
          of such combination), to make, use, sell, offer for sale, have
          made, and/or otherwise dispose of: 1) Modifications made by that
          Contributor (or portions thereof); and 2) the combination of
          Modifications made by that Contributor with its Contributor
          Version (or portions of such combination).

          (c) the licenses granted in Sections 2.2(a) and 2.2(b) are
          effective on the date Contributor first makes Commercial Use of
          the Covered Code.

          (d)    Notwithstanding Section 2.2(b) above, no patent license is
          granted: 1) for any code that Contributor has deleted from the
          Contributor Version; 2)  separate from the Contributor Version;
          3)  for infringements caused by: i) third party modifications of
          Contributor Version or ii)  the combination of Modifications made
          by that Contributor with other software  (except as part of the
          Contributor Version) or other devices; or 4) under Patent Claims
          infringed by Covered Code in the absence of Modifications made by
          that Contributor.

3. Distribution Obligations.

     3.1. Application of License.
     The Modifications which You create or to which You contribute are
     governed by the terms of this License, including without limitation
     Section 2.2. The Source Code version of Covered Code may be
     distributed only under the terms of this License or a future version
     of this License released under Section 6.1, and You must include a
     copy of this License with every copy of the Source Code You
     distribute. You may not offer or impose any terms on any Source Code
     version that alters or restricts the applicable version of this
     License or the recipients' rights hereunder. However, You may include
     an additional document offering the additional rights described in
     Section 3.5.

     3.2. Availability of Source Code.
     Any Modification which You create or to which You contribute must be
     made available in Source Code form under the terms of this License
     either on the same media as an Executable version or via an accepted
     Electronic Distribution Mechanism to anyone to whom you made an
     Executable version available; and if made available via Electronic
     Distribution Mechanism, must remain available for at least twelve (12)
     months after the date it initially became available, or at least six
     (6) months after a subsequent version of that particular Modification
     has been made available to such recipients. You are responsible for
     ensuring that the Source Code version remains available even if the
     Electronic Distribution Mechanism is maintained by a third party.

     3.3. Description of Modifications.
     You must cause all Covered Code to which You contribute to contain a
     file documenting the changes You made to create that Covered Code and
     the date of any change. You must include a prominent statement that
     the Modification is derived, directly or indirectly, from Original
     Code provided by the Initial Developer and including the name of the
     Initial Developer in (a) the Source Code, and (b) in any notice in an
     Executable version or related documentation in which You describe the
     origin or ownership of the Covered Code.

     3.4. Intellectual Property Matters
          (a) Third Party Claims.
          If Contributor has knowledge that a license under a third party's
          intellectual property rights is required to exercise the rights
          granted by such Contributor under Sections 2.1 or 2.2,
          Contributor must include a text file with the Source Code
          distribution titled "LEGAL" which describes the claim and the
          party making the claim in sufficient detail that a recipient will
          know whom to contact. If Contributor obtains such knowledge after
          the Modification is made available as described in Section 3.2,
          Contributor shall promptly modify the LEGAL file in all copies
          Contributor makes available thereafter and shall take other steps
          (such as notifying appropriate mailing lists or newsgroups)
          reasonably calculated to inform those who received the Covered
          Code that new knowledge has been obtained.

          (b) Contributor APIs.
          If Contributor's Modifications include an application programming
          interface and Contributor has knowledge of patent licenses which
          are reasonably necessary to implement that API, Contributor must
          also include this information in the LEGAL file.

               (c)    Representations.
          Contributor represents that, except as disclosed pursuant to
          Section 3.4(a) above, Contributor believes that Contributor's
          Modifications are Contributor's original creation(s) and/or
          Contributor has sufficient rights to grant the rights conveyed by
          this License.

     3.5. Required Notices.
     You must duplicate the notice in Exhibit A in each file of the Source
     Code.  If it is not possible to put such notice in a particular Source
     Code file due to its structure, then You must include such notice in a
     location (such as a relevant directory) where a user would be likely
     to look for such a notice.  If You created one or more Modification(s)
     You may add your name as a Contributor to the notice described in
     Exhibit A.  You must also duplicate this License in any documentation
     for the Source Code where You describe recipients' rights or ownership
     rights relating to Covered Code.  You may choose to offer, and to
     charge a fee for, warranty, support, indemnity or liability
     obligations to one or more recipients of Covered Code. However, You
     may do so only on Your own behalf, and not on behalf of the Initial
     Developer or any Contributor. You must make it absolutely clear than
     any such warranty, support, indemnity or liability obligation is
     offered by You alone, and You hereby agree to indemnify the Initial
     Developer and every Contributor for any liability incurred by the
     Initial Developer or such Contributor as a result of warranty,
     support, indemnity or liability terms You offer.

     3.6. Distribution of Executable Versions.
     You may distribute Covered Code in Executable form only if the
     requirements of Section 3.1-3.5 have been met for that Covered Code,
     and if You include a notice stating that the Source Code version of
     the Covered Code is available under the terms of this License,
     including a description of how and where You have fulfilled the
     obligations of Section 3.2. The notice must be conspicuously included
     in any notice in an Executable version, related documentation or
     collateral in which You describe recipients' rights relating to the
     Covered Code. You may distribute the Executable version of Covered
     Code or ownership rights under a license of Your choice, which may
     contain terms different from this License, provided that You are in
     compliance with the terms of this License and that the license for the
     Executable version does not attempt to limit or alter the recipient's
     rights in the Source Code version from the rights set forth in this
     License. If You distribute the Executable version under a different
     license You must make it absolutely clear that any terms which differ
     from this License are offered by You alone, not by the Initial
     Developer or any Contributor. You hereby agree to indemnify the
     Initial Developer and every Contributor for any liability incurred by
     the Initial Developer or such Contributor as a result of any such
     terms You offer.

     3.7. Larger Works.
     You may create a Larger Work by combining Covered Code with other code
     not governed by the terms of this License and distribute the Larger
     Work as a single product. In such a case, You must make sure the
     requirements of this License are fulfilled for the Covered Code.

4. Inability to Comply Due to Statute or Regulation.

     If it is impossible for You to comply with any of the terms of this
     License with respect to some or all of the Covered Code due to
     statute, judicial order, or regulation then You must: (a) comply with
     the terms of this License to the maximum extent possible; and (b)
     describe the limitations and the code they affect. Such description
     must be included in the LEGAL file described in Section 3.4 and must
     be included with all distributions of the Source Code. Except to the
     extent prohibited by statute or regulation, such description must be
     sufficiently detailed for a recipient of ordinary skill to be able to
     understand it.

5. Application of this License.

     This License applies to code to which the Initial Developer has
     attached the notice in Exhibit A and to related Covered Code.

6. Versions of the License.

     6.1. New Versions.
     Netscape Communications Corporation ("Netscape") may publish revised
     and/or new versions of the License from time to time. Each version
     will be given a distinguishing version number.

     6.2. Effect of New Versions.
     Once Covered Code has been published under a particular version of the
     License, You may always continue to use it under the terms of that
     version. You may also choose to use such Covered Code under the terms
     of any subsequent version of the License published by Netscape. No one
     other than Netscape has the right to modify the terms applicable to
     Covered Code created under this License.

     6.3. Derivative Works.
     If You create or use a modified version of this License (which you may
     only do in order to apply it to code which is not already Covered Code
     governed by this License), You must (a) rename Your license so that
     the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape",
     "MPL", "NPL" or any confusingly similar phrase do not appear in your
     license (except to note that your license differs from this License)
     and (b) otherwise make it clear that Your version of the license
     contains terms which differ from the Mozilla Public License and
     Netscape Public License. (Filling in the name of the Initial
     Developer, Original Code or Contributor in the notice described in
     Exhibit A shall not of themselves be deemed to be modifications of
     this License.)

7. DISCLAIMER OF WARRANTY.

     COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS,
     WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
     WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF
     DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING.
     THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE
     IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT,
     YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE
     COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER
     OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF
     ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

8. TERMINATION.

     8.1.  This License and the rights granted hereunder will terminate
     automatically if You fail to comply with terms herein and fail to cure
     such breach within 30 days of becoming aware of the breach. All
     sublicenses to the Covered Code which are properly granted shall
     survive any termination of this License. Provisions which, by their
     nature, must remain in effect beyond the termination of this License
     shall survive.

     8.2.  If You initiate litigation by asserting a patent infringement
     claim (excluding declatory judgment actions) against Initial Developer
     or a Contributor (the Initial Developer or Contributor against whom
     You file such action is referred to as "Participant")  alleging that:

     (a)  such Participant's Contributor Version directly or indirectly
     infringes any patent, then any and all rights granted by such
     Participant to You under Sections 2.1 and/or 2.2 of this License
     shall, upon 60 days notice from Participant terminate prospectively,
     unless if within 60 days after receipt of notice You either: (i)
     agree in writing to pay Participant a mutually agreeable reasonable
     royalty for Your past and future use of Modifications made by such
     Participant, or (ii) withdraw Your litigation claim with respect to
     the Contributor Version against such Participant.  If within 60 days
     of notice, a reasonable royalty and payment arrangement are not
     mutually agreed upon in writing by the parties or the litigation claim
     is not withdrawn, the rights granted by Participant to You under
     Sections 2.1 and/or 2.2 automatically terminate at the expiration of
     the 60 day notice period specified above.

     (b)  any software, hardware, or device, other than such Participant's
     Contributor Version, directly or indirectly infringes any patent, then
     any rights granted to You by such Participant under Sections 2.1(b)
     and 2.2(b) are revoked effective as of the date You first made, used,
     sold, distributed, or had made, Modifications made by that
     Participant.

     8.3.  If You assert a patent infringement claim against Participant
     alleging that such Participant's Contributor Version directly or
     indirectly infringes any patent where such claim is resolved (such as
     by license or settlement) prior to the initiation of patent
     infringement litigation, then the reasonable value of the licenses
     granted by such Participant under Sections 2.1 or 2.2 shall be taken
     into account in determining the amount or value of any payment or
     license.

     8.4.  In the event of termination under Sections 8.1 or 8.2 above,
     all end user license agreements (excluding distributors and resellers)
     which have been validly granted by You or any distributor hereunder
     prior to termination shall survive termination.

9. LIMITATION OF LIABILITY.

     UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
     (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL
     DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE,
     OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR
     ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
     CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL,
     WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER
     COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN
     INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF
     LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY
     RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
     PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
     EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO
     THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.

10. U.S. GOVERNMENT END USERS.

     The Covered Code is a "commercial item," as that term is defined in
     48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer
     software" and "commercial computer software documentation," as such
     terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48
     C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995),
     all U.S. Government End Users acquire Covered Code with only those
     rights set forth herein.

11. MISCELLANEOUS.

     This License represents the complete agreement concerning subject
     matter hereof. If any provision of this License is held to be
     unenforceable, such provision shall be reformed only to the extent
     necessary to make it enforceable. This License shall be governed by
     California law provisions (except to the extent applicable law, if
     any, provides otherwise), excluding its conflict-of-law provisions.
     With respect to disputes in which at least one party is a citizen of,
     or an entity chartered or registered to do business in the United
     States of America, any litigation relating to this License shall be
     subject to the jurisdiction of the Federal Courts of the Northern
     District of California, with venue lying in Santa Clara County,
     California, with the losing party responsible for costs, including
     without limitation, court costs and reasonable attorneys' fees and
     expenses. The application of the United Nations Convention on
     Contracts for the International Sale of Goods is expressly excluded.
     Any law or regulation which provides that the language of a contract
     shall be construed against the drafter shall not apply to this
     License.

12. RESPONSIBILITY FOR CLAIMS.

     As between Initial Developer and the Contributors, each party is
     responsible for claims and damages arising, directly or indirectly,
     out of its utilization of rights under this License and You agree to
     work with Initial Developer and Contributors to distribute such
     responsibility on an equitable basis. Nothing herein is intended or
     shall be deemed to constitute any admission of liability.

13. MULTIPLE-LICENSED CODE.

     Initial Developer may designate portions of the Covered Code as
     "Multiple-Licensed".  "Multiple-Licensed" means that the Initial
     Developer permits you to utilize portions of the Covered Code under
     Your choice of the NPL or the alternative licenses, if any, specified
     by the Initial Developer in the file described in Exhibit A.

EXHIBIT A -Mozilla Public License.

     The contents of this file are subject to the Mozilla Public License
     Version 1.1 (the "License"); you may not use this file except in
     compliance with the License. You may obtain a copy of the License at
     http://www.mozilla.org/MPL/

     Software distributed under the License is distributed on an "AS IS"
     basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
     License for the specific language governing rights and limitations
     under the License.

     The Original Code is ______________________________________.

     The Initial Developer of the Original Code is ________________________.
     Portions created by ______________________ are Copyright (C) ______
     _______________________. All Rights Reserved.

     Contributor(s): ______________________________________.

     Alternatively, the contents of this file may be used under the terms
     of the _____ license (the  "[___] License"), in which case the
     provisions of [______] License are applicable instead of those
     above.  If you wish to allow use of your version of this file only
     under the terms of the [____] License and not to allow others to use
     your version of this file under the MPL, indicate your decision by
     deleting  the provisions above and replace  them with the notice and
     other provisions required by the [___] License.  If you do not delete
     the provisions above, a recipient may use your version of this file
     under either the MPL or the [___] License."

     [NOTE: The text of this Exhibit A may differ slightly from the text of
     the notices in the Source Code files of the Original Code. You should
     use the text of this Exhibit A rather than the text found in the
     Original Code Source Code for Your Modifications.]

Utility: ImageResizer

Brice Lams's Image Resizer License

Source: https://github.com/bricelam/ImageResizer/

The MIT License (MIT)

Copyright (c) Brice Lambson. All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Utility: PowerToys Run

Wox License

Fork project source: https://github.com/jjw24/Wox/ Base project source: https://github.com/Wox-launcher/Wox

The MIT License (MIT)

Copyright (c) 2015 Wox

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Beta Tadele's Window Walker License

Source: https://github.com/betsegaw/windowwalker

The MIT License (MIT)

Copyright 2020 Betsegaw Tadele

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Utility: PowerRename

Chris Davis's SmartRename License

Source: https://github.com/chrdavis/SmartRename

MIT License

Copyright (c) 2017 Chris Davis

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

PowerToy: Installer/Runner

spdlog

Source: https://github.com/gabime/spdlog

The MIT License (MIT)

Copyright (c) 2016 Gabi Melman.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

-- NOTE: Third party dependency used by this software -- This software depends on the fmt lib (MIT License), and users must comply to its license: https://github.com/fmtlib/fmt/blob/master/LICENSE.rst

expected-lite

Source: https://github.com/martinmoene/expected-lite

Boost Software License - Version 1.0 - August 17th, 2003

Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:

The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

zip

Source: https://github.com/kuba--/zip

All Rights Reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Utility: Measure tool

sse2neon

We adopted some functions from it.

Source: https://github.com/DLTcollab/sse2neon

sse2neon is freely redistributable under the MIT License. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Utility: Peek

Monaco Editor

Source: https://github.com/Microsoft/monaco-editor

Additional third party notifications: https://github.com/microsoft/monaco-editor/blob/main/ThirdPartyNotices.txt

The MIT License (MIT)

Copyright (c) 2016 - present Microsoft Corporation

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

The Quite OK Image Format reference decoder

Source: https://github.com/phoboslab/qoi

Note: @pedrolamas translated and adapted the reference decoder code to C# that is in PowerToys from the original C++ implementation.

MIT License

Copyright (c) 2022 Dominic Szablewski

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

UTF Unknown

We use the UTF.Unknown NuGet package for detecting encoding in text/code files.

Source: https://github.com/CharsetDetector/UTF-unknown

                          MOZILLA PUBLIC LICENSE
                                Version 1.1

                              ---------------

1. Definitions.

     1.0.1. "Commercial Use" means distribution or otherwise making the
     Covered Code available to a third party.

     1.1. "Contributor" means each entity that creates or contributes to
     the creation of Modifications.

     1.2. "Contributor Version" means the combination of the Original
     Code, prior Modifications used by a Contributor, and the Modifications
     made by that particular Contributor.

     1.3. "Covered Code" means the Original Code or Modifications or the
     combination of the Original Code and Modifications, in each case
     including portions thereof.

     1.4. "Electronic Distribution Mechanism" means a mechanism generally
     accepted in the software development community for the electronic
     transfer of data.

     1.5. "Executable" means Covered Code in any form other than Source
     Code.

     1.6. "Initial Developer" means the individual or entity identified
     as the Initial Developer in the Source Code notice required by Exhibit
     A.

     1.7. "Larger Work" means a work which combines Covered Code or
     portions thereof with code not governed by the terms of this License.

     1.8. "License" means this document.

     1.8.1. "Licensable" means having the right to grant, to the maximum
     extent possible, whether at the time of the initial grant or
     subsequently acquired, any and all of the rights conveyed herein.

     1.9. "Modifications" means any addition to or deletion from the
     substance or structure of either the Original Code or any previous
     Modifications. When Covered Code is released as a series of files, a
     Modification is:
          A. Any addition to or deletion from the contents of a file
          containing Original Code or previous Modifications.

          B. Any new file that contains any part of the Original Code or
          previous Modifications.

     1.10. "Original Code" means Source Code of computer software code
     which is described in the Source Code notice required by Exhibit A as
     Original Code, and which, at the time of its release under this
     License is not already Covered Code governed by this License.

     1.10.1. "Patent Claims" means any patent claim(s), now owned or
     hereafter acquired, including without limitation,  method, process,
     and apparatus claims, in any patent Licensable by grantor.

     1.11. "Source Code" means the preferred form of the Covered Code for
     making modifications to it, including all modules it contains, plus
     any associated interface definition files, scripts used to control
     compilation and installation of an Executable, or source code
     differential comparisons against either the Original Code or another
     well known, available Covered Code of the Contributor's choice. The
     Source Code can be in a compressed or archival form, provided the
     appropriate decompression or de-archiving software is widely available
     for no charge.

     1.12. "You" (or "Your")  means an individual or a legal entity
     exercising rights under, and complying with all of the terms of, this
     License or a future version of this License issued under Section 6.1.
     For legal entities, "You" includes any entity which controls, is
     controlled by, or is under common control with You. For purposes of
     this definition, "control" means (a) the power, direct or indirect,
     to cause the direction or management of such entity, whether by
     contract or otherwise, or (b) ownership of more than fifty percent
     (50%) of the outstanding shares or beneficial ownership of such
     entity.

2. Source Code License.

     2.1. The Initial Developer Grant.
     The Initial Developer hereby grants You a world-wide, royalty-free,
     non-exclusive license, subject to third party intellectual property
     claims:
          (a)  under intellectual property rights (other than patent or
          trademark) Licensable by Initial Developer to use, reproduce,
          modify, display, perform, sublicense and distribute the Original
          Code (or portions thereof) with or without Modifications, and/or
          as part of a Larger Work; and

          (b) under Patents Claims infringed by the making, using or
          selling of Original Code, to make, have made, use, practice,
          sell, and offer for sale, and/or otherwise dispose of the
          Original Code (or portions thereof).

          (c) the licenses granted in this Section 2.1(a) and (b) are
          effective on the date Initial Developer first distributes
          Original Code under the terms of this License.

          (d) Notwithstanding Section 2.1(b) above, no patent license is
          granted: 1) for code that You delete from the Original Code; 2)
          separate from the Original Code;  or 3) for infringements caused
          by: i) the modification of the Original Code or ii) the
          combination of the Original Code with other software or devices.

     2.2. Contributor Grant.
     Subject to third party intellectual property claims, each Contributor
     hereby grants You a world-wide, royalty-free, non-exclusive license

          (a)  under intellectual property rights (other than patent or
          trademark) Licensable by Contributor, to use, reproduce, modify,
          display, perform, sublicense and distribute the Modifications
          created by such Contributor (or portions thereof) either on an
          unmodified basis, with other Modifications, as Covered Code
          and/or as part of a Larger Work; and

          (b) under Patent Claims infringed by the making, using, or
          selling of  Modifications made by that Contributor either alone
          and/or in combination with its Contributor Version (or portions
          of such combination), to make, use, sell, offer for sale, have
          made, and/or otherwise dispose of: 1) Modifications made by that
          Contributor (or portions thereof); and 2) the combination of
          Modifications made by that Contributor with its Contributor
          Version (or portions of such combination).

          (c) the licenses granted in Sections 2.2(a) and 2.2(b) are
          effective on the date Contributor first makes Commercial Use of
          the Covered Code.

          (d)    Notwithstanding Section 2.2(b) above, no patent license is
          granted: 1) for any code that Contributor has deleted from the
          Contributor Version; 2)  separate from the Contributor Version;
          3)  for infringements caused by: i) third party modifications of
          Contributor Version or ii)  the combination of Modifications made
          by that Contributor with other software  (except as part of the
          Contributor Version) or other devices; or 4) under Patent Claims
          infringed by Covered Code in the absence of Modifications made by
          that Contributor.

3. Distribution Obligations.

     3.1. Application of License.
     The Modifications which You create or to which You contribute are
     governed by the terms of this License, including without limitation
     Section 2.2. The Source Code version of Covered Code may be
     distributed only under the terms of this License or a future version
     of this License released under Section 6.1, and You must include a
     copy of this License with every copy of the Source Code You
     distribute. You may not offer or impose any terms on any Source Code
     version that alters or restricts the applicable version of this
     License or the recipients' rights hereunder. However, You may include
     an additional document offering the additional rights described in
     Section 3.5.

     3.2. Availability of Source Code.
     Any Modification which You create or to which You contribute must be
     made available in Source Code form under the terms of this License
     either on the same media as an Executable version or via an accepted
     Electronic Distribution Mechanism to anyone to whom you made an
     Executable version available; and if made available via Electronic
     Distribution Mechanism, must remain available for at least twelve (12)
     months after the date it initially became available, or at least six
     (6) months after a subsequent version of that particular Modification
     has been made available to such recipients. You are responsible for
     ensuring that the Source Code version remains available even if the
     Electronic Distribution Mechanism is maintained by a third party.

     3.3. Description of Modifications.
     You must cause all Covered Code to which You contribute to contain a
     file documenting the changes You made to create that Covered Code and
     the date of any change. You must include a prominent statement that
     the Modification is derived, directly or indirectly, from Original
     Code provided by the Initial Developer and including the name of the
     Initial Developer in (a) the Source Code, and (b) in any notice in an
     Executable version or related documentation in which You describe the
     origin or ownership of the Covered Code.

     3.4. Intellectual Property Matters
          (a) Third Party Claims.
          If Contributor has knowledge that a license under a third party's
          intellectual property rights is required to exercise the rights
          granted by such Contributor under Sections 2.1 or 2.2,
          Contributor must include a text file with the Source Code
          distribution titled "LEGAL" which describes the claim and the
          party making the claim in sufficient detail that a recipient will
          know whom to contact. If Contributor obtains such knowledge after
          the Modification is made available as described in Section 3.2,
          Contributor shall promptly modify the LEGAL file in all copies
          Contributor makes available thereafter and shall take other steps
          (such as notifying appropriate mailing lists or newsgroups)
          reasonably calculated to inform those who received the Covered
          Code that new knowledge has been obtained.

          (b) Contributor APIs.
          If Contributor's Modifications include an application programming
          interface and Contributor has knowledge of patent licenses which
          are reasonably necessary to implement that API, Contributor must
          also include this information in the LEGAL file.

               (c)    Representations.
          Contributor represents that, except as disclosed pursuant to
          Section 3.4(a) above, Contributor believes that Contributor's
          Modifications are Contributor's original creation(s) and/or
          Contributor has sufficient rights to grant the rights conveyed by
          this License.

     3.5. Required Notices.
     You must duplicate the notice in Exhibit A in each file of the Source
     Code.  If it is not possible to put such notice in a particular Source
     Code file due to its structure, then You must include such notice in a
     location (such as a relevant directory) where a user would be likely
     to look for such a notice.  If You created one or more Modification(s)
     You may add your name as a Contributor to the notice described in
     Exhibit A.  You must also duplicate this License in any documentation
     for the Source Code where You describe recipients' rights or ownership
     rights relating to Covered Code.  You may choose to offer, and to
     charge a fee for, warranty, support, indemnity or liability
     obligations to one or more recipients of Covered Code. However, You
     may do so only on Your own behalf, and not on behalf of the Initial
     Developer or any Contributor. You must make it absolutely clear than
     any such warranty, support, indemnity or liability obligation is
     offered by You alone, and You hereby agree to indemnify the Initial
     Developer and every Contributor for any liability incurred by the
     Initial Developer or such Contributor as a result of warranty,
     support, indemnity or liability terms You offer.

     3.6. Distribution of Executable Versions.
     You may distribute Covered Code in Executable form only if the
     requirements of Section 3.1-3.5 have been met for that Covered Code,
     and if You include a notice stating that the Source Code version of
     the Covered Code is available under the terms of this License,
     including a description of how and where You have fulfilled the
     obligations of Section 3.2. The notice must be conspicuously included
     in any notice in an Executable version, related documentation or
     collateral in which You describe recipients' rights relating to the
     Covered Code. You may distribute the Executable version of Covered
     Code or ownership rights under a license of Your choice, which may
     contain terms different from this License, provided that You are in
     compliance with the terms of this License and that the license for the
     Executable version does not attempt to limit or alter the recipient's
     rights in the Source Code version from the rights set forth in this
     License. If You distribute the Executable version under a different
     license You must make it absolutely clear that any terms which differ
     from this License are offered by You alone, not by the Initial
     Developer or any Contributor. You hereby agree to indemnify the
     Initial Developer and every Contributor for any liability incurred by
     the Initial Developer or such Contributor as a result of any such
     terms You offer.

     3.7. Larger Works.
     You may create a Larger Work by combining Covered Code with other code
     not governed by the terms of this License and distribute the Larger
     Work as a single product. In such a case, You must make sure the
     requirements of this License are fulfilled for the Covered Code.

4. Inability to Comply Due to Statute or Regulation.

     If it is impossible for You to comply with any of the terms of this
     License with respect to some or all of the Covered Code due to
     statute, judicial order, or regulation then You must: (a) comply with
     the terms of this License to the maximum extent possible; and (b)
     describe the limitations and the code they affect. Such description
     must be included in the LEGAL file described in Section 3.4 and must
     be included with all distributions of the Source Code. Except to the
     extent prohibited by statute or regulation, such description must be
     sufficiently detailed for a recipient of ordinary skill to be able to
     understand it.

5. Application of this License.

     This License applies to code to which the Initial Developer has
     attached the notice in Exhibit A and to related Covered Code.

6. Versions of the License.

     6.1. New Versions.
     Netscape Communications Corporation ("Netscape") may publish revised
     and/or new versions of the License from time to time. Each version
     will be given a distinguishing version number.

     6.2. Effect of New Versions.
     Once Covered Code has been published under a particular version of the
     License, You may always continue to use it under the terms of that
     version. You may also choose to use such Covered Code under the terms
     of any subsequent version of the License published by Netscape. No one
     other than Netscape has the right to modify the terms applicable to
     Covered Code created under this License.

     6.3. Derivative Works.
     If You create or use a modified version of this License (which you may
     only do in order to apply it to code which is not already Covered Code
     governed by this License), You must (a) rename Your license so that
     the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape",
     "MPL", "NPL" or any confusingly similar phrase do not appear in your
     license (except to note that your license differs from this License)
     and (b) otherwise make it clear that Your version of the license
     contains terms which differ from the Mozilla Public License and
     Netscape Public License. (Filling in the name of the Initial
     Developer, Original Code or Contributor in the notice described in
     Exhibit A shall not of themselves be deemed to be modifications of
     this License.)

7. DISCLAIMER OF WARRANTY.

     COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS,
     WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
     WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF
     DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING.
     THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE
     IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT,
     YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE
     COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER
     OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF
     ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

8. TERMINATION.

     8.1.  This License and the rights granted hereunder will terminate
     automatically if You fail to comply with terms herein and fail to cure
     such breach within 30 days of becoming aware of the breach. All
     sublicenses to the Covered Code which are properly granted shall
     survive any termination of this License. Provisions which, by their
     nature, must remain in effect beyond the termination of this License
     shall survive.

     8.2.  If You initiate litigation by asserting a patent infringement
     claim (excluding declatory judgment actions) against Initial Developer
     or a Contributor (the Initial Developer or Contributor against whom
     You file such action is referred to as "Participant")  alleging that:

     (a)  such Participant's Contributor Version directly or indirectly
     infringes any patent, then any and all rights granted by such
     Participant to You under Sections 2.1 and/or 2.2 of this License
     shall, upon 60 days notice from Participant terminate prospectively,
     unless if within 60 days after receipt of notice You either: (i)
     agree in writing to pay Participant a mutually agreeable reasonable
     royalty for Your past and future use of Modifications made by such
     Participant, or (ii) withdraw Your litigation claim with respect to
     the Contributor Version against such Participant.  If within 60 days
     of notice, a reasonable royalty and payment arrangement are not
     mutually agreed upon in writing by the parties or the litigation claim
     is not withdrawn, the rights granted by Participant to You under
     Sections 2.1 and/or 2.2 automatically terminate at the expiration of
     the 60 day notice period specified above.

     (b)  any software, hardware, or device, other than such Participant's
     Contributor Version, directly or indirectly infringes any patent, then
     any rights granted to You by such Participant under Sections 2.1(b)
     and 2.2(b) are revoked effective as of the date You first made, used,
     sold, distributed, or had made, Modifications made by that
     Participant.

     8.3.  If You assert a patent infringement claim against Participant
     alleging that such Participant's Contributor Version directly or
     indirectly infringes any patent where such claim is resolved (such as
     by license or settlement) prior to the initiation of patent
     infringement litigation, then the reasonable value of the licenses
     granted by such Participant under Sections 2.1 or 2.2 shall be taken
     into account in determining the amount or value of any payment or
     license.

     8.4.  In the event of termination under Sections 8.1 or 8.2 above,
     all end user license agreements (excluding distributors and resellers)
     which have been validly granted by You or any distributor hereunder
     prior to termination shall survive termination.

9. LIMITATION OF LIABILITY.

     UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
     (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL
     DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE,
     OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR
     ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
     CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL,
     WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER
     COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN
     INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF
     LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY
     RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
     PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
     EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO
     THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.

10. U.S. GOVERNMENT END USERS.

     The Covered Code is a "commercial item," as that term is defined in
     48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer
     software" and "commercial computer software documentation," as such
     terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48
     C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995),
     all U.S. Government End Users acquire Covered Code with only those
     rights set forth herein.

11. MISCELLANEOUS.

     This License represents the complete agreement concerning subject
     matter hereof. If any provision of this License is held to be
     unenforceable, such provision shall be reformed only to the extent
     necessary to make it enforceable. This License shall be governed by
     California law provisions (except to the extent applicable law, if
     any, provides otherwise), excluding its conflict-of-law provisions.
     With respect to disputes in which at least one party is a citizen of,
     or an entity chartered or registered to do business in the United
     States of America, any litigation relating to this License shall be
     subject to the jurisdiction of the Federal Courts of the Northern
     District of California, with venue lying in Santa Clara County,
     California, with the losing party responsible for costs, including
     without limitation, court costs and reasonable attorneys' fees and
     expenses. The application of the United Nations Convention on
     Contracts for the International Sale of Goods is expressly excluded.
     Any law or regulation which provides that the language of a contract
     shall be construed against the drafter shall not apply to this
     License.

12. RESPONSIBILITY FOR CLAIMS.

     As between Initial Developer and the Contributors, each party is
     responsible for claims and damages arising, directly or indirectly,
     out of its utilization of rights under this License and You agree to
     work with Initial Developer and Contributors to distribute such
     responsibility on an equitable basis. Nothing herein is intended or
     shall be deemed to constitute any admission of liability.

13. MULTIPLE-LICENSED CODE.

     Initial Developer may designate portions of the Covered Code as
     "Multiple-Licensed".  "Multiple-Licensed" means that the Initial
     Developer permits you to utilize portions of the Covered Code under
     Your choice of the NPL or the alternative licenses, if any, specified
     by the Initial Developer in the file described in Exhibit A.

EXHIBIT A -Mozilla Public License.

     The contents of this file are subject to the Mozilla Public License
     Version 1.1 (the "License"); you may not use this file except in
     compliance with the License. You may obtain a copy of the License at
     http://www.mozilla.org/MPL/

     Software distributed under the License is distributed on an "AS IS"
     basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
     License for the specific language governing rights and limitations
     under the License.

     The Original Code is ______________________________________.

     The Initial Developer of the Original Code is ________________________.
     Portions created by ______________________ are Copyright (C) ______
     _______________________. All Rights Reserved.

     Contributor(s): ______________________________________.

     Alternatively, the contents of this file may be used under the terms
     of the _____ license (the  "[___] License"), in which case the
     provisions of [______] License are applicable instead of those
     above.  If you wish to allow use of your version of this file only
     under the terms of the [____] License and not to allow others to use
     your version of this file under the MPL, indicate your decision by
     deleting  the provisions above and replace  them with the notice and
     other provisions required by the [___] License.  If you do not delete
     the provisions above, a recipient may use your version of this file
     under either the MPL or the [___] License."

     [NOTE: The text of this Exhibit A may differ slightly from the text of
     the notices in the Source Code files of the Original Code. You should
     use the text of this Exhibit A rather than the text found in the
     Original Code Source Code for Your Modifications.]

Utility: Registry Preview

HexBox.WinUI

We use HexBox.WinUI to show a preview of binary values.

Source: https://github.com/hotkidfamily/HexBox.WinUI

MIT License

Copyright (c) 2019 Filip Jeremic
Copyright (c) 2024~2025 hotkidfamily@gmail.com

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Monaco Editor

Source: https://github.com/Microsoft/monaco-editor

Additional third party notifications: https://github.com/microsoft/monaco-editor/blob/main/ThirdPartyNotices.txt

The MIT License (MIT)

Copyright (c) 2016 - present Microsoft Corporation

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

NuGet Packages used by PowerToys

  • AdaptiveCards.ObjectModel.WinUI3
  • AdaptiveCards.Rendering.WinUI3
  • AdaptiveCards.Templating
  • Appium.WebDriver
  • CoenM.ImageSharp.ImageHash
  • CommunityToolkit.Common
  • CommunityToolkit.Labs.WinUI.Controls.MarkdownTextBlock
  • CommunityToolkit.Labs.WinUI.Controls.OpacityMaskView
  • CommunityToolkit.Mvvm
  • CommunityToolkit.WinUI.Animations
  • CommunityToolkit.WinUI.Collections
  • CommunityToolkit.WinUI.Controls.Primitives
  • CommunityToolkit.WinUI.Controls.Segmented
  • CommunityToolkit.WinUI.Controls.SettingsControls
  • CommunityToolkit.WinUI.Controls.Sizers
  • CommunityToolkit.WinUI.Converters
  • CommunityToolkit.WinUI.Extensions
  • CommunityToolkit.WinUI.UI.Controls.DataGrid
  • ControlzEx
  • HelixToolkit
  • HelixToolkit.Core.Wpf
  • hyjiacan.pinyin4net
  • Interop.Microsoft.Office.Interop.OneNote
  • LazyCache
  • Mages
  • Markdig.Signed
  • MessagePack
  • ModernWpfUI
  • Moq
  • MSTest
  • NJsonSchema
  • NLog
  • NLog.Extensions.Logging
  • NLog.Schema
  • OpenAI
  • ReverseMarkdown
  • ScipBe.Common.Office.OneNote
  • SharpCompress
  • SkiaSharp.Views.WinUI
  • StreamJsonRpc
  • StyleCop.Analyzers
  • ToolGood.Words.Pinyin
  • UnicodeInformation
  • UnitsNet
  • UTF.Unknown
  • WinUIEx
  • WPF-UI
  • WyHash