SNMP OID sysdescr for windows 10 returns version 6.3 but supposed to be 10.0 RRS feed

  • Question

  • I get windows information by SNMP on "" for windows 10, it get back version 6.3 instead of 10.0. This is crucial if you want monitor Windows 10 via SNMP to know which version is installed.

    . = STRING: "Hardware: Intel64 Family 6 Model 44 Stepping 2 AT/AT COMPATIBLE - Software: Windows Version 6.3 (Build 10240 Multiprocessor Free)".

    6.3 is for Windows 8 or Windows server 2012

    Do you have any suggestion about this? Or can you show us how to get the correct version number of windows 10?

    If there is no solution to this problem, I want to confirm if it is a bug of windows 10, or how can I report a bug for windows 10 at microsoft official web site.

    Friday, October 16, 2015 2:22 AM

All replies

  • What version number to you get if you run ver locally from cmd?

    Are all of your Windows 10 systems still on 10240?

    Friday, October 16, 2015 3:47 PM
  • Below is the result of snmp get result from snmputil.exe for

    D:\software\SnmpWalk>snmputil.exe get public .

    Variable = system.sysDescr.0
    Value    = String Hardware: x86 Family 6 Model 45 Stepping 7 AT/A
    Software: Windows Version 6.3 (Build 10240 Multiprocessor Free)

    Below is the command "ver" result for


    Microsoft Windows [Version 10.0.10240]

    Monday, October 19, 2015 2:10 AM
  • I tested this on several computers which is windows 10, same snmp result "6.3", and software information by "ver" command are all 10240.

    Monday, October 19, 2015 6:56 AM
  • Is this program you are using from an old RK like Windows 2000?
    Monday, October 19, 2015 6:55 PM
  • Hi Tripredacus,

    What do you mean by "from an old RK like Windows 2000"?

    It seems to be definitely a big bug. How can I report this bug to Microsoft official website?

    Tuesday, October 20, 2015 2:03 AM
  • Where does this program come from?
    Tuesday, October 20, 2015 4:55 PM
  • The snmputil.exe is a common SNMP tool you can get from Internet anywhere. Before snmp get over windows 10, you must install snmp service on that windows 10 system.

    Wednesday, October 21, 2015 3:49 AM
  • Hi Daniel,

    Thank you for the update.

    If it is convenient for you, please submit the findings through Windows Feedback.

    I will help to submit this once confirmed at my side.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact

    Thursday, October 22, 2015 5:57 AM
  • The snmputil.exe is a common SNMP tool you can get from Internet anywhere. Before snmp get over windows 10, you must install snmp service on that windows 10 system.

    Can you post a link to the program? Who makes it? What version are you using?

    Anyways, the issue could be with the program itself and not the OS.

    Thursday, October 22, 2015 4:01 PM
  • I can't post the snmputil.exe download url here. I tried the snmputil.exe version 4.0 and version 5.0, it gets "6.3" for all of them. Besides, I use other snmp tools like snmpwalk in linux as client, it also gets result "6.3" for windows 10.

    Monday, October 26, 2015 2:12 AM
  • SNMPutil.exe is from in the Sever 2000/2003/NT4 Resource Kit. I can't find this currently, so I cannot test.

    I wonder what it was replaced with, support wise...

    Monday, October 26, 2015 6:39 PM
  • Is there any solution found for this issue.

    Has an issue raised for Microsoft , so that they are ware of it?

    Thursday, December 1, 2016 11:00 AM
  • Well we still don't have specifics on the original posted question because the OP could not provide where the program he used came from. So without knowing exactly the problem, it can't be reported.

    If you have this same issue, then we can continue testing it if you can provide how to get the binary you are using and seeing this issue. But if this is indeed being caused by the program from the Server 2003 Resource Kit, I doubt it is supported to be used on a modern OS.

    Friday, December 2, 2016 7:50 PM
  • My apologies for resurrecting it, since this thread is almost two years old now, and 10 months since the last post, but it comes up near the top of search results on the subject.

    Tripredacus, SNMP is a standard protocol.  The point that the original poster was trying to make is that it doesn't matter what program you use to query SNMP - it only matters how the SNMP service responds from Windows Server 2016.

    Clearly, the server is not responding with the expected "Windows Server 10" (or maybe 10.0) and the fact that it is responding with an older version means that the server can be mis-identified as Windows Server 2012 R2 or Windows 8.1.

    I have read elsewhere that Microsoft is planning to deprecate standard SNMP use and require WMI use instead, but this would defeat the point of standards.  Yes, it is possible to OIDs and get a proper version that way, but asking the system for its "sysdescr" should yield the correct version without any special OID activities.

    See also:

    • Edited by ShadowLynx Tuesday, September 12, 2017 6:32 PM Clarified mis-identification
    Tuesday, September 12, 2017 6:31 PM