How to open a WIM file? How to edit the Windows registry in the system image A program for editing wim files

... the development of OS cloning from a handicraft sector through a USB flash drive to a promissory file measure ...

For cloning operating systems, I hacked the paid programs Symantec Ghost or Acronis True Image. The stinks beat their functions and ruled over me ... Until I got to know Windows Deployment Services - an even more difficult way for Microsoft to centralize the OS, as it is more accessible as the role of Windows Server starting from the 2008 version.

These articles will be reviewed by the following topics:

Cloning methods

There are two ways of cloning the OS: sector and file, the skin one has its own poles and minuses.

Sector

The traditional way of doing yoga is to use such programs as Symantec Ghost and Acronis True Image.

Advantages:

• Universality - as a rule, when cloning the type of operating system is not important, the file system would be supported.
• Shvidkіst - sector copying richly behind the file (the structure of the file system and fragmentation do not greatly affect the copying speed).

Noodles:

• After the creation of the image, there is no possibility of yogo re-editing in offline mode (not burning to disk).
• It is not possible to open the image on the whole image on top of yoga instead (leaving the actual files).
• Closing the format - as a rule, only software, which, having created an image, can work in such a rank.

fileovium

With this method of implementation by Microsoft, the OS image is taken at file level for the additional ImageX utility, the resulting image file is in the WIM format.

Advantages:

• Possibility to connect the image to the file system and edit it online. You can install updated drivers on the OS (starting from Vista) to improve this functionality.
• Accept the format, third-party software can be used with it.
• Well embossed, nothing zayvogo from the process of znyatya image is not given to him. It is possible to combine a sprat of images into one file, with which the files that are duplicated do not take up additional space.

Noodles:

• Low speed of work (all features of file allocation and fragmentation may be significant).
• Fixed OS support and file systems (Microsoft only, starting with Windows XP)

Working with WIM images

For the creation, editing, and phrasing of WIM-images in the operational іsnuє kіlka standard zabіv, yakі add one to one:

• ImageX is a text-based utility for creating, editing and storing WIM images.
• Windows Automated Installation Kit - a set of tools for creating images for automated installation of the OS, to replace Windows PE.
• Windows Deployment Services, which will be described below.
• Microsoft Deployment Toolkit - a package for fine-tuning installation images (zavantage). Functionality often overlaps with WDS: the robot is surrounded by a file sack, but there is a wider possibility of setting up a task sequence.
• System Center Configuration Manager - hard work for centralized OS re-rendering without the participation of a zero-touch installer, which combines and re-renders the program.

Note

There are a lot of articles on the Internet about how to create such a rozgortati image of the OS from the command line for ImageX help; rozmіchati and format disks for the help of more non-manual DiskPart. I'm not particularly a fan of the command line, to that will work all these operations with a bear, vicorous ability of WDS.

Windows Deployment Services

This role is available in Windows Server since 2008, the front role in Windows Server 2003 was called RIS.

WDS allows:

• It is systematized to save on one site the preparation of WIM-images of operating systems.
• Take advantage of computers through a network of interesting images (Boot Images) for the help of PXE.
• Expand the OS of the Windows family (XP, Server 2003, Vista, 7, Server 2008/2008R2) to save installation images (Install Images).
• To run the OS on a sprig of computers for additional rich address distribution in parallel.

The WDS service is simple and friendly to the point of cursing, and getting help to it is short and wise. After installing WDS in the mail configuration, I recommend choosing Respond to all clients computers at the stage of setting up the PXE Response Policy. Let us take a look at the front manual creation of objects in the Active Directory for the skin computer, which is entangled through the mesh.

After passing through the master of the cob configuration, the WDS is ready to work. Start mastering the process of adding a standard WIM-image (Install Image) of Windows 7 to the server, which can be taken from the installation disk at the address \sources\install.wim. For zavantazhennya kom'yuterіv through the mesh that rozgortannya on them іnstalyatsіynykh images it is necessary to add zavantаzhuvalnі images (Boot Images), about which I gave rozpovim report.

Note

For the implementation of scenarios in cloning, it is necessary to manually select virtual machines.

In order for a virtual machine on Hyper-V to be able to get involved as much as possible, it is necessary to add a Legacy Network Adapter to its hardware configuration.

Captivating images of WDS

These are the sets of images, from which the computer is taken up to the point of cloning. Use 3 standard types of exciting images.

Setup Boot Image - install enchanting image

If you are interested in such an image, the computer connects to the WDS server as soon as possible (it asks for the password), reads the list of default images available for opening, after selecting the image, it allows you to select the image from the graphical medium to cut through the partitions of the computer’s hard drive, so it goes, like The original Windows 7 installer (view, create, format). After the choice of distribution for installation, we begin the reorganization of the documents before the installation image.

To add the Setup Boot Image to the WDS server, simply type the Add Boot Image command and enter \sources\boot.win as a generic installation disk of Win7/WS2008R2 as required.

Note

64-bit enchanting images allow you to expand and clone 32-bit and 64-bit OS, and 32-bit enchanting images - only 32-bit OS.

Capture Boot Image

Having taken advantage of such an image, a graphical interface will be provided that allows:

• Select the distribution on the computer, which is necessary to "receive" the WIM image.
• Ask im'ya and describe the image.
• Select the layout of the WIM file.
• Optionally upload a WIM image to a WDS server via a link.

Note

Capture Boot Image allows you to create images only for preparation for additional SysPrep operating systems.

I guess that SysPrep for WinXP/WS2003 is located on the \support\deploy.cab installation disk. Preparation is done with the sysprep-mini-reseal-reboot command.

In the OS, starting with Vista, SysPrep is located on the system drive in the directory \windows\system32\sysprep. Preparation is done with the sysprep/oobe/generalize/reboot command.

To add the Capture Boot Image to the WDS server, just right-click on the already existing Setup Boot Image and select Create Capture Image from the context menu.

Discover Boot Image - reveals a fascinating image

This image allows computers, if not to take advantage of the size (PXE), to start in the traditional way (from a compact-abo flash drive) and connect to the WDS server to open the new available installation images, similarly to the Setup Boot Image robot.

To create a Discover Boot Image, right-click on the already existing Setup Boot Image and select Create Discover Image. The result of this operation will be a captivating WIM image. About those, how to create exciting ISO-images and flash drives with WIM-files, I will tell you further.

Creation of an exciting nose

If you don't need to capture your computer from a WDS server, you may need to locally capture Setup and Capture images from CDs or flash drives.

To install such noses, it is necessary to install the Windows Automated Installation Kit (WAIK, you can get it) and later on.

1. Run Deployment Tools Command Prompt as administrator.

2. Viconati

copype x86 c:\Deploy\WinPE_x86

you can choose a different capacity (x86, amd64, ia64).

3. Copy to the c:\Deploy\WinPE_x86\ISO\sources folder the WIM image you need (Setup, Capture, Discover) and name it boot.wim.

4. Now, behind the address c:\Deploy\WinPE_x86\ISO, there is a preparation of an exciting nose.

Creation of an exciting ISO image

W Deployment Tools Command Prompt Viconati

oscdimg -bc:\Deploy\WinPE_x86\etfsboot.com c:\Deploy\WinPE_x86\ISO c:\Deploy\WinPE_x86\image.iso

As a result, an exciting ISO-image image.iso will be created, ready to be written to a disc or connected to virtual machines.

Creation of an exciting flash drive

1. Format the flash drive to FAT32, make it active.

2. Get the bootsect.exe utility from the \boot folder of the Win7/WS2008R2 installation disk with the required capacity.

3. Vikonati in the name of the administrator

bootsect /nt60 e: /force

de e: - the drive letter of the flash drive.

4. Copy to c:\Deploy\WinPE_x86\ISO from the root of the flash drive.

The exciting flash drive is ready.

Note

This option is especially handy, because once you have created such a flash drive, you can easily change it to the new exciting (boot.win) and install (install.wim) image in the world of need.

Buttstock WDS for centralized laryngeal OS

1. We add a standard Windows 7 installation image to the WDS server (from the \sources\install.wim installation disk).
2. Get a smart computer as you install the Setup Boot Image, and open Windows 7 from the standard image.
3. We installed the OS as we need it.
4. Ready OS for cloning for help SysPrep.
5. Clone for the help of Capture Boot Image and to take the WIM image to the WDS server.
6. Rozgortaєmo zrazkovy WIM on the need of a computer through a network for help Install Boot Image or from other media (flash drives, compacts).

Korisn_ message

• Deploying Windows 7 - A series of 29 articles by Mitch Tulloch, author of many Microsoft Press books

If you are a system administrator, then before you is obov'yazkovo postanya power supply of the mass disgorgement of the operating system on the computer of the cores. I didn’t use any of the methods - from USB, via the WDS server from MDT, for the help of SCCM, - in any case, you will twist the WIM file from the image of the operating system.

Overview of OS debugging methods

1. Installing from an advanced USB storage device. On the new one in the root of the disk, the error file is to blame autounattend.xml. You create this file behind the back for help Windows System Image Manager (SIM), which is included before the Windows ADK. To respect, for all builds of Windows 10, the ADK version has its own. You can get it from the Microsoft website. The OS image file itself with WIM or ESD extensions is located in the sources folder of your USB. You can take the original MSDN, copy the stars or prepare your own. Drivers you need to integrate the WIM file later, or put it in the $OEM$ subfolder, and go to it in the autounattend.xml file.
   This method is suitable for single installations without the possibility of deep customization for different jobs, different colors.
2. Calling for help MDT with USB storage device. For some reason, the very exciting disk is prepared for the help of MDT (Microsoft Deployment Toolkit). The MDT package can be freely downloaded from the Microsoft website (I am aware that different versions of MDT support different OS versions that are being developed). MDT also requires the correct ADK version. Remaining now MDT 8450 now supports only Windows 10 1709 and older. In the MDT environment, you prepare a Task Sequence, add packages, drivers, and an operating system WIM file. Then you create an exciting media, so that you can turn everything on and copy it to USB. The subtlety lies in the fact that here you can customize the image, either by modifying the WIM file later, or by editing the unattend.xml file, which will be added to the Task Sequence created by you in MDT, which will be automatically included in the media, or write scripts, if you add them to packages, include during installation as a Task Sequence.
   When you create media MDT, you will create a boot.wim file that will be downloaded when you download from a flash drive. We'll try to get you a Windows PE environment, which will help you install.
   It’s also a smart way, which allows you to install any drivers and install any software for the hour of OS installation.
3. Asking for help MDT and WDS servers. Vіdminnіst kogo way polyaє in the fact that boot.wim, MDT creations, will be transferred not to USB, but on the WDS server, the zvіdki can be downloaded via PXE.
4. Rooting for help SCCM and WDS servers. Client engagement is similar to option 3, but the difference is that all WIM files, drivers and packages, as well as the Task Sequence itself with the unattend.xml file will be created and run from the SCCM server, not from MDT. An interesting boot.wim image will also be created with the help of SCCM.
   This option is suitable for the most complicated larynxes from the great number of different installations.

Note also that the unattend.xml views file can be included in the WIM image by placing it in the %WINDIR%\Panther\Unattend folder, but for MDT and SCCM you will still need an okremium file for the Task Sequence.

As I already mentioned, the files unattend.xml or autounattend.xml can be edited manually in the editor, or better and safer through SIM. The WIM operating system image file itself is created and edited by an additional console utility DISM, may be anonymous keys. More than that, the utility will also wrap and expand (zastosuvannya, apply) the WIM file to disk.

The DISM utility is included in the ADK package, it is important to check out the version of the utility that supports the OS that is being developed.

Burrowing the image of the WIM fold

To create a WIM file, you need to perform the Sysprep and Capture operation. For whom, install the system on a computer, set it up as usual, install or remove programs, install updates. Also, for a successful sysprep in Windows 10, it is necessary to clean the system and see if the Modern App programs are proponated by HP and Canon, otherwise sysprep will fail. You can do it with Powershell commands:

Sysprep.exe /generalize/shutdown/oobe

When the system switches to OOBE mode (Out-Of-Box Experience, as if it were only being restored from scratch), and then the computer will turn off. You can read more about this procedure in the Microsoft documentation.

Now the image of the disk can be hooted. The hoarding of the disk is already fixed by the DISM utility.

If you want to hack manually, then for which you need to get into the Windows PE environment from USB, or as little as possible, or connect the disk to another computer. The Windows PE warehouse may already have the dism utility. The burying of the image is done with the command (you know, you will bury the C: drive):

Dism /Capture-Image /ImageFile:D:\my-windows-partition.wim /CaptureDir:C:\ /Name:"My Windows partition"

A single WIM file can replace a single OS image, or you can add a new storage disk to an existing image. It's handy if you need one WIM file to expand a different system (for example, with a different set of programs). You can edit the power of a wim file by naming the new image.

The image has a file maє_іndex, which starts from 1. Obviously, if you will save the image to a clean disk, then you will need to specify the system index:

bcdboot C:\Windows

You create a BCD capturer on the drive with the operating system. Damn it, you'll need to build the Recovery. For security, I'll give you a sample bat-script, which is based on Microsoft documentation.

In fact, all the same, not the meta of our article, but rather a look around, which allows you to understand, with which utilities it is necessary to grow in some way. Even the syntax of all commands is well-documented. In addition, the procedure is like sysprep /capture, so it’s easier to turn the image onto the disk from the front formatting through MDT, having created a new Task Sequence in the new Task Sequence, the MDT process will be done first, for new tasks it’s easier to do everything manually.

Utilities for working with WIM images

All utilities in this list will be graphic replacements for console DISM.

This miracle utility, written by my AutoIt script, saves your time, hacking:

• burying the disk in the image (capture)
• pushing the image to disk (apply)
• show information from the finished wim image
• Allows you to mount the image from the folder, mount and unmount it
• vivantage of a framed image from a wim file with a large number of images
• editing the name and description of images in wim files

The current version 2.2.0 is summed up to Windows 10 build 1803. All operations are completed in one click. Installation is not needed. Alternative option: storing another partition on your disk or a connected disk, as well as editing an explicit wim file. The robot in Windows PE is not transferred.

This utility is written in Powershell, but it is also used for other operations, and for servicing that editing of the explicit WIM. All bookmarks are sorted in the order of choice: you mount the image first to the folder, and then edit it or save the changes.

The utility allows:

• Integrate the driver into the image (drivers)
• add packages (cab packages) and enable/disable functions (features)
• Assign license information and key
• stop ready Unattend.xml
• select a list of add-ons (applications) and patches (patches) in the image
• hoot and zastosovuvati image

A third utility is provided for preparing the system prior to capture. Vaughn allows even granulated virazati or add everything you want from her.

• cleaning caches, logs, Appx (Modern programs), time files
• hacking with installed Appx add-ons - allows you to see Modern Apps, which you could previously only through Powershell.
• optimization and customization of menus, icons
• adding and removing drivers
• adding and removing Windows components
• Adding that functionality to Windows (Features on Demand)
• update and update
• setting up association files
• Editing the Widows File Unattend.xml

Good afternoon. What did they say.

Ale, I have a problem with a trocha іnsha.

I want to activate Windows, like in the AiRecovery distribution.

I have a license in AiRecovery Windows 7pro x64.

After installing from the AiRecovery distribution via F9

activated with a key, which is on the back

laptop roof, 100% no problem.

At the same time, just small inconsistencies

installations from the AiRecovery distribution. Before renovation

if I install windows 7, it will automatically

activated. If the Internet was not connected, then windows

was restored with 3-day automatic activation,

if for 3 days there was no access to the merezhі, then windows

went into a 30 day trial status, that activate

you can do it manually.

Infection when installed in the right

to the lower corner of the screen under the ASUS obviature in a fine font

write that I won't legalize the version of Windows.

І after the installation of the black screen, installation

the picture is not installed. Tse means that I am guilty

activate windows manually once every once in a while

activation insert the installation image

so I'll do it manually.

4 rocks to that on asus.ru bula article

Editing the Recovery section. The stats have the same

After successful completion of the process, it is necessary to capture the laptop from the disk… and… The OS is captured, as we have deployed the images, and the Audit will be launched.

I didn’t feel like that, maybe, the article was written

for windows 7 x32.

On the official website of asus I know

If you can tweak your Windows image to boot to OOBE, but it will require you to tweak it for your image in audit mode, you can do it with one:
Victory CTRL+SHIFT+F3 keyboard shortcut. The computer will reboot into audit mode.
This option can have three scripts that you have configured to launch in OOBE

And just like that, I managed to get into the audit mode. Activating Windows

And after passing “generalize”, I got two drivers

all video and audio drivers.

Zagalom with Windows activation

everything went well, ale oskіlki I re-installed the driver

Windows came out about 500 megabytes down.

I have viniclo 3 meals:

one). You can in the distribution of AiRecovery combine the image of swm into a wim image and activate windows in a new one,

Shards are the best way to improve your nutrition.

2). If it’s not possible, then you can forget villota

video and audio drivers during the walkthrough of “generalize”.

3). If not, then you can activate the drivers if,

yakscho marvel at obsyag, svidche for everything, deactivated

sub hour of passage “generalize”

Oskіlki when installing anew drivers, when windows is installed, it will be replaced by a newly installed driver.

To work with archives in the .wim format, the Windows warehouse has the Dism utility (and the wimlib library is an open source alternative).
Let's take a look at a sample of typical tasks, on the back of the Dism version 6.1.7600 (embedded in Windows 7), then Dism version 10.0.14393 (embedded in Windows 10).

dism version 6.1.7600 with nothing:
/Get-MountedWimInfo
/Get-WimInfo
/commit-wim
/Unmount-Wim
/mount-wim
/Remount-Wim
/Cleanup-Wim

List images from wim file

Dism/Get-WimInfo/WimFile:install.wim
For example, install.wim from the windows 7 installation disk to remove the image (may be sensitive to the Index and Name fields):

Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Details for image: install.wim Index: 1 Name: Windows 7 HOMEPREMIUM Size: 12 045 241 621 bytes Index: 3 Name: Windows 7 1 Deployed successfully.

Look in the image

To review a thorough image, it is necessary to mount it after the index or im'yam (having named it a little more carefully, I'll put the butt only with the index):
Dism /Mount-Wim /WimFile:install.wim /index:3 /MountDir:C:\win7 /ReadOnly
With this command, we mounted the Windows 7 PROFESSIONAL image to the C:\win7 directory. For locking, the image is mounted writable, and the /ReadOnly key sets the read-only access mode.

Make changes to the image

1. Mount the desired change image (without the /ReadOnly key):
Dism /Mount-Wim /WimFile:install.wim /index:3 /MountDir:C:\win7
2. Edit/Change/Add/View files in the C:\win7 directory, as you wish.
3. Install the image from saving changes:
Dism/Unmount-Wim/MountDir:C:\Win7/commit
or those two are the same with the same commands:
Dism/Commit-Wim/MountDir:C:\win7

Dism/Unmount-Wim/MountDir:C:\Win7/discard

Look through the list of all mounted images (as well as their stans)

Dism / Get-MountedWimInfo

Dism version 10.0.14393 also includes axis:

/split-image
/Apply-Image

Split a wim file into a sprat of swm files

Wim - file type archives, split it up like dd, don't go into it. Natomіst viyde offensive team. Might be in luck, for example, if you manually rob an install flash drive in FAT32 (the file system can be exchanged for a file size - a maximum of 4GB). The resulting swm files are located in the sources directory. The FileSize key accepts a size in megabytes.
Dism /Split-Image /ImageFile:install.wim /SWMFile:install.swm /FileSize:4096

Zastosuvati (unzip) the image on the file system
Dism /Apply-Image /Image-File:install.wim /Index:1 /ApplyDir:D:\ /EA
For a file split on swm, it is necessary to specify the file naming pattern for the archive.
Dism /Apply-Image /Image-File:install.swm /SWMFile:install*.swm /Index:1 /ApplyDir:D:\ /EA
The /EA switch tells you to set extended file attributes.

16.06.2010 20:41

Files installed in Windows 7 can be corrupted or seen after a while or after infection of the computer with viruses, trojans and other unsafe programs. Alternatively, to reinstall Windows 7 using one or two bundled files, you can extract the required files from the Windows 7 installation DVD.

All Windows 7 files are squeezed and packed in an image file install.wim, roztashovaniya at the daddy sources Windows 7 installation disk. There are two ways to open the WIM file and extract the necessary data:

Connecting the image using DISM

1. Insert the Windows 7 installation disc from the DVD drive, open it and copy the file install.wim from the folder sources to drive D.

2. Create a folder on drive D and name it її, for example, wseven. Up to this folder, there will be connections to the install.wim image. Please note that as the folder for connecting the install.wim image, you CANNOT change the root of the C drive.

3. Open Start > Use Programs > Standard .

4. Follow the command:

dism /Mount-Wim /WimFile:D:\install.wim /name:"Windows 7 Ultimate" /MountDir:D:\wseven

Explanation:

• dism - a command line utility introduced in Windows 7 that allows you to connect WIM images and manage them.
• The /Mount-Wim option mounts the WIM file.
• The /WimFile option allows you to specify the name of the WIM file that you need to include.
• The /name option allows you to specify the name of the edition of Windows 7 that will be mounted.
• Option /MountDir: Specify the folder where the WIM image will be mounted.

6. Dock, image docks connect. Tse mozhe trivati ​​kіlka khvilin.

7. Open the D:\wseven folder, find the required file and copy it to a hard disk somewhere (for example, replace the Windows 7 file).

Wipe the image in DISM

After copying the required image files, you can turn off.

1. Close all folders and files.

2. Open Start > Use Programs > Standard, right-click on the command row icon and select Run as administrator.

3. Follow the command:

dism /Unmount-Wim /MountDir:D:\wseven /discard

Explanation:

• The /Unmount-Wim option unmounts the image.
• Parameter /MountDir: specify the folder in which the image is mounted, which you need to mount.
• The /discard parameter will tell you all the changes that have been made.

4. Check the included image.

5. Remove folder wseven that file install.wim from drive D.

Opening the WIM file for the help of the 7-zip archiver

1. Download and install the 7-zip free archiver.

2. Insert the Windows 7 installation disc from the DVD drive, open the folder Sources and find his file install.wim.

3. Right-click on files install.wim and select in the context menu Vіdkriti with help.

4. Vіknі choose 7zip File Manager ta press OK.

5. In the archiving window, you can see up to five folders in one folder, in addition to the Windows 7 release. In the installation images of 32-bit Windows 7, all editions are present, including Enterprise, there will be five folders:

• folder "1" has all folders and files Windows 7 Starter (Pochatkov);
• for folder "2" - have folders and files Windows 7 Home Basic (Home Basic);
• for dad "3" - Windows 7 Home Premium (Home Extended);
• for dad "4" - Windows 7 Professional (Professional);
• dad "5" - Windows 7 Ultimate (Maximum).

Installed images of 64-bit Windows 7 have a Pochatkov release every day, so there will be less folders:

• folder "1" has all folders and files Windows 7 Home Basic (Home Basic);
• for dad "2" - Home Premium (Home Expanded);
• for dad "3" - Professional (Professional);
• dad "4" - Ultimate (Maximum).

In the installation images of Windows 7 Enterprise (Corporate) there is only one folder - with "Corporate", other editions are not included in the distribution.