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 35

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,890 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 0 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.

Your answer

VEMULA SRISAI 13,890 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 0 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.