"First week of year" setting keeps resetting to default value

[MarkoPolo785]

Using Windows 10 & T-Clock Redux x64 - 2.4.4. build 492

"First week of year" setting keeps resetting to ?default? value "Week containing January 1 (USA)" after some time. Desired setting is "first full week". Hence calendar view (which shows week numbers) is not consistent calendar week number in taskbar. I use "Advanced clock format" - HH:nn\ndd.mm.\nddd, "W"Wi. Right not taskbar is showing W26 value, but in calendar current week is shown as S27 (when setting of "First week of year" defaults by itself).

[White-Tiger]

As the settings page states, this is a Windows user setting. If it changes "magically", it's either you or some other app changing it.

[MarkoPolo785]

Thank you for reply.

Where does T-Clock read the Windows setting from? I edited "iFirstWeekOfYear" attribute in regedit to value "2" which should correspond to first week with full 4-days, but the setting in T-clock still resets to USA setting. I am guessing this is not the correct setting.

Any ideas which software could affect it? Besides Outlook I am not using any other calendar type apps...

Many thanks.

[White-Tiger]

T-Clock "uses" HKEY_CURRENT_USER\Control Panel\International
It's just the systems locale setting. So if your locale is set to US, you should use the week with January 1st (iFirstWeekOfYear = 0)
You can change the value and reopen T-Clocks options, and you'll see it'll display the new value.

To figure out who changes it, you'll either have to be able to reproduce it, or try to find a program that can watch the registry key for modification. (maybe Process Monitor might do)

[MarkoPolo785]

Hi René,

many thanks for your help. I believe we fixed the issue. Process Monitor showed svchost.exe was changing the value from "2" to "0" and with that T-Clock was also changing the view. I have reduced rights in the regedit for this specific entry to read only. Seems to be working fine. Not sure if I made worse something else :-)

Best regards

[White-Tiger]

Was this your personal computer or is it part of a Windows domain?
Could you try to reset the default rights on that key and run gpupdate.exe to see if that changes it again? Then change it to 2 and run gpupdate.exe again? It seems to be a group policy then.

It's generally not a good idea to enforce registry settings by changing permissions... worst case are Windows updates that fail and you wouldn't immediately figure out what causes it. (if at all) I'm not even sure if T-Clock will ever show an error when it can't change that setting (as it normally would be able to)