Flow-Launcher / Flow-Launcher/Flow.Launcher

BUG: Startup task in Task Scheduler doesn't point to new version after an update

Open
#4,485 2 comments 0 reactions 0 assignees View on GitHub
bug
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.

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

### Problem Description

After updating Flow from 2.1.1 to 2.1.2, the startup task created by Flow with the "Start Flow Launcher on system startup" setting still points to 2.1.1. On system startup, it runs 2.1.1 and repeatedly asks me to update to 2.1.2 despite having already done so.

### To Reproduce

_No response_

### Screenshots

_No response_

### Flow Launcher Version

2.1.2

### Windows Build Number

10.0.26200.8457

### Error Log

_No response_

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.