The system cannot find the file specified. (0x0095007F00000002)

[mehasleoforum]

Hi there.

Before I move on to a different backup solution, I want to see if there is a fix for this:

Error while trying to do a System backup:
The system cannot find the file specified. (0x0095007F00000002)

Latest Hasleo Backup version but, started happening with several versions back.
Happening on several PCs.
This does NOT happen with other Backup software (Macrium Reflect finishes the backup without error).

From the Hasleo Log (below), it shows the shadow files being the issue:

2026-02-04 15:55:57 T:0000B37C 87 - Deleting shadow copy set {4d54d302-e714-4936-80d4-d67c73cda2b4} ...
2026-02-04 15:55:57 T:0000B37C 87 Error while deleting shadow copies...
2026-02-04 15:55:57 T:0000B37C 87 - Last shadow copy that could not be deleted: {00000000-0000-0000-0000-000000000000}
2026-02-04 15:55:57 T:0000B37C 87 ERROR: COM call L"m_pVssObject->DeleteSnapshots(snapshotSetID, VSS_OBJECT_SNAPSHOT_SET,FALSE,&lSnapshots,&idNonDeleted)" failed.
2026-02-04 15:55:57 T:0000B37C 87 - Returned HRESULT = 0x80042308
2026-02-04 15:55:57 T:0000B37C 87 - Error text: VSS_E_OBJECT_NOT_FOUND

I can see shadow copy created when backup started shows up, nothing else.
vssadmin list shadows
After backup finishes, shadow list shows empty.

Already tried VSS Repair, checkdsk /f, dism /restorehealth and sfc /scannow.


Hasleo Log:

...
2026-02-04 15:55:57 T:0000B37C .\ImageMaker.cpp 630 nRet=0x0095007F00000002
2026-02-04 15:55:57 T:0000B37C .\FilePublic.cpp 1807 nRet=0x070E007F00000002
2026-02-04 15:55:57 T:0000B37C .\IncompleteBackupHandler.cpp 172 nRet=0x070E007F00000002
2026-02-04 15:55:57 T:0000B37C .\ImageWriterCluster.cpp 173 nRet=0x070E007F00000002
2026-02-04 15:55:57 T:0000B37C .\DiskBackup.cpp 447 nRet=0x0095007F00000002
2026-02-04 15:55:57 T:0000B37C 149 - Mark all writers as succesfully backed up...
2026-02-04 15:55:57 T:0000B37C 149 Completing the backup (BackupComplete) ...
2026-02-04 15:55:57 T:0000B37C 127 (Waiting for the asynchronous operation to finish...)
2026-02-04 15:55:57 T:0000B37C 127 (Waiting for the asynchronous operation to finish...)
2026-02-04 15:55:57 T:0000B37C 87 - Deleting shadow copy set {4d54d302-e714-4936-80d4-d67c73cda2b4} ...
2026-02-04 15:55:57 T:0000B37C 87 Error while deleting shadow copies...
2026-02-04 15:55:57 T:0000B37C 87 - Last shadow copy that could not be deleted: {00000000-0000-0000-0000-000000000000}
2026-02-04 15:55:57 T:0000B37C 87 ERROR: COM call L"m_pVssObject->DeleteSnapshots(snapshotSetID, VSS_OBJECT_SNAPSHOT_SET,FALSE,&lSnapshots,&idNonDeleted)" failed.
2026-02-04 15:55:57 T:0000B37C 87 - Returned HRESULT = 0x80042308
2026-02-04 15:55:57 T:0000B37C 87 - Error text: VSS_E_OBJECT_NOT_FOUND
2026-02-04 15:55:57 T:0000B37C .\VolumeShadowCopy.cpp 979 nRet=0x03D2015080042308
2026-02-04 15:55:57 T:0000B37C .\VolumeShadowCopy.cpp 217 nRet=0x03D2015080042308
2026-02-04 15:55:57 T:0000B37C .\DiskBackupWrapper.cpp 422 nRet=0x0095007F00000002
2026-02-04 15:55:57 T:0000B37C .\DiskBackupWrapper.cpp 866 nRet=0x0095007F00000002
2026-02-04 15:55:57 T:0000B37C .\DiskBackupWrapper.cpp 2332 nRet=0x0095007F00000002
2026-02-04 15:55:57 T:0000B37C .\DiskBackupWrapper.cpp 2342 nRet=0x0095007F00000002
2026-02-04 15:55:57 T:0000B37C .\DiskBackupWrapper.cpp 1682 nPos=100
2026-02-04 15:55:59 T:0000B37C .\BackupWorker.cpp 282 nRet=0x0095007F00000002
2026-02-04 15:55:59 T:0000B37C .\BackupWorker.cpp 1540 nRet=0x0095007F00000002
2026-02-04 15:55:59 T:0000B37C .\WorkerPublic.cpp 1236 nRet=0x006E001600000000
2026-02-04 15:55:59 T:00008758 .\BackupWorker.cpp 1351 nRet=0x0000000000000000
2026-02-04 15:55:59 T:0000B37C .\BackupWorker.cpp main 1657 End...


=====================

vssadmin list shadows

shadow copy created when backup started shows up, nothing else.
After backup finishes
Shadow list shows empty.

Hope this can be fixed as I like Hasleo and want to support them.
Thanks.

[admin]

This issue is unrelated to VSS. Please verify whether the target drive or folder where the backup images are stored still exists.

[mehasleoforum]

This issue is unrelated to VSS. Please verify whether the target drive or folder where the backup images are stored still exists.

Thanks for the quick reply.
Yes, it is a shared drive and I just realized this only happens for Full Backups and it ends up working at the third try.
(Same VSS error still in Hasleo Log).

I can see there is something going up with the share drive. I will do further checks on the share drive.

BUT, if other Backup solutions work fine (same exact share drive), and Hasleo does work if you try a few times,
can Hasleo be changed to simply NOT delete the backup at the end if this error happens?

Thanks.

[admin]

I’m sorry, this issue is not caused by VSS, so please don’t focus too much on the VSS-related information recorded in the log file. In the event of a backup failure, the newly generated image file must be deleted because the data stored within it is incomplete.

[mehasleoforum]

I’m sorry, this issue is not caused by VSS, so please don’t focus too much on the VSS-related information recorded in the log file. In the event of a backup failure, the newly generated image file must be deleted because the data stored within it is incomplete.

Confirming that the issue was not VSS related made me dig deeper and found the issue to be SMB share ACL permissions.

Strange thing is that the NAS settings have not changed, and not all PCs had this issue, plus there was no problem
with other Backup software (do they deal better with whatever condition this was?).

Thanks.

[garioch7]

@admin,

In the event of a backup failure, the newly generated image file must be deleted because the data stored within it is incomplete.

This leads to a question: Macrium deletes images that fail verification (Check Image), but are reported to have successfully completed, whereas ETBH does not.

This is not applicable to to the OP's question, but was does HBSP do if an image fails a "Check Image."  I ask because, if an image can be successfully mounted, then while all not files may be recoverable, and the backup cannot be used to completely restore a system, it may be that the user only wants to find one or more data files ...

As you know, I always verify/check my images, and I think the Macrium approach is a little draconian.  Twice over the years, I have encountered situations to which I was alerted by a failed verify or check image, to investigate that my target external HDD was no longer reliable and needed to be replaced.  I might also have wanted to only salvage one or more recently created or modified document files.  My backup strategy is now more advanced, so I have all of my documents immediately and automatically backed on my Proton Drive, but in those days, I did not.

Have a great day.

Regards,
Phil

[admin]

@admin,

In the event of a backup failure, the newly generated image file must be deleted because the data stored within it is incomplete.

This leads to a question: Macrium deletes images that fail verification (Check Image), but are reported to have successfully completed, whereas ETBH does not.

This is not applicable to to the OP's question, but was does HBSP do if an image fails a "Check Image."  I ask because, if an image can be successfully mounted, then while all not files may be recoverable, and the backup cannot be used to completely restore a system, it may be that the user only wants to find one or more data files ...

As you know, I always verify/check my images, and I think the Macrium approach is a little draconian.  Twice over the years, I have encountered situations to which I was alerted by a failed verify or check image, to investigate that my target external HDD was no longer reliable and needed to be replaced.  I might also have wanted to only salvage one or more recently created or modified document files.  My backup strategy is now more advanced, so I have all of my documents immediately and automatically backed on my Proton Drive, but in those days, I did not.

Have a great day.

Regards,
Phil

Dear Phil,

Hasleo Backup Suite will only delete the backup image file(s) created during the backup if the backup fails, and it will not automatically delete the backup image(s) if the verification fails. You are right that a failed image verification does not mean all files cannot be recovered, unless the header or footer of the image file is damaged.

Have a great weekend!

Best regards,

[garioch7]

@admin,

Thank you for replying to my query.  I am pleased that HBSP will not normally delete an image that fails a "Check Image" test, "unless the header or footer of the image file is damaged."

Have a great day.

Regards,
Phil