2 Replies Latest reply on Mar 28, 2016 6:57 PM by solgaeDK

    Windows 10 Microsoft Edge broken after logoff and login with Writable Volumes

    solgaeDK Enthusiast

      I am currently evaluating Windows 10 build 1511 with App Volumes 2.10 and Horizon View 6.2.2. When I assigned a Writable Volume (UIA+Profile) and logged in, everything seemed fine. On my second or third login, however, I noticed that Microsoft Edge browser crashes shortly after launch - specifically it crashes when News feed from the start page was about to show up. I could get the browser to not crash by browsing quickly to the other site, but I also found that the settings weren't being saved probably as well, nor is it feasible to do ti every time.

       

      Further troubleshooting yielded that my profile lost all registration to AppX packages. When I ran Get-AppXPackage right after writable volume is created, I can see whole bunch of packages that are registered, including Microsoft Edge. Upon second or third login, however, running the same cmdlet results in empty list.

       

      To fix it, I had to run the following command on an elevated powershell window:

      Get-AppxPackage -AllUsers -Name Microsoft.MicrosoftEdge | foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" -Verbose}

       

      After that, Get-AppXPackage will show the Microsoft Edge being registered, and Edge no longer crashes on launch.

       

      To get back all the list of packages that was registered before, I use this command:

      Get-AppxPackage -AllUsers | Where-Object {$_.InstallLocation -like '*WINDOWS\SystemApps*' -or $_.InstallLocation -like '*Program Files\WindowsApps*' } | foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" -Verbose}

       

      However, upon logoff and login, all the AppX package registration goes away, and I have to manually run the command again.

       

      This is not too feasible since even putting in the Logon Script, I can't guarantee the user won't try to launch the browser before the script kicks in.


      Anyone else having this issue and any suggestions?