Why does Windows 10 return the version number 6.3?












8















On Windows 10, the VB.NET code Environment.OS.VersionString outputs Microsoft Windows NT 6.3.9600.0. According to Microsoft documentation, Windows 10's version number is 10.0, so why does VB.NET recognise Windows 10 as Windows 8.1?



I did systeminfo | findstr /C:"OS" in Command Prompt and it returned the correct value of 10.0.10240 N/A Build 10240 under "OS Version".










share|improve this question


















  • 1





    Because it is picking up the fact you upgraded from Windows 8.1. The method you are using is looking at the registry. It is working as intended. There is a more appropriate function then using the environment variable to determine what operating system is being used. I can't provide code since this isn't Stackoverflow

    – Ramhound
    Aug 26 '15 at 1:12






  • 1





    Someone experienced the same problem in the comments here: msdn.microsoft.com/en-us/library/windows/desktop/… You need to update the manifest for your application.

    – MC10
    Aug 26 '15 at 1:13











  • You also are using it wrong. This should be over at Stackoverflow since its a coding problem and although I suspect using the environment variable is still the wrong way to go about it, the manifest file, clearly isn't right.

    – Ramhound
    Aug 26 '15 at 1:16











  • @Ramhound Yes, I thought that might have been the case. I know that after a month of upgrading to Windows 10, Windows 8.1 is removed - does that mean the version number will be correct?

    – Dog Lover
    Aug 26 '15 at 2:34











  • The version number is correct. As I said he method your using is reading the registry, which wasn't updated, and wouldn't be updated unless it was a clean install of Windows 10. Go about this task a different way, in other words, don't use the environmental variable.

    – Ramhound
    Aug 26 '15 at 2:37
















8















On Windows 10, the VB.NET code Environment.OS.VersionString outputs Microsoft Windows NT 6.3.9600.0. According to Microsoft documentation, Windows 10's version number is 10.0, so why does VB.NET recognise Windows 10 as Windows 8.1?



I did systeminfo | findstr /C:"OS" in Command Prompt and it returned the correct value of 10.0.10240 N/A Build 10240 under "OS Version".










share|improve this question


















  • 1





    Because it is picking up the fact you upgraded from Windows 8.1. The method you are using is looking at the registry. It is working as intended. There is a more appropriate function then using the environment variable to determine what operating system is being used. I can't provide code since this isn't Stackoverflow

    – Ramhound
    Aug 26 '15 at 1:12






  • 1





    Someone experienced the same problem in the comments here: msdn.microsoft.com/en-us/library/windows/desktop/… You need to update the manifest for your application.

    – MC10
    Aug 26 '15 at 1:13











  • You also are using it wrong. This should be over at Stackoverflow since its a coding problem and although I suspect using the environment variable is still the wrong way to go about it, the manifest file, clearly isn't right.

    – Ramhound
    Aug 26 '15 at 1:16











  • @Ramhound Yes, I thought that might have been the case. I know that after a month of upgrading to Windows 10, Windows 8.1 is removed - does that mean the version number will be correct?

    – Dog Lover
    Aug 26 '15 at 2:34











  • The version number is correct. As I said he method your using is reading the registry, which wasn't updated, and wouldn't be updated unless it was a clean install of Windows 10. Go about this task a different way, in other words, don't use the environmental variable.

    – Ramhound
    Aug 26 '15 at 2:37














8












8








8


1






On Windows 10, the VB.NET code Environment.OS.VersionString outputs Microsoft Windows NT 6.3.9600.0. According to Microsoft documentation, Windows 10's version number is 10.0, so why does VB.NET recognise Windows 10 as Windows 8.1?



I did systeminfo | findstr /C:"OS" in Command Prompt and it returned the correct value of 10.0.10240 N/A Build 10240 under "OS Version".










share|improve this question














On Windows 10, the VB.NET code Environment.OS.VersionString outputs Microsoft Windows NT 6.3.9600.0. According to Microsoft documentation, Windows 10's version number is 10.0, so why does VB.NET recognise Windows 10 as Windows 8.1?



I did systeminfo | findstr /C:"OS" in Command Prompt and it returned the correct value of 10.0.10240 N/A Build 10240 under "OS Version".







windows windows-10 vb.net






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Aug 26 '15 at 1:00









Dog LoverDog Lover

279314




279314








  • 1





    Because it is picking up the fact you upgraded from Windows 8.1. The method you are using is looking at the registry. It is working as intended. There is a more appropriate function then using the environment variable to determine what operating system is being used. I can't provide code since this isn't Stackoverflow

    – Ramhound
    Aug 26 '15 at 1:12






  • 1





    Someone experienced the same problem in the comments here: msdn.microsoft.com/en-us/library/windows/desktop/… You need to update the manifest for your application.

    – MC10
    Aug 26 '15 at 1:13











  • You also are using it wrong. This should be over at Stackoverflow since its a coding problem and although I suspect using the environment variable is still the wrong way to go about it, the manifest file, clearly isn't right.

    – Ramhound
    Aug 26 '15 at 1:16











  • @Ramhound Yes, I thought that might have been the case. I know that after a month of upgrading to Windows 10, Windows 8.1 is removed - does that mean the version number will be correct?

    – Dog Lover
    Aug 26 '15 at 2:34











  • The version number is correct. As I said he method your using is reading the registry, which wasn't updated, and wouldn't be updated unless it was a clean install of Windows 10. Go about this task a different way, in other words, don't use the environmental variable.

    – Ramhound
    Aug 26 '15 at 2:37














  • 1





    Because it is picking up the fact you upgraded from Windows 8.1. The method you are using is looking at the registry. It is working as intended. There is a more appropriate function then using the environment variable to determine what operating system is being used. I can't provide code since this isn't Stackoverflow

    – Ramhound
    Aug 26 '15 at 1:12






  • 1





    Someone experienced the same problem in the comments here: msdn.microsoft.com/en-us/library/windows/desktop/… You need to update the manifest for your application.

    – MC10
    Aug 26 '15 at 1:13











  • You also are using it wrong. This should be over at Stackoverflow since its a coding problem and although I suspect using the environment variable is still the wrong way to go about it, the manifest file, clearly isn't right.

    – Ramhound
    Aug 26 '15 at 1:16











  • @Ramhound Yes, I thought that might have been the case. I know that after a month of upgrading to Windows 10, Windows 8.1 is removed - does that mean the version number will be correct?

    – Dog Lover
    Aug 26 '15 at 2:34











  • The version number is correct. As I said he method your using is reading the registry, which wasn't updated, and wouldn't be updated unless it was a clean install of Windows 10. Go about this task a different way, in other words, don't use the environmental variable.

    – Ramhound
    Aug 26 '15 at 2:37








1




1





Because it is picking up the fact you upgraded from Windows 8.1. The method you are using is looking at the registry. It is working as intended. There is a more appropriate function then using the environment variable to determine what operating system is being used. I can't provide code since this isn't Stackoverflow

– Ramhound
Aug 26 '15 at 1:12





Because it is picking up the fact you upgraded from Windows 8.1. The method you are using is looking at the registry. It is working as intended. There is a more appropriate function then using the environment variable to determine what operating system is being used. I can't provide code since this isn't Stackoverflow

– Ramhound
Aug 26 '15 at 1:12




1




1





Someone experienced the same problem in the comments here: msdn.microsoft.com/en-us/library/windows/desktop/… You need to update the manifest for your application.

– MC10
Aug 26 '15 at 1:13





Someone experienced the same problem in the comments here: msdn.microsoft.com/en-us/library/windows/desktop/… You need to update the manifest for your application.

– MC10
Aug 26 '15 at 1:13













You also are using it wrong. This should be over at Stackoverflow since its a coding problem and although I suspect using the environment variable is still the wrong way to go about it, the manifest file, clearly isn't right.

– Ramhound
Aug 26 '15 at 1:16





You also are using it wrong. This should be over at Stackoverflow since its a coding problem and although I suspect using the environment variable is still the wrong way to go about it, the manifest file, clearly isn't right.

– Ramhound
Aug 26 '15 at 1:16













@Ramhound Yes, I thought that might have been the case. I know that after a month of upgrading to Windows 10, Windows 8.1 is removed - does that mean the version number will be correct?

– Dog Lover
Aug 26 '15 at 2:34





@Ramhound Yes, I thought that might have been the case. I know that after a month of upgrading to Windows 10, Windows 8.1 is removed - does that mean the version number will be correct?

– Dog Lover
Aug 26 '15 at 2:34













The version number is correct. As I said he method your using is reading the registry, which wasn't updated, and wouldn't be updated unless it was a clean install of Windows 10. Go about this task a different way, in other words, don't use the environmental variable.

– Ramhound
Aug 26 '15 at 2:37





The version number is correct. As I said he method your using is reading the registry, which wasn't updated, and wouldn't be updated unless it was a clean install of Windows 10. Go about this task a different way, in other words, don't use the environmental variable.

– Ramhound
Aug 26 '15 at 2:37










5 Answers
5






active

oldest

votes


















3















Because it is picking up the fact you upgraded from Windows 8.1. The method you are using is looking at the registry. It is working as intended. There is a more appropriate function then using the environment variable to determine what operating system is being used. I can't provide code since this isn't Stackoverflow




– Ramhound Aug 26 at 1:12



That's the answer in a nutshell. During the upgrade, the registry doesn't change the build number from the old to the new one. It just sticks.






share|improve this answer



















  • 2





    In other words, the upgrade doesn't work properly... Well, nothing new in the west ;)

    – Quandary
    Mar 8 '16 at 15:51



















0














So, to get back to the root question... I use Windows Management Instrumentation (WMI) to generate the Windows version number in the manner in which you are expecting. For example, it reports 10.0.10586



Here is a short code snippet



Public Class OS

' Use Windows Management Instrumentation (WMI) to get the OS version
Public Shared Function GetOSVersion() As String
Dim answer As String = ""

' add Imports System.Management and add a resource to System.Management
Dim osClass As New ManagementClass("Win32_OperatingSystem")
For Each queryObj As ManagementObject In osClass.GetInstances()
answer = DirectCast(queryObj.GetPropertyValue("Version"), String)
Next

Return answer
End Function
End Class





share|improve this answer

































    0














    That's because you were reading CurrentVersion from HKLMSOFTWAREMicrosoftWindows NTCurrentVersion and, as has already been said, that entry doesn't get updated change with Windows updates.



    The entries to check are CurrentMajorVersionNumber, CurrentMinorVersionNumber and CurrentBuildNumber, in the same key.






    share|improve this answer































      -1














      6.3 is the internal version of Windows, which reveals that since Windows 7, there have not been any major releases, contrary to what Microsoft wants you to believe. The names Windows 7, 8, 10, etc. are just marketing names. They decided to skip 9 to match Mac OS X. But the real version number is 6.3






      share|improve this answer



















      • 1





        There are many different reasons floated for why they skipped v9 (a particularly neat one was that many legacy apps would see the 9 and mistakenly think the OS was Windows 95/98 - but I don't think they've ever confirmed or denied that). That said, try to refrain from random speculation in your answers - sources are best :)

        – Mikey T.K.
        Mar 18 '16 at 19:52



















      -1














      I installed Windows 10 (anniversary edition 1607) from scratch and the currentversion registry entry also reports 6.3, but, for example, 'ver' reports 10.0.14393



      BTW 1) I read that the Windows 10 preview was 6.4



      BTW 2) I installed Windows 10 as a Hyper-V VM on Windows Server 2012 R2, but I do not think that this has to do anything with it.






      share|improve this answer


























      • "I read that the windows 10 preview was 6.4" - You read wrong. This is a comment, it does not answe the author's question, if you wish to leave a comment earn the require reputation point to do so.

        – Ramhound
        Nov 1 '16 at 13:19













      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f962796%2fwhy-does-windows-10-return-the-version-number-6-3%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      5 Answers
      5






      active

      oldest

      votes








      5 Answers
      5






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      3















      Because it is picking up the fact you upgraded from Windows 8.1. The method you are using is looking at the registry. It is working as intended. There is a more appropriate function then using the environment variable to determine what operating system is being used. I can't provide code since this isn't Stackoverflow




      – Ramhound Aug 26 at 1:12



      That's the answer in a nutshell. During the upgrade, the registry doesn't change the build number from the old to the new one. It just sticks.






      share|improve this answer



















      • 2





        In other words, the upgrade doesn't work properly... Well, nothing new in the west ;)

        – Quandary
        Mar 8 '16 at 15:51
















      3















      Because it is picking up the fact you upgraded from Windows 8.1. The method you are using is looking at the registry. It is working as intended. There is a more appropriate function then using the environment variable to determine what operating system is being used. I can't provide code since this isn't Stackoverflow




      – Ramhound Aug 26 at 1:12



      That's the answer in a nutshell. During the upgrade, the registry doesn't change the build number from the old to the new one. It just sticks.






      share|improve this answer



















      • 2





        In other words, the upgrade doesn't work properly... Well, nothing new in the west ;)

        – Quandary
        Mar 8 '16 at 15:51














      3












      3








      3








      Because it is picking up the fact you upgraded from Windows 8.1. The method you are using is looking at the registry. It is working as intended. There is a more appropriate function then using the environment variable to determine what operating system is being used. I can't provide code since this isn't Stackoverflow




      – Ramhound Aug 26 at 1:12



      That's the answer in a nutshell. During the upgrade, the registry doesn't change the build number from the old to the new one. It just sticks.






      share|improve this answer














      Because it is picking up the fact you upgraded from Windows 8.1. The method you are using is looking at the registry. It is working as intended. There is a more appropriate function then using the environment variable to determine what operating system is being used. I can't provide code since this isn't Stackoverflow




      – Ramhound Aug 26 at 1:12



      That's the answer in a nutshell. During the upgrade, the registry doesn't change the build number from the old to the new one. It just sticks.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Nov 16 '15 at 23:55









      RookieTEC9RookieTEC9

      879728




      879728








      • 2





        In other words, the upgrade doesn't work properly... Well, nothing new in the west ;)

        – Quandary
        Mar 8 '16 at 15:51














      • 2





        In other words, the upgrade doesn't work properly... Well, nothing new in the west ;)

        – Quandary
        Mar 8 '16 at 15:51








      2




      2





      In other words, the upgrade doesn't work properly... Well, nothing new in the west ;)

      – Quandary
      Mar 8 '16 at 15:51





      In other words, the upgrade doesn't work properly... Well, nothing new in the west ;)

      – Quandary
      Mar 8 '16 at 15:51













      0














      So, to get back to the root question... I use Windows Management Instrumentation (WMI) to generate the Windows version number in the manner in which you are expecting. For example, it reports 10.0.10586



      Here is a short code snippet



      Public Class OS

      ' Use Windows Management Instrumentation (WMI) to get the OS version
      Public Shared Function GetOSVersion() As String
      Dim answer As String = ""

      ' add Imports System.Management and add a resource to System.Management
      Dim osClass As New ManagementClass("Win32_OperatingSystem")
      For Each queryObj As ManagementObject In osClass.GetInstances()
      answer = DirectCast(queryObj.GetPropertyValue("Version"), String)
      Next

      Return answer
      End Function
      End Class





      share|improve this answer






























        0














        So, to get back to the root question... I use Windows Management Instrumentation (WMI) to generate the Windows version number in the manner in which you are expecting. For example, it reports 10.0.10586



        Here is a short code snippet



        Public Class OS

        ' Use Windows Management Instrumentation (WMI) to get the OS version
        Public Shared Function GetOSVersion() As String
        Dim answer As String = ""

        ' add Imports System.Management and add a resource to System.Management
        Dim osClass As New ManagementClass("Win32_OperatingSystem")
        For Each queryObj As ManagementObject In osClass.GetInstances()
        answer = DirectCast(queryObj.GetPropertyValue("Version"), String)
        Next

        Return answer
        End Function
        End Class





        share|improve this answer




























          0












          0








          0







          So, to get back to the root question... I use Windows Management Instrumentation (WMI) to generate the Windows version number in the manner in which you are expecting. For example, it reports 10.0.10586



          Here is a short code snippet



          Public Class OS

          ' Use Windows Management Instrumentation (WMI) to get the OS version
          Public Shared Function GetOSVersion() As String
          Dim answer As String = ""

          ' add Imports System.Management and add a resource to System.Management
          Dim osClass As New ManagementClass("Win32_OperatingSystem")
          For Each queryObj As ManagementObject In osClass.GetInstances()
          answer = DirectCast(queryObj.GetPropertyValue("Version"), String)
          Next

          Return answer
          End Function
          End Class





          share|improve this answer















          So, to get back to the root question... I use Windows Management Instrumentation (WMI) to generate the Windows version number in the manner in which you are expecting. For example, it reports 10.0.10586



          Here is a short code snippet



          Public Class OS

          ' Use Windows Management Instrumentation (WMI) to get the OS version
          Public Shared Function GetOSVersion() As String
          Dim answer As String = ""

          ' add Imports System.Management and add a resource to System.Management
          Dim osClass As New ManagementClass("Win32_OperatingSystem")
          For Each queryObj As ManagementObject In osClass.GetInstances()
          answer = DirectCast(queryObj.GetPropertyValue("Version"), String)
          Next

          Return answer
          End Function
          End Class






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited May 21 '16 at 12:45

























          answered May 19 '16 at 1:56









          egrayegray

          60238




          60238























              0














              That's because you were reading CurrentVersion from HKLMSOFTWAREMicrosoftWindows NTCurrentVersion and, as has already been said, that entry doesn't get updated change with Windows updates.



              The entries to check are CurrentMajorVersionNumber, CurrentMinorVersionNumber and CurrentBuildNumber, in the same key.






              share|improve this answer




























                0














                That's because you were reading CurrentVersion from HKLMSOFTWAREMicrosoftWindows NTCurrentVersion and, as has already been said, that entry doesn't get updated change with Windows updates.



                The entries to check are CurrentMajorVersionNumber, CurrentMinorVersionNumber and CurrentBuildNumber, in the same key.






                share|improve this answer


























                  0












                  0








                  0







                  That's because you were reading CurrentVersion from HKLMSOFTWAREMicrosoftWindows NTCurrentVersion and, as has already been said, that entry doesn't get updated change with Windows updates.



                  The entries to check are CurrentMajorVersionNumber, CurrentMinorVersionNumber and CurrentBuildNumber, in the same key.






                  share|improve this answer













                  That's because you were reading CurrentVersion from HKLMSOFTWAREMicrosoftWindows NTCurrentVersion and, as has already been said, that entry doesn't get updated change with Windows updates.



                  The entries to check are CurrentMajorVersionNumber, CurrentMinorVersionNumber and CurrentBuildNumber, in the same key.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Dec 29 '18 at 8:12









                  Nuno AndréNuno André

                  21124




                  21124























                      -1














                      6.3 is the internal version of Windows, which reveals that since Windows 7, there have not been any major releases, contrary to what Microsoft wants you to believe. The names Windows 7, 8, 10, etc. are just marketing names. They decided to skip 9 to match Mac OS X. But the real version number is 6.3






                      share|improve this answer



















                      • 1





                        There are many different reasons floated for why they skipped v9 (a particularly neat one was that many legacy apps would see the 9 and mistakenly think the OS was Windows 95/98 - but I don't think they've ever confirmed or denied that). That said, try to refrain from random speculation in your answers - sources are best :)

                        – Mikey T.K.
                        Mar 18 '16 at 19:52
















                      -1














                      6.3 is the internal version of Windows, which reveals that since Windows 7, there have not been any major releases, contrary to what Microsoft wants you to believe. The names Windows 7, 8, 10, etc. are just marketing names. They decided to skip 9 to match Mac OS X. But the real version number is 6.3






                      share|improve this answer



















                      • 1





                        There are many different reasons floated for why they skipped v9 (a particularly neat one was that many legacy apps would see the 9 and mistakenly think the OS was Windows 95/98 - but I don't think they've ever confirmed or denied that). That said, try to refrain from random speculation in your answers - sources are best :)

                        – Mikey T.K.
                        Mar 18 '16 at 19:52














                      -1












                      -1








                      -1







                      6.3 is the internal version of Windows, which reveals that since Windows 7, there have not been any major releases, contrary to what Microsoft wants you to believe. The names Windows 7, 8, 10, etc. are just marketing names. They decided to skip 9 to match Mac OS X. But the real version number is 6.3






                      share|improve this answer













                      6.3 is the internal version of Windows, which reveals that since Windows 7, there have not been any major releases, contrary to what Microsoft wants you to believe. The names Windows 7, 8, 10, etc. are just marketing names. They decided to skip 9 to match Mac OS X. But the real version number is 6.3







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Mar 18 '16 at 16:52









                      user319563user319563

                      292




                      292








                      • 1





                        There are many different reasons floated for why they skipped v9 (a particularly neat one was that many legacy apps would see the 9 and mistakenly think the OS was Windows 95/98 - but I don't think they've ever confirmed or denied that). That said, try to refrain from random speculation in your answers - sources are best :)

                        – Mikey T.K.
                        Mar 18 '16 at 19:52














                      • 1





                        There are many different reasons floated for why they skipped v9 (a particularly neat one was that many legacy apps would see the 9 and mistakenly think the OS was Windows 95/98 - but I don't think they've ever confirmed or denied that). That said, try to refrain from random speculation in your answers - sources are best :)

                        – Mikey T.K.
                        Mar 18 '16 at 19:52








                      1




                      1





                      There are many different reasons floated for why they skipped v9 (a particularly neat one was that many legacy apps would see the 9 and mistakenly think the OS was Windows 95/98 - but I don't think they've ever confirmed or denied that). That said, try to refrain from random speculation in your answers - sources are best :)

                      – Mikey T.K.
                      Mar 18 '16 at 19:52





                      There are many different reasons floated for why they skipped v9 (a particularly neat one was that many legacy apps would see the 9 and mistakenly think the OS was Windows 95/98 - but I don't think they've ever confirmed or denied that). That said, try to refrain from random speculation in your answers - sources are best :)

                      – Mikey T.K.
                      Mar 18 '16 at 19:52











                      -1














                      I installed Windows 10 (anniversary edition 1607) from scratch and the currentversion registry entry also reports 6.3, but, for example, 'ver' reports 10.0.14393



                      BTW 1) I read that the Windows 10 preview was 6.4



                      BTW 2) I installed Windows 10 as a Hyper-V VM on Windows Server 2012 R2, but I do not think that this has to do anything with it.






                      share|improve this answer


























                      • "I read that the windows 10 preview was 6.4" - You read wrong. This is a comment, it does not answe the author's question, if you wish to leave a comment earn the require reputation point to do so.

                        – Ramhound
                        Nov 1 '16 at 13:19


















                      -1














                      I installed Windows 10 (anniversary edition 1607) from scratch and the currentversion registry entry also reports 6.3, but, for example, 'ver' reports 10.0.14393



                      BTW 1) I read that the Windows 10 preview was 6.4



                      BTW 2) I installed Windows 10 as a Hyper-V VM on Windows Server 2012 R2, but I do not think that this has to do anything with it.






                      share|improve this answer


























                      • "I read that the windows 10 preview was 6.4" - You read wrong. This is a comment, it does not answe the author's question, if you wish to leave a comment earn the require reputation point to do so.

                        – Ramhound
                        Nov 1 '16 at 13:19
















                      -1












                      -1








                      -1







                      I installed Windows 10 (anniversary edition 1607) from scratch and the currentversion registry entry also reports 6.3, but, for example, 'ver' reports 10.0.14393



                      BTW 1) I read that the Windows 10 preview was 6.4



                      BTW 2) I installed Windows 10 as a Hyper-V VM on Windows Server 2012 R2, but I do not think that this has to do anything with it.






                      share|improve this answer















                      I installed Windows 10 (anniversary edition 1607) from scratch and the currentversion registry entry also reports 6.3, but, for example, 'ver' reports 10.0.14393



                      BTW 1) I read that the Windows 10 preview was 6.4



                      BTW 2) I installed Windows 10 as a Hyper-V VM on Windows Server 2012 R2, but I do not think that this has to do anything with it.







                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Sep 1 '17 at 11:52









                      Peter Mortensen

                      8,371166185




                      8,371166185










                      answered Nov 1 '16 at 12:02









                      Theo VroomTheo Vroom

                      1




                      1













                      • "I read that the windows 10 preview was 6.4" - You read wrong. This is a comment, it does not answe the author's question, if you wish to leave a comment earn the require reputation point to do so.

                        – Ramhound
                        Nov 1 '16 at 13:19





















                      • "I read that the windows 10 preview was 6.4" - You read wrong. This is a comment, it does not answe the author's question, if you wish to leave a comment earn the require reputation point to do so.

                        – Ramhound
                        Nov 1 '16 at 13:19



















                      "I read that the windows 10 preview was 6.4" - You read wrong. This is a comment, it does not answe the author's question, if you wish to leave a comment earn the require reputation point to do so.

                      – Ramhound
                      Nov 1 '16 at 13:19







                      "I read that the windows 10 preview was 6.4" - You read wrong. This is a comment, it does not answe the author's question, if you wish to leave a comment earn the require reputation point to do so.

                      – Ramhound
                      Nov 1 '16 at 13:19




















                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f962796%2fwhy-does-windows-10-return-the-version-number-6-3%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Список кардиналов, возведённых папой римским Каликстом III

                      Deduzione

                      Mysql.sock missing - “Can't connect to local MySQL server through socket”