Problems using a Japanese or Traditional Chinese IME on a non-Japanese or non-Traditional Chinese version of Windows 10 immediately after installing the April 2018 Update.

Anonymous
2018-04-30T21:12:28+00:00

To improve Windows’ efficiency, beginning with the April 2018 Update, the Japanese IME and the Traditional Chinese IME dictionaries will be moved to Features on Demand (FOD) if you are not also respectively running a Japanese or Traditional Chinese version of Windows 10.  If you are running a Japanese or Traditional Chinese version of Windows, you will not be affected by this change.  But if, for example, you are running an English version of Windows, when you first add the Japanese IME or Traditional Chinese IME, you won’t be able to immediately type using the IME while the dictionary is busy downloading in the background.    Due to this delay while the IME dictionaries are being downloaded, you may see the following symptoms:

  1. You may not be able to type Japanese or Traditional Chinese characters when first signing into your account. During the setup screens while installing the April 2018 Update, you might not initially be able to type an account name that includes Japanese or Traditional Chinese characters on a non-Japanese or non-Traditional Chinese OS.
  2. You may not be able to type Japanese or Traditional Chinese characters if you do not have an Internet connection or before the dictionary is downloaded. An Internet connection is required to use Features on Demand.  Once you are connected to the Internet, the IME dictionaries will start downloading, but it may take a few minutes.  You will be notified before the downloading is finished.
  3. Windows server update services (WSUS) may not detect your Japanese or Traditional Chinese IME in some corporate environments. WSUS enables system administrators in corporate environments to manage the distribution of updates and hotfixes.  Windows server updates may not detect your IME dictionaries in some cases.
Windows for home | Windows 10 | Settings

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes
Answer accepted by question author
  1. Anonymous
    2018-04-30T21:17:13+00:00

    If you are running a non-Japanese or non-Traditional Chinese version of Windows 10 and are experiencing any of these problems, try these steps to resolve them:

    Symptom 1: You may not able to type Japanese or Traditional Chinese characters when first signing into your account. 

    If you are connected to the Internet, you can wait for the IME dictionaries to download.  If you’d prefer not to wait, or if are not connected to the Internet, when selecting your operating system language, please choose a Japanese or Traditional Chinese operating system.  These languages include pre-loaded IME dictionaries.  In some cases, your PC manufacturer or enterprise may offer a customized Windows 10 you may choose that already includes an IME dictionary to avoid this problem.

    Symptom 2: You may not be able to type Japanese or Traditional Chinese characters if your do not have an Internet connection or before the dictionary is downloaded. 

    If you think you might have problems downloading the IME dictionary, first check if the download was successful.  To do this, open Settings, and select Apps.  Then select Manage Optional Features.  If your Japanese or Traditional Chinese IME dictionaries have been successfully installed, you should see “Japanese typing” or “Chinese (Taiwan) typing” within the list of Optional Features. 

    If you don’t see a successful download, try resolving this issue by manually downloading the IME dictionary.  (These steps require an Internet connection.)

    1. At the Start menu, click Cortana’s search box and type “Command Prompt”.
    2. Right-click Command Prompt in the search results and select Run as Administrator.
    3. In the Command Prompt window, type one of the following command and press Enter to install the basic typing Features on Demand package:
    • For Japanese basic typing:

    DISM.exe /Online /Add-Capability /CapabilityName:Language.Basic~~~ja-JP~0.0.1.0

    • For Traditional Chinese basic typing:

    DISM.exe /Online /Add-Capability /CapabilityName:Language.Basic~~~zh-TW~0.0.1.0

    Symptom 3: Windows server update services (WSUS) may not detect your Japanese or Traditional Chinese IME in some corporate environments. 

    If you’re using Windows 10 Enterprise in a corporate environment and can't type Japanese or Traditional Chinese characters, please ask your local IT administrator for help.

    You can find detailed information about Features on Demand and Language Packs in Windows 10 at these English-language sites:

    Language packages

    Features on demand

    Language features on demand

    1,085 people found this answer helpful.
    0 comments No comments

6 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-06-08T06:52:04+00:00

    DISM.exe /Online /Add-Capability /CapabilityName:Language.Basic~~~ja-JP~0.0.1.0

    doesn't work: 0x800f0950

    23 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-07-06T01:11:57+00:00

    DISM.exe /Online /Add-Capability /CapabilityName:Language.Basic~~~ja-JP~0.0.1.0

    doesn't work: 0x800f0950

    I am having the same issue...

    13 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-07-11T08:06:39+00:00

    I got the error

    Deployment Image Servicing and Management tool

    Version: 10.0.17692.1004

    Image Version: 10.0.17692.1004

    Error: 0x800f0950

    DISM failed. No operation was performed.

    For more information, review the log file.

    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log


    2018-07-11 16:05:12, Info                  DISM   PID=2224 TID=1516 Scratch directory set to 'C:\Users\h\AppData\Local\Temp'. - CDISMManager::put_ScratchDir

    2018-07-11 16:05:12, Info                  DISM   PID=2224 TID=1516 DismCore.dll version: 10.0.17692.1004 - CDISMManager::FinalConstruct

    2018-07-11 16:05:12, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

    2018-07-11 16:05:12, Info                  DISM   PID=2224 TID=1516 Successfully loaded the ImageSession at "C:\WINDOWS\system32\Dism" - CDISMManager::LoadLocalImageSession

    2018-07-11 16:05:12, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=2224 TID=1516 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=2224 TID=1516 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=2224 TID=1516 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect

    2018-07-11 16:05:12, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

    2018-07-11 16:05:12, Info                  DISM   DISM Manager: PID=2224 TID=1516 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE:

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE:

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.17692, Running architecture=amd64, Number of processors=4

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.17692.1004

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Executing command line: DISM.exe  /Online /Add-Capability /CapabilityName:Language.Basic~~~zh-TW~0.0.1.0

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=2224 TID=1516 Connecting to the provider located at C:\WINDOWS\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Manager: PID=2224 TID=1516 physical location path: C:\ - CDISMManager::CreateImageSession

    2018-07-11 16:05:12, Info                  DISM   DISM Manager: PID=2224 TID=1516 Event name for current DISM session is Global{DB94CDB4-DB98-4928-B493-8A2665C4CAD0} - CDISMManager::CheckSessionAndLock

    2018-07-11 16:05:12, Info                  DISM   DISM Manager: PID=2224 TID=1516 Create session event 0x1fc for current DISM session and event name is Global{DB94CDB4-DB98-4928-B493-8A2665C4CAD0}  - CDISMManager::CheckSessionAndLock

    2018-07-11 16:05:12, Info                  DISM   DISM Manager: PID=2224 TID=1516 Copying DISM from "C:\WINDOWS\System32\Dism" - CDISMManager::CreateImageSessionFromLocation

    2018-07-11 16:05:12, Info                  DISM   DISM Manager: PID=2224 TID=1516 Successfully loaded the ImageSession at "C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B" - CDISMManager::LoadRemoteImageSession

    2018-07-11 16:05:12, Info                  DISM   DISM Image Session: PID=7268 TID=3384 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM OS Provider: PID=7268 TID=3384 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect

    2018-07-11 16:05:12, Info                  DISM   DISM OS Provider: PID=7268 TID=3384 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

    2018-07-11 16:05:12, Warning               DISM   DISM Provider Store: PID=7268 TID=3384 Failed to load the provider: C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect

    2018-07-11 16:05:12, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

    2018-07-11 16:05:12, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

    2018-07-11 16:05:12, Info                  DISM   DISM Manager: PID=2224 TID=1516 Image session successfully loaded from the temporary location: C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B - CDISMManager::CreateImageSession

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Target image information: OS Version=10.0.17692.1004, Image architecture=amd64

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Image session version: 10.0.17692.1004

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  CSI    00000001 Shim considered [l:126]'??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17692.1004_none_dcdd6e86dc8d84a7\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND

    2018-07-11 16:05:12, Info                  CSI    00000002 Shim considered [l:123]'??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17692.1004_none_dcdd6e86dc8d84a7\wcp.dll' : got STATUS_SUCCESS

    2018-07-11 16:05:12, Info                  DISM   DISM Package Manager: PID=7268 TID=3384 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize

    2018-07-11 16:05:12, Info                  CSI    00000001 Shim considered [l:126]'??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17692.1004_none_dcdd6e86dc8d84a7\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND

    2018-07-11 16:05:12, Info                  CSI    00000002 Shim considered [l:123]'??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17692.1004_none_dcdd6e86dc8d84a7\wcp.dll' : got STATUS_SUCCESS

    2018-07-11 16:05:12, Info                  DISM   DISM Package Manager: PID=7268 TID=3384 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize

    2018-07-11 16:05:12, Info                  DISM   DISM Package Manager: PID=7268 TID=3384 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  CSI    00000001 Shim considered [l:126]'??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17692.1004_none_dcdd6e86dc8d84a7\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND

    2018-07-11 16:05:12, Info                  CSI    00000002 Shim considered [l:123]'??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17692.1004_none_dcdd6e86dc8d84a7\wcp.dll' : got STATUS_SUCCESS

    2018-07-11 16:05:12, Info                  DISM   DISM Driver Manager: PID=7268 TID=3384 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Warning               DISM   DISM Provider Store: PID=7268 TID=3384 Failed to load the provider: C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\SysprepProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Transmog Provider: PID=7268 TID=3384 Current image session is [ONLINE] - CTransmogManager::GetMode

    2018-07-11 16:05:12, Info                  DISM   DISM Transmog Provider: PID=7268 TID=3384 Audit Mode: [No] - CTransmogManager::Initialize

    2018-07-11 16:05:12, Info                  DISM   DISM Transmog Provider: PID=7268 TID=3384 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType

    2018-07-11 16:05:12, Info                  DISM   DISM Transmog Provider: PID=7268 TID=3384 Product Type: [WinNT] - CTransmogManager::Initialize

    2018-07-11 16:05:12, Info                  DISM   DISM Transmog Provider: PID=7268 TID=3384 Product Type ServerNT : [No] - CTransmogManager::Initialize

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Connecting to the provider located at C:\Users\h\AppData\Local\Temp\25EF356C-6266-4944-90B0-1B6E0BF9961B\SetupPlatformProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IBSManager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AppxManager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AppxManager.

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: ProvManager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: ProvManager.

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AssocManager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AssocManager.

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericManager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericManager.

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: OfflineSetupManager.

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SysprepManager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: SysprepManager.

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SetupPlatformManager

    2018-07-11 16:05:12, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: SetupPlatformManager.

    2018-07-11 16:05:12, Info                  DISM   DISM Package Manager: PID=7268 TID=3384 Processing the top level command token(add-capability). - CPackageManagerCLIHandler::Private_ValidateCmdLine

    2018-07-11 16:05:12, Info                  DISM   DISM Package Manager: PID=7268 TID=3384 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine

    2018-07-11 16:05:12, Info                  DISM   DISM Package Manager: PID=7268 TID=3384 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine

    2018-07-11 16:05:13, Error                 DISM   DISM Package Manager: PID=7268 TID=3384 Failed enumerating capabilities - CDISMPackageManager::GetCapabilityCollection(hr:0x800f0950)

    2018-07-11 16:05:13, Error                 DISM   DISM Package Manager: PID=7268 TID=3384 Failed to get capability collection. - CPackageManagerCLIHandler::Private_GetCapabilitiesFromCommandLine(hr:0x800f0950)

    2018-07-11 16:05:13, Error                 DISM   DISM Package Manager: PID=7268 TID=3384 Failed to get the list of packages from the command line. - CPackageManagerCLIHandler::ProcessCmdLine_AddCapability(hr:0x800f0950)

    2018-07-11 16:05:13, Error                 DISM   DISM Package Manager: PID=7268 TID=3384 Failed while processing command add-capability. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0950)

    2018-07-11 16:05:13, Info                  DISM   DISM Package Manager: PID=7268 TID=3384 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

    2018-07-11 16:05:13, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0950

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Package Manager: PID=7268 TID=3384 Finalizing CBS core. - CDISMPackageManager::Finalize

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(SysprepManager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: SysprepManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Finalizing the servicing provider(SetupPlatformManager) - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: SetupPlatformManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=7268 TID=3384 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Manager: PID=2224 TID=1516 Closing session event handle 0x1fc - CDISMManager::CleanupImageSessionEntry

    2018-07-11 16:05:13, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.

    2018-07-11 16:05:13, Info                  DISM   DISM.EXE:

    2018-07-11 16:05:13, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->

    2018-07-11 16:05:13, Info                  DISM   DISM.EXE:

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=2224 TID=1516 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=2224 TID=1516 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-07-11 16:05:13, Info                  DISM   DISM Provider Store: PID=2224 TID=1516 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

    10 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-07-15T23:20:54+00:00

    I managed to fix the problem by using the "Go back to the previous version of Windows 10" feature under "Update & Security" and "Recovery" in the Settings app, then pausing updates and unpausing updates under "Advanced Options" for Windows Update. Once Windows updated to the latest version again, Japanese IME worked.

    4 people found this answer helpful.
    0 comments No comments