Click here to Skip to main content
Click here to Skip to main content

Getting Operating System Version Info - Even for Windows 8!

By , 20 Nov 2012
 
OSVersionInfo

Introduction

I was looking for a way to determine the version of the operating system my program was running under. When I Googled it, I got a lot of code hits, but they all had the same problem: They were not updated for Windows 7. 

Also, all of them had the same two shortcomings:

  1. They didn't include all available Windows editions (especially the absence of "Professional" bothered me as that is the operating system edition I normally use)
  2. I wanted to know if the operating system was 32 bit or 64 bit, and none of the solutions I found correctly determined that. Much more on that later...

Background

I found this article http://www.csharp411.com/determine-windows-version-and-edition-with-c/ and that was in my opinion the best and most updated version. So I decided to simply amend that code and add the things that were missing.

Please note: ALL CREDIT FOR THE ORIGINAL CODE GOES TO "TIMM", THE AUTHOR OF THE ABOVEMENTIONED ARTICLE...

Changes Made By Me

  1. I added "Windows 7" and "Windows Server 2008 R2" to the detection scheme.
  2. I added all the missing Windows editions I could find.
  3. Completely rewrote the 32/64 bit detection code.

Using the Code

The class I came up with is very easy to use. Just include the CS file in your project (or compile it to a DLL for use in your VB project), and query the properties like this:

StringBuilder sb = new StringBuilder(String.Empty);
sb.AppendLine("Operation System Information");
sb.AppendLine("----------------------------");
sb.AppendLine(String.Format("Name = {0}", OSVersionInfo.Name));
sb.AppendLine(String.Format("Edition = {0}", OSVersionInfo.Edition));
if (OSVersionInfo.ServicePack!=string.Empty)
sb.AppendLine(String.Format("Service Pack = {0}", OSVersionInfo.ServicePack));
else
sb.AppendLine("Service Pack = None");
sb.AppendLine(String.Format("Version = {0}", OSVersionInfo.VersionString));
sb.AppendLine(String.Format("ProcessorBits = {0}", OSVersionInfo.ProcessorBits));
sb.AppendLine(String.Format("OSBits = {0}", OSVersionInfo.OSBits));
sb.AppendLine(String.Format("ProgramBits = {0}", OSVersionInfo.ProgramBits));

textBox1.Text = sb.ToString();

Points of Interest

The big problem with this was actually the detection of whether or not your OPERATING SYSTEM is 32 or 64 bits. As mentioned, I found a lot of suggestions to how this could be detected, but none of them worked properly. For those who are interested and for the sake of learning/sharing information, I'll list the different suggestions here:

  1. Using the IntPtr size

    The most popular method seems to be variations on this:

    return IntPtr.Size * 8;

    But this doesn't actually return the Bit architecture of the OS, it returns the bit value for the running program. So for programs running in 32 bit mode on 64 bit Windows, the above code will return 32.

  2. Using the 'PROCESSOR_ARCHITECTURE' Environment variable:
    string pa = Environment.GetEnvironmentVariable("PROCESSOR_ARCHITECTURE");
    return ((String.IsNullOrEmpty(pa) || String.Compare(pa, 0,
        "x86", 0, 3, true) == 0) ? 32 : 64);

    This is actually very misleading, because the result of this is exactly the same as version 1: It doesn't return the PROCESSOR bit architecture as the name says, but the bit architecture of the running program. For programs running in 32 bit mode on 64 bit Windows, the above code will ALSO return 32.

  3. Using PInvoke and GetSystemInfo

    Please note: To keep the article at a reasonable length, I'm not including the Structure declarations and the PInvoke API declarations... They can be found in the source code.

    ProcessorArchitecture pbits = ProcessorArchitecture.Unknown;
    try
    {
    SYSTEM_INFO l_System_Info = new SYSTEM_INFO();
    GetSystemInfo(ref l_System_Info);
    switch (l_System_Info.uProcessorInfo.wProcessorArchitecture)
    {
    case 9: // PROCESSOR_ARCHITECTURE_AMD64
    pbits = ProcessorArchitecture.Bit64;
    break;
    case 6: // PROCESSOR_ARCHITECTURE_IA64
    pbits = ProcessorArchitecture.Itanium64;
    break;
    case 0: // PROCESSOR_ARCHITECTURE_INTEL
    pbits = ProcessorArchitecture.Bit32;
    break;
    default: // PROCESSOR_ARCHITECTURE_UNKNOWN
    pbits = ProcessorArchitecture.Unknown;
    break;
    }
    }
    catch
    {
    Ignore 
    }
    return pbits;

    Once again, I was disappointed. This code - despite the presence of the processor specific flags - ALSO returned the bits of the running program, not the OS and not the processor.

  4. Using PInvoke and GetNativeSystemInfo

    I read somewhere that the above was not to be trusted (as I had already discovered), and that you should use the GetNativeSystemInfo API instead.

    The code is exactly the same as the above, but GetSystemInfo is replaced by GetNativeSystemInfo, and the same in the API declaration.

    NOW I got another result. But alas, it seemed that this API actually returns the bit architecture of the processor itself. And I was interested in the OS bit architecture. You can easily have a 32 bit windows version running on a 64 bit processored machine.

    So I was still not done.

    After A LOT of research, I found the method I decided to use in the class:

  5. A combination of IntPtr.Size and IsWow64Process:
    static public SoftwareArchitecture OSBits
    {
    get
    {
    SoftwareArchitecture osbits = SoftwareArchitecture.Unknown;
    
    switch (IntPtr.Size * 8)
    {
    case 64:
    osbits = SoftwareArchitecture.Bit64;
    break;
    
    case 32:
    if (Is32BitProcessOn64BitProcessor())
    osbits = SoftwareArchitecture.Bit64;
    else
    osbits = SoftwareArchitecture.Bit32;
    break;
    
    default:
    osbits = SoftwareArchitecture.Unknown;
    break;
    }
    
    return osbits;
    }
    }
    
    private static IsWow64ProcessDelegate GetIsWow64ProcessDelegate()
    {
    IntPtr handle = LoadLibrary("kernel32");
    
    if (handle != IntPtr.Zero)
    {
    IntPtr fnPtr = GetProcAddress(handle, "IsWow64Process");
    
    if (fnPtr != IntPtr.Zero)
    {
    return (IsWow64ProcessDelegate)Marshal.GetDelegateForFunctionPointer((IntPtr)fnPtr,
        typeof(IsWow64ProcessDelegate));
    }
    }
    
    return null;
    }
    
    private static bool Is32BitProcessOn64BitProcessor()
    {
    IsWow64ProcessDelegate fnDelegate = GetIsWow64ProcessDelegate();
    
    if (fnDelegate == null)
    {
    return false;
    }
    
    bool isWow64;
    bool retVal = fnDelegate.Invoke(Process.GetCurrentProcess().Handle, out isWow64);
    
    if (retVal == false)
    {
    return false;
    }
    
    return isWow64;
    }

    If the IntPtr size is 64, then the OS MUST be 64 bits as well because you can't run a 64 bit program on a 32 bit OS.

    If the program is running as 32 bits, then the code checks the process the code runs in to determine if that's 32 or 64 bits.

    If it is 64, then the OS will be 64 bits, but the program is running as 32 bits. And if it's 32 then the OS is also 32 bits.

    In the end, I included most of these methods in the final class lib, because it can be nice to be able to distinguish between the bit architecture of the Program, the OS and the Processor.

History 

  • 2012-11-21 - Version 2.0, Added version numbers for Windows 8 & Windows Server 2012 
  • 2010-04-15 - Version 1.0, Initial release  

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

About the Author

Johnny J.
Software Developer (Senior) JC Software Solutions
Sweden Sweden
Member
Born in Copenhagen, Denmark
Have been living in Paris, France and L.A., The United States
Now live in Stockholm, Sweden
 
Started programming when I got my first VIC 20, and a few months later on Commodore 64. Those were the days!
 
Studied programming at the Copenhagen Engineering Academy
 
Professional console, winforms and webforms programming in Comal, x86 Assembler, Fortran, Pascal, Delphi, Visual Basic 3 through 6, Classic ASP, C# and VB.NET
 
I now work as Senior .NET developer building Airline Booking Systems, and have a number of projects in various states of progress to work on in the spare time...
 
PS: The cat on my profile is one of my three cats, Ramses. He's all white, odd-eyed, deaf and definitely the coolest cat there is!

Sign Up to vote   Poor Excellent
Add a reason or comment to your vote: x
Votes of 3 or less require a comment

Comments and Discussions

 
You must Sign In to use this message board.
Search this forum  
    Spacing  Noise  Layout  Per page   
BugWindows Server 2003 R2 x64 ErrormemberMember 855836922 Mar '13 - 2:33 
Great Job! But I think that don't show the correct text in Name Property if S.O. version is Microsoft Windows Server 2003 R2 x64, showing "Microsoft Windows Server 2003", without the "R2" text.
NewsImportant: All is useless in Compatibility ModememberElmue14 Jan '13 - 16:57 
Note that all information returned by OSVERSIONINFOEX is nonsense if the user has right-cliked your application (EXE) and selected a compatibility mode.
 
Example:
If your operating system is Windows 7 and the user has chosen to run your application in compatibilty mode with Windows XP, the code above will tell that the operating system is Windows XP although it really is Windows 7 (or 8)! Windows will lie to you.
 
This makes the whole code useless if you have to know on which operating system you are REALLY running!
 
Be aware of this caveat!
 
Elmü
QuestionPerfectmembernishantenet21 Nov '12 - 8:00 
But using Systeminfo command we can perform the same activity
AnswerRe: PerfectmemberJohnny J.21 Nov '12 - 19:55 
Sure, if you only need to check for your own sake.
 
The deal with my code is that you can use it in your programs and get the information programmatically so that you can e.g. enable/disable certain functionality based on what operating system the program is run on.
 
You can't do that with System Info.
Why can't I be applicable like John? - Me, April 2011
-----
Beidh ceol, caint agus craic againn - Seán Bán Breathnach
-----
Da mihi sis crustum Etruscum cum omnibus in eo!
-----
Just because a thing is new don’t mean that it’s better - Will Rogers, September 4, 1932

QuestionArticle updated!memberJohnny J.20 Nov '12 - 22:47 
I've updated the source now and added the version numbers for Windows 6 & Windows Server 2012.
 
Personally, I don't have access to any systems running the mentioned operating systems, so I haven't actually been able to test it. I'm keeping my fingers crossed that it works.
 
I haven't found any information about Windows RT, so the code is not able to detect that.
 
Please note: I've kept the Visual Studio 2008 solution and compiled it for .NET runtime 2.0 to make it usable even for older projects. You can update the solution file and or the framework version yourself and recompile it in a matter of seconds if you need to do that!
Why can't I be applicable like John? - Me, April 2011
-----
Beidh ceol, caint agus craic againn - Seán Bán Breathnach
-----
Da mihi sis crustum Etruscum cum omnibus in eo!
-----
Just because a thing is new don’t mean that it’s better - Will Rogers, September 4, 1932

AnswerRe: Article updated!memberdherrmann20 Nov '12 - 23:07 
Hi Johnny,
 
I tested it:
 
[http://img38.imageshack.us/img38/1188/osversion.png[^]]
 
Thanks!!
Regards-
Dietrich
GeneralRe: Article updated!memberJohnny J.20 Nov '12 - 23:09 
Great, so it works for Windows 8, but doesn't seem like it detects any edition. I'll look into that, because there was no info from Microsoft about that being changed.
 
Is your windows 8 version the Standard Windows 8 or is it Pro/enterprise[^]
Why can't I be applicable like John? - Me, April 2011
-----
Beidh ceol, caint agus craic againn - Seán Bán Breathnach
-----
Da mihi sis crustum Etruscum cum omnibus in eo!
-----
Just because a thing is new don’t mean that it’s better - Will Rogers, September 4, 1932

AnswerRe: Article updated!member GeekBond 25 Apr '13 - 6:35 
Johnny J. wrote:
and added the version numbers for Windows 6 ...

 
You mean Windows 8 right?
The first step in the acquisition of wisdom is SILENCE, the second is LISTENING, the third MEMORY, the forth, PRACTICE and the fifth is TEACHING others!

QuestionWindows 8 is on the road!!!memberdherrmann16 Nov '12 - 6:41 
Please could you update this like you promised...
 
Regards from Austria
Dietrich
AnswerRe: Windows 8 is on the road!!!memberJohnny J.20 Nov '12 - 22:45 
OK, I took time off to fix this, so try to test now... Wink | ;)
Why can't I be applicable like John? - Me, April 2011
-----
Beidh ceol, caint agus craic againn - Seán Bán Breathnach
-----
Da mihi sis crustum Etruscum cum omnibus in eo!
-----
Just because a thing is new don’t mean that it’s better - Will Rogers, September 4, 1932

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Permalink | Advertise | Privacy | Mobile
Web04 | 2.6.130523.1 | Last Updated 21 Nov 2012
Article Copyright 2010 by Johnny J.
Everything else Copyright © CodeProject, 1999-2013
Terms of Use
Layout: fixed | fluid