If you’re asking yourself how to the check .NET version on your Windows server, you found the right guide.
Some applications require specific .net versions to run properly, and the information regarding how to find this information out is not easy to find online.
For this reason, in today’s how-to article we will discuss the best methods to find out the version of your .net on Windows server.
Please follow the steps presented here carefully to avoid causing any issues on your Windows server machine.
Want to know your Windows server .net version? Follow these methods
1. Check with PowerShell:
- Press Win+X keys on your keyboard -> choose PowerShell (Admin) from the list.
- Paste the following command import-module servermanager -> press Enter.
- On ASP.NET 3.5: run the command get-windowspackage web-asp-net -> the output will state Installed or Available.
- On ASP.NET 4.5: run the command get-windowsfeature Net-Framework-45-Code -> the output will state the install state (Installed or Available).
If your version of ASP.NET doesn’t show as installed, you can use these commands to install them:
ASP.NET 3.5: add-windowsfeature web-asp-net
ASP.NET 4.5: add-windowsfeature Net-Framework-45-Core
2. Check using the Server Manager GUI:
- Open Server Manager (usually first pinned icon inside your taskbar).
- Under the section Configure this local server -> click the option Add roles and features to start the wizard.
- Choose Role-based or feature-based installation -> click Next.
- Click Select a server from the server pool -> click Next.
- If ASP.NET 3.5 or 4.5 are installed they will be located under Web Server (IIS) -> Web Server -> Application Development.
In today’s how-to article we explored the best methods to find out what your .NET version is on your Windows server machine.
If you found this guide helpful, please let us know by using the comment section found below this article.
- Many users can’t update .NET Framework to version 4.7.1
- How to fix corrupted .NET Framework issues
- Full Fix: Windows Driver Frameworks uses too much CPU