Guide to preserve Windows 8.x OEM Activation

Discussion in 'Windows 8' started by Tito, Dec 11, 2012.

  1. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,681
    18,589
    340
    @All

    First post updated... info about CoreCountrySpecific SKU is added.

    :worthy::worthy: -> ambidav & BTOR.
     
  2. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,681
    18,589
    340
    Job done!!
     
  3. BTOR

    BTOR MDL Addicted

    Nov 18, 2009
    574
    584
    30
    #63 BTOR, Feb 17, 2013
    Last edited by a moderator: Apr 20, 2017
  4. zbteck

    zbteck MDL Member

    Jul 27, 2009
    132
    31
    10
    There how change the ISO to another language?
     
  5. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,681
    18,589
    340
    Go to ACPI -> MSDM table & note down the key.
     
  6. Please-8

    Please-8 MDL Junior Member

    Sep 12, 2012
    92
    50
    0
    See here:
    View attachment 20838
     
  7. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,681
    18,589
    340
  8. foxathome

    foxathome MDL Novice

    Mar 18, 2013
    7
    0
    0
    I want tot make a clean and fast install and make an image of Windows 8 OEM to put this one on new computers and laptops. My English is not very good, but I wonder if there is somebody who use this way also and know how and IF this is possible. What do I need to know?

    If I put a clean install image from an HP laptop on a Acer, will Windows 8 automatically see the key in de BIOS and activate that key? Will it actually work...?

    I hope there is someone out there who can tell me the facts and if I can work this way as I did with Windows 7 (keyless installation and put the key in Windows 7 after) for years.

    Thnx!
     
  9. mdlguy10

    mdlguy10 MDL Novice

    Jul 10, 2010
    33
    14
    0
    This may be a stupid question, but here goes.

    If I buy a Windows 8 computer in a store like Best Buy in the USA or Canada, will I ever come across one with CoreSingleLanguage or CoreCountrySpecific?
     
  10. BTOR

    BTOR MDL Addicted

    Nov 18, 2009
    574
    584
    30
    CoreSingleLanguage - POSSIBLE CoreCountrySpecific -NOT POSSIBLE only in china
     
  11. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,681
    18,589
    340
    Should be Core or CoreSingleLanguage; CoreCountrySpecific is meant for only China.
     
  12. mdlguy10

    mdlguy10 MDL Novice

    Jul 10, 2010
    33
    14
    0
    Thanks for the answer guys.
     
  13. konstanteen

    konstanteen MDL Novice

    Oct 17, 2012
    7
    7
    0
    Windows 8 x64 CoreCountrySpecific Russian

    I assembled CoreCountrySpecific US iso image Win8_64_CCSUS_V1.0.iso [3.44 GB] using guide from thread 40897-How-to-preserve-Windows-8-OEM-Activation-Guide.

    But I was unsuccessful in replacing the en-US language in this image with ru-RU language following the other guide provided in thread 41471-CoreSingleLanguage-image.

    My command log:

    C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>dism.exe /mount-wim /wimfile:c:\_w8\wimorig\install.wim /index:1 /mountdir:c:\_w8\mount


    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384


    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.


    C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>dism /image:c:\_w8\mount /get-packages


    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384


    Image Version: 6.2.9200.16384


    Packages listing:


    Package Identity : Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e3
    5~amd64~en-US~6.2.9200.16384
    State : Installed
    Release Type : Language Pack
    Install Time : 7/26/2012 7:49 AM


    Package Identity : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~
    6.2.9200.16384
    State : Installed
    Release Type : Foundation
    Install Time : 7/26/2012 7:20 AM


    The operation completed successfully.


    C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>dism /image:c:\_w8\mount /remove-package /packagepath:c:\_w8\lang\en-us\lp.cab


    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384


    Image Version: 6.2.9200.16384


    Processing 1 of 1 - Removing package Microsoft-Windows-Client-LanguagePack-Packa
    ge~31bf3856ad364e35~amd64~en-US~6.2.9200.16384
    [==========================100.0%==========================]
    The operation completed successfully.


    C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>dism /image:c:\_w8\mount /scratchdir:c:\_w8\temp /add-package /packagepath:c:\_w8\lang\ru-ru\lp.cab


    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384


    Image Version: 6.2.9200.16384


    Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package
    ~31bf3856ad364e35~amd64~ru-RU~6.2.9200.16384
    [==========================100.0%==========================]
    The operation completed successfully.


    C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>dism /image:c:\_w8\mount /get-packages


    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384


    Image Version: 6.2.9200.16384


    Packages listing:


    Package Identity : Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e3
    5~amd64~ru-RU~6.2.9200.16384
    State : Install Pending
    Release Type : Language Pack
    Install Time : 3/26/2013 9:27 PM


    Package Identity : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~
    6.2.9200.16384
    State : Installed
    Release Type : Foundation
    Install Time : 7/26/2012 7:20 AM


    The operation completed successfully.


    C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>dism /image:c:\_w8\mount /set-allintl:ru-RU


    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384


    Image Version: 6.2.9200.16384


    Input locale has been set to: ru-RU
    System locale has been set to: ru-RU
    User locale has been set to: ru-RU
    UI language has been set to: ru-RU
    The operation completed successfully.


    C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>dism /image:c:\_w8\mount /set-skuintldefaults:ru-RU


    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384


    Image Version: 6.2.9200.16384


    Set SKU default settings for: ru-RU
    The operation completed successfully.


    C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>dism /image:c:\_w8\mount /set-inputlocale:0409:00020409 /set-inputlocale:0419:00000419


    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384


    Image Version: 6.2.9200.16384


    Input locale has been set to: 0409:00020409;0419:00000419
    The operation completed successfully.


    C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>dism /image:c:\_w8\mount /set-timezone:"Russian Standard Time"


    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384


    Image Version: 6.2.9200.16384


    The time zone has been set to: Russian Standard Time
    The operation completed successfully.


    C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>dism /unmount-image /mountdir:c:\_w8\mount /commit


    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384


    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.


    C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>imagex.exe /flags "CoreCountrySpecific" /info C:\_W8\WIMORIG\install.wim 1 "Windows 8 CoreCountrySpecific" "Windows 8 CoreCountrySpecific"


    ImageX Tool for Windows
    Copyright (C) Microsoft Corp. All rights reserved.
    Version: 6.2.9200.16384


    Successfully set image name: [Windows 8 CoreCountrySpecific]


    Successfully set image description: [Windows 8 CoreCountrySpecific]


    Successfully set image flags: [CoreCountrySpecific]


    C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>dism.exe /export-image /sourceimagefile:c:\_w8\wimorig\install.wim /sourceindex:1 /destinationimagefile:c:\_w8\win8_x64_ccs_ru\install.wim /destinationname:"Windows 8 CoreCountrySpecific" /compress:max


    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384


    Exporting image
    [==========================100.0%==========================]
    The operation completed successfully.
    After this I replaced install.wim in Win8_64_CCSUS_V1.0.iso with my install.wim created in previous steps.

    During the installation everything was in English and I got an error saying that I do not have an EULA in my image and I was advised by setup to check my installation source for errors. IMHO it's because EULA is not a part of a language pack and there was no EULA in Russian to display by setup.

    So, my question is what did I do wrong and how can I assemble this kind of an image - Windows 8 x64 CoreCountrySpecific Russian?
    p.s. cannot use links yet, cause got less then 20 posts in forum.
     
  14. BTOR

    BTOR MDL Addicted

    Nov 18, 2009
    574
    584
    30
    PLAYING WITH CoreCountrySpecific IS NOT WORTH IT.

    Now for the purpose of learning

    The license [eula] is placed in following folders,

    1. mount the WIM

    2. in windows look for folders

    Windows\System32\Licenses\neutral [_Default] [OEM] [VOLUME] -- [CoreCountrySpecific]

    Windows\System32\ru-RU\Licenses [_Default] [OEM] [VOLUME] -- [CoreCountrySpecific]

    Windows\SysWOW64\Licenses\neutral [_Default] [OEM] [VOLUME] -- [CoreCountrySpecific]

    Windows\SysWOW64\ru-RU\Licenses [_Default] [OEM] [VOLUME] -- [CoreCountrySpecific]

    under each of the above folder there should be a valid license.rtf file

    though only the line marked in red is accessed during setup. so you should check if a valid file is present in those folders.
     
  15. konstanteen

    konstanteen MDL Novice

    Oct 17, 2012
    7
    7
    0
    BTOR, there is only Core folder, so i suppose I should rename it to CoreCountrySpecific and reassemble the wim?

    I disagree regarding "
    PLAYING WITH CoreCountrySpecific IS NOT WORTH IT".
    A friend of mine got notebook from China, and he was assured, that there will be russian interface. There was, because seller entered a banned MAK key and converted this CoreCountrySpecific China version to Windows 8 PRO with illegal licence.
    So my goal is:
    1. switch to Russian interface
    2. stick to original licence key build int BIOS
    I see the altered
    CoreCountrySpecific from China wim image to Russian interface as an only solution. Correct me if I'm wrong.

    UPD:
    Reassembling the install.wim didn't help. Something(last modification date of the boot.wim in the
    Win8_64_CCSUS_V1.0.iso) tells me that I sould check the boot.wim.
    UPD2:
    On boot.wim found nothing, problem is the same :(
     
  16. BTOR

    BTOR MDL Addicted

    Nov 18, 2009
    574
    584
    30
    don't change the core folder to CoreCountrySpecific since we are actually doing a frankenbuild , just check if you have license.rtf in the Windows\System32\ru-RU\Licenses [_Default] [OEM] [VOLUME] then also you should have ei.cfg

    why i am saying not worth it because

    we are actually using a mis-matched xrm license files hence the following limitation will be met

    printer not working

    all personalization not working

    snipping tool not working
     
  17. konstanteen

    konstanteen MDL Novice

    Oct 17, 2012
    7
    7
    0
    #80 konstanteen, Mar 28, 2013
    Last edited by a moderator: Apr 20, 2017
    I copied the license file from Windows\System32\ru-RU\Licenses [_Default] [OEM] [VOLUME] Core folder to the new folder CoreCountrySpecific
    And also I have a ei.cfg in my \Sources\folder with this content in it:
    Code:
    [Channel]
    Retail
    
    [VL]
    0
    This does not help.

    I got Your point of view and I understand that this is a frankenbuild, but it "speaks" Russian not Chinese :)

    I solved problem with language following this way:
    1. Install Windows 8 x64 CCS English from Win8_64_CCSUS_V1.0.iso
    2. Install Russian LP: dism /online /add-package /packagepath:C:\Lang\ru-RU\lp.cab
    3. Restart
    4. Switch to Russian: delete the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MUI\UILanguages\en-US with it's content
    5. Restart
    6. Enjoy!

    Now I think that I should try to leave the English inside the Win8_64_CCSUS_V1.0.iso and add the Russian as default, then maybe it will work out.
    Unfortunately this notebook is not available for tests anymore and the only way to test it is to use virtual machine.