hbashton / hbashton/DS4Windows

Startup tasks remain disabled after a fresh install, and the UI reports it as a user preference

Open
#77 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
272
Forks
10
Avg merge
13d 5h
Merged PRs (30d)
1

Description

On a fresh install where usbip-win2 is provisioned for the first time, setup logs:

Verified startup tasks are registered but disabled until the pinned USB-IP
package and runtime ABI pass after reboot.
Repair will re-enable them only after usbip-win2 passes its runtime ABI check.

Nothing triggers that repair. After reboot both RunDS4Windows and RunVIIPER remain Disabled with correct targets, so neither auto-starts at logon.

Because HasTaskEntry() requires task.Enabled, and runAtStartup = runStartProg || runStartTask derives purely from observed state, Settings then shows "Run At Startup" unchecked — presenting setup's temporary state as a preference the user never made. ViiperSetupManager reads it as "startup explicitly disabled" and silently launches VIIPER per-session, so nothing appears broken.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing HasTaskEntry(), runAtStartup, and ViiperSetupManager from the setup and settings paths described in the issue. Reproduce a fresh install and reboot, then verify that the registered RunDS4Windows and RunVIIPER tasks recover after the runtime ABI check, that Settings does not present setup state as a user preference, and that VIIPER is not launched per session as a workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.