Errors reported - A system shutdown is in progress

Michał Smereczyński 20 MVP

Hi,

I see deployment overall status for number of Azure VMs (Windows Server 2022 DC Azure Edition-based custom image), manual update, as Failed, where updates installed is 4 out of 4. The problem is, that VMs are being restarted during the update and because of that the update status is probably not delivered to Update Manager properly:

"1 errors reported. The latest 3 errors are shared in details. To view all errors, review this log file on the machine:[C:\WindowsAzure\Logs\Plugins\Microsoft.CPlat.Core.WindowsPatchExtension\1.5.71]
"[A system shutdown is in progress.

A system shutdown is in progress.
]."

2025-02-21_15-01-58

After having this errors in history and running the assessment again, everything is OK. Machines are updated, but I have a bunch of Fails in statistics but this, in fact, is not true.

2025-02-21_15-35-57

It is also showing in summary statistcis:

User's image

Is there any way to prevent manual updates with VM restart showing as failed?

Pranay Reddy Madireddy 2,400 Reputation points Microsoft Vendor

2025-02-21T16:58:01.23+00:00

Hi Michał Smereczyński

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

To prevent VMs from restarting during updates, you can configure the update settings to disable automatic restarts. This can be achieved by adjusting the maintenance window settings or utilizing Group Policy to control restart behavior.

check your Update Management configuration is properly set up. You can leverage the Azure Automation Update Management feature to schedule updates during off-peak hours or times of minimal disruption.

If there are problems with the agent, it might not report the update status properly. Restarting or reinstalling the agent can fix these issues.

If you have any further queries, do let us know.

If the answer is helpful, please and "Upvote it".
Michał Smereczyński 20 Reputation points MVP

2025-02-21T17:44:40.3933333+00:00

Hi @Pranay Reddy Madireddy
I don't want to disable restarts. I want them to be a part of update process if needed. Because of that I have "Restart if Needed" parameter set to true. It's possible that not restarting during update process will cause update to be uncompleted. Restart itself is not a problem for me and I'm not asking about what to do to not restart VaMs. I don't want to have "Failed" status in history if update process needed a restart.
I don't know why you are writing about AMA agent. It is not used to report updates in Update Manager. If it is AI response, change AI or don't use it.
Madugula Jahnavi 0 Reputation points Microsoft Vendor

2025-02-24T06:32:07.56+00:00

Hello Michał Smereczyński, Did you get a chance to look into update Manager Logs!
Michał Smereczyński 20 Reputation points MVP

2025-02-24T08:23:51.0533333+00:00

@Madugula Jahnavi yes, I did. It is the same. Cumulative update installed, then restart as above. Everything is ok with the updates, just "Failed" status in Update Manager history.
Madugula Jahnavi 0 Reputation points Microsoft Vendor

2025-02-24T12:15:22.4466667+00:00

Michał Smereczyński, Have you checked this https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/vm-stuck-in-failed-state?tabs=portal.
Michał Smereczyński 20 Reputation points MVP

2025-02-24T12:37:58.71+00:00

@Madugula Jahnavi link does not work.
Madugula Jahnavi 0 Reputation points Microsoft Vendor

2025-02-24T14:31:55.7666667+00:00

Michał Smereczyński, Can you check it now!

1 answer

Madugula Jahnavi 0 Reputation points Microsoft Vendor

2025-02-24T14:39:17.2366667+00:00

Hello Michał Smereczyński,

Below are the troubleshooting ways to try resolving the issue: -

Firstly, as I mentioned earlier, check all the logs to see all log entries that the deployment has created under different status scenarios.

This issue might be a transient issue and sometimes redeploy or reapply option here to make the VM updates or VM work as expected without any conflict as shown below.

Also, you can use Get-WindowsUpdateLog command to get all the VM update log entries into a log file for better understanding.

Refer https://learn.microsoft.com/en-us/powershell/module/windowsupdate/get-windowsupdatelog?view=windowsserver2025-ps MS Doc for more relevant information.

Hope this helps.

If the answer is helpful, please click Accept Answer and kindly upvote it. If you have any further questions about this answer, please click Comment.
Please sign in to rate this answer.
Michał Smereczyński 20 Reputation points MVP

2025-02-24T17:26:05.0933333+00:00

This is the second time (beside of original post) when I need to write it: there is NO PROBLEM WITH THE UPDATES. I have them installed, up, running, perfect, incredibly fast, 101% of satisfaction. The problem is that "Failed" status is showing in the history, because of restart during the update. As a Microsoft Vendor, please read the question precisely.

Madugula Jahnavi 0 Reputation points Microsoft Vendor

2025-02-25T09:13:42.61+00:00

Michał Smereczyński, I totally understand that the updates are installed successfully and working as expected, but the issue is with the 'Failed' status showing in the update history due to a restart during the update process. This can sometimes happen if Windows detects an interruption during installation but later after some time, it completes and updates the status successfully.

Michał Smereczyński 20 Reputation points MVP

2025-02-25T13:05:21.9233333+00:00

@Madugula Jahnavi I need to wait more or less than 5 days? Asking because I still see "Failed" in History. It's hard to believe, that it will change in History - it's a kind of log. Do you have any docs background for your theory?

Michał Smereczyński 20 Reputation points MVP

2025-02-25T13:09:46.96+00:00

@Madugula Jahnavi I need to wait more or less than 5 days? Asking because I still see "Failed" in History. It's hard to believe, that it will change in History - it's a kind of log. Do you have any docs background for your theory?

Madugula Jahnavi 0 Reputation points Microsoft Vendor

2025-02-25T17:05:56.0733333+00:00

Michał Smereczyński, As I added an image here, check for the event logs once by visiting windows update client path.

And also run the Windows Update troubleshooter for Windows server and you can refer here for the relevant details.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/installing-updates-features-roles/troubleshoot-windows-server-update-guidance#step-4-run-the-windows-update-troubleshooter-for-windows

Michał Smereczyński 20 Reputation points MVP

2025-02-26T13:50:27.4133333+00:00

ONCE AGAIN: there is no single update that is failing. Every single update is installed correctly. Everything works great. Every next assessment is showing proper, green status. NO PROBLEM AT ALL, beside of "Failed" status in history.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Errors reported - A system shutdown is in progress

1 answer

Your answer