Recently migrated to Endeavor and have Windows for Rainbow Six Siege (anticheat isn’t setup to work with Proton). Was curious why the clock was always wrong.
Ok, at least that explains that. Thanks ^^ didn’t have to switch that often so never bothered looking for a solution. So you spared me some searching, many thanks!
The clock thing is normal. Windows doesn’t like UTC clocks with local adjustment for timezone like every sane system does it.
About the resolution issue. Did you deactivate fast boot in Windows. That’s a bullshit feature decreasing boot time by not actually shutting off. It’s some kind of hybrid standby. And it can lead to all kinds of problems, like for example not properly shutting down and releasing control over hardware. Which then leads to stuff like graphics or network cards not working properly in linux.
Garuda / win11 dualboot here.
When I go back to Garuda I find my display settings out of whack. Usually 800x640 resolution and desktop image back to default.
When I go back to win11 i find the timezone changed.
So dual boot is annoying for both in my experience
https://feldspaten.org/2019/11/03/windows-10-clock-in-utc/
Amazing, thank you for the link.
Recently migrated to Endeavor and have Windows for Rainbow Six Siege (anticheat isn’t setup to work with Proton). Was curious why the clock was always wrong.
Ok, at least that explains that. Thanks ^^ didn’t have to switch that often so never bothered looking for a solution. So you spared me some searching, many thanks!
The clock thing is normal. Windows doesn’t like UTC clocks with local adjustment for timezone like every sane system does it.
About the resolution issue. Did you deactivate fast boot in Windows. That’s a bullshit feature decreasing boot time by not actually shutting off. It’s some kind of hybrid standby. And it can lead to all kinds of problems, like for example not properly shutting down and releasing control over hardware. Which then leads to stuff like graphics or network cards not working properly in linux.
Thought I had but I double checked and it turns out to be enabled. Turned it off, we’ll see if that helps, thanks.
Haha, I forgot it also broke the clock. But as others explained, it’s fixable.