Tutorial: Localize Your Windows 8.1 RTM ISO/Distribution

Discussion in 'Windows 8' started by sevenacids, Aug 31, 2013.

  1. sevenacids

    sevenacids MDL Addicted

    Aug 17, 2012
    667
    232
    30
    #1 sevenacids, Aug 31, 2013
    Last edited by a moderator: Apr 20, 2017
  2. sevenacids

    sevenacids MDL Addicted

    Aug 17, 2012
    667
    232
    30
    #2 sevenacids, Aug 31, 2013
    Last edited by a moderator: Apr 20, 2017
    (OP)
  3. OldMX

    OldMX MDL Addicted

    Jul 30, 2009
    538
    229
    30
    Pure gold brother, thanks a lot!!
     
  4. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    7,389
    11,614
    240
    Correct me if I'm wrong, but don't you also need to add the lp stuff to the boot.wim from the win81 adk?
     
  5. sevenacids

    sevenacids MDL Addicted

    Aug 17, 2012
    667
    232
    30
    #7 sevenacids, Sep 1, 2013
    Last edited: Sep 1, 2013
    (OP)
    Yes, that's right, but we don't have the RTM version of the ADK yet, and mixing the final bits with the preview stuff might cause problems. It's not really needed for the boot.wim - it will only change the language during setup. You would like to edit the recovery image inside the install.wim, though (same Windows PE). I will update the tutorial when we have the final ADK.
     
  6. s1ave77

    s1ave77 Has left at his own request

    Aug 15, 2012
    16,104
    24,378
    340
    #8 s1ave77, Sep 1, 2013
    Last edited by a moderator: Apr 29, 2017
    As this code is very sensitive for errors, better use [code=rich][/code], it´s the '#' symbol in post editor. (used the [noparse] feature of BBCode to show :D.)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. VelleX

    VelleX MDL Member

    Jul 14, 2009
    202
    26
    10
    #11 VelleX, Sep 1, 2013
    Last edited by a moderator: Apr 20, 2017
    I tried a much easier way to install localized Windows.
    Just add Languagepacks to an "Langpacks" Folder in the Root of the DVD (like: x:\langpacks\de-de\lp.cab) and edit the "lang.ini" in the sources folder to add the language.
    eg:

    Code:
    [Available UI Languages]
    de-de = 0
    en-US = 3
    
    [Fallback Languages]
    en-US = en-us
    
    I think the "0" should state that the Language Pack isn't installed yet. Then it will be installed after Installation files has been expanded.
    Of course installation may take a little longer, because LP has to be installed.
     
  8. kastrel

    kastrel MDL Member

    Mar 7, 2013
    247
    52
    10
    I used the tool WINDOWS DOWNLOADER INTEGRATOR 3.5 in the WINDOWS 8.1 RTM and integrated the LP in the isos WINDOWS 8.1 using this tool,this method also works well.
     
  9. luky

    luky MDL Addicted

    Dec 21, 2008
    729
    33
    30
    Windows Downloader Integrator v3.5 not OK integrate LP the ISO Windows 8.1.
     
  10. Boops

    Boops MDL Addicted

    Jan 5, 2008
    912
    1,203
    30
    Yes, it does. I've tested, and working correctly. It does Wim image directly.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. Larson

    Larson MDL Junior Member

    Jul 30, 2009
    57
    15
    0
    Great guide, can't wait for you to update it with ADK but please add commands lines to completely remove en-US as well and make not just a multilanguage iso but a localized one.
     
  12. Sliden

    Sliden MDL Junior Member

    May 20, 2009
    90
    53
    0
    #16 Sliden, Sep 1, 2013
    Last edited by a moderator: Apr 20, 2017
    To remove LanguagePack en-US for W8.1 X64 :

    Code:
    DISM.exe /Image:C:\Win81\Mount\Install /remove-package /packagename:Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384
     
  13. Boops

    Boops MDL Addicted

    Jan 5, 2008
    912
    1,203
    30
    #17 Boops, Sep 1, 2013
    Last edited by a moderator: Apr 20, 2017
    I'm not sure we want to do, because in my case, some Apps not correctly translated to my language.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    7,389
    11,614
    240
    #18 murphy78, Sep 1, 2013
    Last edited by a moderator: Apr 20, 2017
    I'm sure he'll cover it tomorrow, but for people who are new to adding languages to Windows install files,
    here's some small bits of advice.

    First:
    -Add language pack cabs (lp.cab) from the appropriate languages to your mounted dism install.wim index
    -You should make all indexes identical with regards to which language packs you add because of the limitations of the lang.ini

    Second:
    -Run the /Gen-LangINI dism option to generate a new lang.ini with appropriate settings for your index.
    Code:
    DISM.exe /image:c:\mount\windows /Gen-LangINI /distribution:c:\my_distribution
    -This will re-create the lang.ini

    Third:
    -Mount the boot.wim index 2
    -Add the winPE lp and component language additions using /add-package
    -You can do a dism /image:c:\mount /get-packages to find out which ones are being used by the primary language, and add ones for the secondary language
    Here's an example of the /get-packages from the win81x86 boot.wim:
    Code:
    Deployment Image Servicing and Management toolVersion: 6.3.9600.16384
    
    
    Image Version: 6.3.9600.16384
    
    
    Packages listing:
    
    
    Package Identity : Microsoft-Windows-Common-Foundation-Package~31bf3856ad364e35~
    x86~~6.3.9600.16384
    State : Install Pending
    Release Type : Feature Pack
    Install Time : 8/22/2013 6:29 AM
    
    
    Package Identity : Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35
    ~x86~en-US~6.3.9600.16384
    State : Install Pending
    Release Type : Language Pack
    Install Time : 8/22/2013 6:47 AM
    
    
    Package Identity : Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~6.3.960
    0.16384
    State : Install Pending
    Release Type : Foundation
    Install Time : 8/22/2013 6:29 AM
    
    
    Package Identity : WinPE-EnhancedStorage-Package~31bf3856ad364e35~x86~en-US~6.3.
    9600.16384
    State : Install Pending
    Release Type : Language Pack
    Install Time : 8/22/2013 6:56 AM
    
    
    Package Identity : WinPE-EnhancedStorage-Package~31bf3856ad364e35~x86~~6.3.9600.
    16384
    State : Install Pending
    Release Type : Feature Pack
    Install Time : 8/22/2013 6:56 AM
    
    
    Package Identity : WinPE-IbsProvider-Package~31bf3856ad364e35~x86~en-US~6.3.9600
    .16384
    State : Install Pending
    Release Type : Language Pack
    Install Time : 8/22/2013 6:55 AM
    
    
    Package Identity : WinPE-IbsProvider-Package~31bf3856ad364e35~x86~~6.3.9600.1638
    4
    State : Install Pending
    Release Type : Feature Pack
    Install Time : 8/22/2013 6:55 AM
    
    
    Package Identity : WinPE-Scripting-Package~31bf3856ad364e35~x86~en-US~6.3.9600.1
    6384
    State : Install Pending
    Release Type : Language Pack
    Install Time : 8/22/2013 6:55 AM
    
    
    Package Identity : WinPE-Scripting-Package~31bf3856ad364e35~x86~~6.3.9600.16384
    State : Install Pending
    Release Type : Feature Pack
    Install Time : 8/22/2013 6:54 AM
    
    
    Package Identity : WinPE-SecureStartup-Package~31bf3856ad364e35~x86~en-US~6.3.96
    00.16384
    State : Install Pending
    Release Type : Language Pack
    Install Time : 8/22/2013 6:56 AM
    
    
    Package Identity : WinPE-SecureStartup-Package~31bf3856ad364e35~x86~~6.3.9600.16
    384
    State : Install Pending
    Release Type : Feature Pack
    Install Time : 8/22/2013 6:55 AM
    
    
    Package Identity : WinPE-Setup-Client-Package~31bf3856ad364e35~x86~en-US~6.3.960
    0.16384
    State : Install Pending
    Release Type : Language Pack
    Install Time : 8/22/2013 6:58 AM
    
    
    Package Identity : WinPE-Setup-Client-Package~31bf3856ad364e35~x86~~6.3.9600.163
    84
    State : Install Pending
    Release Type : Feature Pack
    Install Time : 8/22/2013 6:58 AM
    
    
    Package Identity : WinPE-Setup-Package~31bf3856ad364e35~x86~en-US~6.3.9600.16384
    
    
    State : Install Pending
    Release Type : Language Pack
    Install Time : 8/22/2013 6:58 AM
    
    
    Package Identity : WinPE-Setup-Package~31bf3856ad364e35~x86~~6.3.9600.16384
    State : Install Pending
    Release Type : Feature Pack
    Install Time : 8/22/2013 6:57 AM
    
    
    Package Identity : WinPE-SRT-Package~31bf3856ad364e35~x86~en-US~6.3.9600.16384
    State : Install Pending
    Release Type : Language Pack
    Install Time : 8/22/2013 6:54 AM
    
    
    Package Identity : WinPE-SRT-Package~31bf3856ad364e35~x86~~6.3.9600.16384
    State : Install Pending
    Release Type : Feature Pack
    Install Time : 8/22/2013 6:54 AM
    
    
    Package Identity : WinPE-WDS-Tools-Package~31bf3856ad364e35~x86~en-US~6.3.9600.1
    6384
    State : Install Pending
    Release Type : Language Pack
    Install Time : 8/22/2013 6:55 AM
    
    
    Package Identity : WinPE-WDS-Tools-Package~31bf3856ad364e35~x86~~6.3.9600.16384
    State : Install Pending
    Release Type : Feature Pack
    Install Time : 8/22/2013 6:55 AM
    
    
    Package Identity : WinPE-WMI-Package~31bf3856ad364e35~x86~en-US~6.3.9600.16384
    State : Install Pending
    Release Type : Language Pack
    Install Time : 8/22/2013 6:54 AM
    
    
    Package Identity : WinPE-WMI-Package~31bf3856ad364e35~x86~~6.3.9600.16384
    State : Install Pending
    Release Type : Feature Pack
    Install Time : 8/22/2013 6:54 AM
    
    You can see that there are a few localized features other than just the language pack.
    Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~x86~en-US~6.3.9600.16384
    WinPE-EnhancedStorage-Package~31bf3856ad364e35~x86~en-US~6.3.9600.16384
    WinPE-IbsProvider-Package~31bf3856ad364e35~x86~en-US~6.3.9600.16384
    WinPE-Scripting-Package~31bf3856ad364e35~x86~en-US~6.3.9600.16384
    WinPE-SecureStartup-Package~31bf3856ad364e35~x86~en-US~6.3.9600.16384
    WinPE-Setup-Client-Package~31bf3856ad364e35~x86~en-US~6.3.9600.16384
    WinPE-Setup-Package~31bf3856ad364e35~x86~en-US~6.3.9600.16384
    WinPE-SRT-Package~31bf3856ad364e35~x86~en-US~6.3.9600.16384
    WinPE-WDS-Tools-Package~31bf3856ad364e35~x86~en-US~6.3.9600.16384
    WinPE-WMI-Package~31bf3856ad364e35~x86~en-US~6.3.9600.16384

    You need to add all of these packages for each language. es-es, fr-fr, de-de or whatever.
    If you add Korean, you should know that you also need to add the Korean language support and that it will change the version and add a K to the SKU.
    I believe there is also a Chinese and Japanese font package requirement.

    Fourth:
    -You need to extract the lp.cab to a directory and navigate to the setup directory till you find the lang code of your desired language addition. You need to copy the folder to your distro\sources folder.
    Ex: es-es or fr-fr, etc.
    -This has setup files that will be used for people who install by running setup while in another Windows, rather than installing from boot

    Lastly:
    -Make sure you copy the lang.ini that you generated from your mounted install.wim index /gen-langini command to the boot.wim's mounted sources\ directory.

    Minor notes:
    -Removing a language pack does not reduce the size of the boot.wim as it sets the package removal as a pending removal.
    -Failure to copy the lang.ini to boot.wim index 2 will not give you a choice to install in a different language, and though you might be able to change your language and locale option, the entire setup will be in the primary language. If you do copy the lang.ini to the mounted boot.wim index 2 sources\ directory, it will change the entire setup language.
    -Install any Windows features such as NetFX3 or Hyper-V or anything else you are going to add BEFORE adding the language packs to the install.wim. You will have issues if you try to install them afterwards.
    -Don't add too many languages. It will increase the duration of your setup by approximately 1 minute per language and adds a lot of small files that can bog down the hard drive. Also, you will not be able to boot if you run out of memory from adding too many boot.wim languages. I once tried to do a full 38lang boot.wim with even zh-tw rare lang pack.
    It simply crashed my computer.

    That's about all I remember from when I used to do my lang-addition stuff last october-november.
    Hope it helps someone. Feel free to PM me if you get stuck on something.
     
  15. Sliden

    Sliden MDL Junior Member

    May 20, 2009
    90
    53
    0
    Thanck for this.
     
  16. Boops

    Boops MDL Addicted

    Jan 5, 2008
    912
    1,203
    30
    Fantastic, thank you very much murphy78. :worthy:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...