Issue with PatchMyPC ScriptRunner not completing due to computer restart

[mparker]

Hi,

I just experienced an issue with a Google Chrome update that did not remove the registry key to block execution of chrome.exe from running.

The following timeline of events was retrieved from the c:\windows\ccm\logs\PatchMyPC-ScriptRunner.log and the Windows Event Viewer:

User was notified Chrome needed an update 8/27/2024 12:04:11 pm
Registry hooks set for blocking chrome.exe execution 8/27/2024 12:04:11 pm
User selected Close and Update option 8/27/2024 12:14:01 pm
Update of Chrome started 8/27/2024 12:14:23 pm
Update of Chrome finished 8/27/2024 12:14:46 pm (last log entry from PatchMyPC, log has no more data past this point)
User initiated reboot of the computer 8/27/2024 12:14:39 pm

The timeline indicates that the PatchMyPC ScriptRunner was unable to finish performing its clean-up tasks, one of which was to remove the execution block of Chrome, due to the computer rebooting.

My question is: Is this an actual possibility?

We do run all application updates along with Windows Security updates, so the above reboot might have been a Windows Security update or the User actually initiated a reboot.

Thanks

[Michael (Patch My PC)]

Hi MParker,

Yes, it is possible that the cleanup tasks don't run because of a reboot, or some other scenario that kills the scriptrunner process prematurely.

Were there any other updates that ran that required a restart?

A scenario that can happen if you use the Restart grace period, and update runs that needs a reboot, the user will get the prompt about the restart, the user chooses to reboot now, but another update already started running and gets cut off early.
Intune's Restart Grace Period Simplified - Patch My PC

[mparker]

Thanks for the quick response.  As long as we know this can happen, we will take appropriate actions.