Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Error detected in sparse file records after you run OOBE with WIMBoot

Error detected in sparse file records after you run OOBE with WIMBoot

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You start a computer that's running Windows 8.1 together with Windows image file boot (WIMBoot).
  • You finish running Windows Out of Box Experience OOBE) and then log on to Windows.
  • You run the chkdsk command to check the system drive.

In this scenario, the following errors may be reported. The segment number may vary case by case.

Stage 2: Examining file name linkage ...

Errors detected in sparse file record segment 5415.

Errors detected in sparse file record segment 5418.

Errors detected in sparse file record segment 55416.

↑ Back to the top

Cause

The issue occurs if the sparse flag for certain files is not synchronized correctly when WIMBoot is used. This has been confirmed as a known issue in Windows.

↑ Back to the top

Resolution

The file content is not affected, and the NTFS driver will fix this file attribute mismatch issue automatically after a system restart. You can also fix this issue manually by running chkdsk or by using the error-checking tool on the properties of the corresponding drive in Windows Explorer.

↑ Back to the top

Keywords: kbexpertiseadvanced, kbsurveynew, kbtshoot, kb

↑ Back to the top

Article Info
Article ID : 3002793
Revision : 1
Created on : 1/7/2017
Published on : 9/23/2014
Exists online : False
Views : 403