Flow-Launcher / Flow-Launcher/Flow.Launcher

BUG: Unable to run test.ps1 script from OneDrive folder through Flow Launcher - "Unable to open the path"

Open
#3,385 4 comments 0 reactions 0 assignees View on GitHub
bug keep-fresh Needs investigation
Dominant language
C#
Stars
15.6k
Forks
644
Avg merge
3d 14h
Merged PRs (30d)
4

Description

### Checks

- [x] I have checked that this issue has not already been reported.

- [x] I am using the latest version of Flow Launcher.

### Problem Description

I am encountering an issue when attempting to run a PowerShell script (test.ps1) from my OneDrive folder using Flow Launcher. The error message returned is:
`Unable to open the path C:\Users\xuehu\OneDrive\test.ps1, please check if it exists.`
However, when I move the script to other directories, such as the Desktop, it executes normally without any issues.Additionally, if I right-click on the script in Flow Launcher’s search results and choose "Open with," the script runs correctly.

### To Reproduce

1. Place a PowerShell script (test.ps1) in the OneDrive directory (e.g., C:\Users\xuehu\OneDrive).
2. Use Flow Launcher to search and run the script directly.
3. Observe the error message:
`Unable to open the path C:\Users\xuehu\OneDrive\test.ps1, please check if it exists.
`
4. Move the same script to a different directory (e.g., Desktop) and execute it via Flow Launcher again.
5. The script executes successfully from the new location.
6. Alternatively, right-click on the script in Flow Launcher’s search results and choose "Open with," and the script runs as expected.

### Screenshots

![Image](https://github.com/user-attachments/assets/3e8180fd-9e80-4484-a379-b3cf82cfde02)

### Flow Launcher Version

1.19.5

### Windows Build Number

10.0.22621.4317

### Error Log

`Unable to open the path C:\Users\xuehu\OneDrive\test.ps1, please check if it exists.
`

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.