Contacts

Installing DISM. DISM - Managing Windows Image Components. Using DISM with Install ESD File

Operational wINDOVS system It can boast a diversity of tools that allow you to restore the functionality of this OS when different problems occur. One of these tools is DISM (acronym from "Deployment Imaging and Servicing Management"), which not only checks the image of Windows OS for damage, but also restores its functionality using the effective DISM / Online / CleanUp-image / restoreHealth command. Below we will analyze the features of this command, and also tell detail how to use it.

The "Deployment Image Servicing and Management" (maintenance and placement of placement of images) also known as DISM appeared in the WINDOVS Family functionality from versions of Windows Vista (SP1).

Initially, DISM was positioned as a tool for creating and managing windows based on file format .wim. (Abbreviated from "Windows Image" - the image of windows). With the introduction of B. wINDOVS functionality 8 encrypted and compressed file format. eSD. (Acronym from "Electronic Software Download") DISM was able to work directly and with the files of said format.

The use of the word "maintenance" (Servicing) in the DISM functionality includes a wide variety of functions, in particular:

  • Capture disk images (sections);
  • Using disk images;
  • Installing and modifying images;
  • Creating images 32 or 64-bit windows in a single.wim file;
  • Creating separaty data images and other features.

Now the possibilities of DISM allow you to conduct operations for checking, scanning and restoring windows image files, reduce installation sizes window files (I note work with WINSXS component), adding updates to Windows 10 in manual mode, Identification of windows ET Cetera images.

DISM / Online / CleanUp-image / RestoreHealth - Features of the functionality

When there is various errors on PC file System, we often appeal to the SFC utility for analyzing and restoring integrity system files. In some cases, SFC is ineffective, which may be due to the damage to the image of Windows on the rigid disk of our PC. Then we use the DISM command using Windows Update Center ( Windows Update.) To download missing system files. Usually, after performing this procedure, the SFC may further work effectively.

The DISM team usually has three main forms:

DISM / Online / CleanUp-Image / Checkhealth - detects damage or modification of the image of windows;

DISM / ONLINE / CLEANUP-Image / SCANHEALTH - Scans the image of windows for damage.

Well, the most important for us DISM / ONLINE / CLEANUP-Image / RESTOREHEALTH Used to restore the image of the Windows OS using the update center. In addition to using the latter, you can specify the DISM yourself where exactly look for files to restore the image of windows.

How to use the DISM / ONLINE / CLEANUP-Image / RestoreHealth team

To use the DISM / restoreHealth command, run the command line from the admin, and dial the above command in it:

After that click on the input. In the process of performing the procedure, you will see the progress of execution in percentage.


Wait for the end of the procedure. The latter can take about 10-20 minutes, after which you will receive a message about the successful end of the operation.


In addition to the traditional form of implementing this command, you can also specify the DISM where to take files to restore the image of Windows. If the default DISM draws files from the Windows Update Center, then the operator / Source. Let you specify where to take the specified files from.

Usually it will take the image of Windows of the same assembly as installed windows On your PC. From this image, make a copy of the file install.wim.And place it in a convenient directory on your hard disk.

DISM / Online / CleanUp-Image / RestoreHealth / Source: Recovery Folder \\ Install.wim

Instead of "Recovery Folder" you must specify the path to the folder where the file is located install.wim.For example, D: \\ Sources \\. Now the team will look like:

DISM / ONLINE / CLEANUP-IMAGE / RESTOREHEALTH /SOURCE :::\\Sources\\Install.wim


To lock DISM access to UPDATE UPDATE node, you can use the operator / Limitaccess., then the team will look like:

DISM / ONLINE / CLEANUP-Image / RestoreHealth / Source: Recovery Folder \\ Install.wim / Limitaccess

In this case, the DISM will only refer to the recovery folder you specified, and does not use the update center.

You can also use the commanded command with encrypted images .ESD, in this case the team will have the following form:

DISM / ONLINE / CLEANUP-Image / RestoreHealth / Source: Recovery Folder \\ Install.esd


Note that DISM always creates a log file on the way % Windir% / Logs / CBS / CBS.logwhere you can find a list of discovered and corrected utility problems.

Conclusion

The DISM / Online / CleanUp-Image / RestoreHealth team is used in the Windows OS functionality to restore the working capacity of Windows OS, from which various system tools (in particular, SFC) draw the operating versions of system files. Treat DISM when damaged system files, discharged disk and other similar dysfunctions, and in most cases the efficiency of your system will be effectively restored.

The freshly installed "dozens", we will talk about the useful functionality of the most popular Windows 7 taken from the Arsenal Windows 8, namely the restoration of damaged components with the participation of the console utility Dism.exe.. Moreover, this functionality is not the newest, but absolutely deprived of all Russian-speaking IT.-Resours. About the reasons and, in fact, about the most Deployment. Image. Servicing. and. Management (eng. "System of maintenance and management of deployment images", DISM.) Read in a short note below.

Everything is simple: the option appeared exactly a year ago with the release of the update KB2966583. what in the announcement was told literally a few words, which was, because of dislike for FAQ.-am, the cause of the silence of "native fenats" ("The discoverer" of the DISMLL Windows 7 - blogger Vadim Skin). Well, replenish the gap in the formation and opportunities of the beloved "seven", but for starters in one paragraph about why all this is needed.

Starting with Vista, the deployment and maintenance of "windows" is built on components and packages defined by manifests (screenshot). In directories C: \\ Windows \\ Winsxs There are all operating system files, including previous versions - this is component storage Windows. BUT package storage The system is represented by a folder C: \\ Windows \\ Servicing \\ Packageswhere you can see the available packages and their manifestos. Revealing said packageohms can be a fix for OS or driver, and manifesto There is text Xml-File, where definitions are set for components and deployment elements. Due to the fact that the practice of updates of the system is the thing necessary, and the most common cause of the failure during the update is the damage of the voiced storage, utility Dism.exe.is real " stick-outdoor"With similar bugs. After the initiation of KB2966583All, the seven users can evaluate today's heroine in action, because earlier for this was required a separate decision. Checksur. CHECK FOR SYSTEM UPDATE READINESS), which is not correct.

We work with Dism.exe


Again, everything is simple: from under account administrator (if you are the only one windows user, it is not worried about what) Run the command line (" Start" → cmd. In the search field → " ENTER") And enter, with confirmation, command DISM / ONLINE / CLEANUP-Image / SCANHEALTH → We are waiting for the end of the process (screenshot) → Work results DISM.for compulsory, see the address C: \\ Windows \\ Logs \\ CBS in file checksur.log.. The presence in the critical number of problem components in the critical number will be a signal to look for a USB flash drive (disk) with a Windows image or download the desired regenerating package System.Update.ReadinessTool..

Ideally, you should see the text ("no errors detected") as in the screenshot above, which everyone wish. And this is all that you need to know on the topic of any little more to the experienced Windows user.

Note: PC owners managed by a later "eight" to expand the horizons can familiarize themselves with the article " Parameters command line DISM to maintain operating system packages"From Microsoftovskaya MSDN.- Bible.

DISM ++ - a multifunction program that is designed to configure and windows optimization, as well as to restore the performance of this operating system. In general, the "original" DISM ++ is a command line application, but in order to simplify its use, we offer a version equipped with a graphic shell (with full Russian localization).

One of the most useful features DISM ++ is clearing the disk from unnecessary files. Moreover, the integrated tool to fight "garbage" works much more efficiently than many popular "independent" solutions like the same he will help get rid of the cache of the system and third-party programs, delete report files, empty folders, "broken" labels and so on. In addition to getting rid of unnecessary files, it will be possible to get rid of the unnecessary elements of the autoload.

Now to more interesting possibilities that are not in ordinary "cleaners". This includes the function of creating a backup backup system and a backup license, own file manager with flexible folder display settings and files, WIM file converter, SWM and ESD in ISO, as well as manager installed drivers. In a separate DISM ++ section, you will find a list of system parameters that are recommended to be changed in order to increase its safety, speed and stability.

If you have serious troubleshooting, you can use DISM ++ to restore the system from the image. There is also a "compression" function of the installed Windows by removing unnecessary components and programs from it. Extremely useful opportunity for those who use small capacity SSDs.

To create your own distribution, do not necessarily capture the prepared system, kit Waik. Provides us with another opportunity, work directly with ISO Imageoh. installation diskIn Microsoft Terminology, this type of images is called: autonomous image. This tool is called DISM ( Deployment Image SERVICING AND MANAGEMENT) It allows you to deeply modify the Windows image, add the driver there (one file or a whole collection), turn on / off the various components of the system, add OS update packets as well language packages And a bunch of everything else, in general, we can rather deeply "stamping" the distribution of Windows. By the way, Waik allows you to maintain Distributions Windiows 8/2012
Another option is possible, you already have a configured image that turned out with you after capturing, about how it is created can be read in the article :, it all works in it, but there is a problem, a newer technique has entered, and the drivers that are already Present in the image, do not suit the new gland, respectively, the equipment does not work at full capacity. In this situation, we need to find out the configuration of the new equipment and in the already existing image, just add drivers, and if the image has been created for a long time, then the packages of updates, otherwise our image is not safe, but on the recommendation "The best dog breeders", from Microsoft, our image must be safe, and contain current security updates, at the time of deployment ...
If you think about logically, then in the office network, with time, "different" workstations will appear, this may be due to the growth of the company or the planned replacement of obsolete equipment on a new one, and simply by different suppliers or batches of equipment, in any case, the idea of Uniform equipment can be forgotten and do not even count on it, I also believe my experience in the company where almost 14,000 people work in the Russian Federation, with the technique there is a complete zoo, on this, you may need to add drivers, updates, and the like . The ideal option is a single service point, which will be our installation image, we can add drivers to it, as new techniques arrive.

I will say honestly, this is quite difficult in understanding, but having mastered it, you will get a powerful tool for servicing and tuning distributions MS Windows. In principle, you can safely open "your" MSDN, provided that your images will be collected qualitatively, well, for one, raise the "pirate flag", but it is so, lyrics ...
All actions are made from the command line, it is on the one hand, a big plus, with another disadvantage. The modern people brought their "button button" reflex to such heights that the speed of operation by the mouse simply rolls up, but the view of the black field of the command line and the flashing cursor-causes a nervous tick and personal hostility to those who came up with.

The important-article will be divided into several points, each of them is not mandatory, you are free to choose, perform all items or only some you need, in any case, the image will be operational!

All actions will be held on example Windows 7 Professional AMD64, but all commands are relevant for windows Distributions 8/2012 / 2008 / 2008R2
To work, we will need:
1) Windows 7 installation disk (editorial and bit, values \u200b\u200bdoes not have, for example, the X64 architecture will be used), you can download from torrents or with MSDN. - Who has access to subscription. In this work, I will use the pure image of MSDN, I do not recommend taking the image that someone has already converted, it's not a fact that you have something to do with him, so to understand the principle of work Take an interior from Microsoft, it is directly like Scrap in flight ...
2) WAIK installation disk (Windows Automated Installation Kit), download from Microsoft, as well as an additional package to properly work with OS with SP1.
3) physical machine, with Windows 7 on board, the discharge and editors of the OS value does not have, but the editors Starter. It is better not to use, with a sufficient amount of free space on a C-should be free at least 25GB (just in case).
4) A set of drivers, and updates that will be installed in the system.

It is assumed that all this has already been downloaded and lies on the disk, to configure the image of the Internet we will not need.

To work, we need to create the necessary directories on the C. disc
We will work with the image in the folder dISM.I called it so much to be clear for what it is (the name of the folder does not affect anything) the only condition is not to assign the name of the Cyrillic folder, in order to avoid problems, also inside this folder, we will create a whole bunch of other folders their destination I am I'll tell you in the course of the article:
We will work on the command line, yes windows like Linux allows you to do it and as in Linux, many tasks like this, better to perform from it. The mouse is too long, although in Linux, the command line is more functional.
Run the command line, on behalf of the administrator and perform in it:

MKDIR C: \\ DISM MKDIR C: \\ DISM \\ ISO MKDIR C: \\ DISM \\ OFFLINE MKDIR C: \\ DISM \\ UPDATES MKDIR C: \\ DISM \\ DRIVERS MKDIR C: \\ DISM \\ DRIVERS \\ Network MKDir C: \\ DISM \\ DRIVERS \\ Now, we need to copy the contents of the entire Windows installation disk to the folder

C: \\ DISM \\ ISO as it is. Also next to the folder
ISO. there is a folder offline the file will be mounted in it. Working with which we will perform. install.wim. We will not pull the cat for the "causal place" and mounted the image

Which, if you all copied correctly, should lie on your way: install.wim. C: \\ DISM \\ ISO \\ Sources \\ Install.wim
Go: Start

All programs->Microsoft Windows AIK. ->Deployment Command Line ->Run it on behalf of the administrator The disk may contain several editions of the operating system, we are interested

Windows 7 Professianal , it all depends on what kind of serial number you will enter.We get a list of OS from the disk:
DISM / Get-Wiminfo /Wimfile :C :\\Dism\\iso\\Sources\\Install.wim
We are interested in the image of the OS with an index 3. (on the screenshot is collapsed in red)
In the window that opens, we enter and press ENTER:

DISM / MOUNT-WIM /WIMFILE :C: \\Dism\\iso\\Sources\\Install.Wim / Index: 3 / Mountdir: C: \\ DISM \\ offline
Where:
- that we run to work
dISM./ Mount-Wim
- That we want to fulfill, in our case-mounting Wim file. /WimFile:C:\\Dism\\iso\\Sources\\Install.wim
-the path to the file / index: 3 install.wim.
-in fileThere may be several images of operating systems, we will take the third of the list. install.wim. / Mountdir: C: \\ DISM \\ OFFLINE
-Patch where the file will be mounted install.wim.

The system will issue, similar:

After connecting the image, the contents of the file install.wim. You can see in the folder c: \\ DISM \\ OFFLINE
If you look there, then there will be no other than the contents of the disk C, for the lazy it is screenshot:

1 add hardware driver
At the beginning, when we created a bunch of folders, we had a folder with the name DRIVERs, and in it various under the folders of the Mainbord, Sound, Network type folders, here they are just designed to store drivers. Sound driver, throw the SOUND folder, and drivers network equipment The Network folder is simple, etc. In principle, you can all fall in one bunch, the main thing that files with the same names are not overwriting each other, but it is better to immediately take about order and then after a few months you can easily figure out where what lies that you can delete, but what you need to leave, but Now, if everything is in a bunch, it is already problematic, so the recommendation is quite simple and banal-normally do, it will be normal!
DISM allows you to add drivers in 2 modes
1) File-when you explicitly specify which file you need to download
2) Recursively-when software itself examines the folder and subfolded subfolders and all the driver files found adds to the image.
Frankly, add to file, it is for "aesthetes" or if you need to add only one file to the ready image. But we "stir up" with you the clean system and it is assumed that there is nothing in it, we will add them recursively.

At the command prompt, enter:
DISM / Image: C: \\ DISM \\ OFFLINE / Add-Driver / Driver: C: \\ DISM \\ Drivers / Recurse

It happens that you need to add drivers that do not have digital signature, then the team takes the form:
DISM / Image: C: \\ DISM \\ OFFLINE / Add-Driver / Driver: C: \\ DISM \\ Drivers / Recurse / Forceunsigned

The system will think a little, then will give the following:

2 add updates to image
Next, assume that the image you have outdated and you decide to add update packages to it. But the main question is where to get updates?!
They can be taken from the operating system, all files with extension .cab. are our goal to be found at C: \\ Windows \\ SoftWaredistrationTribution \\ DOWNLOADIf WinRar is installed, then it highlights them as archives, here we will collect them. All updates are used in the order in which you indicated, try to indicate them, in order of increasing numbers.
Option number 2, updates can be downloaded from the Microsoft website so as not to pass the "exciting quest", here you have a link running through IE.
At the beginning of the article, we created a folder:
MKDIR C: \\ DISM \\ Updates
In it we fold the update files, for example, I have 2 files I will be in order of numbers:
KB2574819.cab.
KB2592687.cab.
Apply updates to our image:
DISM / Image: C: \\ DISM \\ offline / add-package /packagepath:c: \\dism \\updates /kb2574819.cab /packagepath:c: \\dism \\updates /kb2592687.cab
- that we run to work
/PackagePath:C :\\Dism\\Updates\\kb2574819.cab. - show the path to the file with the update

From the system we get:

Problem number 1. Some updates do not want to be installed, without other updates, on this, dependence on this can be a serious problem, but can always be viewed on the Microsoft website, what update, from what depends.
Problem number 2. You have no update files as files * .cab.but there is in the form of files * .msu., the problem is not complicated, the files can be unpaid using expand -F: *The use of the use of this utility will be you as a homework!

3-switch on / off operating system components
Sometimes it is necessary to enable system components that are turned off by default, for example, Telnet client, it is needed to me at work quite often, according to this, in the image, on its example, we will make the inclusion.
To begin with, we will execute the list of all components, it is quite large, we will redirect it to the file, and you can safely read in the file.
We get a list of packages and redirect it to text file:
DISM / Image: C: \\ DISM \\ OFFLINE / GET-Features\u003e C: \\ DISM \\ FeatureList.txt
- that we run to work
dISM / Image: C: \\ DISM \\ OFFLINE-Cature to our connected image
/ Get-Features - request list of system components
\u003e C: \\ DISM \\ FeatureList.txt -Pripping output to the file that we have called FeatureList.txt.and the path to it c: \\ DISM \\ FeatureList.txt

Go to the list of system components, open the file:
C: \\ DISM \\ FeatureList.txt
And at the exit, we get "Krakzyab" of which can be disassembled only by Latin, and even then not all. The problem is not big, in the notebook go to Format-font Choose font Terminal And, voila, all the content becomes readable.
We find in the list of the TelnetClient component, it is marked as disconnected:
Function Name: TelnetClient Status: Disabled

Let's try to enable it, enter:
DISM / Image: C: \\ DISM \\ OFFLINE / Enable-Feature / FeatureName: TelnetClient
The system will think a little and give out:


All component is enabled.

How to disable the component:
For example, let's try to disable the component, we already have a list of components, we find a component Solitaire. Yes, this is the same "Selitzer", which is so loved by employees and so hate "effective managers," because he steals working hours - a real scoundrel, he must die ...;)
DISM / Image: C: \\ DISM \\ Offline / Disable-Feature / FeatureName: Solitaire
The system will think a little, though removes the component system faster than adds, it is clear, breaking up ...

Final part
Working with image completed, we need to save changes and unmumbilize the image:
DISM / UNMOUNT-WIM / MOUNTDIR: C: \\ DISM \\ OFFLINE / COMMIT

Start the process of saving changes, takes about 1-2 minutes, after which, we will be given something similar:

If you have forgotten something, the image can be easily connected again and add the desired one.
Now we need to collect from the resulting, image of the installation disk.
Our resulting distribution lies in as it is. The only problem is that it is not bootable, in principle, this problem is not and we will now collect a full image of ISO, which, later, can be chopped into a DVD-R.

Build the image of the Windows installation disk (ISO)
Because The operating system files are lying in the folder:
C: \\ DISM \\ ISO
Then the resulting ISO image we call windows.iso. And lay out in:
C: \\ DISM \\
Then the way to it will look like:
C: \\ DISM \\ Windows.iso
To make an image bootable, we need some files that go in the Waik kit. The image of the operating system here has an X64 architecture, then the loader we need the appropriate one.
in folder DISM. Create a folder boot.But it is not necessary to create it to create it, it will create automatically when copying, open the command line on behalf of the administrator and write there:

We turn to the folder with utilities:
CD C: \\ Program Files \\ Windows Aik \\ Tools \\ Petools

And copy the utility for the architecture you need:
Copype.cmd AMD64 C: \\ DISM \\ BOOT
For one, add the memory test to our disk, it will not take a lot of space, and in case of occurrence, unknown problems will greatly facilitate life
Copy C: \\ Windows \\ Boot \\ Pcat \\ Memtest.exe C: \\ DISM \\ BOOT \\ ISO \\ Boot

Now we return to the command line, where we worked with DISM and introduce:
OSCDIMG -N -M -O -BC: \\ DISM \\ BOOT \\ ETFSBOOT.com C: \\ DISM \\ ISO C: \\ DISM \\ Windows.iso

The image assembly will start, after which, in the folder dISM. File will appear windows.iso., this is our finished distribution, which can be chopped on a blank or connect to virtual Machine and use.
The assembly process looks like this:

Alternative image use
Cut the blank is not necessary, you always can be made of this installation USB flash drive, about how to do it, you can read in the article: for me, this is the most suitable option, because Burn plastic for the sake of once, I consider it wrong, and the whole technique that is released during the last 3-4 years, supports the download from USB.

Your conscience remains testing that we rope with you ...
On this optimistic note, let it end, well, as always, I ask questions, I ask in the comment, they found a mistake, then write in a personal.
That's all.

The DISM command is used to view, install, delete, and set up components in Windows images of the WIM format ( W.indows. IM.aging Format). Starting with Windows 7, utility dism.exe. (D.eployment. I.mage. S.ervicing and. M.angement) is included in the standard set of software installed Windows. Is a command line tool that can be used for service windows images And replaces packet manager (pkgmgr.exe), peimg and intlcfg, which included in Windows Vista. The functionality of these funds is now collected in one instrument. dism.exe.. In addition, new features have been added, which improve the capabilities of the autonomous maintenance of images.

Unlike sector-oriented formats (such as .iso, .tib, .bin), the image of WIM is a file-oriented format, that is, its smallest logical element is file. This format was developed by Microsoft as the main means of deploying Windows Vista operating systems and later. Its advantages is hardware independence and the ability to store only one copy of a file that has many links in the Single Instance Storage (Single Instance Storage), which ensures the compactness of the images and the high speed of their deployment.

Wim file may include multiple images that are defined by numerical index or a unique name. Single copy technology identical files single Instance Storage When adding a new image to existing, it allows you to reduce the size of the WIM base if the coincident elements will be present. WIM image can also be broken into several files that are assigned expansion. .swm.

WIM image can be mounted as a logic disk in windows Environment With the assignment of the drive letter to facilitate the editing of its contents (thanks to this, the WIM image can be simply converted to the ISO image). In addition to the full-time utilities from Microsoft, you can also extract files from the WIM image using the 7-ZIP archiver.

Wim images can be bootable. In particular, the installation of all modern operating systems of the Windows family system is performed using the image file named Boot.wim containing boot version environments windows installations PE (Windows. P.reinstall E.nVironment), which runs the process of installing the system itself using the contents of the image file named Install.wim. After the standard Windows installation, the environment is created. windows restoration Re ( R.ecoovery. E.nvironment), the load of which is performed from the image Winre.Wim. To restore performance in problems with the loading of the main system. Usually, the Winre.Wim image is located in a hidden section that the logical disk letter is not assigned.

The structure of the WIM file containing 2 images:

As you can see, the WIM file contains 6 content types:

Wim Header. - WIM file header, describing content, attributes, version, size, compression type, etc.

File Resources. - Sequence of packets containing packaged file data as part of the image.

Metadata Resource. - Contains information about files as part of the image, including folder structure and attributes.

Lookup Table - Table of locations and size of resource files in the file.wim

XML Data. - Data in XML format with additional information about the image. Represent uncompressed text in Unicode encoding.

Integrity Table - the integrity table used to control the working state of the image

The WIM image creation process can be represented as follows:

1. The title is created Wim Header. Image file, for example C: \\ Data.wim
2. The memory creates metadata when scanning and indexing the source data directory folded into the image, for example - C: \\ Sources \\
3. Based on the contents of the contents of files from the source data directory, it is written with compression to a portion of packages File Resources. , and at the same time in memory is built table placement table in the image Lookup Table
4. Upon completion of the image creation, table Lookup Table written from memory to file.wim, then add xML data and integrity control.
5. Updated the initial WIM file header.

The process of extracting files from the image is performed according to the following algorithm:

1. The title is read Wim Header. And the location of the metadata in the WIM image is determined.
2. Metadata is rewritten into the computer's memory and build the file location table inside the image.
3. Catalog structure is created based on the contents of the image.
4. Files from the image are processed using constructed tables and rewrite to the created directory structure.

In more detail about the structure of WIM files - in the software developer document (in PDF format in English).

Performance Dism.exe. Without parameters, displays a brief reference to its use. The utility log is saved in the file C: \\ Windows \\ Logs \\ DISM \\ DISM.LOG

Command line format:

Dism.exe (/ image: Path_K_AVTONOM_-DRIVE | / Online) [parameters_dism] (service_And) [arguments__nozhbnaya_command]

The DISM command format differs depending on whether the utility is offline or with Windows data (mode / Online), in which Dism.exe is performed. The utility requires the launch of the command line on behalf of the administrator.

Service commands for working with disk images:

/ Split-image - divides an existing file.wim or file.FFU into multiple WIM / FFU files are read only.

/ Apply-image - Apply new image parameters.

/ Get-mountedimageinfo - Displays information about the WIM and VHD images connected.

/ Get-imageinfo - Displays information about images in WIM or VHD file.

/ COMMIT-image - Saves changes to the connected Wim or VHD image.

/ Unmount-image - Disables the connected WIM or VHD image.

/ Mount-image - Connect the image from the WIM or VHD file.

/ Remount-image - Restores the image connection directory.

/ Cleanup-MountPoints - Deletes the resources associated with damaged connected images.

Service teams:

/ Apply-customdataimage - Canning files contained in a customizable data generation.

/ Capture-CustomImage - writes settings to a difference WIM file in the WimBoot system. Recorded directories include all subfolders and data.

/ Get-wimbootentry - Displays WimBoot configuration records for the specified disk volume.

/ Update-WimBootentry - updates the WimBoot configuration record for the specified disc volume.

/ List-image - Displays a list of files and folders in the specified image.

/ Delete-image - Deletes the specified volume image from the WIM file containing several volume images.

/ Export-Image - Exports a copy of the specified image to another WIM file.

/ Append-image - Add a different image to the WIM file.

/ Capture-image - writes disk image to a new WIM file. Recorded directories include all subdirectories and data.

/ Get-mountedwiminfo - Displays information about the images connected from WIM.

/ Get-Wiminfo - Displays information about images in the WIM file.

/ COMMIT-WIM - Saves changes to the image connected from the WIM.

/ UNMOUNT-WIM - Disables the image connected from the WIM.

/ Mount-Wim - Connects an image from the WIM file.

/ REMOUNT-WIM - Restores the lost WIM connection directory.

/ Cleanup-Wim - Deletes the resources associated with damaged WIM-images connected.

Image specifications:

/ Online - Specifies the operating system as a destination.

/ Image - Specifies the path to the root catalog of the autonomous image of Windows.

DISM parameters:

/ English. - Displays the data displayed by the command line in English.

/ Format. - Specifies the report format. Valid values \u200b\u200b- / Format: Table or / Format: List, define a format in the form of a table or list. The default list is used.

/ Windir. - Specifies the path to the Windows directory.

/ Sysdrivedir. - Specifies the path to the system bootloader with the name BootMGR.

/ LogPath - Specifies the path to the log file.

/ Loglevel. - Sets the level of logging of events (1-4).

/ Norestart. - It prohibits an automatic reboot and output to the user's offer to reboot.

/ Quiet. - hides all messages with the exception of error messages.

/ Scratchdir. - Specifies the path to the directory of temporary files.

For information about these DISM parameters and their arguments, specify the required parameter before "/?".

Examples:

Dism.exe / Mount-Wim /? - Team Hint / Mount-Wim
dism.exe / Format /? - Display DISM output formats certificate.

dism.exe / Online / Get-Drivers /? - Hint for the output mode of driver information in the image or running Windows (/ Online). By default, the list of third-party drivers is retrieved. To withdraw the entire list of drivers, use the parameter / All..

dism.exe / Online / Get-Drivers / Format \u003d Table - Display the list of third-party current Windows drivers as a table:

Dism.exe / List-image /MageFile:C:\\Test \\ iMageSiMyImage.wim / index: 1 - Display the full contents of the first image from the file specified by the parameter / Imagefile:

Work with autonomous images.

dISM / MOUNT-WIM /? - Display the prompt by the image connection mode.

System DISM.
Version: 10.0.10586.0.
/ Mount-Wim / WiMFile: path_Wim file (/ index: design index | / name :) / mountdir: end_catalog_link - Connect the WIM file to the specified directory to be available for maintenance.
Use the / readOnly parameter so that the plug-in is read only.
Examples: Dism.exe / Mount-Wim /Wimfile :C:\\Test \\ index: 1 / Mountdir: C: \\ Test \\ offline
Dism.exe / Mount-Wim /Wimfile :C:\\Test \\ index: 1 / Mountdir: C: \\ Test \\ Offline / Readonly

Dism.exe / mount-wim /wimfile:d :\\Sources\\Boot.wim / Mountdir: C: \\ Test \\ offline - Connect to the catalog C: \\ Test \\ offline Content image D: \\ Sources \\ Boot.wim. After successful implementation This command in the directory defined by the parameter / Mountdir. The contents of the image from the WIM file will be available. / Wimfile. And commands will be available to maintain images.

Dism.exe / Image: C: \\ Test \\ Offline /? - Display a brief help on commands and parameters to maintain autonomous images.

Dism.exe / Image: C: \\ Test \\ Offline / Add-Driver /? - Display the hint by the procedure for adding the driver to the autonomous image.

Dism.exe / Image: C: \\ Test \\ Offline / Get-Features - Display information about all components included in this image. To display information about a separate package uses the parameter / PackagePath Indicating a CAB file or folder.

dISM / GET-MOUNEDIMAGINFO - Display information about connected autonomous images. An example of the information displayed:

Connected images:

Connection directory: C: \\ Test \\ offline
Image file: C: \\ Test \\ Images \\ MyImage.wim
Image index: 1
Connected to read or write: Yes
Condition: OK.
. . .

dISM / UNMOUNT-WIM / MOUNTDIR: C: \\ Test \\ Offline / Commit - Disable offline image connected to the catalog C: \\ Test \\ offline With the preservation of the changes made (saving with the fixation set by the parameter / COMMIT.).

dISM / UNMOUNT-WIM / MOUNTDIR: C: \\ Test \\ Offline / Discard - The same as in the previous example, but without saving changes in the contents of the image (saving without fixation).

Adding drivers to WIM image

The need to add driver occurs in cases where the installation of the system or download windows PE requires non-standard drivers, for example for disk controllers SCSI and RAID or unsupported peripheral devices. The DISM utility makes it easy to add to the existing image the required driver based on information from .inf. files.

Team format:

DISM / Image: Image / Add-Driver (/ Driver: folder_-containing_inf | /driver:nd_k_drier.inf) / Forceunsigned]

Adding a new driver to the autonomous image specified by the parameter / Image:. To search for drivers in all subfolders, use the parameter / Recurse.. To add all the unsigned drivers in the X64 architecture, use the parameter / Forceunsigned..

Dism.exe / Image: C: \\ Test \\ Offline / Add-Driver / Driver: D: \\ Drivers / Recurse - Add all drivers from the catalog to the image D: \\ Drivers and its subdirectories.

Dism.exe / Image: C: \\ Test \\ offline / add-driver /driver :d: \\drivers /usb /usb3.inf - Add to autonomous image Driver based on file information D: \\ DRIVERS \\ USB \\ USB3.INF

Dism.exe / Image: C: \\ Test \\ Offline / Add-Driver /DriverName: "/DriverSers\\1.INF" /DriverSeRME: "/ DRIVERNAME:" C: \\ DRIVERS \\ 3.INF " - Add multiple drivers in one command. When adding multiple drivers, their installation is performed in the same manner in which they are listed in the DISM command prompt

Successful DISM implementation / Add-Driver does not mean changing in the content of the image, since it is necessary to either disable the image with the parameter / COMMIT.or apply changes using the parameter / COMMIT-image

Dism.exe / Commit-Image / Mountdir: C: \\ Test \\ offline - Save changes in the image configured to the directory specified by the parameter / Mountdir.

Using DISM to manage the components of the current Windows OS.

Team DISM. with parameter / Online It is performed relative to the current operating system, and not to its image, which allows you to perform the system deleting, adding or changing its components. Under Windows service it is understood to track and correct the status of components and software packages, including all system files and registry. Component or CBS-based maintenance system ( C.omponent. B.aSED S.ervicing) is a set of service software and specialized data, part of which is the utility Dism.exe.

The initial elements of the service system components were still implemented in Windows Vista. In each subsequent release of the OS, their capabilities were expanded, which led to some serious differences in both the CBS itself and in the use of the Dism.exe utility in different versions Windows. Part of the parameters available in Windows 10 is not applicable in Windows 7, although microsoft. In addition released updates, partially implementing new service system concepts that appear in Windows 8, 8.1, 10. Part of the service opportunities present in Windows 8 are missing, or have undergone significant changes in Windows 10. I will add that Windows maintenance is complicated, Not quite decorated system, many features of which are not documented and many concepts of which can seriously change in the future.

A brief tip on the use of the mode / Online For specific windows version You can get by team:

DISM / ONLINE /?

Examples of using DISM / Online For standard service operations.

As a storage component of the system, the WIM image can be used, the data obtained remotely via Windows Updates Center (Windows Update), or local current Windows storage, which is the contents of the folder % WINDIR% \\ WINSXS (Standard - C: \\ Windows \\ WinSXS). Using the parameter / Source. You can specify the location of the versions of files that can be used to restore. Parameter / Limitaccess. You can use to prohibit updates from the Windows Update Center.

Dism.exe / Online / CleanUp-image / Checkhealth - Check for a sign of image damage or component storage. Not applicable in Windows 7.

Scanning the system component storage. In Windows 7, except for scanning, the restoration of integrity is also performed. This option command is not executed and accompanied by the message. Error 87. SCANHEALTH parameter is not recognized in this context.if the update is not installed in Windows 7 KB2966583..

Dism.exe / Online / CleanUp-Image / RestoreHealth - checking the storage of components and automatic recovery. In Windows 7, these functions executes the command
Dism.exe / Online / CleanUp-Image / Scanhealth

dism.exe / Online / CleanUp-Image / StartComponentCleanup - Clean replaced components and reduce the storage size (folders \\ Windows \\ WINSXS). Not applicable in Windows 7 environment.

dism.exe / Online / Cleanup-Image / StartComponentCleanUp / ResetBase - The same as in the previous example, plus resetting the base of the replaced components. After resetting the base, installed updates Windows cannot be deleted.

Dism.exe / Online / CleanUp-image / AnalyzeComponentstore - Creating a report on the status of local storage of WINSXS components. It is possible only for Windows 8.1 - 10. An example of the displayed information:

Information Storage Information (WINSXS):
The size of the component storage according to the conductor: 5.43 GB
- The size of the WINSXS folder calculated by the conductor. It does not take into account the use of hard connections in the WINSXS folder
Actual component storage size: 5.10 GB - takes into account tough connections in the WINSXS folder.
Together with Windows: 3.18 GB - the size of files that are rigidly linked in such a way that they are displayed both in the component store and in other locations (for normal windows work). It is included in the actual size, but should not be considered as part of the service storage of components.
Backup copies and disconnected components: 1.62 GB - The size of the components that are stored in order to be used in faults in newer components or to provide an option to enable additional functionality. The value also contains the size of parallel components used and component storage metadata.
Cache and temporary data: 304.02 MB - The size of the files that are used by the storage of components for internal purposes to accelerate the maintenance operations of the components. It is included in the actual size and is part of the component storage data service.
Last cleaning date: 2016-10-04 09:45:15
Number of released packages: 3
Recommended Cleaning Component Store: Yes
The operation has been successfully completed.

The use of the analysis allows you to estimate the need to clean the WINSXS repository and determine the limit reduction of its size, which can no longer be more busy Backup copies and disconnected components.

dISM / Online / Get-Features - Display the list of components of the current system.
An example of the information displayed:

Funalog Name: SNMP
Condition: Disabled
Function Name: TelnetClient
Condition: Enabled

In this example, the support for the SNMP protocol is turned off, and the Telnet server client is turned on.

Dism.exe / Online / Enable-Feature: SNMP - Enable the "SNMP protocol" component

It is possible to restore and include components that were previously removed from the image. Use the argument / Source.To set the location of the files required to restore the previously remote component. You can specify several arguments / Source.. If the component is found in the first source, the remaining sources are ignored.
The / limitaccess parameter prohibits the DISM circulation to WU / WSUS.
The / All parameter includes all the parent components of the specified component.

Dism.exe / Online / Get-FeatureInfo: TelnetClient - Display information about the "Telnet client" component

Dism.exe / Online / Disable-Feature: SNMP - Turn off the "SNMP protocol" component.



Did you like the article? Share it