Your device will restart in -2147483648 minutes

Asher Jebbink
2 min readAug 29, 2023

Updated 2023/11/29 — Microsoft have managed to reintroduce this bug into the Intune Management Extension. In my testing, version 1.72.115.0 is affected.

Updated 2023/10/03 — ̶t̶h̶i̶s̶ ̶h̶a̶s̶ ̶b̶e̶e̶n̶ ̶f̶i̶x̶e̶d̶ ̶i̶n̶ ̶I̶n̶t̶u̶n̶e̶ ̶M̶a̶n̶a̶g̶e̶m̶e̶n̶t̶ ̶E̶x̶t̶e̶n̶s̶i̶o̶n̶ ̶v̶e̶r̶s̶i̶o̶n̶ ̶1̶.̶7̶1̶.̶1̶1̶1̶.̶0̶

While testing an Intune Win32 application deployment I was presented with a restart warning popup that said the device would restart in ‘minus’ minutes:

After confirming this was repeatable with any application that forced a restart after installation, I discovered in IntuneManagementExtension.log this oddity:

Hint: the restart deadline has been set to a time that is in the past.

After much, much, much troubleshooting by myself and with Microsoft, we discovered that the permissions on the following registry key is the culprit: HKLM\Software\Microsoft\IntuneManagementExtension\RebootSettings

Standard users (non-admins) do not have read access on this key. When trying to determine the restart deadline, the Intune Management Extension fails to read data from that registry key and is unable to account for the users time zone in its calculation. Interestingly, this bug only affects users with a time zone greater than UTC+0 and where the restart deadline on the application is less than their time zone difference. For example: those of us in Australia who are UTC+10 (at this time of the year), a restart deadline less than 10 hours triggers this bug.

Administrators are unaffected and manually giving users read permissions on the key resolves the issue.

Microsoft will address this bug in a future release of the Intune Management Extension but as of writing version 1.69.111.0 is the latest and is still affected.

--

--