Can't activate 1809 but 1703 works fine different product key?

Discussion in 'Windows 10' started by joshu, Dec 29, 2018.

  1. joshu

    joshu MDL Junior Member

    Sep 10, 2012
    70
    7
    0
    I have a Windows 10 Pro 1703 VM (I created from scratch myself using SW_DVD9_Win_Pro_10_1703.1_64BIT_English_MLF_X21-47998.ISO) that it says is activated using "your organization's activation service".

    I downloaded Win10_1809Oct_English_x64.iso from MS and created a new VM but it won't activate which seems weird. The product key ends with 3V66T.

    How can I check what the product key is in the 1703 VM and do I need to use the same key to activate the 1809?
     
  2. s1ave77

    s1ave77 MDL Guide Dog/Dev

    Aug 15, 2012
    15,769
    22,915
    340
    Message on first system means it's activated by KMS solution.

    Second needs KMS activation likewise. Atm the default Retail key is installed, that would only activate if a valid digital license exists for the respective machine.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. mkuba50

    mkuba50 MDL PHP Wizard

    Nov 9, 2012
    688
    4,624
    30
    If they have KMS server running in network with correctly configured DNS then Windows will automatically detect it and activate using it.
     
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    18,435
    23,887
    340
    I doubt that someone who downloads a OEMRET iso is running a private KMS server, but doesn't know it needs a gVLK, but all is possible these days :)
     
  5. nmook

    nmook MDL Novice

    Aug 2, 2015
    15
    4
    0
    I thought the key that ends in 9MPGT-3V66T was blocked from activation on microsoft servers?
     
  6. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    18,435
    23,887
    340
    It's the generic HWID for Pro key, won't be blocked and only activates when the system already has an established HWID for Pro.