Settings app crashes accessing "Focus Assist" settings

Question

Hi,

I'm experiencing the following issue on a system I just fully reinstalled (i.e. including a reformat of the HDD; I'm now running build 17134.228).

Every time I try to access the "Focus Assist" settings in the Settings app, it just dies.

Any clue?

Answer 1

Thank you, that did it for me.

Answer 2

That indeed was the problem. Thanks. It is working now. But has anyone figured out how to get Avast to turn it back when once it turns it off?

We don't really know if Avast is the problem, but so far no one has complained who doesn't have it. That being said, in the Avast settings (open it, go to Menu , Settings, Components, scroll down the page until Performance, Do Not Disturb Mode, then Customize) there is a setting called "Silence notifications from 3rd-party apps". By default it's on, I turned it off. Maybe it helps.

Answer 3

That indeed was the problem. Thanks. It is working now. But has anyone figured out how to get Avast to turn it back when once it turns it off? I'm assuming it is turning it off when I run games in a new window, but it should turn it back on automatically once I exit the game.  I'm upgrading Avast manually now, hopefully that will keep the problem from coming back.

Answer 4

I'm running Avast 18.7.2354 (build 18.7.4041.0) on Windows 10 version 1809 build 17763.55, with the following services:

PS> get-service | ? { $_.DisplayName -match 'Windows Push' } | ft -auto

Status  Name                  DisplayName

------  ----                  -----------

Stopped PushToInstall         Windows PushToInstall Service

Running WpnService            Windows Push Notifications System Service

Running WpnUserService_155def Windows Push Notifications User Service_155def

and everything works fine for now:

• notification icon is "dark with white outline" when there are 0 notifications pending
• Settings app doesn't crash when I do "right-click / Go to Settings" on the "Focus Assist" tile in Action Center

Answer 5

Haven't seen that issue yet in RS5/1809/October 2018 Update...