-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Fix/issue 3815 #3836
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
base: main
Are you sure you want to change the base?
Fix/issue 3815 #3836
Conversation
ChrisTitusTech
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has been bugging the hell out of me... All this time it was a QWORD instead of a DWORD!!?!??!
Thank you!
😂😂 Happens to the best of us! |
|
Has there been progress regarding this issue? When will you merge it @ChrisTitusTech? |
Everything I'm reading says this is a DWORD value. Trying to track down the QWORD documentation. |
Type of Change
Description
This PR fixes the "Set Time to UTC" tweak. Previously, it set the RealTimeIsUniversal registry key as a DWord (32-bit). On 64-bit Windows systems (especially dual-boot scenarios), this key is often ignored unless it is a QWord (64-bit). Resolves #3815
I have updated
config/tweaks.jsonto useQWordfor this entry.Testing
Verified that the
RealTimeIsUniversalkey is created as aQWORDafter this change.Confirmed that the registry value remains
1.Impact
Users dual-booting with Linux should now have correct time synchronization when switching between OSes.
No impact on 32-bit systems as REG_QWORD is valid there as well (though less critical).
Issue related to PR
Additional Information
Checklist