<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Windows 10 Start Menu in App Volumes</title>
    <link>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418165#M5678</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 03 Jan 2019 08:25:49 GMT</pubDate>
    <dc:creator>Ray_handels</dc:creator>
    <dc:date>2019-01-03T08:25:49Z</dc:date>
    <item>
      <title>Windows 10 Start Menu</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418159#M5672</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just a quick background of my environment....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Horizon 7.6&lt;/P&gt;&lt;P&gt;App Vol 2.14&lt;/P&gt;&lt;P&gt;UEM 9.14&lt;/P&gt;&lt;P&gt;Windows 10 Enterprise 1803&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I recently upgraded to Horizon 7.6 due to compatibility issues with previous version and Win10 Ent 1803.&amp;nbsp; I now have an environment that is compatible according to VMware.&amp;nbsp; I am having the same old start menu and search issues that should be resolved.&amp;nbsp; If i have app vol installed on the image then the start menu and search functions are broken.&amp;nbsp; If I just remove App Vol and recompose the pool then it works again.&amp;nbsp; It doesn't seem to be related to a writable being attached.&amp;nbsp; I tested with and without.&amp;nbsp; I also already added the line to disablehotplug as recommended by VMware.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any other ideas?&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Dec 2018 20:50:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418159#M5672</guid>
      <dc:creator>gpenunuri</dc:creator>
      <dc:date>2018-12-19T20:50:42Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 Start Menu</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418160#M5673</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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? &lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Dec 2018 08:51:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418160#M5673</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2018-12-20T08:51:50Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 Start Menu</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418161#M5674</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In UEM, create a new config file under the Personalization tab.&amp;nbsp; Select "Use a Windows Common Setting" and then choose "Windows 10 Start Menu".&amp;nbsp; I've specified a custom condition where the OS=Windows 10 for that as well.&amp;nbsp; It should then allow for your Start Menu to get populated with everything from your AppStack.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Dec 2018 20:16:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418161#M5674</guid>
      <dc:creator>MrCheesecake</dc:creator>
      <dc:date>2018-12-20T20:16:12Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 Start Menu</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418162#M5675</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Ray_handels.&amp;nbsp; I don't know why I didn't think of doing that.&amp;nbsp; I removed all of the app stacks from the user and the Start Menu works. I will narrow that down.&amp;nbsp; At least I know it works with App Vol installed and with a writable volume attached.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Dec 2018 16:04:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418162#M5675</guid>
      <dc:creator>gpenunuri</dc:creator>
      <dc:date>2018-12-21T16:04:10Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 Start Menu</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418163#M5676</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you find the corrupted appstack? Just curious to know if it is fixed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Jan 2019 07:53:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418163#M5676</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2019-01-02T07:53:03Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 Start Menu</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418164#M5677</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have the same issue. But i am working with old appstacks as well.&lt;/P&gt;&lt;P&gt;So i will check, if i can update the appstacks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interesting is...&lt;/P&gt;&lt;P&gt;it worked before, but after optimizing with the Vmware Optimizing Tool it stopped working (in my case).&lt;/P&gt;&lt;P&gt;So maybe there is something...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2019 06:54:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418164#M5677</guid>
      <dc:creator>danielkrause</dc:creator>
      <dc:date>2019-01-03T06:54:33Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 Start Menu</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418165#M5678</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2019 08:25:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418165#M5678</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2019-01-03T08:25:49Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 Start Menu</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418166#M5679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&amp;nbsp; I have since created a new app stack for that application using a Windows 10 VM and no more issues so far. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2019 15:09:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418166#M5679</guid>
      <dc:creator>gpenunuri</dc:creator>
      <dc:date>2019-01-03T15:09:42Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 Start Menu</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418167#M5680</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeah that Optimization tool does some weird things sometimes.&amp;nbsp; I ran the latest tool using the LoginVSI.com template.&amp;nbsp; I have the best results with that one.&amp;nbsp; Also make sure you add the disable hotplug parameter on the VM.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2019 15:28:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Windows-10-Start-Menu/m-p/1418167#M5680</guid>
      <dc:creator>gpenunuri</dc:creator>
      <dc:date>2019-01-03T15:28:01Z</dc:date>
    </item>
  </channel>
</rss>

