At some point in my checkered career with Windows 8, 8.1, or 10 I apparently downloaded and installed the UK language version (en-GB) on one of my machines, probably through an ill-chosen MSDN download. If you want to repair a Windows image using DISM, the source material for repair and the target image must be identical (same OS, same bittedness – that is, x86 or 圆4, same default language). Identifying and changing international settings Interestingly – and this leads to the next and final item in this article – it also shows that the default language for the image is en-GB (British English)! This particular output shows that it’s Build 10586 of the Windows 10 Pro Technical Preview, 64-bit version. The syntax includes a wimfile specification, followed by /index:1 both must be entered correctly (the former) or verbatim (the latter) for the command to produce the output shown. Here’s the syntax, on a screencap that also shows the results, taken from a USB flash drive upon which I’d deposited a Windows installer without labeling it clearly enough. Though it won’t work on running Windows images, DISM can tell you a fair amount about WIM and ESD files you might have laying around. If you work with multiple versions of Windows, you may find yourself looking at an installer or OS image without being able to tell what’s what. In most cases, putting the right /add-package directive together will get the update added quickly and easily. You’ll have to determine the file specification for yourself, but it will normally include the KB number as part of its name, as with the file that contained KB3122947: In most cases, if you’ve already downloaded the update, the path specification will be C:WindowsSoftwareDistributionDownload (the normal landing place for Windows Update downloads). Here’s an annotated listing of command-line inputs to learn more about what’s going on (remember that DISM requires privileged access to do its thing, so run the CMD.exe program as administrator whenever you need to put it to work): File corruption in system components can cause such flakiness, so it’s wise to keep an eye on such things as part of their diagnosis. This is definitely the DISM command collection I use most often, particularly when trying to troubleshoot flaky system components (such as “File Explorer stopped working” or “Internet Explorer stopped working,” to name the two most frequent culprits). Identifying and changing international settings in Windows imagesĬheck, scan and restore Windows image health.Identifying Windows images, installers and ISO files.Adding updates to Windows 10 manually, usually when Windows Update items fail to install.Compacting Windows installations specifically, the WinSXS component store.Check, scan and (where necessary) restore the health of Windows image files. This list of tasks provides the basis for the remainder of this article: My own recent use of DISM with Windows 10 has produced somewhat more modest tasks at which DISM is equally accomplished, but which are more likely to be of use in day-to-day system upkeep and maintenance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |