After you update MTR from a release earlier than 4.4.41.0, a small subset of MTR may experience an issue that affects the Microsoft Store deployment engine in which the application does not start. All systems that are recovered by using any version of this tool are expected to work correctly. However, you may have a situation in which a system that is running an earlier build of MTR (for example, a new deployment of hardware that was pre-installed with a previous version) stops working when you try to update to MTR release 4.4.41.0 or later. In this case, you can download this PowerShell script, and then run the following PowerShell command:
Run powershell -executionpolicy unrestricted .\MTRemediate-4.4.63.0.ps1
Notes
- If you are running the script from the SYSTEM context, you will have to pass the
-Arm switch after the script file name to explicitly request arming.
- If the script is not in the same path as your current working directory, you will have to specify an appropriate path to the script file. It's permitted to run the file from a network share (the script will automatically copy itself locally to the computer that it's run on).
- The
-Disarm switch can be used after the script file name to explicitly request that the script undo the changes it usually makes when it arms. In the unlikely event that the script gets stuck or otherwise does not clean up a system from the armed state, you can use this switch to force the clean up to run again.
The computer will restart multiple times, and the process will take 10-45 minutes to finish. Any of the following conditions indicates that the system process is finished:
- 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 output for the tool 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 a 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 10, version 1909 or 1903, re-run the script by using the following PowerShell script:
powershell -executionpolicy unrestricted .\MTRemediate-4.5.35.0.ps1 -Uninstall
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 this tool, it’s possible that your system is in an unrecoverable state. In this case, you may have to reimage it by using a recovery image that’s provided by the device OEM.
For additional help, contact your customer service representative to help identify and resolve the problem. Make sure that you provide the log output of this tool when you request support.
Still need help? Go to Microsoft Community.