Win 10 1803 update has killed Japanese language keyboard

Multi tool use
I have Japanese users in my group and once win 10 1803 is installed the language pack fails to work properly
Tried the install on a fresh install and it also does not work. Any ideas other than rolling back which I am doing as we speak - still this can't be left broken.
language-pack windows-10-v1803
add a comment |
I have Japanese users in my group and once win 10 1803 is installed the language pack fails to work properly
Tried the install on a fresh install and it also does not work. Any ideas other than rolling back which I am doing as we speak - still this can't be left broken.
language-pack windows-10-v1803
To be specific the keyboard does not allow Japanese typing!!
– Darin McCoy
May 3 '18 at 17:18
What error do you see after installing language pack in lates windows version?
– Biswapriyo
May 3 '18 at 17:18
It does not show an error just doesn't allow for Japanese character typing
– Darin McCoy
May 3 '18 at 17:19
Since version 1803 isn't being automatically pushed until 8 May 2018, I assume that you are testing this build for capability? This isn't the first Super User post we have seen regarding keyboard language issues related to the 1803 release. In a worst-case scenario, you can always configure your machines to defer the update.
– Run5k
May 3 '18 at 18:06
add a comment |
I have Japanese users in my group and once win 10 1803 is installed the language pack fails to work properly
Tried the install on a fresh install and it also does not work. Any ideas other than rolling back which I am doing as we speak - still this can't be left broken.
language-pack windows-10-v1803
I have Japanese users in my group and once win 10 1803 is installed the language pack fails to work properly
Tried the install on a fresh install and it also does not work. Any ideas other than rolling back which I am doing as we speak - still this can't be left broken.
language-pack windows-10-v1803
language-pack windows-10-v1803
edited May 3 '18 at 19:45


magicandre1981
81.5k20125203
81.5k20125203
asked May 3 '18 at 17:16


Darin McCoyDarin McCoy
612
612
To be specific the keyboard does not allow Japanese typing!!
– Darin McCoy
May 3 '18 at 17:18
What error do you see after installing language pack in lates windows version?
– Biswapriyo
May 3 '18 at 17:18
It does not show an error just doesn't allow for Japanese character typing
– Darin McCoy
May 3 '18 at 17:19
Since version 1803 isn't being automatically pushed until 8 May 2018, I assume that you are testing this build for capability? This isn't the first Super User post we have seen regarding keyboard language issues related to the 1803 release. In a worst-case scenario, you can always configure your machines to defer the update.
– Run5k
May 3 '18 at 18:06
add a comment |
To be specific the keyboard does not allow Japanese typing!!
– Darin McCoy
May 3 '18 at 17:18
What error do you see after installing language pack in lates windows version?
– Biswapriyo
May 3 '18 at 17:18
It does not show an error just doesn't allow for Japanese character typing
– Darin McCoy
May 3 '18 at 17:19
Since version 1803 isn't being automatically pushed until 8 May 2018, I assume that you are testing this build for capability? This isn't the first Super User post we have seen regarding keyboard language issues related to the 1803 release. In a worst-case scenario, you can always configure your machines to defer the update.
– Run5k
May 3 '18 at 18:06
To be specific the keyboard does not allow Japanese typing!!
– Darin McCoy
May 3 '18 at 17:18
To be specific the keyboard does not allow Japanese typing!!
– Darin McCoy
May 3 '18 at 17:18
What error do you see after installing language pack in lates windows version?
– Biswapriyo
May 3 '18 at 17:18
What error do you see after installing language pack in lates windows version?
– Biswapriyo
May 3 '18 at 17:18
It does not show an error just doesn't allow for Japanese character typing
– Darin McCoy
May 3 '18 at 17:19
It does not show an error just doesn't allow for Japanese character typing
– Darin McCoy
May 3 '18 at 17:19
Since version 1803 isn't being automatically pushed until 8 May 2018, I assume that you are testing this build for capability? This isn't the first Super User post we have seen regarding keyboard language issues related to the 1803 release. In a worst-case scenario, you can always configure your machines to defer the update.
– Run5k
May 3 '18 at 18:06
Since version 1803 isn't being automatically pushed until 8 May 2018, I assume that you are testing this build for capability? This isn't the first Super User post we have seen regarding keyboard language issues related to the 1803 release. In a worst-case scenario, you can always configure your machines to defer the update.
– Run5k
May 3 '18 at 18:06
add a comment |
1 Answer
1
active
oldest
votes
Copy C:WindowsIMEIMEJPDICTS
from a non 1803 machine. It completely resolved the issue for me.
For whatever reason, the 1803 update jacked up the Japanese dictionary -- thus it didn't know what characters to type.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1319525%2fwin-10-1803-update-has-killed-japanese-language-keyboard%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Copy C:WindowsIMEIMEJPDICTS
from a non 1803 machine. It completely resolved the issue for me.
For whatever reason, the 1803 update jacked up the Japanese dictionary -- thus it didn't know what characters to type.
add a comment |
Copy C:WindowsIMEIMEJPDICTS
from a non 1803 machine. It completely resolved the issue for me.
For whatever reason, the 1803 update jacked up the Japanese dictionary -- thus it didn't know what characters to type.
add a comment |
Copy C:WindowsIMEIMEJPDICTS
from a non 1803 machine. It completely resolved the issue for me.
For whatever reason, the 1803 update jacked up the Japanese dictionary -- thus it didn't know what characters to type.
Copy C:WindowsIMEIMEJPDICTS
from a non 1803 machine. It completely resolved the issue for me.
For whatever reason, the 1803 update jacked up the Japanese dictionary -- thus it didn't know what characters to type.
edited May 24 '18 at 9:56
Kamil Maciorowski
26.3k155680
26.3k155680
answered May 18 '18 at 17:24
Elijah ElyElijah Ely
661
661
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1319525%2fwin-10-1803-update-has-killed-japanese-language-keyboard%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Nw8Zl,ExOdVlsPkYwOo3pk4I,lhFAzwfP1R,n59x5yzB2
To be specific the keyboard does not allow Japanese typing!!
– Darin McCoy
May 3 '18 at 17:18
What error do you see after installing language pack in lates windows version?
– Biswapriyo
May 3 '18 at 17:18
It does not show an error just doesn't allow for Japanese character typing
– Darin McCoy
May 3 '18 at 17:19
Since version 1803 isn't being automatically pushed until 8 May 2018, I assume that you are testing this build for capability? This isn't the first Super User post we have seen regarding keyboard language issues related to the 1803 release. In a worst-case scenario, you can always configure your machines to defer the update.
– Run5k
May 3 '18 at 18:06