This message was deleted.

Yes we have a script to fix this, ill share it later

your awaesome

What scenario are you seeing this in?

Built a test system and logged in with the same FSLOGIX profile

Yes. It occurs when after first login when you roam to a 2nd VM. Even if it’s exactly the same image. Go back to the first VM and the applications will be OK. Apparently MS is aware and working in a fix.

<#

.FUNCTIONALITY Resets Win10 start-menu left side and right-side .SYNOPSIS Left-side: Removes orphaned entries that appear randomly and when MS Store (Appx) based apps are cached inside FSLogix profiles, but removed from actual OS Right-side (tile section): performs resets based on build XML .NOTES Change log Oct 13, 2019 -Initial version Oct 15, 2019 -Amended to use $env:LOCALAPPDATA Oct 19, 2019 -Added 2nd path to remove-item Feb 25, 2020 -Improved message boxes .DESCRIPTION Author

<mailto:owen.reynolds@procontact.ca|owen.reynolds@procontact.ca> & <mailto:jonathan.pitre@procontact.ca|jonathan.pitre@procontact.ca>

.EXAMPLE

./Reset-StartMenu.ps1

.NOTES

.Link

N/A

#>

Add-Type -AssemblyName System.Windows.Forms

#Button Legend

#                  OK 0

#            OKCancel 1

#    AbortRetryIgnore 2

#         YesNoCancel 3

#               YesNo 4

#         RetryCancel 5

#Icon legend

#                None 0

#                Hand 16

#               Error 16

#                Stop 16

#            Question 32

#         Exclamation 48

#             Warning 48

#            Asterisk 64

#         Information 64

$messageBoxTitle = "Windows Start Menu Reset"

$UserResponse = [System.Windows.Forms.MessageBox]::Show("Do you want to reset the Windows Start Menu to resolve issues with missing/invalid shortcuts?" , $messageBoxTitle, 4, 32)

If ($UserResponse -eq "YES" ) {

write-host "Reseting windows left / right side Windows 10 icons/allignment"

Copy-Item -path "C:\Users\Default\AppData\Local\Microsoft\Windows\Shell\LayoutModification.xml" -Destination "$env:LOCALAPPDATA\Microsoft\Windows\Shell" -force

Remove-Item 'HKCU:\Software\Microsoft\Windows\CurrentVersion\CloudStore\Store\Cache\DefaultAccount\*$start.tilegrid$windows.data.curatedtilecollection.tilecollection' -force -recurse -ErrorAction SilentlyContinue

get-process shellexperiencehost -ErrorAction SilentlyContinue | stop-process -force -ErrorAction SilentlyContinue

write-host "Pausing for for 3 seconds..."

start-sleep -s 3

remove-item -Path "$env:LOCALAPPDATA\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\TempState\StartUnifiedTileModelCache.dat" -Force -ErrorAction SilentlyContinue

remove-item -Path "$env:LOCALAPPDATA\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\TempState\StartUnifiedTileModelCache.dat" -Force -ErrorAction SilentlyContinue

Get-Process Explorer | Stop-Process -force -ErrorAction SilentlyContinue

[System.Windows.Forms.MessageBox]::Show("Windows Start Menu was reset!", $messageBoxTitle, 0, 64)

}

Else {

Write-host "No"

Exit

}

@Jonathan Pitre nice - is that on github anywhere?

good point, nope it's not but yeah I agree with you there

Nice!

Weird, I’ve never run into this issue before.

Ok let me test tomorrow. I like the idea about a troubleshooting folder

@Robert Moore here is the script we were talking about today

You know, it didn't even dawn on me why I have never seen this - I uninstall all of those trash apps as part of my build process. 😉

Sooner that crud concept of modern apps get crushed the better

I do like the new Calculator, though. Felt kinda sad that I had to install Old Calculator for Windows 10.

How about the Snip & Sketch?? We'll lose that too 😄

Greenshot :-)

I know, I was trying to be funny

I fight a fight I won’t win - but I’ll still fight it 😜

I totally agree with you on the modern apps, it's horrible

I like the concepts of some of them - just wish they weren’t rubbish delivery like they are

How do you handle the default FTA? When I remove the UWP dumb stuff breaks like FTA

Default File Type Assocs file imported into image or driven via GPO, which ones are getting you?

I have used the SetUserFTA from Christoph Kolbicz: https://kolbi.cz/blog/2017/10/25/setuserfta-userchoice-hash-defeated-set-file-type-associations-per-user/ I have also used FSLogix App Masking ...and I plan on testing WEM again, as it now should be able to handle FTA in Windows 10, 2016 and 2019

Right now I use SCCM. I guess I can rip out all the uwp and set the FTA the way I want then import.

Probaply. I have configured the SetUserFTA as an external task in WEM, that works pretty good

I modify the OEMDefaultAssociations.xml file and just copy it to $env:WINDIR\System32 as part of my build.

Isn't that still a per machine association, and not user association?

It is, yes. If I had to do per-user FTA, I'd probably roll with SetUserFTA via WEM.

@Jonathan Pitre your awesome! Worked great!

@Cory Zaner thanks but credits goes to @Owen Reynolds since he wrote most of the script!

@Owen Reynolds thanks!

Nice! Glad to see this helped! I wrote it last year when I noted those orphaned entries popping up when an existing FSLogix user would on Win 10 1809 switched over to a Win 10 1903 build. It comes up now and then, so we published the script so users could fix the issue themselves. It's a by-product of running Citrix optimizer and left-over elements on users's FSLogix win profiles

Hello, We are experiencing a similar issue specifically highlighted by the fact the Calculator AppX disappears when a user (with a FSLogix Profile) logs into a 1809 Build, after they log into a 1709 Build. When they log back into a 1709 Build its lost. The script does not appear to restore all the modern apps especially calculator. Has anyone else experienced this?

Hey , @Phil Savage: I had similar issues with the AppX calculator, so replaced it with the following: https://winaero.com/download.php?view.1795 I will say, in general , that my experience at home / work with the MS AppX (store) apps has not been great. We also put in a registry key solution to force use of the old windows Photo viewer. The "moden" Windows Photos app is not reliable, and is slow to open, even on fast systems.

I have been wanting to rip out the appx stuff too.

At the client where I wrote the script that fixed the msresource name Bullsh**, we weren't able to remove all the windows store / Appx stuff that we wanted to . I'm going to try a more aggressive pass via Citrix optimizer on my home lab Win 10 gold image today and see what (if any) improvements are gained for UI response / logon times

@Owen Reynolds you can also try WIMwitch. With that you can do offline servicing and remove the Appx crap in the WIM file.

@Kasper Johansen That name is great!

It is :D

Anyone thinking LSTB would be better? Lol

@Cory Zaner Sometimes :p