Settings > System > Notifications does not work after 28020.2623 (Beta) update

Question

Settings > System > Notifications does not work after 28020.2623 (Beta) update

Bert22306 140

After installing the lengthy feature update for Beta channel 28020.2623 (26H1 build), going to settings > system > notifications doesn't work. It momentarily flashes on and then nothing.

Fortunately, other system settings do seem to operate correctly.

Will report to Feedback Hub.

Oh, I did do sfc /scannow, which found and corrected some problems.

Then I did Dism.exe /Online /Cleanup-Image /Restorehealth, which completed successfully.

0 comments

2 answers

Your answer

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 2

BryceSor 5,475 Volunteer Moderator

Hi Bert22306,

You could try this in PowerShell admin

Get-AppxPackage -AllUsers | ForEach-Object {
    Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"
}

Bert22306 140 Reputation points

2026-08-02T04:30:41.96+00:00

Thanks for the suggestion, Bryce. It did run a whole long sequence of tests or whatever it was, but ultimately, it didn't help.

I even rebooted, and then tried again, still doesn't work. It's too weird. You click on notifications, it looks like it tries to open that window, and then instantly it shuts the whole session "settings" dialogue down, back to a blank desktop.

I did send it in. Let's see how quickly MS fixes this one. Seems rather important to me.
BryceSor 5,475 Reputation points Volunteer Moderator

2026-08-02T05:14:56.5933333+00:00

Can you check your settings are the same as the picture, filter keys can cause an issue sometimes
Bert22306 140 Reputation points

2026-08-02T12:43:10.43+00:00

Yup. Everything set to Off, just like in your screengrab.
BryceSor 5,475 Reputation points Volunteer Moderator

2026-08-02T19:58:22.7666667+00:00

I would roll back tp previous install, make sure everything works in that install, run DISM and sfc, delete the WU download folder contents and try to update again.

I would give you more PowerShell codes if you want but generally when Insider installs have missing or corrupted parts I clean install the latest. Iso for my Insider then use WU.

Sorry I don't have a quick fix
Bert22306 140 Reputation points

2026-08-03T04:33:24.89+00:00

Thanks, Bryce. Before doing time-consuming things like rolling back or using the ISO, I did report the problem to the Feedback Hub and they acknowledged receiving it. Plus, if need be, there's a way of shutting down notifications via command line, or even selecting which notifications you want via the registry.

Luckily for now, it seems that my previous settings were retained.
BryceSor 5,475 Reputation points Volunteer Moderator

2026-08-03T07:15:27.6733333+00:00

Thanks for the update and can you link your FBH back to this post incase others find the same issue and want to vote on it, thanks.
Bert22306 140 Reputation points

2026-08-04T00:42:25.5666667+00:00

Hi again. Here's the link to my Feedback Hub report:

https://aka.ms/AA12zhfb
BryceSor 5,475 Reputation points Volunteer Moderator

2026-08-04T01:13:20.6666667+00:00

Is the fault showing up in Reliability Monitor or event viewer?
Bert22306 140 Reputation points

2026-08-04T12:34:29.9566667+00:00
I think so, going from the timestamp, but I can't make heads or tails out of the content. The timestamp seems about right for the last time I tried going to the Settings > System > Notifications

I removed any personal ID entries, replacing them with xxxxxxx.

Also, my Windows version is actually 28020.2623, not 28000.2623 as it claims below.

System

Provider

[ Name] Application Error [ Guid] {a0e9b465-b939-57d7-b27d-95d8e925ff57} EventID 1000 Version 0 Level 2 Task 100 Opcode 0 Keywords 0x8000000000000000

TimeCreated

[ SystemTime] 2026-08-04T12:20:01.2085988Z EventRecordID 1742 Correlation

Execution

[ ProcessID] 18340 [ ThreadID] 15716 Channel Application Computer DESKTOP-xxxxxxxxxxxx

Security

[ UserID] S-1-5-21-xxxxxxxxxxxxxxxxx

EventData AppName SystemSettings.exe AppVersion 10.0.28000.2623 AppTimeStamp 82ac1754 ModuleName SystemSettingsViewModel.Desktop.dll ModuleVersion 10.0.28000.2623 ModuleTimeStamp 1ba2f0d8 ExceptionCode c000027b FaultingOffset 00000000000fe38a ProcessId 0x1c6c ProcessCreationTime 0x1dd240b8ee3a127 AppPath C:\Windows\ImmersiveControlPanel\SystemSettings.exe ModulePath C:\Windows\ImmersiveControlPanel\SystemSettingsViewModel.Desktop.dll IntegratorReportId df616043-e02c-45a4-b9b3-42a4861e839f PackageFullName windows.immersivecontrolpanel_10.0.8.1000_neutral_neutral_cw5n1h2txyewy PackageRelativeAppId microsoft.windows.immersivecontrolpanel
BryceSor 5,475 Reputation points Volunteer Moderator

2026-08-05T06:57:32.55+00:00

As far as I can tell the Notifications page is crashing because the build shipped a corrupted or mismatched view model DLL

Hopefully the next update for your Insider will clear this up, yes going to pervious install for this error would be a waste of time, hopefully the next update wont be far away.
Bert22306 140 Reputation points

2026-08-05T11:52:06.4533333+00:00

Could be. It bothered me to see 28000.2623 mentioned, but I thought maybe for this module, 28000 and 28020 were the same. Thanks for the help and educating me on the event viewer.

These feedbacks do work. I sent one recently on missing Edge Favorites icons, often showing just a generic globe, and that got fixed after a couple or three more value updates. Amazing how one gets used to these little extras.