Can't upgrade to pro

Discussion in 'Windows 10' started by joe7dust, May 17, 2018.

  1. Tiger-1

    Tiger-1 MDL Guru

    Oct 18, 2014
    7,897
    10,733
    240
    Enth I discovered the reason of my problems really you're right no kidding at this time I checked the sizes of the ISO's that I modified one has 2.7GB 2016 LTSB I did last March and the one I did yesterday has 2.97GB is clear that HAVE ISSUES being that I just removed the "unnecessary things" then ... only remains to format even curse what a guy to go without sleep two days is able ;):mad: good night friend logout and format all again oh my God.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. joe7dust

    joe7dust MDL Junior Member

    May 1, 2011
    69
    3
    0
    I did exactly this and still same error.
     
  3. xinso

    xinso MDL Guru

    Mar 5, 2009
    12,696
    13,695
    340
  4. joe7dust

    joe7dust MDL Junior Member

    May 1, 2011
    69
    3
    0
    Wouldn't a problem with activation tech be detected by sfc /scannow? Also I did a full DISM /online /cleanup-image /restorehealth and then inplace reinstall just 2 days ago.
     
  5. xinso

    xinso MDL Guru

    Mar 5, 2009
    12,696
    13,695
    340
    #25 xinso, May 18, 2018
    Last edited: May 18, 2018
    No. The tokens store may be corrupt. If the Options ended up a no go, I'll tell you how to make a pure Pro edition iso to upgrade.
     
  6. xinso

    xinso MDL Guru

    Mar 5, 2009
    12,696
    13,695
    340
    No. It's from my experiences.
     
  7. xinso

    xinso MDL Guru

    Mar 5, 2009
    12,696
    13,695
    340
    #29 xinso, May 18, 2018
    Last edited: May 18, 2018
    Yes. But there's more than that, we couldn't understand. It just keeps showing the same error prompts.
     
  8. xinso

    xinso MDL Guru

    Mar 5, 2009
    12,696
    13,695
    340
    #31 xinso, May 18, 2018
    Last edited: May 18, 2018
    Not to give up yet. Look into C:\Windows\servicing\Packages for

    Microsoft-Windows-Security-SPP-Component-SKU-Professional-License-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum

    Do it.

    Edit: token reset won't work for your situation now. If it worked, no need to bother, right?
     
  9. joe7dust

    joe7dust MDL Junior Member

    May 1, 2011
    69
    3
    0
    Option 2 worked, thanks!
     
  10. xinso

    xinso MDL Guru

    Mar 5, 2009
    12,696
    13,695
    340
    Good. I can leave now?
     
  11. xinso

    xinso MDL Guru

    Mar 5, 2009
    12,696
    13,695
    340
    Wait. does say pro in settings...
     
  12. joe7dust

    joe7dust MDL Junior Member

    May 1, 2011
    69
    3
    0
    No I do have a profession sku folder now, and it does report as pro in the activation page.
     
  13. xinso

    xinso MDL Guru

    Mar 5, 2009
    12,696
    13,695
    340
    #37 xinso, May 18, 2018
    Last edited: May 18, 2018
    Then the Core's Product Policy remained...

    Wait. 16299.15 x64, right?

    Try this:

    1. dism /online /add-package:C:\Windows\servicing\Packages\Microsoft-Windows-Security-SPP-Component-SKU-Professional-Default-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum

    2. reboot

    3. test gpedit

    If this won't revert the Product Policy to Pro. we need to swap it manually.
     
  14. xinso

    xinso MDL Guru

    Mar 5, 2009
    12,696
    13,695
    340
    #39 xinso, May 18, 2018
    Last edited: May 18, 2018
    Yes, because we swap it by slmgr, not through activation, it won't activate Group Policy.

    BTW, (just in case) to prevent such thing from happening again when upgrade, I'd recommend that you upgrade with a "Pro" iso - not combined consumer one. Otherwise, the embedded Core key may bring it back to Core again.

    Before you run into trouble in upgrading back to Core, make sure these strings exist:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
    "CompositionEditionID"="Professional"
    "EditionID"="Professional"
    "ProductName"="Windows 10 Pro"


    Or install Pro SKU's certificates now:

    dism /online /add-package:C:\Windows\servicing\Packages\Microsoft-Windows-Branding-Professional-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum

    dism /online /add-package:C:\Windows\servicing\Packages\Microsoft-Windows-Editions-Professional-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum
    dism /online /add-package:C:\Windows\servicing\Packages\Microsoft-Windows-Editions-Professional-Package~31bf3856ad364e35~amd64~xx-XX~10.0.16299.15.mum

    dism /online /add-package:C:\Windows\servicing\Packages\Microsoft-Windows-Security-SPP-Component-SKU-Professional-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum

    P.S. xx-XX = en-US, etc.

    Good luck.