After a recent Dell SBE update for networking, I received file checksum critical alerts that will not clear

Question

After a recent Dell SBE update for networking, I received file checksum critical alerts that will not clear

Richard Beyer 136

This is for an Azure Local cluster with two nodes. Last weekend, I did Dell Solution Builder Extension version 5.0.2606.1616 update for Manufacturer 16G-45n0c-Intel, Model AX-760, Solution version 12.2606.1003.205, Services version 10.2606.0.7, Platform version 12.2606.0.3008 which completed successfully. After that update, I received the errors below that currently display on the update readiness check and in the Get-HealthFault command but not in the Cluster Alerts menu.

Critical

Cluster ali-azcluster

6 days ago

The file system detected a checksum error and was not able to correct it. The file(s) or folder(s) impacted are \Device\HarddiskVolume10\efd90aec7be9afd\Virtual Machines\Hyper-V\Transcribe\Virtual Machines\183F2A43-6044-444C-82F8-19C73E9BD007.VMRS

Critical

Cluster ali-azcluster

6 days ago

The file system detected a corruption on a file or folder. The file or folder has been removed from the file system namespace. The file(s) or folder(s) impacted are \Device\HarddiskVolume10\efd90aec7be9afd\Virtual Machines\Hyper-V\Transcribe\Virtual Machines\183F2A43-6044-444C-82F8-19C73E9BD007.VMRS

The VM was in a saved state and I could not get it out of that state. In order to delete it and restore from backup, I had to force it out of the saved state via PowerShell. After that, I was able to successfully delete the VM and restore it from backups.

I have manually initiated the Data Integrity Scan scheduled task on both nodes and they return successful with 0x00.

Any suggestions on how to get these critical alerts to clear so that I can proceed with this month's updates?

Thank you,

Rich Beyer

0 comments

Answer accepted by question author

Anusree Nashetty 6,715 Microsoft External Staff Moderator

Hello Richard Beyer,

Welcome to the Microsoft Q&A Platform. Thank you for posting your query here.

Based on your description, the affected VM was successfully removed and restored from backup, and the Data Integrity Scan completed successfully (0x00) on both nodes. However, the cluster continues to report critical ReFS checksum and corruption faults through Get-HealthFault, which are preventing the update readiness checks from passing.

To better understand whether the reported faults are still active or are referencing the previously affected VMRS file, could you please provide the following information:

Output of:

Get-HealthFault | Format-List *

Confirm whether the file referenced in the fault still exists by running:

Test-Path "<Affected_VMRS_Path>"

Current storage health information:

Get-VirtualDisk | ft FriendlyName,HealthStatus,OperationalStatus

Get-PhysicalDisk | ft FriendlyName,HealthStatus,OperationalStatus

Get-StoragePool | ft FriendlyName,HealthStatus,OperationalStatus

Please confirm:

Are the critical alerts still visible in Windows Admin Center?
Are they also visible in the Azure Portal Update Readiness check?
Have the cluster nodes been restarted after the VM was deleted and restored?

Please provide:

The output of Get-StorageHealthReport
A screenshot of the Update Readiness report showing the remaining critical alerts

Additionally, if available, please collect the recent ReFS operational events from the affected timeframe:

Get-WinEvent -LogName Microsoft-Windows-ReFS/Operational -MaxEvents 200

Once we receive the requested information, we can determine whether the cluster is still detecting active ReFS corruption or whether the Health Service is continuing to report a fault associated with the previously affected VMRS file.

You can share the requested logs in Private message.

Richard Beyer 136 Reputation points

2026-07-25T13:36:32.3733333+00:00
Hi Anusree,

Thank you for the response. I have attached a text file with the results of the powershell commands requested Requested Powersehell Commands.txt. Please note, I examined the event log around the timeframe of the update last week. The only ResFS events of note are the volume dismount and mount messages that occurred during the update. All are informational. No warnings or error events event logs.xml.

Regarding your questions:

Please confirm:

Are the critical alerts still visible in Windows Admin Center? Yes

Are they also visible in the Azure Portal Update Readiness check? Yes

Have the cluster nodes been restarted after the VM was deleted and restored? No

The Update Readiness report screenshot is here: Update Readiness Report.png

If I missed some piece of information requested or if you have any other questions, please let me know.

Best,

Richard
Richard Beyer 136 Reputation points

2026-07-25T20:43:07.7166667+00:00

Looks like, after 8 days in the "Critical" state, the cluster either fixed itself or decided there really wasn't still a fault. It has now reverted to a status of "Healthy" in all areas. This really is quite annoying not being able to find a reason behind the delay in reverting to healthy. The whole Azure Local process has been chasing one issue or non-issue after another. Very frustrating.
Anusree Nashetty 6,715 Reputation points Microsoft External Staff Moderator

2026-07-28T09:08:20.4266667+00:00
Hello Richard Beyer,

Thank you for the update and for providing the requested outputs.

Based on the information you've shared, it appears that the previously reported ReFS corruption-related health faults eventually cleared after the cluster completed its own health reconciliation process. The fact that:

The affected VM was removed and restored successfully.

Data Integrity Scan completed successfully on both nodes (0x00).

No additional ReFS warning or error events were generated.

The cluster health and update readiness status have now returned to Healthy.

suggests that the underlying condition was no longer being actively detected, and the Health Service subsequently cleared the corresponding faults.

I understand the frustration regarding the delay. Unfortunately, Health Service and update readiness checks do not always clear immediately following remediation. In some cases, fault resolution depends on subsequent health evaluations, background validation tasks, storage health refresh cycles, or cluster state reconciliation before the fault is removed from the active health model.

While we cannot definitively determine the exact reason for the approximately 8-day delay after the fact, the information provided indicates that:

The corruption was isolated to the previously affected VMRS file.

No ongoing ReFS corruption was detected after remediation.

The storage subsystem ultimately reported a healthy state, allowing the fault to clear automatically.

At this stage, since the health faults have cleared and the cluster is reporting a healthy status, you should be able to proceed with the planned updates.

Thank you for sharing the outcome. This information may also be helpful for other Azure Local customers who encounter similar situations where health faults persist for some time after the underlying issue has been remediated.

Please let us know if you have any further queries.

1 additional answer

Your answer

Richard Beyer 136 Reputation points

2026-07-25T13:36:32.3733333+00:00

Hi Anusree,

Thank you for the response. I have attached a text file with the results of the powershell commands requested Requested Powersehell Commands.txt. Please note, I examined the event log around the timeframe of the update last week. The only ResFS events of note are the volume dismount and mount messages that occurred during the update. All are informational. No warnings or error events event logs.xml.

Regarding your questions:

Please confirm:

Are the critical alerts still visible in Windows Admin Center? Yes

Are they also visible in the Azure Portal Update Readiness check? Yes

Have the cluster nodes been restarted after the VM was deleted and restored? No

The Update Readiness report screenshot is here: Update Readiness Report.png

If I missed some piece of information requested or if you have any other questions, please let me know.

Best,

Richard
Richard Beyer 136 Reputation points

2026-07-25T20:43:07.7166667+00:00

Looks like, after 8 days in the "Critical" state, the cluster either fixed itself or decided there really wasn't still a fault. It has now reverted to a status of "Healthy" in all areas. This really is quite annoying not being able to find a reason behind the delay in reverting to healthy. The whole Azure Local process has been chasing one issue or non-issue after another. Very frustrating.

Answer 1

Your critical ReFS checksum faults remained after deleting and restoring the saved-state VM, although both integrity scans succeeded. Because the cluster later returned to Healthy, this was stale health or readiness state, not evidence that the restored VM still contained the damaged VMRS file.

Azure Local system health checks run every 24 hours, and portal results can take another cycle to synchronize. Microsoft also documents update-related critical VM alerts that can remain after a successful update and resolve automatically after several days.

Before the next update, select Check again in Update Manager. Run a prepare-only readiness check and inspect full health-check details. Confirm physical disks, virtual disks, storage pools, and ReFS operational events remain healthy. Never bypass a Critical result. If the same file path returns after a fresh cycle, collect Azure Local diagnostic logs and open Microsoft Support, providing the SBE and solution versions, timestamps, and health output.