[DISCUSSION] Windows 10 (1703 RS2) "Creators Update" Final 15063 (PC)

Discussion in 'Windows 10' started by Enthousiast, Mar 21, 2017.

  1. R23

    R23 MDL Member

    Apr 5, 2017
    124
    28
    10
    OK, Bro
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. DeadMan

    DeadMan MDL Junior Member

    Aug 11, 2009
    72
    2
    0
    Is it possible to use the LTSB key to upgrade from Enterprise once you have the CU in place?
     
  3. c6p0

    c6p0 MDL Junior Member

    Aug 17, 2010
    74
    47
    0
  4. bebj1957

    bebj1957 MDL Novice

    Apr 10, 2017
    25
    4
    0
    No
     
  5. Ahsan

    Ahsan MDL Addicted

    Dec 3, 2009
    827
    167
    30
    hi guys
    i am running windows 10 ent x64 bit build 10240 kmspico activated ,
    can i update it to windows 10 creators edition , if so kindly share the link to an enterprise 64bit version of it :)
     
  6. R23

    R23 MDL Member

    Apr 5, 2017
    124
    28
    10
    yes, you can
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. Nucleus

    Nucleus MDL Guru

    Aug 4, 2009
    2,868
    2,950
    90
    And VL Pro? He didn't say Enterprise, he asked...

     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. antonio8909

    antonio8909 MDL Guru

    Feb 16, 2014
    3,111
    1,516
    120
    @Nucleus I think that @Enthousiast said that the VL ISOs will be available on May 1st
     
  9. R23

    R23 MDL Member

    Apr 5, 2017
    124
    28
    10
    proof?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. Nucleus

    Nucleus MDL Guru

    Aug 4, 2009
    2,868
    2,950
    90
    #3192 Nucleus, Apr 22, 2017
    Last edited: Apr 22, 2017
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. MrG

    MrG MDL Expert

    May 31, 2010
    1,402
    1,625
    60
    Yesterday I restored a (legally activated) Win10 x86 partition w/ build 14393 (using WHS2011), it wouldn't boot or show-up on the boot menu so I took a Build 15063 x86 DVD & did a clean install, no problems at all, shows up on boot menu... all is good.
    I checked settings/activation after a restart & it is activated, as was the broken W10 build I had before.

    The new MB has a dual BIOS & I have had problems restoring any working backups... so far.
     
  12. ttmax

    ttmax MDL Member

    Oct 27, 2009
    168
    44
    10
    I downloaded your VL ESD file (Education VL x64 en-us), converted it to ISO, and tried to create an SFV from x64 multiple edition MSDN iso.

    I am unable to obtain a reasonable sized SFV file, the difference file obtained is nearly same size as the whole ISO (more than 3 GB), when generlly this kind of SFV is around 40megs.

    Any explanation to that , please ?
     
  13. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    16,194
    84,743
    340
    Did you use option 1?

    i don't know for sure, maybe because wimlib introduce slightly different compression ratio for WIM files
    or because install.wim lacks integrity table (check option)
     
  14. ttmax

    ttmax MDL Member

    Oct 27, 2009
    168
    44
    10
    #3198 ttmax, Apr 22, 2017
    Last edited: Apr 22, 2017
    Yes option1 was used.

    Your wimlib compression explanation is probably the reason.

    EDUCATION x64 Install.wim after ESD conversion is lighter than EDUCATION x64 MSDN install.wim (3.35gb ESD converted vs 3.39gb MSDN). Different compression used.
     
  15. MonarchX

    MonarchX MDL Expert

    May 5, 2007
    1,732
    313
    60
  16. Simple07

    Simple07 MDL Addicted

    Nov 15, 2012
    580
    221
    30
    Actually a solution was posted on TenForums over a week ago, and this is how it goes:

    Run regedit and locate the following entries:

    1st Location: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]

    2nd Location: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]

    Export both entries, then Delete the 2 Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0 KEYS from the registry.

    Note: giving Administrators Full Control was needed to be able to delete them.

    Running "DISM /Online /Cleanup-Image /RestoreHealth ........" will be successful.

    To re-import the 2 registry entries, you may need to give "PackageIndex" and "Packages" full Administrator control,

    This is a workaround until Microsoft officially fix it.