Skip to content

The new integrations feature doesn't work for some paths? #19217

@ChiriVulpes

Description

@ChiriVulpes

The problem

Trying to replicate what I had in #16980 with the new feature and I can't get it to work for multiple reasons.

This issue is regarding the "Path" input, which doesn't seem to allow me to put in C:\Chiri\AppData\Local\Microsoft\WindowsApps\wt.exe, saying "This path does not appear to be a valid executable."

Release version

3.4.4

Operating system

Windows 10

Steps to reproduce the behavior

  1. Put the Microsoft Store wt.exe path in your "Path" input:
  • C:\YOURUSERNAME\AppData\Local\Microsoft\WindowsApps\wt.exe
  • Theoretically %LOCALAPPDATA%\Microsoft\WindowsApps\wt.exe should also work but it doesn't either

Log files

No response

Screenshots

No response

Additional context

I am able to workaround this issue by making a custom .bat file in another folder that opens wt.exe itself, but it's a little silly that I have to do that

Metadata

Metadata

Assignees

Labels

bugConfirmed bugs or reports that are very likely to be bugspriority-3Bugs that affect small number of users and/or relatively cosmetic in nature

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions