Broken Start Menu after May 2017 Updates?

[FN-GM]

Hello,

 

We have had a new machines with a broken start menu after the May 2017 updates. You press it and nothing happens.

 

If I right click the desktop and click personalization I get this error:

 

MS-settings:personalization-background

 

This file does not have a program associated with it for performing this action. Please install a program or. if one is already installed, create an association in the default programs control.

 

Running the below doesn't help

 

sfc /scannow

Dism.exe /online /Cleanup-Image /StartComponentCleanup

Dism.exe /Online /Cleanup-Image /RestoreHealth

 

Others suggested installing Windows Update but they are fully patched.

 

Any ideas please?

 

Thanks

[Snoochieboochies]

Not sure if it is a similar problem but a staff member brought a laptop in with a Start Menu issue a couple of days ago. It seemed to be an issue with the user, rather than the OS so i just created a new user for him.

[FN-GM]

Does it for all users here.

[Chuckster]

I've had identical problems once MS updates were applied back in Jan and Feb of this year, and I found no real solution other than the alternative of performing a complete rebuild of the affected workstation(s).

[Snoochieboochies]

Not the same issue then.

[Garacesh]

Are you using a mandatory profile?

Have you modified it recently?

When I started fiddling with Windows 10, the Start Menu was one of the things that would break if you logged in with the account used to create the mandatory profile.

 

Last I knew of you've got to faff about with loading/unloading registry hives to make modifications without breaking stuff.

[FN-GM]

All local profiles here, default profile is not modified.

[timbo343]

Are there any errors in the eventviewer?

 

We used to get this with some EXEs on the start menu, it was like the imported file association list wasn't working as it should, so i sat and made sure all the known file extensions and associations were listed - we only had a few to start with.

 

Since then, not a single problem.

[mikkydoos]

Win10 ? @FN-GM

[FN-GM]

The event viewer is moaning about a DCOM, will track that down shortly.

It is windows 10.

[gaz350b]

See my theory thread on this. Are you removing modern Apps?

 

@FN-GM don't you use LTSB still?

 

Are we all removing modern apps?

[FN-GM]

We are on LTSB. Not removing anything from the LTSB image.

 

It is a pain!

[FN-GM]

Did anyone manage to fix this please?

[gaz350b]

Other than a reimage no fix yet. We rolled out June's updates and unless it's gone unreported we haven't had any further issues.

[FN-GM]

This is happening after the June update as well! Argh!

[RTi78]

Manual update to 1703 will fix this..