I remember seeing this update on some machines I set up for work and wondering the same. It occurs the first time the clock app is launched, and the “update” is really just pulling the time zone data and setting the clock to what is accurate (internet based world clock), seperate from the bios time it was going off of prior to that. It’s really just looks worse than it is.
Yeah but that shouldn’t be so data or read/write intensive that you need an entire splash. Should take less than a second on any hardware capable of running w11.
Is it just doing some weird backend patching to make it compatible with the rest of windows somehow?
I remember seeing this update on some machines I set up for work and wondering the same. It occurs the first time the clock app is launched, and the “update” is really just pulling the time zone data and setting the clock to what is accurate (internet based world clock), seperate from the bios time it was going off of prior to that. It’s really just looks worse than it is.
Yeah but that shouldn’t be so data or read/write intensive that you need an entire splash. Should take less than a second on any hardware capable of running w11.
Is it just doing some weird backend patching to make it compatible with the rest of windows somehow?