MTR not installing Windows Updates on reboot

Super Contributor

We have 13 Lenovo ThinkSmart Hub 500 MTR devices and have recently discovered that they are not installing Windows Updates.


We have them configured on the domain and have internet access. We have policies for them to install the updates but, despite this, during their nightly reboot they still won't install them.


Has anyone experienced this before, or does anyone have any tips on how to force install the Windows Updates?


Worth mentioning that the MTR app itself updates fine (along with other Windows Store apps).

5 Replies

@Daniel Hudson We are experiencing the same on our Lenovo Hub 500s. We have seen it in the past on some units when it comes to .NET updates.  This time it is the 1903 updates. Some of our devices are are not passing mic audio to the far end until we reboot or install the update manually.  We have about 300 Lenovo Hub 500s and growing, so manual update pushes are not ideal. 


We opened tickets with Lenovo and Microsoft.  They have not found any issues in the logs.

This is still occurring. How about you @Daniel Hudson

@James McGuire Hi James. We found in the end it was Group Policy preventing the device from rebooting and installing updates. We changed up out policy settings for the MTR's and they're working as expected now.

@Daniel Hudson We currently are not managing the Update/Reboot times and have devices with mic issues all the time due to .NET updates waiting to install and sometimes Feature or Cumulative Updates hanging.  


Where are you managing these policies?  I am on the hardware side of life but trying to help find a solution for our overwhelming fleet of these.  Currently, we have some policies kicked out to the devices by Azure.   Are there any built in Update/Reboot times on the devices you had to bypass before adding your own policy?   


Sorry for all the questions.   

Hi James. Ours are connected to AD on-prem so get local group policy from our AD DC's. I don't control or manage group policy so sadly don't have much I can share, other than knowing it was an issue with our Windows Update policy that caused the problems.

Might be worth looking into it here: