RDP connection not established. Message in Portal: the agent for virtual computers is not ready

Question

RDP connection not established. Message in Portal: the agent for virtual computers is not ready

Stefan Imhof 0

after increasing diskspace for VM. I ran as suggested by Co-Pilot with Mini Tool partition wizard the partitioning. After assigning the full 256GB (C: 56GB E: 200GB) I confirmed the change and then it asked to restart, Which I the also confirmed.

Now it seems that the agent for virtuall computing is not ready. As the messages says.

After 15' I tried alread to reastart now multiple times. Benutzerbild

Adithya Prasad K 1,395 Zuverlässigkeitspunkte Externe Microsoft-Mitarbeiter Moderator

2026-06-30T22:22:13.7333333+00:00
Hi Stedfanb,

Thank you for sharing the details and screenshot.

Based on the current portal message, the VM is running, but the Azure VM Agent is reporting as Not Ready. Since the issue started after increasing the disk size and performing partition changes inside the guest OS, we should first confirm whether the Windows OS is booting properly and then repair the VM Agent/RDP path accordingly.

Please follow the below steps:

Take a snapshot of the OS disk before making any further changes.

Go to VM → Boot diagnostics and review the screenshot/serial log to confirm whether Windows is booting to the login screen or stuck in recovery/boot failure.

Perform a full Stop and Start of the VM from Azure portal, not only Restart.

If the issue persists, run Redeploy + Reapply from Help / Support + troubleshooting.

If the VM boots but the agent remains unhealthy, use Serial Console to check and start the below services:

RdAgent

WindowsAzureGuestAgent

WindowsAzureTelemetryService

Validate connectivity from the VM to Azure WireServer:

168.63.129.16 on port 80

168.63.129.16 on port 32526

Collect the below logs for further analysis:

C:\WindowsAzure\Logs\WaAppAgent.log

C:\WindowsAzure\Logs\TransparentInstaller.log

If Boot diagnostics shows Windows Recovery/boot failure, we may need to perform offline OS disk repair using a repair VM, as the partitioning activity may have impacted the boot/OS volume configuration.

Once the VM Agent becomes healthy, we can proceed with RDP validation and, if required, reset the RDP configuration or password from the Azure portal.
Stefan Imhof 0 Zuverlässigkeitspunkte

2026-07-02T16:47:36.5833333+00:00

I did all this steps (1.-4.) already before. Nevertheless I repeated the steps 1.-4.

unfortunately Redeploy is running and running. After 1h I stopped the process because I got told so be CoPilot when I asked if that long runtime is normal.

I assumed that Reapply doesn't make any sense.

I will now again run the ReDeploy for 15'

then ReApplied

Still no connection possible.

I do not try to execute Step 5.

thanks for any help

Ihre Antwort

Adithya Prasad K 1,395 Zuverlässigkeitspunkte Externe Microsoft-Mitarbeiter Moderator

2026-06-30T22:22:13.7333333+00:00

Hi Stedfanb,

Thank you for sharing the details and screenshot.

Based on the current portal message, the VM is running, but the Azure VM Agent is reporting as Not Ready. Since the issue started after increasing the disk size and performing partition changes inside the guest OS, we should first confirm whether the Windows OS is booting properly and then repair the VM Agent/RDP path accordingly.

Please follow the below steps:

Take a snapshot of the OS disk before making any further changes.

Go to VM → Boot diagnostics and review the screenshot/serial log to confirm whether Windows is booting to the login screen or stuck in recovery/boot failure.

Perform a full Stop and Start of the VM from Azure portal, not only Restart.

If the issue persists, run Redeploy + Reapply from Help / Support + troubleshooting.

If the VM boots but the agent remains unhealthy, use Serial Console to check and start the below services:

RdAgent

WindowsAzureGuestAgent

WindowsAzureTelemetryService

Validate connectivity from the VM to Azure WireServer:

168.63.129.16 on port 80

168.63.129.16 on port 32526

Collect the below logs for further analysis:

C:\WindowsAzure\Logs\WaAppAgent.log

C:\WindowsAzure\Logs\TransparentInstaller.log

If Boot diagnostics shows Windows Recovery/boot failure, we may need to perform offline OS disk repair using a repair VM, as the partitioning activity may have impacted the boot/OS volume configuration.

Once the VM Agent becomes healthy, we can proceed with RDP validation and, if required, reset the RDP configuration or password from the Azure portal.
Stefan Imhof 0 Zuverlässigkeitspunkte

2026-07-02T16:47:36.5833333+00:00

I did all this steps (1.-4.) already before. Nevertheless I repeated the steps 1.-4.

unfortunately Redeploy is running and running. After 1h I stopped the process because I got told so be CoPilot when I asked if that long runtime is normal.

I assumed that Reapply doesn't make any sense.

I will now again run the ReDeploy for 15'

then ReApplied

Still no connection possible.

I do not try to execute Step 5.

thanks for any help