Windows Error 1184: “An Attempt Was Made to Access a Partition That Has Begun Termination”
Why This Error Happens
Error 1184 occurs when a process or service attempts to read from or write to a system partition (often related to Kernel Transaction Manager or a volume) that Windows has already marked for teardown or dismounting. This typically happens due to an improperly terminated application, a corrupted volume shadow copy, or a driver that fails to release a handle before the OS proceeds with partition cleanup. It can also surface when NTFS transactional resources are left in an inconsistent state after a crash or forced shutdown.
Step-by-Step Resolution Guide
- Check Disk for Corruption
Open Command Prompt as Administrator (Win + X → Terminal (Admin)) and run:
chkdsk C: /f /r
Schedule the check on next restart if prompted, then reboot.
- Verify Volume Shadow Copy Service (VSS) Integrity
Run the following to check for VSS errors, as they frequently interact with partition termination states:
vssadmin list writers
If any writer shows “Retryable error” or “Failed,” restart the associated service via services.msc, or reboot the machine.
-
Update Storage and Chipset Drivers
Go to Settings → Windows Update → Advanced Options → Optional Updates → Driver Updates. Install any pending storage controller (AHCI/NVMe/RAID) or chipset driver updates, as outdated drivers can mishandle partition dismount signals. -
Check Event Viewer for the Triggering Process
Openeventvwr.msc→ Windows Logs → System. Filter for Event ID 1184 and note the source application/service in the event details. If it’s tied to a specific third-party backup or disk management tool, update or reinstall that software. -
Repair System Files
Run the following in an elevated Command Prompt to fix underlying corruption that may be causing improper partition state transitions:
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
Restart once complete.
Alternative or Verification Steps
- Verify the fix: Reproduce the original action (e.g., the backup job, disk operation, or app launch) that triggered the error and confirm Event Viewer shows no new Event ID 1184 entries.
- Alternative fix: If the error persists and is tied to a specific disk, disconnect and reconnect the drive (for external disks) or, for internal drives, use Disk Management (
diskmgmt.msc) to manually verify the partition is online and not stuck in a “pending” or “offline” state before retrying the operation.