NS_I_RESTRIPE_DONE (0X400D0194): What It Means & Fix

Quick answer

That code means a restripe operation—where Windows redistributes data across drives in a Storage Space or RAID-like pool—has finished successfully. If it keeps popping up, your disks are having trouble staying healthy.

What's actually happening here

You ran into NS_I_RESTRIPE_DONE (0X400D0194). This is a status code from Windows Storage Spaces or a similar storage subsystem. It's part of the NT Status family—0x400D0194 breaks down as: severity Success (bit 30 = 0, so it's informational), facility FACILITY_NT_STATUS (0xD), and code 0x194, which maps to STATUS_STRIPE_RESTRIPE_DONE.

The real trigger: you likely saw this in the System Event Log (Event Viewer) or in a command-line tool like wmic or fsutil. It's not an error—it's a status notification. But if you're seeing it repeatedly, it means your storage pool keeps initiating restripes. That's a symptom of failing disks, a degraded pool, or a misconfigured parity layout.

I've seen this on Windows Server 2016 and 2019 boxes running Storage Spaces with parity disks. A single bad SATA cable can cause this message to flood the event log every few minutes.

Fix steps

Open Event Viewer — press Win+R, type eventvwr.msc, hit Enter. Navigate to Windows Logs > System. Look for events with source NTFS or volmgr around the same time as the NS_I_RESTRIPE_DONE entries. They'll show you which disk or volume is causing the restripe.
Check Storage Spaces health — open Storage Spaces from Control Panel (Windows 10/11) or Server Manager. Look for a yellow or red warning on any virtual disk. If the pool is degraded, the system will keep restriping to compensate for a missing or failing drive.
Run PowerShell to inspect — open PowerShell as admin. Run:
```
Get-StorageJob | Where-Object {$_.Name -like "*Restripe*"}
```
If you see a restripe job stuck in Running state for hours, something's blocking it. Also run:
```
Get-PhysicalDisk | Select-Object FriendlyName, HealthStatus, OperationalStatus
```
Any disk showing Warning or Unhealthy is likely the culprit.
Replace failing drives — if a physical disk shows OperationalStatus: Predictive Failure or HealthStatus: Warning, replace it. In Storage Spaces, right-click the virtual disk and choose Remove Drive, then physically swap the disk. After replacement, the pool will automatically restripe—that's normal.
Run chkdsk on the volume — if the restripe is triggered by file system corruption on a parity volume, run:
```
chkdsk X: /f /r
```
(Replace X: with the actual drive letter). This fixes metadata that might confuse the striping logic.

Alternative fixes if the main one fails

Disable write-back caching on the volume — in Device Manager, find the disk, go to Policies, and uncheck Enable write caching on the device. Caching can cause the subsystem to think data is missing, triggering restripes. Only do this if you have a UPS—it'll slow writes slightly but makes the system more stable.
Reset the storage pool — in PowerShell:
```
Reset-PhysicalDisk -FriendlyName "NameOfFailingDisk"
```
This marks the disk as healthy again if it was temporarily flagged by a flaky connection. Then run:
```
Repair-VirtualDisk -FriendlyName "YourVirtualDiskName"
```
Wait for it to finish before checking the event log again.
Update storage controller drivers — go to your motherboard or RAID controller manufacturer's site, download the latest SATA/SCSI driver. Outdated drivers miscommunicate with Storage Spaces, causing false restripes.
Check your SATA cables and power — reseat both ends. A loose SATA cable can cause intermittent disconnects that look like disk failures to Storage Spaces. I've fixed two machines this way.

Prevention tip

The best way to avoid seeing NS_I_RESTRIPE_DONE repeatedly: monitor disk health proactively. Use Get-PhysicalDisk | Where-Object {$_.HealthStatus -ne "Healthy"} as a weekly scheduled task or script. Replace any disk that shows Warning before it fails. Also, keep your Storage Spaces pool on a dedicated controller—don't mix boot and data drives on the same chipset unless you're using a proper HBA. One bad cable or failing disk in a parity setup will trigger restripes non-stop, and the message is just the tip of the iceberg.