Settings app crashes accessing "Focus Assist" settings

Anonymous
2018-08-24T17:37:21+00:00

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?

Windows for home | Windows 10 | Settings

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

25 answers

Sort by: Most helpful
  1. Anonymous
    2019-02-04T06:44:10+00:00

    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.

    Now you have someone reporting who doesn't use Avast.

    I'm on AVG, latest updates to all pc packages.

    Focus Assist running almost 24/7?

    When open notifications pane, nothing is there?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-11-13T10:18:43+00:00

    Indeed, your solution also solved my problem, now Skype is receiving calls again.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-09-25T05:53:37+00:00

    I also have this problem (and system is up to date)

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-09-21T20:11:37+00:00

    Same here...

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-09-21T11:33:37+00:00

    Now the problem is back.

    I wonder if the 2018-09 Cumulative Update for Windows 10 Version 1803 x64-based Systems (KB4464218), which was installed a couple of days ago, did something to cause the problem to reappear.

    Was this answer helpful?

    0 comments No comments