Forum Discussion
Windows Virtual Desktop Agent Upgrade Failed
alhenriq_msHere is the version of the bootloader as requested.
PS C:\Windows\system32> Get-WmiObject -Class Win32_Product | Where-Object{$_.Name -eq "Remote Desktop Agent Boot Loader"
}
IdentifyingNumber : {A38EE409-424D-4A0D-B5B6-5D66F20F62A5}
Name : Remote Desktop Agent Boot Loader
Vendor : Microsoft Corporation
Version : 1.0.0.0
Caption : Remote Desktop Agent Boot Loader
When you say that the version 2548.x is in production, isn't supposed to be that version offered in the link by Microsoft? But, the download link points to the 2195.x!
Thank you
Microsoftsimonsays_pt - Hi
"...When you say that the version 2548.x is in production, isn't supposed to be that version offered in the link by Microsoft? But, the download link points to the 2195.x!..."
No. WVD Agents are updated typically in a monthly cadence. And, VMs are auto-updated. Once the updated agent reaches stability over all regions, which can take sometime, the link is then updated
For your issue I feel the quickest mitigation is to rebuild the VM (remove the VM from the hostpool) and uninstall the bootloader and agent and re-install the components. Once you install 2195.x in 5-10 minutes your agent should begin to auto-update.
thank you,
-al
alhenriq_msHello again.
I did what you've suggested, but the issue remains the same.
The upgrade fail as before, with the same error.
I also tried to uninstall the two versions of the agent, I manage to get the msi of the 2548.xxxx version and then installed it, but the agent reported it's still the version 2195.xxxx.
What can I do more? Can I disable the automatic update of the agent? Is that even possible?
- alhenriq_ms
simonsays_pt - Hi
If the bootloader is failing to load the latest agent - could mean the os image you have is missing some external dependency...have you tried re-imaging your VM? I assume you are using Windows (Windows 10 Enterprise for Virtual Desktops) image.
The agent failing to update should not be interrupting the ability for your users to connect to your VM - or interrupt users connections on your VM.
I think you should create an incident - service engineers can quickly guide you through some preliminary troubleshooting steps.
Hello,
I've finally managed to understand that the method failing is related to .Net Framework installation.
So in this case, our VM has the .NET 4.6 installed and in this case it requires the .NET upgrade to the 4.8 version.
After that, the service RDAgent Bootloader started correctly with the wvd agent version 1.0.2548.6500.Problem solved!
