Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug(windows): registry value written two different keys - SRegValue_CheckForUpdates #13216

Open
rc-swag opened this issue Feb 13, 2025 · 0 comments
Assignees
Milestone

Comments

@rc-swag
Copy link
Contributor

rc-swag commented Feb 13, 2025

Investigation needs to be done into the SRegValue_CheckForUpdates
When investigating the report usage statistics not being persisted after installation I notice some strange things with the CheckforUpdates registry value.
In the setup executable it is written to SRegKey_KeymanDesktop_CU whereas in Keyman Configuration options it is written to SRegKey_KeymanEngine_CU. It maybe they are intended to be two different things one is checking for updates on install the other is for automatic updates. The one in Keyman Configuration use to say check weekly prior to version 18.0 however it was still then same registry value name but as noted in a different key.

FCheckForUpdates := ValueExists(SRegValue_CheckForUpdates) and ReadBool(SRegValue_CheckForUpdates);

The second thing to notice is that FCheckForUpdates := True; first then
Has this value line FCheckForUpdates := ValueExists(SRegValue_CheckForUpdates) and ReadBool(SRegValue_CheckForUpdates);

If there is no registry value for SRegValue_CheckForUpdates then this will set FCheckForUpdates to False. Meaning the default value is really False. However maybe I am missing someting this all needs further investigation.

@rc-swag rc-swag self-assigned this Feb 13, 2025
@mcdurdin mcdurdin added this to the B18S1 milestone Feb 13, 2025
@darcywong00 darcywong00 modified the milestones: B18S1, B18S2 Feb 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants