-
Notifications
You must be signed in to change notification settings - Fork 868
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: .NET Framework 4.7 required for agent installation as a service #4841
Comments
Hi @gt97 thanks for reporting! |
I got the same issue. Cannot install the latest Agent due to this. |
is this issue resolved? having the same problem. |
Same issue on Server 2016. Agent stopped yesterday and now won't start because it says it needs .NET Framework 4.7.1, yet the Azure Pipelines Self-Hosted Windows docs say "The agent software installs its own version of .NET so there's no .NET prerequisite.". Lol. Manually installing 4.7.1 doesn't fix the issue. |
If anyone else runs into this, I installed .NET Framework 4.7.2 manually on the VM, and then I was able to ./config the agent successfully. Tried to install 4.8 first, but 4.8 kept failing with "Cannot find object or property. " |
Thanks @JoshWeepie for the feedback. I tried 4.7.1 but it did not work. Let me try 4.7.2. Thanks again. |
I think this is an issue that has to be solved, otherwise I have to keep the update agent on the agent pool unchecked because maybe the update fails. |
Getting this issue on Server 2016, .NET 4.7.1 installed, .NET 4.7.2 installed. Fix it please. |
What happened?
Installing the agent on a windows server from powershell as admin I am not able to continue the installation because framework 4.7 is required.
According to documentation (https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/windows-agent?view=azure-devops#check-prerequisites) The agent software installs its own version of .NET so there's no .NET prerequisite.
Versions
Azure Devops version 2.329.1/WIN2012
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows Server 2012
Version controll system
No response
Relevant log output
The text was updated successfully, but these errors were encountered: