This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 48%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EO%3C/text%3E%3C/svg%3E)
I downloaded Windows Server 2025 Eval to test it out prior to making the commitment to convert my 2016 Essentials server ahead of the January 2027 deadline. I performed a clean-install and tested it out - everything I wanted to do worked fine, so I decided to convert.
Instead of upgrading, I decided to clean-install Windows Server 2025 Standard, re-create the users/devices from my 2016E server, and port over the data; I have a small number of users/devices so it seemed like the cleanest option. I installed 2025 Standard using the installation disk that came with my license. The installation seemed to go fine, but when I checked out the security set-up Windows Security was not installed. In fact, the software for the app was nowhere to be found in the installation - Powershell commands to install it gave errors saying that it could not be found. I even searched with the Search Tool - no luck.
I was under the impression that Windows Security came standard in 2025 Standard. The Eval version had it (that was one of the things I checked). Is it possible I had a bad install? Did I miss answering an installation question about it (I don't recall that when I installed the Eval version)? Can Windows Security be installed as a standalone app? If so, where would I get the installation package? Other ideas? I can do the reinstall, but I don't want to make the same mistake again if I missed something. I guess that, worse case, I could use the Eval version to install and convert it to Standard.
Thanks!
Hi @Scott Nguyen ,
Thanks for your response. The PowerShell command confirms that the Antivirus is not running. I have also used a PowerShell command to turn on the antivirus (Install-WindowsFeature -Name Windows-Defender), but I receive an error that the app name is not valid. Also, Defender does not show up as a feature in Server Manager. This is very weird, which is why I am wondering if I had a bad install.
Any other ideas?
Thanks!
Hi @Scott Nguyen ,
Thanks for your response. The PowerShell command confirms that the Antivirus is not running. I have also used a PowerShell command to turn on the antivirus (Install-WindowsFeature -Name Windows-Defender), but I receive an error that the app name is not valid. Also, Defender does not show up as a feature in Server Manager. This is very weird, which is why I am wondering if I had a bad install.
Any other ideas?
Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 86%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESN%3C/text%3E%3C/svg%3E)
Hi, the core Microsoft Defender Antivirus engine is built into Windows Server 2025 Standard and runs actively in the background. So personally, I think you did not miss any configuration prompts during setup.
You can confirm if the Antivirus is running by execute the command in PowerShell:
Get-MpComputerStatus | Select-Object AMRunningMode, AntivirusEnabled, AntivirusSignatureLastUpdated
If AntivirusEnabled is True, you’re protected, just without the GUI.
And since you already confirmed that the Evaluation edition included Windows Security on the same machine, I would not convert the Evaluation installation to Standard just to work around this.
