Broken Start Menu - even in 1607

[FragglePete]

I'm getting a few machines that appear to have complete broke start menus. ie. Press Start and nothing happens. I can however right click and I get the Context Menu.

 

Tried sfc /scannow and that has not fixed it.

 

Even trying DISM.exe /Online /Cleanup-image /Restorehealth but this fails with a RPC error!

 

Any other tips to get this start menu back? I just amazed this is still an issue.

 

Grrrr

 

Pete

 

[Michael]

Typically Start Menu issues like you describe are down to corrupt roaming profiles, or worse still system, but generally it's a profile issue.

 

I too am surprised this is still an issue, but there's always the Classic Shell route you could explore.

[FragglePete]

Bit confused by this, as it is really random. Even logging in locally as an administrator shows no Start Menu. I've got one room here with five PCs in, Start is ok on only two out of the five PCs !!!!

 

Pete

[Michael]

I feel your pain and the reality is if it's confusing you, it will your end users too.

 

I'm not quite sure why Microsoft can't get this right? As I say, the Classic Shell method is consistent/reliable and manageable. I have it deployed to over 1000 devices overall.

 

Latest templates/guidance you can find here

[FragglePete]

This is turning into something major now. We're getting a 'lot' of these machines with this issue.

 

On downloading the Microsoft Start Menu diagnostics tool, we get the following errors:

 

[TABLE=class: info]

[TR]

[TD]

[TABLE=class: info]

[TR]

[TD=class: title]Required applications are not

installed correctly.

[/TD]

[TD]Not fixed

[/TD]

[TD]res://sdiageng.dll/error.png

[/TD]

[/TR]

[/TABLE]

[/TD]

[/TR]

[TR]

[TD=class: content]"Microsoft.Windows.ShellExperienceHost" and

"Microsoft.Windows.Cortana" applications need to be installed correctly.

[/TD]

[/TR]

[/TABLE]

 

But the damn think won't fix it.

 

Now, we're trying to work out what has caused this. And we think it's when we pushed out the latest .MSU updates remotely!!!!!!! (KB3176934 & KB3176936). Some are ok, but the MAJORITY are not!!!! Machines that didn't switch on remotely do not have this issue. If we apply this update manually it does not seem to affect things. Can't work out an exact pattern.

 

We've imaged 555 machines!!!! Panic is setting in a bit!

 

Pete

[Michael]

If the only difference is 1607 RTM and 1607 + August Update, then I'd agree with you, it's possible this update has broken something.

 

Look at the positives - you've identified an issue now, rather than deploying the September Update (in future) in the middle of a term.

 

Depending how you deployed the update, you might be able to roll it back.

[FragglePete]

I've tried an uninstall on KB3176934 but this did not resolve it.

 

Won't let me uninstall KB3176936

 

We're are seriously looking re-imaging to a basic level in time for their return, we have little over a week!

 

Pete

[Michael]

Or you could look at Classic Shell - definitely a lot easier/quicker and you can remove it afterwards if need be, if deployed via an MSI.

 

Your workstations themselves are probably OK, this is an App issue by the looks of things causing Start to not work correctly.

[Arthur]

we're trying to work out what has caused this.

Are you using Microsoft's Windows 10 .wim as is or did you customise it e.g. by removing apps?

[jonbd]

I've had this happen randomly on 2 computers. 1 that I set up last week and did it randomly at some point as I was installing software. That was using Enterprise LTSB iso. Tried all sorts but couldn't fix it so wiped it and started again and it didn't come back. The second one was at home with the Pro version .iso that i've been running since Win 10 was released. Tried loads of stuff again but no luck. Didn't fancy starting from scratch on this one so installed Classic Shell, which works, except for right clicking on icons in the taskbar which does nothing. I will definitely be holding off on rolling Windows 10 out to the school until I can work out whats going on.

[FragglePete]

Are you using Microsoft's Windows 10 .wim as is or did you customise it e.g. by removing apps?

 

Base ISO of 1607, Office installed and Windows allowed to update. Sysprep'd and captured. During the MDT sequence we run a script that removes all the Apps.

 

We have these two KBs now part of the MDT sequences and the machines deploy no issues. It's just then machines we did at the Start of August and sent the two .MSU down remotely and installed the updates. I tested before on a bunch of machines and we noticed no issues, it just appears random as to why it works on some and not on others - but I believe it's has something to do with those updates.

 

We're now planning what is possible in the time we have.

 

So frustrating. Been testing Windows 10 for months with no issues, spent hours and hours working on GPOs, SPP, GPPs, etc - just got it to how we wanted. Tested on a number of staff machines and the feedback was really positive. But this, it just beggars belief.

 

Pete

[abaxter2]

I had this same problem with that start menu not doing anything and had to rebuild all the devices with an updated image to include all the latest cumulative updates - I found that even if the latest update is installed it does not fix this issue on all my device :-( the real pain is that the only way you know if there is this problem with the start menu is to sign in! I can confirm tho that from my site any device that had cumulative update KB3176495 included with the build image does not have the start menu issue.

 

I can also confirm the issue is with any build that did not have cumulative update KB3176495 installed as part of MDT or base image - if cumulative update KB3176495 was installed as part of MDT or included in the base image the start menu should not have this issue - well that what I am seeing so far.

 

The latest build with cumulative update KB3176934 and service update KB3176936 seem to be a big improvement and stable.

 

One last thing my insider box got another cumulative update last night so keep an eye on patch Tuesdays if your still building devices as still not sure if the WSUS issue of windows update task in MDT has been fixed!

Edited August 26, 2016 by abaxter2

[FragglePete]

I'm currently working my through all the machines to test. It's odd, we've got a whole building that has updated and no issues with the start menu. And we also have machines around the school with including whole suites were start menu is borked! I can sit here and see if I can fix it, but by the looks of all the forums and support sites I could be banging my head against the wall and wasting time.... or.... just get on with it. The school is coming back in a phases, we could plan what we need to do first and get those done. It's going be a new kind of record!

 

Pete

[Winner]

I've got this with our 1607 VDI gold master. Image works with initial 1607 build but when I install the latest cumulative updates the start menu breaks.

 

Fortunately I can roll back to an earlier snapshot to get things working again but I'm stuck on the current patch level until Microsoft release an update that doesn't break the start menu.

[FragglePete]

So, after take a number of long deep breaths, making a cup of tea and I started last night working through the school remotely (the wonders of Teamviewer and Impero). Thankfully this has not affected as many devices as I had feared, but it has affected a lot and I'm working my way through. To break it down, this has been what has happened:

 

 

• PCs re-imaged using MDT with the captured PC that was built the new 1607 update. This had Office 2016 installed, windows updates at the time done, sysprep'd, capture and a task sequence done which does a number of tweaks, including removing the unwanted apps. This was deploying generally very well and we pushed ahead. This was all based on a lot of testing, re-creating GPOs, etc specifically for Windows 10 done over the last six months.
  
• Did start noticing issues with login in giving messages User Profile Service service failure, but it seemed only a few at a time.
  
• Some staff were coming in and signing on with no issues overall so was happy with it so far.
  
• Noticed WSUS wasn't updating machines correctly and that's when we discovered known issue that had been addressed with these two KBs.
  
• Added these to our MDT sequence, but by this time we are 500 machines done with less 100 to go.
  
• Used the BCX Manager that we have to initiate a package task that used wusa.exe to apply each of these fixes remotely. Tested on a number of machines - no problems, then sent it all the machines in our Sixth form, again no problems. Decided to send it to the whole site so initiated a WOL where possible or went around and powered on each machine where we could to let this update.
  
• Noticed a problem with a teacher machine that I logged into and noticed we have a broken start menu. Start randomly checking machines around site and start finding more and more PCs have this problem, whereas others don't.
  
• Panic.... a little - disable the package tasks.
  
• Only machines that updated remotely using wusa.exe are affected. In some cases both KBs had been applied, some it was only the first. Again, can't quite work out why some have and some haven't been affected.
  
• Start process of testing machines, rebuilding where necessary.
  
• Applying these two KB manually as I go and all goes well doing this with machines that have working start menus.
  
• 1607 with these patches does seem better..... however, I do on occasion get a black screen with cursor after a domain login. So, that needs looking at.
  

 

Times like these I wonder why.... somebody a Microsoft needs to give the developer(s) of the Start Menu a bloody good kicking.

 

Onwards......

 

Pete

[Winner]

Had another go with these updates, I manually installed KB3176936, restarted and the start menu works. I then tried the cumulative update KB3176934 and the start menu broke. Rolled back, installed KB3176936 and then the prior cumulative update (kb3176495). Start Menu broken again. I have managed to find an error in the event log under Applications and Service Logs\Microsoft\Windows\Apps. Event ID 5985: ActivateApplicationForContractByAppIdAsUserWithHost of the app Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App for the Windows.Launch contract failed with Install failed. Please contact your software vendor..

 

Checked to see if permissions had changed under C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy after the update but it doesn't look they have. Hopefully someone at Microsoft is aware of this and it will be fixed in the next update.

[FragglePete]

I've spent the weekend and today going through what damage has been caused, and thankfully of the 550 odd devices that we've deployed this has affected some 50 odd devices in total. So we're just getting on and getting it sorted. Should be back to were we where by tomorrow afternoon I reckon.

 

On some helpful investigation from the gents Burconix it would appear that a number of these updates we pushed out 'timed out', failed or we initiated a restart before it had finished we then proceeded to Fubar several of our installs.

 

It happens.... got it sorted, moved on. What annoys me that there seems no way to fix this start menu when there are issues; even the 'official' Microsoft diagnostic tool for the start menu can't fix it.

 

Pete

[popcron13]

Hello. I don't have this Start menu problem, but I have Cortana&Search bug after same update. For me, temporary fix was: Command Prompt(Admin) -> enter --powershell-- -> enter -- Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} -- with Windows Firewall and Windows Update activated. Maybe it works better for you (y)

[Wang2be]

We just finished imaging 3000 student laptops last week. I stumbled on 1 yesterday that start menu wasn't working. Today we have found that majority of our student machines don't have start menu, edge, settings, etc (which is how I stumbled on this post). Anyone found a fix that works for this? We have 1 week until school starts... do we re-image... or do we put in a ticket with Microsoft....

 

Can't uninstall KB3176936, can't repair it... repairing systemapps doesn't seem to work either. Found that newly imaged machines with KB3176936 in the image work just fine...