microsoft/PowerToys

[CmdPal][Window Walker] LabVIEW does not appear in window list

Open

#38,862 opened on Apr 15, 2025

View on GitHub
 (5 comments) (1 reaction) (0 assignees)C# (7,978 forks)batch import
CmdPal - Window WalkerCmdPal-Inbox ExtensionsHelp WantedIssue-BugProduct-Command Palette

Repository metrics

Stars
 (133,154 stars)
PR merge metrics
 (Avg merge 14d 20h) (117 merged PRs in 30d)

Description

Microsoft PowerToys version

0.90.1

Installation method

Microsoft Store

Area(s) with issue?

Command Palette

Steps to reproduce

I started using the new Command Palette feature of PowerToys. I was very excited about the possibility to navigate the forest of windows that comes with LabVIEW development in a better way than ALT+Tab. Unfortunately, none of the windows appear in the list. The "splashscreen" does not show up, the project does not show up and the individual VIs do not show up.

Image

Image

This might be a LabVIEW issue, or it might extend to other programs. I opened a bunch of other programs to see if this is a common problem, but so far LabVIEW is the only one that does not show up. I am using LabVIEW 2021 and 2015 and both do not show up in CmdPal. There is now a community version of LabVIEW that is free to use in case anyone wants to try to replicate this. I am happy to provide more info if I am told what is needed.

✔️ Expected Behavior

I was expecting LabVIEW windows to be listed in CmdPal's Window Walker.

❌ Actual Behavior

LabVIEW windows were absent.

Additional Information

Win 10 Pro 10.0.19045 version 19045 System language: Swedish Running without admin privileges

Other Software

LabVIEW 2021 SP1 LabVIEW 2015

Contributor guide

Research direction
Investigate the window enumeration logic in Window Walker to understand why LabVIEW windows are not captured. Check if LabVIEW windows have a different window class or style that might be filtered out.
Tech stack
csharp
Domain
desktoptooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70