Repository navigation
Follow-ups to the GHSA-pvgf-f87w-4jfp fix from deployment testing (issue #11, thanks to @toseparo).
Fixed
- When the elevated task from 1.3.0 or older can't be removed silently, physmouse no longer shows a bare UAC prompt at every sign-in. Starts at sign-in (
--background, including the restart after a quiet upgrade) never prompt; a start by hand explains the task first and asks before Windows' administrator prompt, as 1.4.0's notes already described. - An interactive update no longer fails when that prompt is declined (for example by a standard user). It installs, keeps the task, and says on its last page that the task remains.
- The task is recognized by its name
\physmouseand by starting an exe outsideProgram Filesand the Windows folder, instead of by the current user's install path.--remove-legacy-tasknow finds it when run as SYSTEM, also removes tasks registered by a portable copy, and returns 0 when there's no task, as documented. A\physmousetask that starts physmouse fromProgram Filesis left alone. --uninstall --quietno longer fails with exit code 1 when theForceAutostartpolicy is set.
Docs
- README: the detection rule uses only the
DisplayVersionregistry value (the exe is deleted a moment after uninstalling), a note onStart-Process -Waitand the restarted copy, and what--remove-legacy-taskremoves. The winget notes point out that the copy in%LOCALAPPDATA%must not be run as SYSTEM.
SHA-256 of physmouse-v1.4.2-installer.exe: D4A18A1852B0FAEDF5C637EAAB037BEF6CEEC886D9D1FB6866FA911A0AA3C0C0
This file was built from this tag by GitHub Actions. To check it, run:
gh attestation verify physmouse-v1.4.2-installer.exe -R lieberlenny/physmouse
The exe is unsigned, so Windows SmartScreen or antivirus software may warn about it.