Why did my application restart automatically during patching, and how can I avoid losing unsaved work?

Modified on Mon, 30 Jun at 4:51 PM

FAQ: Why did my application restart automatically during patching, and how can I avoid losing unsaved work?


Answer:
Some applications require a restart to complete the patching process. If such applications are running when a patch is deployed, they may restart automatically, which can result in unsaved work being lost if users are not notified in advance.

To help prevent this, Saner CVEM displays a warning icon with a message in the Missing Patches section:
"Applying this patch will trigger an automatic application restart for the changes to take effect."



This warning helps IT administrators identify patches that might cause interruptions, so they can take proactive steps like informing users to save their work ahead of time.


Examples of Applications That May Restart During Patching:

  • Google Chrome

  • Mozilla Firefox

  • Visual Studio and etc


Recommended Actions:

  • Check for restart warnings in the Missing Patches section before deploying patches.

  • Notify affected users in advance so they can save their work.

  • Schedule patch jobs during off-hours or maintenance windows to minimize disruption.

By taking these precautions, you can ensure patching is smooth and does not impact end-user productivity.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article