Tracking ID: DZ_H-21Z, there is no sufficient information about the issues.

Question

Tracking ID: DZ_H-21Z, there is no sufficient information about the issues.

Sandip Khadka 40

In this tracking ID, we donot get the information about the issue and also doesnot understand how and why we should restart our vms and also there is no any shows affected vms and how do we verify that the specific vm is affected or not and if we restart then how do we know its done.

tag: Security advisories

VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-07-31T11:09:14.83+00:00
Sandip Khadka Thank you for reaching out.

To better understand your concern regarding Tracking** ID: **DZ_H-21Z, could you please provide some additional details?

Are you seeing any errors, warnings, or impact on your virtual machines?

Is your concern related to the restart recommendation mentioned in the advisory?

Have you identified any specific VMs that you believe may be affected?

Are your VMs configured with Trusted** Launch and Secure **Boot enabled?

What information are you expecting to see in the advisory that is currently missing (for example, affected VM list, validation steps, impact details, etc.)?

Once we have these details, we can better understand your scenario and provide more specific guidance.
MT 5 Reputation points

2026-07-31T13:28:28.3133333+00:00

I echo the same need for significantly more detail to accompany this announcement and am raising this with our ProDirect support team as a very poor communication failure. The announcement needs to clearly reference the CVE, at a minimum, so we can understand what is at stake. My company runs life-critical services, and we don’t know whether we need to perform emergency maintenance immediately or can schedule it, because we have no idea what the issue is or the attack vector so that we can assess our risk. This announcement is an example of what NOT to do when communicating with customers, Microsoft.
VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-08-04T17:08:31.0633333+00:00

Sandip Khadka could you please share the requested information to assist you further ?
Sandip Khadka 40 Reputation points

2026-08-05T04:47:28.61+00:00
@VEMULA SRISAI Please find the below answer.

Are you seeing any errors, warnings, or impact on your virtual machines?
Ans: NO

Is your concern related to the restart recommendation mentioned in the advisory?
Ans: NO

Have you identified any specific VMs that you believe may be affected?
Ans: If i go to the affected resources, it shows nothing, so I have no idea that our VMs was affected or not.

Are your VMs configured with Trusted** Launch and Secure **Boot enabled? Ans: All of our resources are enabled this feature.

What information are you expecting to see in the advisory that is currently missing (for example, affected VM list, validation steps, impact details, etc.)? Ans:

Affected VM list

Validation steps like it only said restart your VM but how do we know that our VMs are affected or not and also if we restart then it will patch or not.
VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-08-05T23:14:34.9066667+00:00

Sandip Khadka Thanks for sharing the details.

1 answer

Your answer

VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-07-31T11:09:14.83+00:00

Sandip Khadka Thank you for reaching out.

To better understand your concern regarding Tracking** ID: **DZ_H-21Z, could you please provide some additional details?

Are you seeing any errors, warnings, or impact on your virtual machines?

Is your concern related to the restart recommendation mentioned in the advisory?

Have you identified any specific VMs that you believe may be affected?

Are your VMs configured with Trusted** Launch and Secure **Boot enabled?

What information are you expecting to see in the advisory that is currently missing (for example, affected VM list, validation steps, impact details, etc.)?

Once we have these details, we can better understand your scenario and provide more specific guidance.
MT 5 Reputation points

2026-07-31T13:28:28.3133333+00:00

I echo the same need for significantly more detail to accompany this announcement and am raising this with our ProDirect support team as a very poor communication failure. The announcement needs to clearly reference the CVE, at a minimum, so we can understand what is at stake. My company runs life-critical services, and we don’t know whether we need to perform emergency maintenance immediately or can schedule it, because we have no idea what the issue is or the attack vector so that we can assess our risk. This announcement is an example of what NOT to do when communicating with customers, Microsoft.
VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-08-04T17:08:31.0633333+00:00

Sandip Khadka could you please share the requested information to assist you further ?
Sandip Khadka 40 Reputation points

2026-08-05T04:47:28.61+00:00

@VEMULA SRISAI Please find the below answer.

Are you seeing any errors, warnings, or impact on your virtual machines?
Ans: NO

Is your concern related to the restart recommendation mentioned in the advisory?
Ans: NO

Have you identified any specific VMs that you believe may be affected?
Ans: If i go to the affected resources, it shows nothing, so I have no idea that our VMs was affected or not.

Are your VMs configured with Trusted** Launch and Secure **Boot enabled? Ans: All of our resources are enabled this feature.

What information are you expecting to see in the advisory that is currently missing (for example, affected VM list, validation steps, impact details, etc.)? Ans:

Affected VM list

Validation steps like it only said restart your VM but how do we know that our VMs are affected or not and also if we restart then it will patch or not.
VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-08-05T23:14:34.9066667+00:00

Sandip Khadka Thanks for sharing the details.

Answer 1

Klaas 6

Microsoft answered a few things in a support case, but there is still conflicting information, even one week after the first public announcement, key facts as communicated a couple of hours ago:

The issue is embargoed, so no details until that ends, end date unclear.

The security issue is rated "Important" on the microsoft scale: https://www.microsoft.com/en-us/msrc/security-update-severity-rating-system

A soft reboot (as in a reboot from within the guest, not via API) is sufficient to address this issue

Impacted resources does not change, it's a static snapshot of VMs that need to be rebooted from last week.

Checking from the guest side: If your VM was rebooted after August 3rd it's safe.

I have asked them to update their security advisory to correctly reflect the as-is status...

Klaas 6 Reputation points

2026-08-25T15:10:49.8133333+00:00

The advisory text was updated last week. However support informed me that for windows you also need to install:

Windows Server 2022: KB5123303

Windows 11 Enterprise, versions 25H2 and 24H2: KB5123607

Windows 11 Enterprise, versions 25H2 and 24H2 — Additional update for devices where the Pluton security processor has been configured as the TPM: KB5123273

And the advisories are now public:

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-6726

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-6727