Which version of Windows operating system am I running?

Find operating system info in Windows 10

To find out which version of Windows your device is running, press the Windows logo key + R, type winver in the Open box, and then select OK.

Here’s how to learn more:

Select the Start button > Settings > System > About .

Under Device specifications > System type, see if you’re running a 32-bit or 64-bit version of Windows.

Under Windows specifications, check which edition and version of Windows your device is running.

Related links

If you’re having a problem with activation, see Activate in Windows 10.

If you forgot the password you use to sign in to Windows devices or email, see How to reset your Microsoft password.

For info about updating Windows, see Windows Update: FAQ.

Find operating system info in Windows 8.1 or Windows RT 8.1

To find out which version of Windows your device is running, press the Windows logo key + R, type winver in the Open box, and then select OK.

If your device is running Windows 8.1 or Windows RT 8.1, here’s how to learn more:

If you’re using a touch device, swipe in from the right edge of the screen, tap Settings, and then tap Change PC settings. Continue to step 3.

If you’re using a mouse, point to the lower-right corner of the screen, move the mouse pointer up, click Settings, and then click Change PC settings.

Select PC and devices > PC info.

Under Windows you’ll see which edition and version of Windows your device is running.

Under PC > System type you’ll see if you’re running a 32-bit or 64-bit version of Windows.

Related links

If you’re having a problem with activation, see Activate Windows 7 or Windows 8.1

If you forgot the password you use to sign in to Windows devices or email, see How to reset your Microsoft password.

For info about updating Windows, see Windows Update: FAQ.

Find operating system info in Windows 7

Select the Start button, type Computer in the search box, right-click on Computer, and then select Properties.

Under Windows edition, you’ll see the version and edition of Windows that your device is running.

Support for Windows 7 ended on January 14, 2020

We recommend you move to a Windows 10 PC to continue to receive security updates from Microsoft.

Related links

If you’re having a problem with activation, see Activate Windows 7 or Windows 8.1.

If you forgot the password you use to sign in to Windows devices or email, see How to reset your Microsoft password.

For info about updating Windows, see Windows Update: FAQ.

What version of Windows am I running?

To determine if your device is enrolled in the Long-Term Servicing Channel (LTSC, formerly LTSB) or the Semi-Annual Channel (SAC) you’ll need to know what version of Windows 10 you’re running. There are a few ways to figure this out. Each method provides a different set of details, so it’s useful to learn about all of them.

System Properties

Click Start > Settings > System > click About from the bottom of the left-hand menu

You’ll now see Edition, Version, and OS Build information. Something like this:

Using Keyword Search

You can simply type the following in the search bar and press ENTER to see version details for your device.

“winver”

“msinfo” or «msinfo32» to open System Information:

Using Command Prompt or PowerShell

At the Command Prompt or PowerShell interface, type «systeminfo | findstr /B /C:»OS Name» /B /C:»OS Version» and then press ENTER

At the Command Prompt or PowerShell, type «slmgr /dlv», and then press ENTER. The /dlv command displays the detailed licensing information. Notice the output displays «EnterpriseS» as seen in the image below:

What does it all mean?

The Long-term Servicing Channel is available only in the Windows 10 Enterprise LTSB edition. This build of Windows doesn’t contain many in-box applications, such as Microsoft Edge, Microsoft Store, Cortana (you do have some limited search capabilities), Microsoft Mail, Calendar, OneNote, Weather, News, Sports, Money, Photos, Camera, Music, and Clock. It’s important to remember that the LTSC model is primarily for specialized devices.

In the Semi-Annual Channel, you can set feature updates as soon as Microsoft releases them. This servicing modal is ideal for pilot deployments and to test Windows 10 feature updates and for users like developers who need to work with the latest features immediately. Once you’ve tested the latest release, you can choose when to roll it out broadly in your deployment.

Version windows server am running

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I have a machine running Windows Server 2019.

I am trying to find out what version of Windows Defender is loaded on Windows Server 2019 but I cannot navigate to a screen that shows me the Windows Defender version.

If I click Start—>Run and type «Winver» then I know that I am running Windows Server 2019 version 1809 but I don’t know where to go to check the Windows Defender version.

Answers

If you mean the Engine version, you can check this as follows:

Settings > Windows Security > Open Windows Security > Settings button (the gear) in the lower left corner > About.

Best regards,
Leon

Blog: https://thesystemcenterblog.com LinkedIn:

Windows Server 2019 System Requirements

Applies to: Windows Server 2019

This topic outlines the minimum system requirements to run Windows ServerВ® 2019.

Review system requirements

The following are estimated system requirements Windows Server 2019. If your computer has less than the minimum requirements, you will not be able to install this product correctly. Actual requirements will vary based on your system configuration and the applications and features you install.

Unless otherwise specified, these minimum system requirements apply to all installation options (Server Core, Server with Desktop Experience, and Nano Server) and both Standard and Datacenter editions.

The highly diverse scope of potential deployments makes it unrealistic to state recommended system requirements that would be generally applicable. Consult documentation for each of the server roles you intend to deploy for more details about the resource needs of particular server roles. For the best results, conduct test deployments to determine appropriate system requirements for your particular deployment scenarios.

Processor

Processor performance depends not only on the clock frequency of the processor, but also on the number of processor cores and the size of the processor cache. The following are the processor requirements for this product:

Minimum:

• 1.4 GHz 64-bit processor
• Compatible with x64 instruction set
• Supports NX and DEP
• Supports CMPXCHG16b, LAHF/SAHF, and PrefetchW
• Supports Second Level Address Translation (EPT or NPT)

Coreinfo is a tool you can use to confirm which of these capabilities your CPU has.

The following are the estimated RAM requirements for this product:

Minimum:

• 512 MB (2 GB for Server with Desktop Experience installation option)
• ECC (Error Correcting Code) type or similar technology, for physical host deployments

If you create a virtual machine with the minimum supported hardware parameters (1 processor core and 512 MB RAM) and then attempt to install this release on the virtual machine, Setup will fail.

To avoid this, do one of the following:

• Allocate more than 800 MB RAM to the virtual machine you intend to install this release on. Once Setup has completed, you can change the allocation to as little as 512 MB RAM, depending on the actual server configuration. If you’ve modified the boot image for Setup with addition languages and updates, you may need to allocate more than 800 MB RAM in order to complete the installation
• Interrupt the boot process of this release on the virtual machine with SHIFT+F10. In the command prompt that opens, use Diskpart.exe to create and format an installation partition. Run Wpeutil createpagefile /path=C:\pf.sys (assuming the installation partition you created was C:). Close the command prompt and proceed with Setup.

Storage controller and disk space requirements

Computers that run Windows Server 2019 must include a storage adapter that is compliant with the PCI Express architecture specification. Persistent storage devices on servers classified as hard disk drives must not be PATA. Windows Server 2019 does not allow ATA/PATA/IDE/EIDE for boot, page, or data drives.

The following are the estimated minimum disk space requirements for the system partition.

Minimum: 32 GB

Be aware that 32 GB should be considered an absolute minimum value for successful installation. This minimum should allow you to install Windows Server 2019 in Server Core mode, with the Web Services (IIS) server role. A server in Server Core mode is about 4 GB smaller than the same server in Server with a GUI mode.

The system partition will need extra space for any of the following circumstances:

• If you install the system over a network.
• Computers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump files.

Network adapter requirements

Network adapters used with this release should include these features:

Minimum:

• An Ethernet adapter capable of at least gigabit throughput
• Compliant with the PCI Express architecture specification.

A network adapter that supports network debugging (KDNet) is useful, but not a minimum requirement.

A network adapter that supports the Pre-boot Execution Environment (PXE) is useful, but not a minimum requirement.

Other requirements

Computers running this release also must have the following:

• DVD drive (if you intend to install the operating system from DVD media)

The following items are not strictly required, but are necessary for certain features:

UEFI 2.3.1c-based system and firmware that supports secure boot

Trusted Platform Module

Graphics device and monitor capable of Super VGA (1024 x 768) or higher-resolution

Keyboard and MicrosoftВ® mouse (or other compatible pointing device)

Internet access (fees may apply)

A Trusted Platform Module (TPM) chip is not strictly required to install this release, though it is necessary in order to use certain features such as BitLocker Drive Encryption. If your computer uses TPM, it must meet these requirements:

• Hardware-based TPMs must implement version 2.0 of the TPM specification.
• TPMs that implement version 2.0 must have an EK certificate that is either pre-provisioned to the TPM by the hardware vendor or be capable of being retrieved by the device during the first boot.
• TPMs that implement version 2.0 must ship with SHA-256 PCR banks and implement PCRs 0 through 23 for SHA-256. It is acceptable to ship TPMs with a single switchable PCR bank that can be used for both SHA-1 and SHA-256 measurements.
• A UEFI option to turn off the TPM is not a requirement.

Update Windows Server containers

As part of servicing Windows Server each month, we publish updated Windows Server Base OS container images on a regular basis. With these updates, you can automate building updated container images or manually update them by pulling the latest version. Windows Server containers don’t have a servicing stack like Windows Server. You can’t get updates within a container like you do with Windows Server. Therefore, every month we rebuild the Windows Server Base OS container images with the updates and publish the updated container images.

Other container images, such as .NET or IIS, will be rebuilt based on the updated Base OS container images and published monthly.

How to get Windows Server container updates

We update Windows Server Base OS container images in alignment with the Windows servicing cadence. Updated container images are published the second Tuesday of each month, which we sometimes refer to as our «B» release, with a prefix number based on the release month. For example, we call our February update «2B» and our March update «3B.» This monthly update event is the only regular release that include new security fixes.

The server hosting these containers, called the container host or just the «host», can be serviced during additional update events other than «B» releases. To learn more about the Windows update servicing cadence, see our Windows update servicing cadence blog post.

New Windows Server Base OS container images go live shortly after 10:00am PST on the second Tuesday of each month in the Microsoft Container Registry (MCR), and the featured tags target the most recent B release. Some examples include:

• ltsc2019 (LTSC): docker pull mcr.microsoft.com/windows/servercore:ltsc2019
• 1909 (SAC): docker pull mcr.microsoft.com/windows/servercore:1909

If you’re more familiar with Docker Hub than MCR, this blog post will give you a more detailed explanation.

For each release, the respective container image also gets published with two additional tags for the revision number and the KB article number for targeting specific container image revisions. For example:

• docker pull mcr.microsoft.com/windows/servercore:10.0.17763.1040
• docker pull mcr.microsoft.com/windows/servercore:1809-KB4546852

These examples both pull the Windows Server 2019 Server Core container image with the February 18 security release update.

For a complete list of Windows Server Base OS container images, versions, and their respective tags, see this Windows Base OS container images on Docker Hub.

Monthly serviced Windows Server images released on Azure Marketplace by Microsoft also come with preinstalled Base OS container images. Find our more at our Windows Server Azure Marketplace pricing page. We usually update these images about five working days after the «B» release.

For a complete list of Windows Server images and versions, see Windows Server release on Azure Marketplace update history.

Host and container version compatibility

There are two types of isolation modes for Windows containers: Process isolation and Hyper-V isolation. Hyper-V isolation is more flexible when it comes to host and container version compatibility. To learn more, see Version compatibility and Isolation Modes. This section will focus on process-isolated containers unless stated otherwise.

When you update your container host or container image with the monthly updates, as long as the host and container image are both supported (Windows Server version 1809 or higher), the host and container image revisions don’t need to match for the container to start and run normally.

However, you might encounter issues when using Windows Server containers with the February 11, 2020 security update release (also called «2B») or later monthly security update releases. See this Microsoft Support article for more details. These issues resulted from a security change that required an interface between user mode and kernel mode to change to ensure the security of your applications. These issues only happen on process isolated containers because process isolated containers share the kernel mode with the container host. This means container images without the updated user mode component were unsecured and incompatible with the new secured kernel interface.

We’ve released a fix as of February 18, 2020. This new release has established a «new baseline.» This new baseline follows these rules:

• Any combination of hosts and containers that are both before 2B will work.
• Any combination of hosts and containers that are both after 2B will work.
• Any combination of hosts and containers on different sides of the new baseline won’t work. For example, a 3B host and a 1B container won’t work.

Let’s use the March 2020 monthly security update release as an example to show you how these new compatibility rules work. In the following table, the March 2020 security update release is called «3B,» the February 2020 update is «2B,» and the January 2020 update is «1B.»

Host	Container	Compatibility
3B	3B	Yes
3B	2B	Yes
3B	1B or earlier	No
2B	3B	Yes
2B	2B	Yes
2B	1B or earlier	No
1B or earlier	3B	No
1B or earlier	2B	No
1B or earlier	1B or earlier	Yes

For reference, the following table lists the version numbers for Base OS container images with 1B, 2B, and 3B monthly security update releases across different major OS releases from Windows Server 2016 to the latest Windows Server, version 1909 release.

Windows Server version (floating tag)	Update version for 1/14/20 release (1B)	Update version for 2/18/20 release (2B)	Update version for 3/10/20 release (3B)
Windows Server 2016 (ltsc2016)	10.0.14393.3443 (KB4534271)	10.0.14393.3506 (KB4546850)	10.0.14393.3568 (KB4551573)
Windows Server, version 1803 (1803)	10.0.17134.1246 (KB4534293)	10.0.17134.1305 (KB4546851)	This version has reached end of support. For more information, see Base image servicing lifecycles.
Windows Server, version 1809 (1809)	10.0.17763.973 (KB4534273)	10.0.17763.1040 (KB4546852)	10.0.17763.1098 (KB4538461)
Windows Server 2019 (ltsc2019)	10.0.17763.973 (KB4534273)	10.0.17763.1040 (KB4546852)	10.0.17763.1098 (KB4538461)
Windows Server, version 1903 (1903)	10.0.18362.592 (KB4528760)	10.0.18362.658 (KB4546853)	10.0.18362.719 (KB4540673)
Windows Server, version 1909 (1909)	10.0.18363.592 (KB4528760)	10.0.18363.658 (KB4546853)	10.0.18363.719 (KB4540673)

Troubleshoot host and container image mismatches

Before you start, make sure sure to get familiar with the information in Version compatibility. This information will help you figure out whether your issue was caused by mismatching patches. When you’ve established mismatching patches as the cause, you can follow the instructions in this section to troubleshoot the issue.

Query the version of your container host

If you can access your container host, you can run the ver command to get its OS version. For example, if you run ver on a system that runs Windows Server 2019 with the latest Feb 2020 security update release, you’ll see this:

The revision number in this example displays as 1039, not 1040, because the Feb 2020 security update release didn’t have an out-of-band 2B release for Windows Server. There was only an out-of-band 2B release for containers, which had a revision number of 1040.

If you don’t have direct access to your container host, check with your IT admin. If you’re running on the cloud, check the cloud provider’s website to find out what container host OS version they’re running. For example, If you are using Azure Kubernetes Service (AKS), you can find the host OS version in the AKS release notes.

Query the version of your container image

Follow these instructions to find out which version your container is running:

Run the following cmdlet in PowerShell:

The output should look something like this:

Run the docker inspect command for the Image ID of the container image that isn’t working. This will tell you which version the container image is targeting.

For example, let’s say we run docker inspect for an ltsc 2019 container image:

In this example, the container OS version shows as 10.0.17763.1039 .

If you’re already running a container, you can also run the ver command within the container itself to get the version. For example, running ver in a Server Core container image of Windows Server 2019 with the latest Feb 2020 security update release will show you this: