Install Language Pack On Windows Server Core (2012 R2) Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!How can I deploy Language Packs to Windows 7 Enterprise domain clients using WSUS?How do I install dotNet Framework 3.51 on Windows Server 2012 core?How to handle updates that aren't appropriate for Server Core editions?Approvals Inheritance for WSUS on windows server 2012 R2unattend file not working with any language packUnable to install .NET Framework 4.6 on Windows Server 2012 R2 CoreApplication localization problems in english windows server 2012Windows Server 2012 R2 Server Core - source files could not be downloaded regardless of source specifiedConvert Windows Server 2016 Desktop Experience to CoreNo recent Windows updates showing as applicable in WSUS
Problem when applying foreach loop
Estimate capacitor parameters
Why does tar appear to skip file contents when output file is /dev/null?
Replacing HDD with SSD; what about non-APFS/APFS?
How to rotate it perfectly?
Can a zero nonce be safely used with AES-GCM if the key is random and never used again?
Is above average number of years spent on PhD considered a red flag in future academia or industry positions?
The following signatures were invalid: EXPKEYSIG 1397BC53640DB551
Do working physicists consider Newtonian mechanics to be "falsified"?
If A makes B more likely then B makes A more likely"
What items from the Roman-age tech-level could be used to deter all creatures from entering a small area?
Cold is to Refrigerator as warm is to?
Slither Like a Snake
Blender game recording at the wrong time
How do I keep my slimes from escaping their pens?
What can I do if my MacBook isn’t charging but already ran out?
What do you call the holes in a flute?
Was credit for the black hole image misattributed?
Cauchy Sequence Characterized only By Directly Neighbouring Sequence Members
Did the new image of black hole confirm the general theory of relativity?
Choo-choo! Word trains
Passing functions in C++
Can I add database to AWS RDS MySQL without creating new instance?
Why is there no army of Iron-Mans in the MCU?
Install Language Pack On Windows Server Core (2012 R2)
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!How can I deploy Language Packs to Windows 7 Enterprise domain clients using WSUS?How do I install dotNet Framework 3.51 on Windows Server 2012 core?How to handle updates that aren't appropriate for Server Core editions?Approvals Inheritance for WSUS on windows server 2012 R2unattend file not working with any language packUnable to install .NET Framework 4.6 on Windows Server 2012 R2 CoreApplication localization problems in english windows server 2012Windows Server 2012 R2 Server Core - source files could not be downloaded regardless of source specifiedConvert Windows Server 2016 Desktop Experience to CoreNo recent Windows updates showing as applicable in WSUS
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have language packs KB3012997 and KB2839636 staged and approved in Windows Server Update Services 2012 R2, but my Windows Server Core 2012 R2 clients refuse to install it. After googling the issue, it appears that these language pack updates are unable to be installed via WSUS, and have to be manually installed on the clients via the Language Control Panel. Unfortunately the Language Control Panel is not available on the Core edition of Windows server, both control.exe input.dll and control.exe /name Microsoft.Language do not work. I've tried installing the CAB files manually with dism /online /Add-Package /Package-Name:E:WsusContent65F1C5505C26603C0E907DEDD5A4B3A0E6511E44C65.cab but the updates are not registered as being installed in the WSUS console.
How can I go about getting these language packs installed on Server Core 2012 R2? Yes I know these language packs do little to nothing on Server Core. And that I could work around this issue by creating separate groups in the WSUS console for the Core and non-Core editions of Windows Server, and approving these updates only for the non-Core editions. But to satisfy my autism i'd like to get these updates installed anyways, because if they really were never intended to target Core editions of Windows Server, i'm assuming the WSUS console wouldn't say my Core servers are applicable for them. Right now the only way I can think of is using a tool like Altiris RapidInstall or Sysinternals Process Monitor to see what file/registry changes are made while adding a language pack on a non-Core edition of Windows Server, after it has already been installed with dism.exe and then applying these changes to the Core edition servers.
windows-server-2012 windows-server-2012-r2 windows-server-core language-packs
asked May 31 '16 at 17:35
MattMatt
222211
add a comment |
I have language packs KB3012997 and KB2839636 staged and approved in Windows Server Update Services 2012 R2, but my Windows Server Core 2012 R2 clients refuse to install it. After googling the issue, it appears that these language pack updates are unable to be installed via WSUS, and have to be manually installed on the clients via the Language Control Panel. Unfortunately the Language Control Panel is not available on the Core edition of Windows server, both control.exe input.dll and control.exe /name Microsoft.Language do not work. I've tried installing the CAB files manually with dism /online /Add-Package /Package-Name:E:WsusContent65F1C5505C26603C0E907DEDD5A4B3A0E6511E44C65.cab but the updates are not registered as being installed in the WSUS console.
How can I go about getting these language packs installed on Server Core 2012 R2? Yes I know these language packs do little to nothing on Server Core. And that I could work around this issue by creating separate groups in the WSUS console for the Core and non-Core editions of Windows Server, and approving these updates only for the non-Core editions. But to satisfy my autism i'd like to get these updates installed anyways, because if they really were never intended to target Core editions of Windows Server, i'm assuming the WSUS console wouldn't say my Core servers are applicable for them. Right now the only way I can think of is using a tool like Altiris RapidInstall or Sysinternals Process Monitor to see what file/registry changes are made while adding a language pack on a non-Core edition of Windows Server, after it has already been installed with dism.exe and then applying these changes to the Core edition servers.
windows-server-2012 windows-server-2012-r2 windows-server-core language-packs
asked May 31 '16 at 17:35
MattMatt
222211
1
You might see if this helps: technet.microsoft.com/en-us/library/cc766472(v=ws.10).aspx That article makes me think that if a core build doesn't have Intlcfg.exe, then language packs will be useless. Also, I wouldn't assume that the WSUS console has accurate knowledge of what updates should be applied in all cases. It wouldn't be the first problem/mistake with a Microsoft tool by a long shot.
– Todd Wilcox
May 31 '16 at 19:09
add a comment |
I have language packs KB3012997 and KB2839636 staged and approved in Windows Server Update Services 2012 R2, but my Windows Server Core 2012 R2 clients refuse to install it. After googling the issue, it appears that these language pack updates are unable to be installed via WSUS, and have to be manually installed on the clients via the Language Control Panel. Unfortunately the Language Control Panel is not available on the Core edition of Windows server, both control.exe input.dll and control.exe /name Microsoft.Language do not work. I've tried installing the CAB files manually with dism /online /Add-Package /Package-Name:E:WsusContent65F1C5505C26603C0E907DEDD5A4B3A0E6511E44C65.cab but the updates are not registered as being installed in the WSUS console.
How can I go about getting these language packs installed on Server Core 2012 R2? Yes I know these language packs do little to nothing on Server Core. And that I could work around this issue by creating separate groups in the WSUS console for the Core and non-Core editions of Windows Server, and approving these updates only for the non-Core editions. But to satisfy my autism i'd like to get these updates installed anyways, because if they really were never intended to target Core editions of Windows Server, i'm assuming the WSUS console wouldn't say my Core servers are applicable for them. Right now the only way I can think of is using a tool like Altiris RapidInstall or Sysinternals Process Monitor to see what file/registry changes are made while adding a language pack on a non-Core edition of Windows Server, after it has already been installed with dism.exe and then applying these changes to the Core edition servers.
windows-server-2012 windows-server-2012-r2 windows-server-core language-packs
asked May 31 '16 at 17:35
MattMatt
222211
I have language packs KB3012997 and KB2839636 staged and approved in Windows Server Update Services 2012 R2, but my Windows Server Core 2012 R2 clients refuse to install it. After googling the issue, it appears that these language pack updates are unable to be installed via WSUS, and have to be manually installed on the clients via the Language Control Panel. Unfortunately the Language Control Panel is not available on the Core edition of Windows server, both control.exe input.dll and control.exe /name Microsoft.Language do not work. I've tried installing the CAB files manually with dism /online /Add-Package /Package-Name:E:WsusContent65F1C5505C26603C0E907DEDD5A4B3A0E6511E44C65.cab but the updates are not registered as being installed in the WSUS console.
How can I go about getting these language packs installed on Server Core 2012 R2? Yes I know these language packs do little to nothing on Server Core. And that I could work around this issue by creating separate groups in the WSUS console for the Core and non-Core editions of Windows Server, and approving these updates only for the non-Core editions. But to satisfy my autism i'd like to get these updates installed anyways, because if they really were never intended to target Core editions of Windows Server, i'm assuming the WSUS console wouldn't say my Core servers are applicable for them. Right now the only way I can think of is using a tool like Altiris RapidInstall or Sysinternals Process Monitor to see what file/registry changes are made while adding a language pack on a non-Core edition of Windows Server, after it has already been installed with dism.exe and then applying these changes to the Core edition servers.
windows-server-2012 windows-server-2012-r2 windows-server-core language-packs
windows-server-2012 windows-server-2012-r2 windows-server-core language-packs
asked May 31 '16 at 17:35
MattMatt
222211
asked May 31 '16 at 17:35
MattMatt
222211
asked May 31 '16 at 17:35
MattMatt
222211
asked May 31 '16 at 17:35
MattMatt
222211
asked May 31 '16 at 17:35
MattMatt
222211
222211
1
You might see if this helps: technet.microsoft.com/en-us/library/cc766472(v=ws.10).aspx That article makes me think that if a core build doesn't have Intlcfg.exe, then language packs will be useless. Also, I wouldn't assume that the WSUS console has accurate knowledge of what updates should be applied in all cases. It wouldn't be the first problem/mistake with a Microsoft tool by a long shot.
– Todd Wilcox
May 31 '16 at 19:09
add a comment |
1
You might see if this helps: technet.microsoft.com/en-us/library/cc766472(v=ws.10).aspx That article makes me think that if a core build doesn't have Intlcfg.exe, then language packs will be useless. Also, I wouldn't assume that the WSUS console has accurate knowledge of what updates should be applied in all cases. It wouldn't be the first problem/mistake with a Microsoft tool by a long shot.
– Todd Wilcox
May 31 '16 at 19:09
1
1
You might see if this helps: technet.microsoft.com/en-us/library/cc766472(v=ws.10).aspx That article makes me think that if a core build doesn't have Intlcfg.exe, then language packs will be useless. Also, I wouldn't assume that the WSUS console has accurate knowledge of what updates should be applied in all cases. It wouldn't be the first problem/mistake with a Microsoft tool by a long shot.
– Todd Wilcox
May 31 '16 at 19:09
You might see if this helps: technet.microsoft.com/en-us/library/cc766472(v=ws.10).aspx That article makes me think that if a core build doesn't have Intlcfg.exe, then language packs will be useless. Also, I wouldn't assume that the WSUS console has accurate knowledge of what updates should be applied in all cases. It wouldn't be the first problem/mistake with a Microsoft tool by a long shot.
– Todd Wilcox
May 31 '16 at 19:09
add a comment |
1 Answer
1
active
oldest
votes
This is working as designed. It is a "feature" / "defect" of WSUS exposed by a select group of "updates" that are not in fact updates in the typical meaning of the term.
Certain WSUS updates including language packs are detected as applicable to a machine in the sense that they may optionally be installed manually by some mechanism outside of Windows Update. By approving the update you are making the update available to be downloaded from WSUS however this does not actually trigger any automatic download or installation. It is necessary to trigger the update through another tool such as the Control Panel language settings.
In addition to language packs various dynamic installers have similar functionality for similar reasons. The dynamic installers are downloaded from WSUS at the time that an installation is run, but are not in fact updates for the system upon which the installation is being run (they update the installer, not the system). They will not register as installed because they do not get installed onto the system, and may be downloaded multiple times if the installer is run multiple times.
This is working as designed, so it is a "feature" that WSUS is able to provide the files from a content delivery system under administrative control and presumably caching/delivering the content closer to the client.
This is fundamentally different from the typical expected behaviour of WSUS, so it is arguably a design "defect" that WSUS handles optional components including language packs in a completely different manor from the vast majority of updates which will automatically be installed by Windows Update.
To install on server core the DISM or LPKSETUP commands can be used.
https://technet.microsoft.com/en-us/library/hh825679.aspx
https://technet.microsoft.com/en-us/library/hh825178.aspx
answered Oct 13 '17 at 5:01
DougDoug
1466
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
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%2fserverfault.com%2fquestions%2f780078%2finstall-language-pack-on-windows-server-core-2012-r2%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
This is working as designed. It is a "feature" / "defect" of WSUS exposed by a select group of "updates" that are not in fact updates in the typical meaning of the term.
Certain WSUS updates including language packs are detected as applicable to a machine in the sense that they may optionally be installed manually by some mechanism outside of Windows Update. By approving the update you are making the update available to be downloaded from WSUS however this does not actually trigger any automatic download or installation. It is necessary to trigger the update through another tool such as the Control Panel language settings.
In addition to language packs various dynamic installers have similar functionality for similar reasons. The dynamic installers are downloaded from WSUS at the time that an installation is run, but are not in fact updates for the system upon which the installation is being run (they update the installer, not the system). They will not register as installed because they do not get installed onto the system, and may be downloaded multiple times if the installer is run multiple times.
This is working as designed, so it is a "feature" that WSUS is able to provide the files from a content delivery system under administrative control and presumably caching/delivering the content closer to the client.
This is fundamentally different from the typical expected behaviour of WSUS, so it is arguably a design "defect" that WSUS handles optional components including language packs in a completely different manor from the vast majority of updates which will automatically be installed by Windows Update.
To install on server core the DISM or LPKSETUP commands can be used.
https://technet.microsoft.com/en-us/library/hh825679.aspx
https://technet.microsoft.com/en-us/library/hh825178.aspx
answered Oct 13 '17 at 5:01
DougDoug
1466
add a comment |
This is working as designed. It is a "feature" / "defect" of WSUS exposed by a select group of "updates" that are not in fact updates in the typical meaning of the term.
Certain WSUS updates including language packs are detected as applicable to a machine in the sense that they may optionally be installed manually by some mechanism outside of Windows Update. By approving the update you are making the update available to be downloaded from WSUS however this does not actually trigger any automatic download or installation. It is necessary to trigger the update through another tool such as the Control Panel language settings.
In addition to language packs various dynamic installers have similar functionality for similar reasons. The dynamic installers are downloaded from WSUS at the time that an installation is run, but are not in fact updates for the system upon which the installation is being run (they update the installer, not the system). They will not register as installed because they do not get installed onto the system, and may be downloaded multiple times if the installer is run multiple times.
This is working as designed, so it is a "feature" that WSUS is able to provide the files from a content delivery system under administrative control and presumably caching/delivering the content closer to the client.
This is fundamentally different from the typical expected behaviour of WSUS, so it is arguably a design "defect" that WSUS handles optional components including language packs in a completely different manor from the vast majority of updates which will automatically be installed by Windows Update.
To install on server core the DISM or LPKSETUP commands can be used.
https://technet.microsoft.com/en-us/library/hh825679.aspx
https://technet.microsoft.com/en-us/library/hh825178.aspx
answered Oct 13 '17 at 5:01
DougDoug
1466
add a comment |
This is working as designed. It is a "feature" / "defect" of WSUS exposed by a select group of "updates" that are not in fact updates in the typical meaning of the term.
Certain WSUS updates including language packs are detected as applicable to a machine in the sense that they may optionally be installed manually by some mechanism outside of Windows Update. By approving the update you are making the update available to be downloaded from WSUS however this does not actually trigger any automatic download or installation. It is necessary to trigger the update through another tool such as the Control Panel language settings.
In addition to language packs various dynamic installers have similar functionality for similar reasons. The dynamic installers are downloaded from WSUS at the time that an installation is run, but are not in fact updates for the system upon which the installation is being run (they update the installer, not the system). They will not register as installed because they do not get installed onto the system, and may be downloaded multiple times if the installer is run multiple times.
This is working as designed, so it is a "feature" that WSUS is able to provide the files from a content delivery system under administrative control and presumably caching/delivering the content closer to the client.
This is fundamentally different from the typical expected behaviour of WSUS, so it is arguably a design "defect" that WSUS handles optional components including language packs in a completely different manor from the vast majority of updates which will automatically be installed by Windows Update.
To install on server core the DISM or LPKSETUP commands can be used.
https://technet.microsoft.com/en-us/library/hh825679.aspx
https://technet.microsoft.com/en-us/library/hh825178.aspx
answered Oct 13 '17 at 5:01
DougDoug
1466
This is working as designed. It is a "feature" / "defect" of WSUS exposed by a select group of "updates" that are not in fact updates in the typical meaning of the term.
Certain WSUS updates including language packs are detected as applicable to a machine in the sense that they may optionally be installed manually by some mechanism outside of Windows Update. By approving the update you are making the update available to be downloaded from WSUS however this does not actually trigger any automatic download or installation. It is necessary to trigger the update through another tool such as the Control Panel language settings.
In addition to language packs various dynamic installers have similar functionality for similar reasons. The dynamic installers are downloaded from WSUS at the time that an installation is run, but are not in fact updates for the system upon which the installation is being run (they update the installer, not the system). They will not register as installed because they do not get installed onto the system, and may be downloaded multiple times if the installer is run multiple times.
This is working as designed, so it is a "feature" that WSUS is able to provide the files from a content delivery system under administrative control and presumably caching/delivering the content closer to the client.
This is fundamentally different from the typical expected behaviour of WSUS, so it is arguably a design "defect" that WSUS handles optional components including language packs in a completely different manor from the vast majority of updates which will automatically be installed by Windows Update.
To install on server core the DISM or LPKSETUP commands can be used.
https://technet.microsoft.com/en-us/library/hh825679.aspx
https://technet.microsoft.com/en-us/library/hh825178.aspx
answered Oct 13 '17 at 5:01
DougDoug
1466
answered Oct 13 '17 at 5:01
DougDoug
1466
answered Oct 13 '17 at 5:01
DougDoug
1466
answered Oct 13 '17 at 5:01
DougDoug
1466
1466
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f780078%2finstall-language-pack-on-windows-server-core-2012-r2%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
1
You might see if this helps: technet.microsoft.com/en-us/library/cc766472(v=ws.10).aspx That article makes me think that if a core build doesn't have Intlcfg.exe, then language packs will be useless. Also, I wouldn't assume that the WSUS console has accurate knowledge of what updates should be applied in all cases. It wouldn't be the first problem/mistake with a Microsoft tool by a long shot.
– Todd Wilcox
May 31 '16 at 19:09