[Solved] another home to pro question

Discussion in 'Windows 10' started by sjusjusju, May 18, 2017.

Tags:
  1. sjusjusju

    sjusjusju MDL Novice

    Jun 4, 2010
    21
    4
    0
  2. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    22,412
    31,046
    390
    You can establish a HWID for pro on a system with an oem : dm for Home.

    Install windows 7 SP1 and activate by using daz loader. Next use a modified 14393/15063 iso (either use a correct ei.cfg* or delete the home index from the wim) to upgrade or go the gatherosstate route.

    And with a 10240 is it always has to work, that iso doesn't readout/uses the oem : dm key at all, from 10586 up it can.

    This ei.cfg should work:
    Code:
    [Channel]
    _Default
    
    [VL]
    0
    
    Or this one:
    Code:
    [EditionID]
    
    [Channel]
    Volume
    
    [VL]
    1
    
    The problem of having Pro (HWID or KMS) on a system with a Home OEM : DM you always have to do some extra steps to keep on Pro during the frequent upgrade periods (2 times a year)..

    To get a free HWID from a 8.1 KMS activated install you have to use 10586 or 10240, to establish a hwid.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. sjusjusju

    sjusjusju MDL Novice

    Jun 4, 2010
    21
    4
    0
    Just tried it again - no luck :-(

    I really managed to install Windows 7 professional on my system, but I needed to use my second (non-SSE) hard drive (with the MS hotfixes injected, it inevitably meant: bluescreen when booting my bootable usb flash drive with Windows 7 pro!).

    I had to fight against Microsoft's "Hardware not supported" (kaby lake processor) and use an unofficial patch someone wrote to be able to (from the running system) install nvme drivers and get access to my SSD, too.

    I ended with a device Manager having no exclamation marks - I found drivers for virtually everything.

    Activating with Daz loader - no Problem!
    "Genuine"!


    But please be aware:
    I made a bootable usb flash drive with Windows 10 (10240) and tried an upgrade (from the running win7 pro system) to Windows 10 pro - but again: I was only offered a Windows 10 *Home* Installation - didn't matter which version of ei.cfg I put in that sources Folder! It just didn't let me choose "pro" - no way!

    So since that upgrade test failed, I guess, creating a genuineticket.xml and doing a clean install will be pointless - I will end in Windows 10 home, that much appears to be sure.


    I suppose, I will have to stay with Windows 10 Home. So 10240 must be able to detect my bioskey for home.
     
  4. pf100

    pf100 MDL Expert

    Oct 22, 2010
    1,645
    2,365
    60
    #5 pf100, May 19, 2017
    Last edited: May 19, 2017
    You need to use the 10240 pro only iso, not 10240 pro/home. You already have a windows 10 pro digital entitlement from windows 7 pro's gatherosstate.xml file. I've done this several times and it works to upgrade windows 8 with oem: dm bios to windows 10 pro. I'm typing this on a laptop with windows 10 pro that has an oem: dm windows 8 bios.
     
  5. sjusjusju

    sjusjusju MDL Novice

    Jun 4, 2010
    21
    4
    0
    Thanks for trying to help, pf100,
    but:


    Unbelievable!
    Success!

    Instead of starting the upgrade procedure from inside windows 7, I simply tried a clean install of windows 10 pro with that same iso (10240, home/pro) and the same ei.cfg and not only did it REALLY install windows 10 pro, but I also did it on my SSD this time.

    gatherosstate.exe and genuineticket.xml etc. -> windows 10 pro activated!


    So I must have been under the impression that when upgrade procedures only offer *home*, not pro, then a clean install must be no different. Wrong!


    @Enthousiast

    Thanks so much, you are definitely right and your statements helped a lot.

    quoting Enthousiast:
    "
    The problem of having Pro (HWID or KMS) on a system with a Home OEM : DM you always have to do some extra steps to keep on Pro during the frequent upgrade periods (2 times a year)..
    "

    Does that mean that going the windows 7/Daz route (instead of the windows 8.1 route etc.) can still end in losing one's activation after a windows update?

    And what would be the extra steps then?
    Would it suffice to put that genuineticket.xml in the corresponding folder again? I cannot quite see what would have to be done when activation has been lost?


    Many thanks
     
  6. Hadron-Curious

    Hadron-Curious MDL Guru

    Jul 4, 2014
    3,574
    531
    120
    @OP

    Please, add 'solved' to the title.
     
  7. pf100

    pf100 MDL Expert

    Oct 22, 2010
    1,645
    2,365
    60
    "The problem of having Pro (HWID or KMS) on a system with a Home OEM : DM you always have to do some extra steps to keep on Pro during the frequent upgrade periods (2 times a year)."

    *I've never had that problem. I think he's talking about you might have to re-enter your pro key under some circumstances.

    Does that mean that going the windows 7/Daz route (instead of the windows 8.1 route etc.) can still end in losing one's activation after a windows update?

    *Definitely not.

    And what would be the extra steps then?
    Would it suffice to put that genuineticket.xml in the corresponding folder again? I cannot quite see what would have to be done when activation has been lost?

    *You never have to do the genuineticket.xml thing ever again once you're activated. You can only lose activation after changing a motherboard or something like that and in that case genuineticket.xml won't help you, unless you start all over with windows 7 again and do the genuineticket thing. But you can call microsoft and get your activation straightened out without having to start all over again.
     
  8. intruder16

    intruder16 MDL Novice

    Jul 17, 2014
    23
    13
    0
    Or you can link your Microsoft account. So that after a motherboard (or similar) change you can just login with your MS account and it'll be activated. There are some success stories out there using this method. Never tried this personally though.
     
  9. sjusjusju

    sjusjusju MDL Novice

    Jun 4, 2010
    21
    4
    0
    I must be blind: I cannot see how to edit the thread title and mark it "solved", sorry.

    /edit:
    Found it, haha :)



    Great help here, at any rate.


    Just a final observation:
    It looks like in win10pro I lost that nice login wallpaper rotation that I had in windows 10 home. Can it be enabled again?
     
  10. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    22,412
    31,046
    390
    Once the HWID for pro is established it is valid for the lifetime of the hardware it's established on (you can use your msa to transfer the HWID to other hardware).

    The extra steps i was talking about is that next upgrade (>RS3) thru WU or with an unmodified iso, it will upgrade to Home again. When this happens you only have to re-enter the generic Pro key (ending on 3V66T).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. sjusjusju

    sjusjusju MDL Novice

    Jun 4, 2010
    21
    4
    0
    Regarding my login screen question:
    Is this a difference between windows 10 home and pro?

    In spite of selecting "spotlight" for the lock screen AND turning on the option to make the *login screen* use the same background pictures as the lock screen, I still only see the same picture again and again.

    I really liked those nice background pictures when I rebooted my PC and logged into windows 10 (home) again.

    Minor annoyance, I know...
     
  12. lobo11

    lobo11 TOMAHAWK CHOP

    Feb 16, 2012
    6,573
    5,260
    210
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. sjusjusju

    sjusjusju MDL Novice

    Jun 4, 2010
    21
    4
    0
    Just some feedback regarding my sign-in screen background picture question:

    After a few days of running windows 10 pro, I notice that the wallpapers in the login screen DO change (just like in windows 10 home). So all is fine now. :)