What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
For a current Intune deployment, package a compatible Windows language-pack CAB and installer as a Win32 app, install it in System context, then configure each user’s language preferences separately. Installing the package alone does not necessarily change the active display language. The older Microsoft Store for Business workflow described in the 2024 HTMD article is legacy; Store for Business was retired, so do not use it as the default path. This guide covers the current Win32 pattern and when to use Store-delivered Local Experience Packs, scripts, or offline image servicing instead.
Windows 10 note: ordinary Windows 10 support ended on October 14, 2025. In 2026, use these steps only for Windows 10 devices covered by an applicable extended-support arrangement or other support plan. For new deployments, prefer a supported Windows 11 release. Package compatibility still depends on OS build, edition, architecture, and language.
What you are deploying: package versus language settings
“Language pack” can refer to different Windows components. Choose the right one before packaging anything:
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Language Pack (LP): broad Windows localization content, often delivered as a servicing package such as a CAB.
- Language Interface Pack (LIP): partial localization for a subset of interface content; it is not interchangeable with a full LP.
- Local Experience Pack (LXP): a Store-delivered package intended to localize the Windows experience. Availability and delivery depend on the language, Windows version, region, and Store configuration.
- Features on Demand (FOD): optional capabilities such as basic typing, handwriting, OCR, speech recognition, and text-to-speech. A base language package may not include everything users need.
- Language preferences: per-user display-language choice, preferred-language order, keyboard layout, and regional format. Related device settings include system locale and home location.
These are separate outcomes. A package can install successfully while the user still sees the previous display language. A device may also have the interface language it needs but lack handwriting or speech features. Microsoft’s Local Experience Packs overview explains the LXP model; the original HTMD guide also distinguishes LPs, LIPs, and LXPs.
#1 Best Overall
- 1.1 GHz (boost up to 2.4GHz) Intel Celeron N5030 Quad-Core
Choose a deployment method
| Need | Practical method | Trade-off |
|---|---|---|
| Deploy a version-matched language-pack CAB or several related files | Intune Win32 app | Requires packaging, compatibility checks, and reliable detection. |
| Use a Store-delivered language experience that is available in your tenant | Current Microsoft Store app integration | Catalog availability and delivery behavior vary; installing the app still may not activate it for users. |
| Automate a Store or repository app that is available through Windows Package Manager | WinGet, invoked through an approved management workflow | Not a general replacement for version-specific Windows servicing CABs; catalog identity, Store access, user session, and elevation can matter. |
| Have language content present before first sign-in | Offline image servicing with DISM | Requires image lifecycle management and validation for each Windows servicing baseline. |
| Change only a user’s locale or preferred language | Intune PowerShell script or remediation in the user context | Does not install missing language content or optional features. |
| Support many locales or user populations | Language-specific assignments using groups, filters, or provisioning profiles | Targeting data and assignment timing must be dependable. |
For a controlled CAB-based enterprise deployment, a Win32 app is a useful general-purpose pattern, not an official ranking of Microsoft methods. Intune Win32 apps support packaged files and scripts, custom commands, requirements, dependencies, and detection rules; see Microsoft’s Win32 app management documentation.
Before you start
- Confirm the devices are enrolled in Intune and you have rights to add and assign Windows apps.
- Identify whether you need a full LP, an LXP, a LIP, one or more FOD capabilities, or only user settings.
- Record the target language tag, such as
en-GB, and the required keyboard layouts, regional format, and system locale. A regional variant may not have its own full CAB. - Check the Windows release/build, edition, and processor architecture (for example, x64 or ARM64). Obtain language content from an authorized Microsoft source and verify that it applies to the target baseline. Do not use CAB files from unverified third-party mirrors.
- Determine how optional features will be sourced. Depending on the deployment, devices may need access to Windows Update, Microsoft Store, or another approved content source.
- Decide whether the target is a single-user PC, shared device, Cloud PC, Azure Virtual Desktop session host, or Autopilot device. Those cases affect timing and whether settings must apply to one user or many.
- Plan for separate package-installation and user-configuration steps. A device-context install does not by itself configure every current or future user.
A CAB-based example and packaging pattern is documented in HTMD’s Win32 language-pack walkthrough. Its package and minimum Windows version are historical examples, not universal settings for current Windows releases.
Deploy a CAB as an Intune Win32 app
1. Prepare and validate the language content
Choose the exact language and components first. Verify the package’s language tag, Windows release applicability, architecture, and whether separate FOD packages are required. Use a lab device with the same relevant Windows baseline as the deployment group. If the CAB is not intended for that baseline, stop rather than treating a successful upload as proof of compatibility.
2. Create an installer that fails clearly
Place the installer and CAB together in a source folder. The following example installs a CAB online with no automatic restart and writes a marker only after the package command succeeds. Replace the example filename, language tag, and marker location. Validate the package and detection approach in a test ring before broad assignment.
$ErrorActionPreference = "Stop"
$PackagePath = Join-Path $PSScriptRoot "Microsoft-Windows-Client-Language-Pack_x64_en-GB.cab"
$MarkerPath = "C:ProgramDataContosoLanguagePack-en-GB.txt"
if (-not (Test-Path -LiteralPath $PackagePath)) {
throw "Language-pack CAB not found: $PackagePath"
}
New-Item -ItemType Directory -Path (Split-Path -Parent $MarkerPath) -Force | Out-Null
Add-WindowsPackage -Online -PackagePath $PackagePath -NoRestart
"en-GB installed $(Get-Date -Format o)" |
Set-Content -LiteralPath $MarkerPath -Encoding UTF8Run this as a packaged Win32 installation in System context so the servicing operation is not dependent on an interactive user. In production, consider adding a log file and validating the installed package state before writing the marker. A marker is only as trustworthy as the script that creates it. Do not remove the source files before Intune has completed installation and detection.
Rank #2
- 256 GB SSD of storage.
- Multitasking is easy with 16GB of RAM
- Equipped with a blazing fast Core i5 2.00 GHz processor.
Language-pack removal is not necessarily equivalent to uninstalling an ordinary app. Do not point the Intune uninstall command at the install script. Either provide a separately tested removal procedure for your package and OS baseline, or configure the app as install-only and document that decision.
3. Package the source as an .intunewin file
Use Microsoft’s Win32 Content Prep Tool. A simple source layout is:
Free tools Windows power users keep installed
One-click scans. No signup required.
Source
Install-LanguagePack.ps1
Microsoft-Windows-Client-Language-Pack_x64_en-GB.cabRun IntuneWinAppUtil.exe, select the source folder, and choose Install-LanguagePack.ps1 as the setup file. Save the generated .intunewin package in a separate output folder.
4. Add and configure the Intune app
In the Intune admin center, the functional workflow is Apps > Windows > Windows apps > Add > Windows app (Win32). Upload the .intunewin file, provide app information, and configure the install behavior, requirements, detection, and assignments.
Use an install command such as:
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .Install-LanguagePack.ps1- Install behavior: System.
- Requirements: restrict by architecture, Windows build, and edition as needed. Use a custom requirement or assignment filter if package applicability is narrower than your device population.
- Detection: prefer a stable package identity or verified installed-package/capability state when one is dependable for your supported baselines. If using a marker file, make it specific to the language and package version and write it only after successful installation.
- Assignments: target only compatible devices. Use a test group first, then expand after checking installation and user-facing results.
A marker-file rule can check for C:ProgramDataContosoLanguagePack-en-GB.txt, but that proves only that your installer wrote the marker. It does not independently prove that Windows has the desired language active. Avoid detecting a temporary folder or an unversioned generic file that could be left behind from an earlier attempt.
Rank #3
- 14" diagonal, 1366x768 resolution, HD BrightView LED, Glossy NON-TOUCH Display
5. Configure the user’s language preferences separately
After the package is available, use a separate PowerShell script in the intended user context to configure per-user preferences. For example, this sets the preferred language list to just en-GB, changes culture, sets the system locale, and sets the home-location GeoID used in the original HTMD example:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11$LanguageTag = "en-GB"
$GeoId = 242
Set-Culture -CultureInfo $LanguageTag
Set-WinSystemLocale -SystemLocale $LanguageTag
Set-WinUserLanguageList -LanguageList $LanguageTag -Force
Set-WinHomeLocation -GeoId $GeoIdDo not copy this unchanged if users need multiple languages or keyboards. Set-WinUserLanguageList replaces the existing list; it can remove a user’s preferred languages and input layouts. Build and test a list that preserves required entries, or apply a policy that matches your organization’s intent. The system-locale command changes a device-level setting, while the user language list and culture are user-related preferences. Run each in the intended context. A sign-out or restart may be needed before the user sees the new interface language.
The original HTMD article reports testing these commands and recommends a restart or logoff. Treat them as a configuration pattern to validate in your environment, not as a guarantee that every Windows build, account type, or language variant activates identically.
Verify both installation and user experience
Check the Intune app’s device installation status, the install exit code, and the detection-rule result. On the device, inspect the intended user’s settings with:
Get-Culture
Get-WinUserLanguageList
Get-WinSystemLocale
Get-WinHomeLocationAlso check intl.cpl and Windows Settings for the display language, preferred languages, keyboard, and regional format. If speech, handwriting, or OCR is part of the requirement, verify those features independently; the base LP may not provide them.
Rank #4
- EFFORTLESS EVERYDAY PERFORMANCE: Powered by Intel Celeron N4020 processor and Windows 11 Home system, delivering reliable, low-power efficiency for daily tasks like document editing, email, online classes, and web browsing
- 15.6-INCH FULL HD DISPLAY: Enjoy immersive visuals on the 15.6" FHD (1920x1080) anti-glare screen with micro-edge bezels. Delivers clear details and comfortable viewing for long study sessions, working on spreadsheets, and video playback
- RESPONSIVE MULTITASKING & STORAGE: Built with 4GB LPDDR4 RAM and 128GB eMMC storage for smooth daily essential use. Expand your storage by up to 1TB via the integrated TF card slot to easily store movies, photos, and working files
- ADVANCED CONNECTIVITY: Outfitted with 2x Full-Featured Type-C ports for data transfer, fast charging, and dual-monitor output, alongside 2x USB 3.2 Gen1 ports and a 3.5mm audio jack for complete peripheral compatibility
- LIGHTWEIGHT & SILENT OPERATION: Slim and portable for effortless travel or commuting. Features a 1MP HD webcam for remote meetings, 38Wh battery with 45W Type-C fast charging, and a fanless silent design for peaceful work environments.
For failures, collect Intune Management Extension logs, the app’s detection result and exit code, and relevant servicing records such as DISM and CBS logs. For Store- or Windows Update-delivered content, investigate the corresponding delivery access and logs as well. Define success as two checks: the required package/capability is installed and the intended user has the expected language settings after sign-out or restart.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Other supported deployment paths
Store-delivered LXP
Use a current Microsoft Store integration only when the required language experience is actually available and your tenant and device configuration support it. Store delivery can simplify package distribution, but it does not necessarily set the active display language. Do not follow older instructions to import and synchronize apps through Microsoft Store for Business; that service was retired. The 2024 article’s workflow is useful as historical context, not a current deployment recipe.
WinGet
WinGet can automate supported applications in its catalog, but it is not a universal language-pack installer. Confirm that the exact package has a stable catalog identity and that Store, source-agreement, user-session, and elevation requirements fit your managed deployment. See the HTMD discussion of WinGet and Intune for the Store retirement context.
Offline image servicing
For reference images or provisioning where language content should exist before the first sign-in, DISM can add a package to a mounted Windows image. The general pattern is:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteDISM /Image:C:MountWindows /Add-Package /PackagePath:C:RepositoryMicrosoft-Windows-Client-Language-Pack_x64_en-GB.cabUse content matched to the image and maintain the image as Windows releases and servicing baselines change. Image servicing does not remove the need to configure each user’s language preferences. See HTMD’s offline DISM language-pack example.
Best Value
- 【Efficient Performance】 Powered by Intel Core i3 processor (2 cores, 4 threads, up to 3.4GHz) with 12GB RAM and 256GB SSD. Handles multitasking, office software, online classes, and HD video streaming smoothly. Integrated Intel UHD Graphics 620
- Backlit Keyboard & Complete Package】Comes with a cool backlit keyboard. Comes with awebcam, dual stereo speakers (8Ω/1.0W each), DC charger, and user manual – ready for late-night studying, online classes, video conferencing, and daily productivity
- 【Vibrant Display】 15.6-inch Full HD (1920x1080) anti-glare screen with 16:9 aspect ratio delivers crisp images and vivid colors – perfect for studying, watching lectures, or entertainment. Thin-bezel design maximizes viewing area
- 【Fast Connectivity & Expansion】 Equipped with WiFi 6 (802.11ax) and Bluetooth 5.2 for stable, high-speed wireless. Features 3 x USB 3.0, HDMI 2.1, Type-C (supports PD3.0 fast charging), and a TF card slot expandable up to 2TB – easily connect external monitors, mice, drives, or expand storage for all your files
- 【Long Battery Life & Portable】 Built-in 11.55V 5000mAh/57.75Wh high-capacity battery delivers approximately 7 hours of mixed-use battery life – enough for a full day of classes and assignments. Lightweight at just 1.63kg (3.6 lbs) and 19.5mm thin, plus a compact packing size – easily slips into a backpack for campus, library, or coffee shop
Troubleshooting common failures
Intune reports installed, but the display language is unchanged
- Confirm the actual package or capability is installed; do not rely only on a marker file.
- Check that the intended user’s language list and culture were configured in that user’s context.
- Check whether the existing preferred-language order still selects another language.
- Sign out or restart, then check Windows Settings and the language commands again.
- Confirm the package is the expected type and matches the OS release and architecture.
Package installation and display-language activation are separate states. The original HTMD article’s comments describe this same kind of mismatch; its practical lesson is to verify user settings and restart behavior rather than infer activation from app status.
The requested language or regional variant is not available
Not every language shown in Settings has a separate full CAB or LXP. A regional variant may use a parent language or a different package model. Confirm availability in the current Microsoft content for the exact Windows release before building assignments; do not assume that an English regional variant, for example, has an independently downloadable full language pack.
Speech, handwriting, or OCR is missing
Identify and deploy the matching FOD capability, then verify its content source is reachable. The base LP alone may not provide the optional feature. Delivery can require Windows Update or another approved source and can involve additional bandwidth.
Recommended Free Tools
Autopilot deployment is inconsistent
Check whether the language app is assigned and installed before the user-configuration script runs. Dynamic group membership may arrive too late, and required-app assignment order should not be assumed deterministic. Use dependencies or another tested ordering strategy where available, avoid disruptive restarts during Enrollment Status Page processing, and validate the complete first-sign-in sequence on representative devices.
Shared devices show different languages for different users
A user-context language-list change affects that user, not every future user of the PC. Decide whether you need a device-wide system locale, a default for new profiles, a per-user display language, or simply a user-selectable option. Choose a mechanism and test it against the shared-device design rather than assuming one user’s profile settings are global.
Windows 10 and Windows 11 are not interchangeable targets
The original HTMD article covers Windows 10, and its companion CAB example uses a historical Windows 10 baseline. Do not carry its old minimum version, architecture assumptions, or package file forward as a universal 2026 configuration. Validate package applicability separately for each Windows release, architecture, edition, and servicing baseline. Microsoft lists October 14, 2025 as the end-of-support date for ordinary Windows 10 support; see the Windows end-of-support page for current lifecycle information. Windows 10 deployment in 2026 should be limited to devices with an applicable support arrangement.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
