startmenu in windows 10 build 10586 not working

[ryan1980]

The start menu in windows 10 build 10568 is not working doe somebody have a solucion for this issue.

[DalekSec]

The start menu in windows 10 build 10568 is not working doe somebody have a solucion for this issue.

 

Need a bit more information that its not working, have you tried updating it today with all the updates yesterday might sort it out.

[ryan1980]

It's already full updated , if you click on the startmenu i does not open. i already did a sfc /scanow in powershell

i removed the profiles. I ran this command: Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

in the powershell as well. butt still it is not working . it is a windows 10 buil 10586 version that im using

[Arthur]

Is this on a home PC or one which you have imaged from a modified or sysprep'd .wim?

[ryan1980]

this is a computer at work that is connected on a network use. yes i made a image of it with sysprep d.wim files

[mrwoberts]

I've seen this behaviour before and spent hours trying all kinds of fixes, but ultimately had to re-install Windows 10 !!

[mrwoberts]

You could attempt to rollback/system restore..

[Arthur]

yes I made a image of it with sysprep d.wim files

Did you create the image on a physical PC or VM?

[ryan1980]

i created it on a physical machine

[Arthur]

i created it on a physical machine

I would try re-creating the image in a VM since you can rule out any issues cause by the physical PC then (and it's best practice anyway!).

 

https://technet.microsoft.com/en-us/itpro/windows/deploy/create-a-windows-10-reference-image

 

The reference image described in this documentation is designed primarily for deployment to physical machines. However, the reference image is created on a virtual platform, before being automatically run through the System Preparation (Sysprep) tool process and captured to a Windows Imaging (WIM) file. The reasons for creating the reference image on a virtual platform are the following:

 

• You reduce development time and can use snapshots to test different configurations quickly.
  
• You rule out hardware issues. You simply get the best possible image, and if you have a problem, it's not likely to be hardware related.
  
• It ensures that you won't have unwanted applications that could be installed as part of a driver install but not removed by the Sysprep process.
  
• It's easy to move between lab, test, and production.
  

[DJ-1701]

I did have an issue with a AppLocker at one point which disabled me from opening the Start Menu, also Search and the Notification Area. If you have that setup and having the same problems, it might be worth isolating to test if this could be causing the issue.

[Arthur]

The start menu in windows 10 build 10568 is not working does somebody have a solution for this issue.

Which version of build 10586 are you using? I noticed the Start Menu is mentioned on the Windows 10 update history website for 10586.122.

 

http://windows.microsoft.com/en-us/windows-10/update-history-windows-10

 

1 March 2016 — KB3140743 (OS Build 10586.122)

This update includes quality improvements. No new operating system features or security fixes are being introduced in this update. Key changes include:

 

• Improved reliability in numerous areas, including OS and Windows Update installation, startup, installing and configuring Windows for the first time, authentication, resuming from hibernation, shutdown, kernel, Start menu, storage, Windows Hello, display modes, Miracast, AppLocker, Internet Explorer 11, Microsoft Edge browser, network connectivity and discovery, and File Explorer.
  

[Arthur]

As @DJ-1701 mentioned, the issue might be caused by the Group Policies you are applying to your Windows 10 PCs.

[mrwoberts]

I've seen this on two home PCs, so I think Microsoft broke something around March time. The only difference I've noticed is that both those home PCs were in-place upgrades from 7.

 

EDIT: You could try uninstalling KB3140743 (as @Arthur pointed out, there are changes to the start menu)

Edited May 12, 2016 by mrwoberts

[Arthur]

You could try uninstalling KB3140743 (as Arthur pointed out, there are changes to the start menu)

Unless not installing KB3140743 (or the latest cumulative update) is the cause?

 

If the image was created with the February 2016 (build 10586.104) install media from VLSC and not updated, it won't contain the Start Menu fixes in KB3140743.

 

The lack of information makes it difficult to diagnose the cause.