gpenunuri
Enthusiast
Enthusiast

Windows 10 Start Menu

Jump to solution

Just a quick background of my environment....

Horizon 7.6

App Vol 2.14

UEM 9.14

Windows 10 Enterprise 1803 

I recently upgraded to Horizon 7.6 due to compatibility issues with previous version and Win10 Ent 1803.  I now have an environment that is compatible according to VMware.  I am having the same old start menu and search issues that should be resolved.  If i have app vol installed on the image then the start menu and search functions are broken.  If I just remove App Vol and recompose the pool then it works again.  It doesn't seem to be related to a writable being attached.  I tested with and without.  I also already added the line to disablehotplug as recommended by VMware. 

Any other ideas? 

0 Kudos
1 Solution

Accepted Solutions
Ray_handels
Virtuoso
Virtuoso

You say when you have Appvolumes installed it doesn't work. What happens if the agent is installed and no appstacks or writables are attached?

Could it be that this is related to an appstack? Are you using UEM to capture the start menu? Did you upgrade from 17xx to 1803? Because there is a known issue with upgrading and the start menu.

View solution in original post

0 Kudos
8 Replies
Ray_handels
Virtuoso
Virtuoso

You say when you have Appvolumes installed it doesn't work. What happens if the agent is installed and no appstacks or writables are attached?

Could it be that this is related to an appstack? Are you using UEM to capture the start menu? Did you upgrade from 17xx to 1803? Because there is a known issue with upgrading and the start menu.

0 Kudos
MrCheesecake
Enthusiast
Enthusiast

In UEM, create a new config file under the Personalization tab.  Select "Use a Windows Common Setting" and then choose "Windows 10 Start Menu".  I've specified a custom condition where the OS=Windows 10 for that as well.  It should then allow for your Start Menu to get populated with everything from your AppStack.

0 Kudos
gpenunuri
Enthusiast
Enthusiast

Thanks Ray_handels.  I don't know why I didn't think of doing that.  I removed all of the app stacks from the user and the Start Menu works. I will narrow that down.  At least I know it works with App Vol installed and with a writable volume attached. 

0 Kudos
Ray_handels
Virtuoso
Virtuoso

Did you find the corrupted appstack? Just curious to know if it is fixed.

0 Kudos
danielkrause
Enthusiast
Enthusiast

I have the same issue. But i am working with old appstacks as well.

So i will check, if i can update the appstacks.

Interesting is...

it worked before, but after optimizing with the Vmware Optimizing Tool it stopped working (in my case).

So maybe there is something...

0 Kudos
Ray_handels
Virtuoso
Virtuoso

I have seen issues on the UEM forum that there seems to be an issue with running the OSOT and having a low start menu when using UEM to capture this setting.

No idea if this already has been fixed but it is worth a try to rebuild the golden image (if possible) and try and use a later version of the OSOT tool. Maybe some info on the fling forum as well?

0 Kudos
gpenunuri
Enthusiast
Enthusiast

I was able to narrow it down to an app stack that was created on a Win 7 x64 machine but made available to Windows 10.  I have since created a new app stack for that application using a Windows 10 VM and no more issues so far.

Thanks again!

0 Kudos
gpenunuri
Enthusiast
Enthusiast

Yeah that Optimization tool does some weird things sometimes.  I ran the latest tool using the LoginVSI.com template.  I have the best results with that one.  Also make sure you add the disable hotplug parameter on the VM. 

0 Kudos