Windows 10 Start Menu Broken

[talksr]

Another Windows 10 Problem....

 

I have a brand new, fresh Windows 10 computer, fully updated and not tampered with.

Initially, I found that calculator (which used to be accessed via Ctrl+R>calc>enter) now no longer works.

In addition to this Calender and some other apps such as mail have vanished.

 

Going back to Calculator.

If I search for it in All Apps, it is not listed, yet it is still in existence in: C:\Windows\System32\calc.exe

 

If you try and execute it, you get this:

 

I found a useful website online which covered Start Menu problems, and suggested executing the following in PowerShell:

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

 

I have tried this twice now and it has not helped.

 

Before this, I ran sfc /scannow from an elevated command prompt. I have since ran it again in System Recovery and tried chkdsk /f/r but neither are helping.

When I ran sfc /scannow from System Recovery command prompt, it said Windows Resouce Protection could not perform the requested operation.

 

My next step was to try and set up a new user account on the computer and see if it still refuses to work.

 

Has anyone came across this problem before? Could understand if this was an upgrade, but this is a bran new, fresh install, with nothing but MS Office 16 and Adobe Reader installed. Getting a little tired of all of the bugs and querks in this new OS.

[Michael]

There are probably a number of factors, including profile corruption, but I can see you've already tried creating a second user.

 

I would suggest you also have a look at Classic Shell which will save you a lot of problems.

[talksr]

There are probably a number of factors, including profile corruption, but I can see you've already tried creating a second user.

 

I would suggest you also have a look at Classic Shell which will save you a lot of problems.

 

Hello, no no not tried new user yet. Will give that a try later. I am hoping that it may solve the issue.

If it still fails, I will take a look at your Classic Shell link, otherwise I will have no option but to wipe it! It's literally two days old. M$ need to sort these issues out.

[Arthur]

Can you try running the following two commands (in the order shown below)?

 

DISM.exe /online /Cleanup-Image /RestoreHealth

 

DISM.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase

 

If this fixes the issue you are having it could be caused by a Windows update breaking the component store (as described in the following article).

 

http://deploymentbunny.com/2014/06/05/nice-to-know-get-rid-of-all-junk-before-sysprep-and-capture-when-creating-a-reference-image-in-mdt

[talksr]

Can you try running the following two commands (in the order shown below)?

 

DISM.exe /online /Cleanup-Image /RestoreHealth

 

DISM.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase

 

If this fixes the issue you are having it could be caused by a Windows update breaking the component store (as described in the following article).

 

http://deploymentbunny.com/2014/06/05/nice-to-know-get-rid-of-all-junk-before-sysprep-and-capture-when-creating-a-reference-image-in-mdt

 

Thanks very much, will give this a go in a couple of hours and let you know the result.

Everything else works perfectly, so it is a little odd. I had wondered if Windows Update may have been the cause, but didn't see any update errors. It was fine when Windows was installed - only seems to have gone funny since the updates and Office.

 

Will let you know

[talksr]

Can you try running the following two commands (in the order shown below)?

 

DISM.exe /online /Cleanup-Image /RestoreHealth

 

DISM.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase

 

If this fixes the issue you are having it could be caused by a Windows update breaking the component store (as described in the following article).

 

http://deploymentbunny.com/2014/06/05/nice-to-know-get-rid-of-all-junk-before-sysprep-and-capture-when-creating-a-reference-image-in-mdt

 

Ok, here is the result...

The first command did not work so well:

PS C:\WINDOWS\system32> dism.exe /online /Cleanup-image /Restorehealth

 

Deployment Image Servicing and Management tool

Version: 10.0.10586.0

 

Image Version: 10.0.10586.0

 

[==========================100.0%==========================]

 

Error: 0x800f081f

 

The source files could not be found.

Use the "Source" option to specify the location of the files that are required to restore the feature. For more informat

ion on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

 

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

 

The second worked very well:

PS C:\WINDOWS\system32> DISM.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase

 

Deployment Image Servicing and Management tool

Version: 10.0.10586.0

 

Image Version: 10.0.10586.0

 

[==========================100.0%==========================]

The operation completed successfully.

 

 

The start menu still seems to be broken.

The log file from the first one is quite long to post in this reply. I have put a copy of it here for your reference.

 

It would appear that the Start Menu has got even worse with four or five missing apps on the left hand side and one missing right to the Twitter tile:

Edited February 8, 2016 by talksr

[Arthur]

The log file from the first one is quite long to post in this reply. I have put a copy of it here for your reference.

Based on that log file it looks like something is corrupt (see screenshot below). Try running the following command but change the highlighted path to a .wim file from a Windows ISO.

 

Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:[color="#FF0000"]X:\sources\install.wim[/color]:1 /LimitAccess

 

http://i.cubeupload.com/MWt3CU.png

 

Did you install Windows using the latest Windows 10 ISO from VLSC?

[talksr]

Based on that log file it looks like something is corrupt (see screenshot below). Try running the following command but change the highlighted path to a .wim file from a Windows ISO.

 

Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:[color="#FF0000"]X:\sources\install.wim[/color]:1 /LimitAccess

 

http://i.cubeupload.com/MWt3CU.png

 

Did you install Windows using the latest Windows 10 ISO from VLSC?

 

Ok, will need to get my USB key with that ISO on so I can use it as a source. Can't remember when I downloaded my 10 ISO. Is there a way I can quickly establish if it is the latest?

[Arthur]

will need to get my USB key with that ISO on so I can use it as a source.

Try your USB key first since the source files would have to match the build and edition of the currently installed OS. e.g. if you used a November 2015 (build 10586) ISO to install Windows 10 Education you would need to use that as the source.

[talksr]

Try your USB key first since the source files would have to match the build and edition of the currently installed OS. e.g. if you used a November 2015 (build 10586) ISO to install Windows 10 Education you would need to use that as the source.

 

Ok, yes makes sense. I am running your command again, its on 20% and has been there for quite some time, let's see what happens! Fingers crossed.

Edited February 8, 2016 by talksr

[talksr]

I am getting the following error..

Any ideas?

 

PS C:\WINDOWS\system32> Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:L:\sources\install.wim:1 /LimitAccess

 

Deployment Image Servicing and Management tool

Version: 10.0.10586.0

 

Image Version: 10.0.10586.0

 

[==========================100.0%==========================]

 

Error: 0x800f081f

 

The source files could not be found.

Use the "Source" option to specify the location of the files that are required to restore the feature. For more informat

ion on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

 

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

 

The path its looking for is there: L:\sources\install.wim

Seems to be getting to 20% and then hanging before showing the below error and changing to 100.0%

 

Have even tried copying the sources folder locally, rather than using the USB drive, but exact same error again.

Edited February 8, 2016 by talksr

[Arthur]

The path it's looking for is there: L:\sources\install.wim

Does your .wim contain multiple images? You can check by running...

 

dism /Get-WimInfo /WimFile:"L:\sources\install.wim"

 

The index number should correspond to the edition of Windows that you have installed on the laptop. In the example below, 1 = Windows 10 Pro.

 

If yours is different that could be why the source files weren't found and the command failed.

 

dism /Online /Cleanup-Image /RestoreHealth /Source:wim:L:\sources\install.wim:[color="#FF0000"][b]1[/b][/color] /LimitAccess

 

http://i.cubeupload.com/Tj7a3q.png

Edited February 9, 2016 by Arthur

[talksr]

Does your .wim contain multiple images? You can check by running...

 

dism /Get-WimInfo /WimFile:"L:\sources\install.wim"

 

The index number should correspond to the edition of Windows that you have installed on the laptop. In the example below, 1 = Windows 10 Pro.

 

If yours is different that could be why the source files weren't found and the command failed.

 

dism /Online /Cleanup-Image /RestoreHealth /Source:wim:L:\sources\install.wim:[color="#FF0000"][b]1[/b][/color] /LimitAccess

 

http://i.cubeupload.com/Tj7a3q.png

 

Hi, thanks again for your post, no just one version, here is the result:

 

PS C:\WINDOWS\system32> dism /Get-WimInfo /WimFile:"L:\sources\install.wim"

 

Deployment Image Servicing and Management tool

Version: 10.0.10586.0

 

Details for image : L:\sources\install.wim

 

Index : 1

Name : Windows 10 Pro

Description : Windows 10 Pro

Size : 13,741,636,711 bytes

 

The operation completed successfully.

[talksr]

Interestingly, I have just ran the same command from last night, but in command prompt rather than power shell and it worked no problem:

C:\WINDOWS\system32>dism /Online /Cleanup-Image /RestoreHealth /Source:wim:L:\sources\install.wim:1 /LimitAccess

 

Deployment Image Servicing and Management tool

Version: 10.0.10586.0

 

Image Version: 10.0.10586.0

 

[==========================100.0%==========================]

The restore operation completed successfully.

The operation completed successfully.

 

Although, the tiles look the same as before even after a bounce

Edited February 9, 2016 by talksr

[talksr]

Thanks everyone for your help on this, I tried making a new account, same problem so took the decision to completely wipe it.

Can't say I am all that impressed with Windows 10 as this is another of many systems to have gone wrong. Can see why the upgraded ones could go funny, but didn't expect it with a fresh install.

 

Really hope they can get these bugs sorted asap as it is ruining a really good product.