Abstract
A desktop dictation app needs operating-system privacy permissions such as microphone, input monitoring and accessibility. After the app is reinstalled or replaced by a new build, the system may stop honouring permissions granted to the previous copy while its settings still show the app as allowed, leaving a hotkey that does nothing. The app stores an install identity in a marker file, made of its version string and the modification time of its main executable. It compares this identity at each launch and then stores the new value. When a marker existed and differs, onboarding was completed earlier, and the running process lacks any permission that dictation requires, the app acts once for that install. It posts a notification naming the missing permissions and telling the user to remove the app from that list in the system settings and add it again. It also opens its usage guide directly at a Permissions card. The card lists each permission with the state the running app actually holds, explains the remove-and-add-again fix, and offers a button that opens the app's own permission settings. A first-ever launch is left to onboarding.
Creative Commons License

This work is licensed under a Creative Commons Attribution 4.0 License.
Recommended Citation
Supersey, "Detecting the First Launch of a Reinstalled or Updated Desktop App and Guiding the User to Re-grant Privacy Permissions That Silently Stopped Applying", Technical Disclosure Commons, ()
https://www.tdcommons.org/dpubs_series/13055