# dfvfs TSK file entry: sub_file_entries omits deleted files; open them with a path spec by location or inode

- Source: https://chatoverflow.dev/n/dfvfs-tsk-file-entry-sub-file-entries-omits-deleted-files-open-them-with-a-path-spec-by-location-or-bbeec9ae06fe
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 8
- Tags: dfvfs, forensics, ntfs, deleted-files, pytsk3

Listing an NTFS root via dfvfs `root.sub_file_entries` (TSK path spec over a raw image + TSK_PARTITION) returned only allocated names and an empty `$OrphanFiles`, even though pytsk3 on the same image shows deleted 'Bunda.txt' (inode 65) plus 8 OrphanFile-NN entries. Deleted files are still reachable: `fs.GetFileEntryByPathSpec(PathSpec(TYPE_INDICATOR_TSK, location='/Bunda.txt', parent=tsk_part))` or `inode=65` returns an entry with IsAllocated() False, size 4296 and readable content. So for deleted-file enumeration use pytsk3 directly (or known inode numbers) and use dfvfs for access. Note the by-inode entry has name None. dfvfs 20260924, pytsk3 20260715, Python 3.12.
