Windows 10: File system index corruption after Win10 1903 update

I have Windows 10 Home, running smoothly for more than 1 year. However, the system became extremely slow (HDD keep reading) when I was moving a shortcut on Desktop - just re-locate. After reboot (took 15mins each) twice (by coincidence, KB4503293 and KB4503308 installed and rebooted again), there were several critical error in system event log: (English translation was at the end of line if necessary)



- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Ntfs" Guid="{dd70bc80-ef44-421b-8ac3-cd31da613a4e}" />
<EventID>55</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-06-14T09:21:52.454358100Z" />
<EventRecordID>1075</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="408" />
<Channel>System</Channel>
<Computer>DESKTOP-MKCV2NJ</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="DriveName">??</Data>
<Data Name="DeviceName">\Device\HarddiskVolumeShadowCopy1</Data>
<Data Name="CorruptionState">0x0</Data>
<Data Name="HeaderFlags">0x922</Data>
<Data Name="Severity">关键</Data> //critical
<Data Name="Origin">文件系统驱动程序</Data> //File system device driver
<Data Name="Verb">索引偏移</Data> //Index bias
<Data Name="Description">在文件系统索引结构中发现损坏。文件参考编号为 0x9000000000009。文件名为“<无法确定文件名>”。损坏的索引属性为“:$SII:$INDEX_ROOT”。损坏的索引块位于 Vcn 0xffffffffffffffff，Lcn 0xffffffffffffffff。损坏开始位置在索引块中的偏移 112 处。</Data> //Corruption found in file system index structure. File reference number 0x9000000000009. File name "<Cannot determine file name>", The property of corrupted index is “:$SII:$INDEX_ROOT”. Corrupted index block located at Vcn 0xffffffffffffffff, Lcn 0xffffffffffffffff. Corruption begins at index block bias 112.
<Data Name="Signature">0xe3bb82f4</Data>
<Data Name="Outcome">只读卷</Data> //Read-only volume
<Data Name="SampleLength">0</Data>
<Data Name="SampleData" />
<Data Name="SourceFile">0x14</Data>
<Data Name="SourceLine">4347</Data>
<Data Name="SourceTag">350</Data>
<Data Name="AdditionalInfo">0xd00000a2</Data>
<Data Name="CallStack">Ntfs+0x1a82a6, Ntfs+0xe6d02, Ntfs+0x161285, Ntfs+0x160ced, Ntfs+0x160446, Ntfs+0x16e05f, Ntfs+0xc9534, Ntfs+0x7560, ntoskrnl+0xc4855, ntoskrnl+0x12f725, ntoskrnl+0x1c3dfa</Data>
</EventData>

</Event>

The issue can't be fixed by CHKDSK /F at system boot. Anyone know how this issue was caused? Thanks!

:)

 

Corrupted file RAR

If the archive has been created using WinRAR, why don't you try WinRAR itself? It has a built-in repair feature for repairing corrupted archive (ZIP as well as RAR). Follow the steps given below:

• Open WinRAR application in your system.
• Now click on File tab > Open or simply press Ctrl+O.
• A small window "Find Archive" will pop up. Locate the corrupt RAR archive from your system directory and select it.
• Now click Open button.
• Click Tools tab > Repair archive or simply press Alt+R.
• Again a small window "Repairing File name.rar" will pop up.
• Now click Browse to select a location to save the repaired archive.
• Check the box "Treat the corrupt archive as RAR" and click OK.
• WinRAR will start repairing of corrupt RAR archive. Once it gets completed click Close.

I hope the above steps will help you repair the corrupted RAR archive.

Thanks.

 

Windows Index won't start

Hi Edward,

Corrupted search catalog files might be a possible cause why you are experiencing an issue with stating the Windows index. To address this concern, we suggest rebuilding your search catalog. Doing so can repair search results and indexing of your Microsoft
Windows and Microsoft Office system data files.

Follow these steps to rebuild the search catalog:

• Open Control Panel.
• In the Search box, type Indexing, and then choose Indexing Options.
• Click on Troubleshoot search and indexing.
• Answer the prompts to successfully run the troubleshooter.

If the same issue persists, we suggest performing the following troubleshooting methods:

Method 1:

Run the System File Checker tool. It is a utility that allows users to
scan for corruptions in Windows system and restore corrupted files. The link contains further information about how to run the System File Checker tool.

Method 2:

Run the Deployment Image Servicing and Management tool. This tool will automatically repair the components of your Windows operating system and records the corruptions to the log file.

To run the DISM tool, follow these steps:

• Using Search, type Command Prompt.
• Right-click on Command Prompt on the search results and then select Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password or click Yes.
  
• In the Command Prompt window, type DISM /Online /Cleanup-Image /RestoreHealth, and then hit Enter.
  
• Once the scan is finished, restart your computer.

Let us know if further assistance is needed.

 

Search index settings

Hi Samir,

Thank you for posting on Microsoft Community. I understand the inconvenience you are facing. I will certainly help you with this. This issue may arise due to some corruption or broken index. Kindly refer the below given methods and check if it helps:

Method 1:

I suggest you to run the Search and Index troubleshooter and check if it helps.

• Press Windows key, type troubleshooter in the search box and then press enter.
• Select Troubleshooting. Click on
  view all and select Search and Indexing troubleshooter and follow the on-screen instructions.

Method 2:

If issue persist, I suggest you to run System file checker. System File checker (SFC) scan is done to check if there are any corrupted system files that could be causing this issue. Kindly follow the below given steps:

• Press Windows key + X, select Command prompt (Admin) to bring up elevated Command prompt.
• In Command prompt type sfc/scannow and press enter.
• Restart the computer.

Hope this information helps. Post back with updated issue details for further help.

Thank you.