Device.hotplug False was already added.
still same issue.
will continue working on this issue in my DEV space.
Are you using writable volume? If so, are you delaying attaching appstacks with registry in svservice? If so, we had exactly the same issue and removing that entry solved it
not using any reg keys on delaying app vol.
This is strange as its happening on multiple versions of windows 10 from 1607 to 1809.
This is driving me nuts also tried using the new profile only template from appvol 2.15 same issue without the profile works fine.
Will keep chasing this down as i would like to use uia_plus_profile or Profile only but both having the same issue.
thanks in advanced
We are actually using AV 2.15 with writable volume profile only and it is working just fine after we stopped delaying on AppVolumes agent. We do have Device.hotplug False already added as well
will any of these help ?
We have seen ctfmon not running. 1803 i think is then 1st saw it. Not sure if same issue sorry.. ours is - clicking the start menu works .. but CANT type anything to search for. I think rev 1803 i saw the actual start button not working. That site mainly talks about resetting the Metro / EWP apps.
Whats 'odd' is we are running LTSB/C 2016.. so in theory we should have No apps
In Task Schedular - UNder TextServicesFramework.
- ( quote from the site ).
- Open Task Scheduler
- Go to Microsoft > Windows > TextServicesFramework
- On MsCtfMonitor, right-click and enable the task
- Restart your computer.
I have about the same setup as you and have been fighting with this issue for a while now. I finally got it working using Mandatory profiles. My writable profiles are now working perfectly.
Windows 10 Ent 1803
App Volumes 2.14.2
Validate any AppStacks you are trying to attach aren't built using < 2.13.3 templates. If so the Start Menu won't start. You will have to recreate the package using > 2.13.3 template or downgrade the AppVolumes Agent to 2.12.