| Previous | Next |
| IMAPI_E_INVALID_DATE | IMAPI_E_NOT_FILE |
IMAPI_E_FILE_SYSTEM_NOT_EMPTY
IMAPI_E_FILE_SYSTEM_NOT_EMPTY is an image-state precondition failure. IFileSystemImage builds a directory hierarchy under its root, and some configuration changes are only valid before that hierarchy has content. Microsoft explicitly documents empty-image restrictions for strict file-system compliance and other image settings. The error therefore means the requested operation was issued after files or directories had already been introduced.
Check configuration order, not the optical disc contents
- Record
FileCountandDirectoryCountbefore the failing call. - Identify which configuration property is being changed and when the first item was added to the root hierarchy.
- Create and configure a fresh image object when the setting is required from the beginning.
The phrase “file system” here refers to the in-memory image under construction. Erasing or replacing the disc will not empty that COM object. A robust builder sets file-system selection, compliance, revision, and related global policy before AddFile, AddDirectory, or AddTree. Make that ordering explicit in code and logs so later refactoring cannot move configuration after content insertion.
IFileSystemImage · Strict compliance · IFsiDirectoryItem
Looking for a different code? Search another status or error code.