On-Premise Windows 2019 Server Rebooting Automatically after installing MARS

Question

On-Premise Windows 2019 Server Rebooting Automatically after installing MARS

Vijay Lonkar 0

We have on-premise 2019 Windows server. This server reboots automatically.

After removing MARS, server do not reboot.

This is the third time issue has reflected. We need solution on this issue.

Suchitra Suregaunkar 11,635 Reputation points Microsoft External Staff Moderator

2026-04-07T11:25:16.0666667+00:00

Hello Vijay Lonkar

Thank you for posting your query on Microsoft Q&A platform.

We are looking into this issue and will keep you posted updates.

Thanks,

Suchitra.
Suchitra Suregaunkar 11,635 Reputation points Microsoft External Staff Moderator

2026-04-07T13:54:35.04+00:00
Hello Vijay Lonkar

If a Windows Server restarts immediately after installing or running Azure Backup with MARS, this might be an underlying OS‑level crash, most commonly triggered when VSS interacts with drivers such as antivirus, storage, or other filter drivers.

The supported resolution is to validate VSS health, update the MARS agent, configure antivirus exclusions, and collect crash dumps if the issue persists.

1. Check for unexpected restart evidence

Event Viewer → Windows Logs → System

Look for:

Kernel‑Power (Event ID 41)

BugCheck or memory dump related events This pattern is referenced in Azure Backup crash scenarios.

Verify VSS health: All writers must show Stable

vssadmin list writers

Check dump configuration

Ensure crash dumps are enabled and sufficient disk space exists.

Without a dump, reboots cannot be diagnosed.

Please look into below resolution:

Update to the latest MARS agent

Older agents are explicitly called out as problematic in multiple scenarios.

If you've already installed the agent on any machines, ensure you're running the latest agent version. Find the latest version in the portal, or download from here.

Reference: https://dori-uw-1.kuma-moon.com/en-us/azure/backup/install-mars-agent#download-the-mars-agent

Exclude MARS processes from antivirus

Microsoft documents required AV exclusions for Azure Backup components to avoid crashes/conflicts.

Reference : https://docs.azure.cn/en-us/backup/backup-azure-mabs-troubleshoot

Ensure all VSS writers are stable

VSS failures are a documented blocking condition for Azure Backup stability.

Thanks,

Suchitra.

1 answer

Your answer

Suchitra Suregaunkar 11,635 Reputation points Microsoft External Staff Moderator

2026-04-07T11:25:16.0666667+00:00

Hello Vijay Lonkar

Thank you for posting your query on Microsoft Q&A platform.

We are looking into this issue and will keep you posted updates.

Thanks,

Suchitra.
Suchitra Suregaunkar 11,635 Reputation points Microsoft External Staff Moderator

2026-04-07T13:54:35.04+00:00

Hello Vijay Lonkar

If a Windows Server restarts immediately after installing or running Azure Backup with MARS, this might be an underlying OS‑level crash, most commonly triggered when VSS interacts with drivers such as antivirus, storage, or other filter drivers.

The supported resolution is to validate VSS health, update the MARS agent, configure antivirus exclusions, and collect crash dumps if the issue persists.

1. Check for unexpected restart evidence

Event Viewer → Windows Logs → System

Look for:

Kernel‑Power (Event ID 41)

BugCheck or memory dump related events This pattern is referenced in Azure Backup crash scenarios.

Verify VSS health: All writers must show Stable

vssadmin list writers

Check dump configuration

Ensure crash dumps are enabled and sufficient disk space exists.

Without a dump, reboots cannot be diagnosed.

Please look into below resolution:

Update to the latest MARS agent

Older agents are explicitly called out as problematic in multiple scenarios.

If you've already installed the agent on any machines, ensure you're running the latest agent version. Find the latest version in the portal, or download from here.

Reference: https://dori-uw-1.kuma-moon.com/en-us/azure/backup/install-mars-agent#download-the-mars-agent

Exclude MARS processes from antivirus

Microsoft documents required AV exclusions for Azure Backup components to avoid crashes/conflicts.

Reference : https://docs.azure.cn/en-us/backup/backup-azure-mabs-troubleshoot

Ensure all VSS writers are stable

VSS failures are a documented blocking condition for Azure Backup stability.

Thanks,

Suchitra.

Answer 1

Vijay Lonkar hey and thx for stay with us at Q&A,

if server stops rebooting after removing MARS its 100 percent agent related, not random OS issue. What usually happens MARS (Azure Backup agent) installs

filter drivers

VSS integration

sched + services

if something conflicts u get crashes Windows just reboots, most common causes i have seen, bad VSS state MARS hooks into VSS hard. if VSS writers are broken > backup job triggers > boom reboot

run

vssadmin list writers

if anything not stable thats ur trigger. Outdated MARS version older builds had bugs with Server 2019

just reinstall latest agent, not upgrade. Conflict with AV / security tools seen this a lot tbh MARS + endpoint protection = random restarts.

try exclude C:\Program Files\Microsoft Azure Recovery Services Agent\ processes like cbengine.exe

corrupted install since u said its 3rd time smells like dirty reinstall, dont just uninstall/reinstall wipe it properly

uninstall MARS

check event viewer before reboot look at System log, BugCheck / Kernel-Power, u will likely see crash tied to MARS driver or VSS.

:)))))))))))))) MARS itself not stable on that box or conflicting with something most likely VSS or AV.

again if u want quick fix so.... reinstall latest + check VSS + disable AV temporarily and test

rgds,

Alex

Share via

On-Premise Windows 2019 Server Rebooting Automatically after installing MARS

1 answer

Your answer