To enable powerful meeting experiences across the hybrid workplace, we’ve been working to deliver new features and experiences across our shared space devices. Updates for these device experiences ar...
Updated Jan 26, 2021
Version 3.0
Blog Post
I've noticed a particular behavior when updating the room systems manually using the SRS deployment kit, and I'm hoping someone can shed some light on it. Here are the steps that I perform (and I've done this with both the 4.5.37.0 and the 4.6.20.0 updates just for testing purposes):
1. Download the latest SRSDeployment kit and run the installation.
2. Once installed, copy the $oem$ folder to C:\TEMP (just to keep the PS command short)
3. Run the following command in an elevated PS window: Add-AppxPackage -ForceApplicationShutdown -Path 'C:\Temp\$oem$\$1\Rigel\x64\Ship\AppPackages\*\*.appx' -DependencyPath (Get-ChildItem 'C:\Temp\$oem$\$1\Rigel\x64\Ship\AppPackages\*\Dependencies\x64\*.appx' | Foreach-Object {$_.FullName})
4. Wait about 5 minutes or so, then reboot the MTR system.
5. After the reboot the system has the latest version of the MTR application.
Now for the issue:
Go into the admin account and most of the time (not always but very often) the right-click menu will open, but if an item is clicked, the MTR application will start and if the process is killed, it will restart until its allowed to run.
So for example, if I need to adjust a display setting, I would be unable to do so by right-clicking on the desktop and selecting "Display Settings" as the act of selecting display settings would close the right-click menu, and launch the MTR application (within the administrator account).
Thoughts on this?
This is compute independent (I have confirmed on a NUC and an HP Slice), and also appears to be version independent.