Apps appear for only one second, then disappear

OldGrantonian · 06 Feb 2018

I have Win 10 Pro. I have an account for myself, with Admin privileges. I also have an account called "Kids".

In the Kids account, I'm unable to use the "PC Settings" app, from Start > PC Settings

The app appears momentarily for no more than 1 second, then disappears.

The "Taskbar Settings" app behaves in the same way.

In my own account, with Admin privileges, both of those apps persist after launching.

What action can I take.

Thanks.

dalchina · 06 Feb 2018

Hi, the most straightforward option would be to create a new Kids account- it depends how much configuration is needed.

Otherwise, do you have a system restore point you could use, assuming this started happening recently?

You could also try re-registering the Settings app, if it's only that which is affected.
Reinstall and Re-register Apps in Windows 10 Performance Maintenance Tutorials
(search for Settings and follow instructions at the start of the section carefully, under Option 2
To Reinstall and Re-register Specific App for Current Account )

OldGrantonian · 18 Feb 2018

Thanks @dalchina.

I tried all suggestions with no success.

But a couple of nights ago, a had a very long windows update (an upgrade I think, from 1703 to 1709).

Now, all problems have been solved (including the problem of the Kids account automatically logging out immediately after logging in, which was discussed on another thread).

dalchina · 18 Feb 2018

Assuming you had suffered some Windows corruption, an upgrade (or an in-place upgrade repair install - the same procedure, essentially, but using the same build as you have installed) would resolve it.

It is a useful repair technique to be aware of (there is a tutorial).

Glad your upgrade went smoothly. Whilst these can create major difficulties, one benefit is that some problems are automatically resolved- quite different from e.g. the Win 7 series of service packs.

OldGrantonian · 18 Feb 2018

Thanks @dalchina.

As mentioned on another post, this problem disappeared after a recent Windows Update from 1703 to 1709.