Immediately after upgrading to Windows 10 1709 "Fall Creators Update", I've noticed three problems with my main profile that I suspect are all related.

  1. Notification Center is out of whack

When alerts show up in the Notification Center, I can clear them away with the "Clear all" button, but the number on the icon showing how many alerts there are does not change. If I check the Notification Center a minute or so later, the alerts that I cleared are back. Also, the "Action Center" (buttons on the bottom of the Notification Center that do things like enable/disable Wi-Fi, adjust brightness, turn on "night light", etc.) does not show up, even though I have it configured to show up in Settings.

  1. Start Menu icons are missing

Err... Pic shows it all. Tiles are present and functional but the icons and graphics are gone.

Top portion of Start Menu

  1. Can't right-click on taskbar buttons

If I right-click on a program on the taskbar (for example, to get to the menu to unpin an icon)... The right-click menu does not show up.

[Edit] Just noticed that right-clicking on Start Menu tiles does not work either (the context menu does not appear).

It's like some of the "modern" elements of the UI have decided not to work. The clock fly-out and Cortana still work. Anyone else seen something like this? Any ideas on how to solve (without losing my profile)? Other profiles on the machine work fine.

  • My suggestion is revert to 1703 and attempt to install the upgrade again. – Ramhound Oct 19 '17 at 14:25
  • 1
    Have you rebooted since the problem started? Usually I encounter these weird things after an upgrade, and a reboot fixes everything. – LPChip Oct 19 '17 at 14:25
  • Yes, many reboots, always the same. – Aaron Oct 19 '17 at 14:25
  • Found this article, maybe it will end up being a known issue (and fixed by MS) windowslatest.com/2017/10/18/… – Aaron Oct 19 '17 at 14:31
  • "Anyone else seen something like this?" - This can happen on any installation, it is a question that has been asked in the past, typically the best advice is to repair your installation. Since other user profiles don't have the problem, typically I would suggest creating a new user profile, and migrating the data to it. However, you specifically don't wish to do that, so I have no other suggestion outside of reverting to 1703 and waiting to update to 1709 – Ramhound Oct 19 '17 at 14:32

Under various scenarios on different computers (some via upgrade from version 1703, while other times just installing software like SQL on version 1709) the Start Menu and Notification stop working for Windows Fall Creator Update Version 1709. None of the methods posted on the web solved the problem, but the good news for many out there like me, is that there is another method that works under every scenario I've encountered. I stumbled upon this after fighting with trying to install SQL Developer (either version 2016 with SP1 or 2017) on Windows 10 Fall Creator Update Update Version 1709.

How to Solve Windows Start and Notification Not Working: 1st of all, you can get the start menu and notification working again by logging off and back on again, but after each reboot, the problem returns. To persist the working of start menu and notification, disable Windows Hello and disable PIN and disable Picture password. Be sure that only the traditional password security sign-on option exists. Reboot your box and start menu and notification once again works. In fact, you can then re-enable Windows Hello and PIN and upon re-boot, the start button and notification will work and persist working even upon reboots.

This is a reproducible verified Microsoft Bug :(
At least between SQL 2016/2017 and Windows 10 Fall Creator Update Version 1709.

| improve this answer | |
  • Thanks for your reply. Unfortunately, I can't check it as I have since re-built my profile, but I'm glad that a solution seems to have been found. I do indeed have SQL Server 2017 and SSMS installed on my system, so that could have something to do with it. – Aaron Jan 3 '18 at 18:07

It happened to me also. I was able to fix it by enabling the Administrator user, login with the administrator account, and then came back to my user account. Now all is working correctly

| improve this answer | |
  • it appears you have mistakenly submitted a comment as an answer. The author already indicated that logging in and logging out of the user in question didn't resolve the problem. – Ramhound Oct 24 '17 at 17:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.