Changing system time completely breaks start menu functionality on CU

This might sound like a weird issue, but I can confirm it's not just me, and an inherent problem in the 1703 installation (at least using the MDSN ISO with Windows 10 Pro x64 selected.)

Tried it on my laptop (which I wanted to upgrade from Anniversary to Creator's, and wiped in the process since clean installs are always better) and also in a virtual machine to make sure it wasn't a hardware-specific problem with my laptop. Same behavior in the VM.

Let me explain how to replicate the problem. If you guys don't believe me I can make a video, but it's pretty simple.

First setup a Windows 10 machine from scratch. I did it without a network connection so I could turn off the annoying "auto install sponsored apps" garbage, but this shouldn't affect anything really.

Enter your username, make a password if you want, I left that blank. I turned Cortana off and set all the privacy stuff to NO.

Once it put me at the desktop, I opened the start menu, and unpinned everything to get rid of the default groups/bloatware.

Then I pinned two apps to start. Which two don't matter, same behavior with anything.

So, Windows 10 defaults to Pacific Standard Time (GMT-8) since Microsoft is in California, and unlike earlier versions it doesn't ask you during the OOBE. OK, so I changed it to Eastern time (GMT-5) - and because the clock is now 3 hours AHEAD (hint, my onboard clock was correct when running the installation, so it got "adjusted" to be the wrong time), I changed it back by 3 hours.

Now, if I try to drag an icon around on the start menu, or even pin something to start or unpin one of those two, it doesn't work. Dragging an icon crashes the start menu (e.g. it just exits, and the icon is back where it started when I reopen it), where pinning does absolutely nothing. Unpinning appears to work, until you reboot in which case it comes back.

Oddly, this problem doesn't happen if you do the reverse. I tried going from GMT-8 to like GMT-11 and adjusting 3 hours the other way, it didn't crash. It only does it if you go FORWARD timezones. And it also doesn't matter if you use NTP to fix the clock or not, changing it by any means (manual or online) causes the same crash.

I should point out that it's only changing the clock from inside Windows (even in safe mode!) that does it. I tried livebooting Linux, updating the hardware clock after changing to GMT-5 in Windows, going back to Windows and it was working. BUT... changing the clock even a minute or two causes the crash again, so it's not a real solution because if your hardware clock "drifts" and you use NTP syncing as I normally do, you'll wind up right back in the same spot.

Some more tests and observations -

If you create a second profile after changing the timezone/clock, that profile's start menu will work fine. Until you change the clock using *that* profile, then *that* profile's start menu breaks. So another temporary workaround until this is fixed is to make a second dummy profile, fix your clock to the proper timezone (lucky folks actually living in GMT-8 won't have to worry), then use the main again.

Changing it back to GMT-8 and manually changing the clock forward 3 hours seems to "fix" the start menu crashing.

Changing the time forward/backwards while it's in GMT-8 seems to not cause the crash (if I recall correctly, I could be wrong about this part)

So in short, it's only changing the clock TO GMT-5 (I'd imagine any other timezone east of GMT-8 would do the same) then changing your clock that causes a crash.

I tried installing all of the newest updates from Windows Update to make sure I was up to date. Bug still persists. I thought maybe it was my video drivers or something so I tried this with an absolute fresh install, doing nothing but unpinning the default shortcuts and pinning new ones, and even *that* is enough to trigger the crash.

So... this is pretty infuriating, and I'm stuck without a computer until this gets fixed. Has anyone else run into this themselves? Can I somehow bring this to Microsoft's attention so they can fix it with the next Patch Tuesday update? "Feedback Hub" or whatever is useless and probably just gets ignored.

Right... Washington, not California, my bad. Same timezone though.

OK, so I tested this some more - it actually has nothing to do with timezones, simply changing the clock backwards causes the issue, even if you leave it in pacific time.

So let's say you install Windows and it has the clock set to 3:00. If you change the time and set it to 2:00, it breaks. If you change it forwards to 4:00, it doesn't break.

I'm going to test one thing - it's possible simply waiting an hour in the above scenario will fix it and I'm just being impatient. But it's still annoying!

If you're connected to the Internet when installing, it will attempt to sync your clock to time.windows.com as part of the OOBE. In that case, it shouldn't cause any issues unless you have RTC drift (which does happen, just not usually by more than a few seconds in either direction). But, I've also had a couple test installs where it didn't sync automatically despite being online, so there's that.

I set my clock back two hours. No affect at all here. I would create a new user (local with administrator privileges). Sign in to the new user account and see if it does it in that account.

OK, I just tested in a brand new VM.

Installed it with default settings, unpinned the default pins, pinned my own stuff.

Changed clock backwards 5 minutes, can confirm it breaks.

Shutdown VM and wait 5 minutes - boot it back up, it works again.

So I guess the problem does sorta resolve itself, if you just wait until your hardware clock matches the original time it did after finishing the OOBE.

I suspect it's some sort of "security" feature with the start menu databases, but I'm not sure. Incredibly stupid either way...
@NavyLCDR, I tried that already. The new account works fine, until you change the clock using that account. LOL

Did you test a brand new clean install of 1703? What source did you use? I'm using the MSDN ISO.

OK, so try this in a VM...

Don't have a network connection during the initial setup (like I said, if it syncs with NTP before you sign in for the first time, the issue won't happen)

Otherwise install as normal

Once you're at the desktop, unpin everything and pin two apps. Confirm you can drag them around, unpin, repin.

Now turn off "set the clock automatically" and set it backwards. Any amount of time is fine, whether 5 minutes or 5 hours.

Try again.

If it doesn't break for you I'll be shocked.

What it does is if you try to drag the pins around, they just go back to their original position and won't move - unpinning them makes them come right back, and pinning anything new won't work either.

I'm definitely thinking it's some quirk with the last modified date/time on the start menu database files, it just never seemed to do this before CU...

Edit: Also, I'm using PRO 64-bit. I haven't tried any other editions (home, enterprise, education) or x86. I can't say if they have the same problem or not.