I have a personal “Windows install / configuration playbook” so I don’t fall into these types of pitfalls for the Nth time (including the very example you give).
Some fun ones: windows defaults to storing the hardware clock time as a time-zone local offset, so whenever it syncs time with network servers, it messes up your time in other OSes (in multi-boot setups). You have to set the RealTimeIsUniversal registry key to make Windows behave.
What made me figure this out? Another pair of issues: the XBox/gaming app/overlay would give nonspecific errors, or at best not let my party hear me, when I’d try to join my brother’s party when playing games. Eventually connected the dots: I would reboot into Windows after working in Linux, the time would be messed up, and the Windows gaming overlay’s party stuff would be broken, suggesting the local time is used in some way for the chat/voice protocol, but of course they don’t tell you that. I initially scoured pages, and pages of Google search results, leading to countless MS forums and Reddit posts, none of which pointed out the importance of the system time. This wouldn’t be as much of an issue if Windows would more regularly sync the system time, or at least do so upon booting, but of course there isn’t a first-party way to do that, either — the best I could do without installing crap was go into the time settings and unset then set the option for syncing time automatically, coercing it into updating the time right then and there — at least, until I sorted out why the time was all messed up when rebooting after running Linux.
Now with the ads and forced online account creation, it’s only becoming more of a dumpster fire than it already was.