Perform the following steps to resolve this issue:
-
Attach a keyboard to the unit.
-
Press the Windows key five times in rapid succession. This will bring you to the Windows logon screen, login to the Administrator account to proceed with the recovery steps.
If your MTR system operated as expected prior to the installation of the 4.4.41.0 release, but has since stopped working correctly, refer to the following link to download the PowerShell script
https://go.microsoft.com/fwlink/?linkid=21340155, then run the following PowerShell command:
Run powershell -executionpolicy unrestricted .\MTRemediate-4.5.35.0.ps1
The computer will restart multiple times, and the process will take 10 to 45 minutes to finish. You'll know that the system is finished when one of the following conditions is true:
Running the script by using the - Check flag generates a "Disarmed" message.
The log file indicates that the script finished running.
The C:\Rigel\MTRemediate.ps1 file no longer exists.
The log to trace occurred is available from the following location:
C:\Users\Skype\AppData\Local\Packages\Microsoft.SkypeRoomSystem_8wekyb3d8bbwe\LocalState\Tracing\MTRemediate\
Check this file for information about whether the remediation process is successful. If the tool encounters an unexpected problem, it should automatically generate a compressed log file in C:\Rigel\. This compressed log file will contain the traces from running the tool, in addition to other system logs.
If the tool does not automatically resolve your problem, and you are running Windows version 1903, re-run the script by using the following PowerShell script:
powershell -executionpolicy unrestricted .\MTRemediate-4.5.35.0.ps1 -Uninstall
note:
This will force a more aggressive recovery. Notice that this mode risks losing both the application settings and the diagnostic logs that the script generates in case of errors. Therefore, we do not recommend that you use this mode in typical conditions.
If your problem is not resolved by the remediation tool, it's possible that we are not aware of it, or the underlying issue might not be related to the application update. If you require additional help, contact your customer service representative to help identify and resolve the problem.
