Do drivers affect activation status?

Discussion in 'Windows 10' started by x6phenom, Mar 18, 2016.

  1. x6phenom

    x6phenom MDL Novice

    Feb 16, 2013
    30
    1
    0
    I had Windows 8.1 on my laptop (legit) and upgraded to Windows 10.

    Next I instaleld an SSD and installed a clean Windows 10 on it. However it does not activate claiming no digital entitlement.

    Is it because it doesnt recognize the hardware? Will installing drivers from the vendors website help?
     
  2. trungpt

    trungpt MDL Addicted

    Dec 15, 2009
    522
    49
    30
    I'd like to know too.

    You can install all drivers needed and let me know the answer :D You have the basics to do.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. pisthai

    pisthai Imperfect Human

    Jul 29, 2009
    6,857
    2,029
    210
    It's the SSD (HDD) Drive! Drivers are not any problem AFAIK!

    Normally, 3 instances have to get changed before it has a effect on activation. The MB alone are already more than 3 instances: Chipset-BIOS-Graphic-Controller etc.!

    Just, from my own experiences, all time that problems were easy to settle using the Phone-Activation and talk with an MS Employee! I just installed the latest Build of W10 on my Laptop and used finally a new HDD, and the activation were just done automatically. I had problems with the Upgrade via WU on that Laptop, and was start to Low-Level Format the 750GB HDD, which will last till tomorrow morning, so I used an other HDD for to do a clean install, activation were done with no problems. But it were not a SSD, just a normal, old style 2.5" HDD!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. x6phenom

    x6phenom MDL Novice

    Feb 16, 2013
    30
    1
    0
    Im trying slui 4 and when I enter the 9 batches of code, there is one batch the system doesnt recognize because of error.

    Like batch 3, retry, work. Batch 5 retry, retry, fail.

    Call again

    Try batch 5 work.

    so annoying
     
  5. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    16,782
    21,024
    340
    By HWID AND/OR by oem:Dm embedded bioskey (my 2in1 Asus laptab, i bought in 2014, had already a genuine 10 oem:Dm bioskey in it).
     
  6. x6phenom

    x6phenom MDL Novice

    Feb 16, 2013
    30
    1
    0
    I even installed Windows 8.1 using a generic key.

    Removed the key using slmgr /upk.

    Tried to install the BIOS key using SLUI 3 and it still wont recognize the key.

    Ill try the other two key fetchers (from BIOS).
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    16,782
    21,024
    340
    What iso's are you using?
     
  8. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    16,782
    21,024
    340
    What did the OEM Query tool show? Does it show : VALID OS: 8.x/10

    If yes, 10 (10586) home (most likely) will be auto activated, no keys are asked during install. For 8.1 you have to modify the installmedium as explained in the Multi OEM Thread i showed.
     
  9. x6phenom

    x6phenom MDL Novice

    Feb 16, 2013
    30
    1
    0
    They gave the same BIOS key. I think the culprit is SINGLE EDITION windows because when I enter the BIOS key it says " this key cannot be used to activate this product" for windows 8.1

    Ill download 8.1 SE.
     
  10. x6phenom

    x6phenom MDL Novice

    Feb 16, 2013
    30
    1
    0

    Yes it shows

    VALID [OEM OS] - Win8.x/Win10 Only

    I will try the multi oem thread.
     
  11. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    16,782
    21,024
    340
    What single sku iso? There are only core-singlelanguage iso with just one sku or the esd files pro or core only.

    I'm beginning to think you're not installing the corresponding edition (as i said most likely it's 10 Home which will be installed and officially activated by the oem:Dm key).

    For genuine oem use of win 10, The Multi OEM thread is not needed, only for 7 or 8.x. Since 10586 was released it's able to doe the oem "thingy" by itself.
     
  12. x6phenom

    x6phenom MDL Novice

    Feb 16, 2013
    30
    1
    0
    Btw here is the result from the OEM tool.

    OEM Query Tool v7.3 Build 5 Advanced 08:15 PM Fri 03/18/2016

    OEM INFORMATION FOR THIS MACHINE
    --------------------------------
    OS Name: Windows 8.1 [x64]
    OS Version: 6.3.9600.17415.amd64fre.winblue_r4.141028-1500
    Processor: Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz
    Processor Cores: [4] Logical Processors: [8]
    Processor Architecture: [AMD64]
    HDD Partition Type: [MBR]
    Bios Version: [Insyde Corp. V1.07, 9/5/2014]
    Total Physical Memory: [16,311 MB] Available Memory: [15,346 MB]

    SCANNED
    -------
    #1 CSPRODUCT NAME - Aspire VN7-791
    #2 COMPUTERSYSTEM MODEL - Aspire VN7-791
    #3 BASEBOARD PRODUCT - Aspire VN7-791
    #4 CSPRODUCT VENDOR - Acer
    #5 COMPUTERSYSTEM MFR - Acer
    #6 BASEBOARD MFR - Acer
    #7 SERIAL/SERV TAG -
    #8 BIOS ID - ACRSYS
    #9 SLIC OA - Un-Listed
    #10 INSTALLED KEY - REMOVED
    #11 MSDM TABLE [OEM:DM] - REMOVED
    #12 BIOS MODE - LEGACY
    #13 CERTIFICATE - Un-Listed
    #14 LICENSE STATUS - Notification

    SUMMARY
    -------
    THEME - ACER [id:-`#4']
    ACTIVATION - ACER [id:-`#8']
    VALID [OEM OS] - Win8.x/Win10 Only



    SLIC TABLE
    ----------
    Un-Listed



    MSDM TABLE
    ----------

    MS Digital Marker Table:

    REMOVED

    Signature : "MSDM"
    Length : 0x55 (85)
    Revison : 0x3 (3)
    Checksum : 0xC2 (C2)
    OEM ID : "ACRSYS"
    OEM Table ID : "ACRPRDCT"
    OEM Revision : 0x1 (1)
    Creator ID : "1025"
    Creator Revision : 0x40000 (262144)
    Version : 0x1 (1)
    Reserved : 0x0 (0)
    Type : 0x1 (1)
    Data Reserved : 0x0 (0)
    Data Length : 0x1D (29)
    Data : REMOVED



    CERTIFICATE
    -----------
    Un-Listed

    So I just place the ACER folder in Source of the Win8.1 / Win10 USB? Thats it? And run the installation?
     
  13. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    16,782
    21,024
    340
    #16 Enthousiast, Mar 18, 2016
    Last edited: Mar 18, 2016
    That seems okay:

    OEM INFORMATION FOR THIS MACHINE
    --------------------------------
    OS Name: Windows 8.1 [x86]
    OS Version: 6.3.9600.18090.x86fre.winblue_ltsb.151014-0600
    Processor: Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
    Processor Cores: [4] Logical Processors: [4]
    Processor Architecture: [x86]
    HDD Partition Type: [GPT-Secured Boot Enabled]
    Bios Version: [T100TA.304, 03/14/2014]

    SCANNED
    -------
    #1 CSPRODUCT NAME - T100TA
    #2 COMPUTERSYSTEM MODEL - T100TA
    #3 BASEBOARD PRODUCT - T100TA
    #4 CSPRODUCT VENDOR - ASUSTeK COMPUTER INC.
    #5 COMPUTERSYSTEM MFR - ASUSTeK COMPUTER INC.
    #6 BASEBOARD MFR - ASUSTeK COMPUTER INC.
    #7 SERIAL/SERV TAG - Exxxxxxxxxxxxxxx
    #8 BIOS ID - _ASUS_
    #9 SLIC OA - Un-Listed
    #10 INSTALLED KEY - XXXXX-XXXXX XXXXX-XXXXX-XXXXX-XXXXX
    #11 MSDM TABLE [OEM:DM] - XXXXX-XXXXX XXXXX-XXXXX-XXXXX-XXXXX
    #12 BIOS MODE - UEFI
    #13 CERTIFICATE - Un-Listed
    #13 LICENSE STATUS - Licensed

    SUMMARY
    -------
    THEME - ASUS [id:-`#4']
    ACTIVATION - ASUS [id:-`#8']
    VALID [OEM OS] - Win8.x/Win10 Only




    SLIC TABLE
    ----------
    Un-Listed



    MSDM TABLE
    ----------

    MS Digital Marker Table:

    4D 53 44 4D 55 00 00 00 03 01 5F 41 53 55 53 5F MSDMU....._ASUS_
    4E 6F 74 65 62 6F 6F 6B 00 00 00 00 41 53 55 53 Notebook....ASUS
    01 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 ................
    00 00 00 00 1D 00 00 00 51 4B 39 33 4E 2D 58 46 ........XXXXX-XX
    00 00 00 00 1D 00 00 00 51 4B 39 33 4E 2D 58 46 XXX-XXXXX-XXXXX-
    48 38 50 34 33 XXXXX

    Signature : "MSDM"
    Length : 0x55 (85)
    Revison : 0x3 (3)
    Checksum : 0x1 (1)
    OEM ID : "_ASUS_"
    OEM Table ID : "Notebook"
    OEM Revision : 0x0 (0)
    Creator ID : "ASUS"
    Creator Revision : 0x1 (1)
    Version : 0x1 (1)
    Reserved : 0x0 (0)
    Type : 0x1 (1)
    Data Reserved : 0x0 (0)
    Data Length : 0x1D (29)
    Data : XXXXX-XXXXX XXXXX-XXXXX-XXXXX-XXXXX




    CERTIFICATE
    -----------
    Un-Listed
     
  14. x6phenom

    x6phenom MDL Novice

    Feb 16, 2013
    30
    1
    0
    Before installing, I remember it said Windows 10 Home Single Language.

    After that I installed, Windows 10 home, without product key. It did not activate.
    Then I installed Windows 8.1 with the HOME generic key. It did not activate (event after using slmgr /upk and trying slui 3 BIOS key).
     
  15. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    16,782
    21,024
    340
    #18 Enthousiast, Mar 18, 2016
    Last edited: Mar 18, 2016
    Don't know for sure but maybe use UEFI will help you. Now it's in legacy mode, i don't know if it interferes with the use of the oem:Dm key.

    Try to forget all those commands, it should be really simple. You have an official key inside the hardware, no generic keys or whatever are needed, njust the correct windows edition and i say it's probably home (or maybe singlelanguage, it's not made for my country/language so i don't know it but i believe it also uses the oem:Dm bioskey).
     
  16. Threat

    Threat Lord of the Files

    Feb 23, 2014
    1,064
    835
    60
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. x6phenom

    x6phenom MDL Novice

    Feb 16, 2013
    30
    1
    0
    The problem with UEFI is that it does not detect any bootable device, even after turning off secure boot and arranging the drives in different patterns.

    This is after I made the USB using GPT partition for UEFI

    GPT is newer right? Should work :g: the laptop is Acer Aspire VN7-791G

    Anyway Im downloading Windows 10 Home Single Language, since Home only windows 8.1 or 10 didnt work.

    Hopefully I wont have a problem between Arabic or English now zzzzzzzz :mad: