Windows image recovery

A corrupt WIM or ESD can lose one image index or shared resource while other stored files remain readable.

Windows Imaging Format can store multiple volume images that share file resources. ESD uses stronger compression, and deployments may also use split SWM files. Damage to metadata, resource streams, one split member, or the source disk can stop DISM from listing, mounting, exporting, or applying an image.

Understand the symptom

WIM metadata maps image indexes to deduplicated resources stored in the container.

WHY

What is happening

Microsoft documents DISM integrity checking for mount, apply, capture, export, and commit operations. A failure can affect container metadata, one shared resource, split-image order, or the underlying media, so write operations belong on copies only.

What you may see

Symptoms that change the recovery path.

01

DISM reports the image is corrupt

Integrity checking found unreadable or inconsistent WIM structures.

02

Get-ImageInfo fails

Container metadata or the XML image table may not be readable.

03

One index applies and another fails

The affected image may reference a damaged resource stream.

04

A split image part is missing

The SWM sequence is incomplete or named incorrectly.

Protect the source

Actions that can make the situation worse.

01

Append and commit write metadata

They can change the only remaining container state.

02

Cleanup can remove recoverable mount data

A stale mount directory may contain useful files or logs.

03

Copying from failing media repeats bad reads

Image the source before repeated DISM attempts.

Do this now

Safe steps before evaluation.

01

Copy every image component

Keep original names, sizes, hashes, order, catalogs, and split members.

02

Save DISM evidence

Preserve dism.log, command lines, indexes, versions, and error codes.

03

Run read-only inventory first

Collect image information and integrity results without committing changes.

04

Identify priority content

List required indexes, paths, drivers, applications, or deployment artifacts.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Container assessment

NEPFOSYS maps headers, XML metadata, indexes, resource tables, split parts, and readable ranges.

02

Resource extraction

Reachable files and image resources are copied to new storage without changing the source.

03

Image validation

Recovered indexes, paths, hashes, ACLs, and representative files are checked against expected deployment content.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Does DISM CheckIntegrity repair a WIM?

It detects and tracks corruption; it does not recreate missing bytes.

Must every SWM part be present?

Files can span split members, so the full correctly named sequence is normally required.

Can a working index be exported?

Possibly from a protected copy, if every resource referenced by that index is readable.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case