Action Center stopped working after 1809

So I just realized that I am not getting any notifications, I check with several programs and with Notifications Visualizer app from the store.
The weirdest thing is that the speech bubble icon shows the notification count correctly but no notification sound or toast is displayed when the notification arrives and on top of that, after opening the action center itself, the notifications don't appear in the list, it's completely empty.

I tried to create a new user and without even restarting the pc, I just logged off and switched account, the notifications work on the other account.

Focus assist is disabled, I double checked.

Do you happen to know any way to reset the action center?
The event viewer lists:

Toast with notification tracking id 46 is being delivered to 58300WindowsNotifications.NotificationsVisualizer_8rkfj2ay7vd1w!App on session 1.

Start Toast Notification Forwarding activity

Stop Toast Notification Forwarding activity



58300WindowsNotifications.NotificationsVisualizer_8rkfj2ay7vd1w!App looks like an app, maybe reinstalling it could fix the issue?

dalchina said:

Hi, there's this: you could try checking/toggling it:

Sadly it didn't work

Maybe it has to do with allowing applications in the background (Settings-Privacy), I read that that was the cause of the problem in some cases.

I'm still having this problem, and all my settings are turned on in notifications and action, and in background apps.

Had the notification centre glitch a couple of times after rebooting after the upgrade but seems to be rightened.

Background apps are allowed anyway.

What I'm annoyed about is the uCode updates. I purposely took two routes;

Desktop PC - used for Gaming - do not want any Spectre uCode

Laptop PC - used for all day every day work - absolutely want all Spectre uCode

this build of 1809 updates my Desktop PC (custom UEFI BIOS) from 0x22 (pre Spectre) to 0x24 (Spectre variant 2 patched)

it does absolutely nothing for my Laptop PC (latest vendor BIOS) 0x2A (only Spectre variant 2 patched)

If this was done with the correct baseline of OS carries pre Spectre uCode then the uCode updates carry the updated uCode; one patch for Spectre variant 2 and another patch for Spectre variant 3a & 4 as per the old KB4100347 and KB 4346084 in 1803, I'd be happy.

Instead I'm now super annoyed I can't run my PCs the way I want. Unless of course, anyone knows of a way to stop mcupdate_GenuineIntel.dll from being loaded.

Microsoft could still ship protections enabled by default and I could via registry either selectively enable or disable as I saw fit. This is a halfway house that helps no-one, especially me for what I want.

kado897 said:

This needs to be on. It's a fault I have reported numerous times and been ignored. You need to reboot for it to come into effect.

Basically I had tried it earlier today without rebooting, you would assume the setting gets applied as soon you close the panel but that's not the case for this one.

I will mark the issue as resolved but this isn't nice, Microsoft need to fix this.
I noticed that with the apps allowed to run in the background Cortana and the Windows Shell Experience stay in memory.
With the background apps deactivated they took less than 1 MB of ram each, which was the improvement I liked the most out this entire update since I use Open Start which Cortana search and the modern start menu altogether.

[QUOTE=winactive;1476684]Instead I'm now super annoyed I can't run my PCs the way I want. Unless of course, anyone knows of a way to stop mcupdate_GenuineIntel.dll from being loaded.
[/QUOTE]

I have a PC dedicated to rendering only, basically I connect it to the internet only for driver updates.
I run it with all the mitigations disabled, to circumvent mcupdate_GenuineIntel.dll I just renamed it to "mcupdate_GenuineIntel.dll.disabled" and it looks like it gets disabled correctly according to the get-speculationcontrolsettings powershell module.

If you run a sfc/ scannow, the file gets marked as corrupted and you need to rename it again.
It's also protected so you need to get ownership of the file in order to rename it.