Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
FIXED: 0x083f00850000003 (cannot find path) (Windows 11 or Parallels bug)
#1
Hello,

am no longer able to safe backups. I do not know why.

The destination path is
H:\Backup\Windows\Hasleo\Data\VM_Data_2024-03-20

The files there are:
VM_Data_2024-03-20_20240321_Full_V1_1.DBI
VM_Data_2024-03-20_20240402_Incremental_V2_1.DBI
VM_Data_2024-03-20_20240408_Differential_V4_1.DBI
VM_Data_2024-03-20_20240408_Incremental_V3_1.DBI
VM_Data_2024-03-20_20240415_Incremental_V5_1.DBI

I am able to RESTORE files from VM_Data_2024-03-20_20240415_Incremental_V5_1.DBI with NO PROBLEMS when I ciick on the BLACK icon for restoring and select VM_Data_2024-03-20_20240415_Incremental_V5_1.DBI .

But when I try to create another incremental, I get the error "0x083f00850000003 System cannot find the path specified".

When I go to Backup properties, the folder icon at the end of the field "Path" is greyed out. (I think that's normal).

I have a second backup on H: (based on 2023). The problem is the same there. So it is not a specific problem with the 2024-03-20 backup. It is a general problem.

When I click "Open Location", I also get the error! Even though the location is accessible (can restore, can see it in Windows Explorer).

I don't know what happened.
Reply
#2
I was able to fix the bug. It was a Windows bug. Perhaps it was related to Parallels.
I went to disk management and assigned a different drive. Then I assigned a different drive (e.g. T:\). Then I re-assigned H:
Then it worked.
But note that H: was visible in Explorer ALL THE TIME and Hasleo could RESTORE all the time. A weird bug.
Windows 11 ARM no Paralllels.
Note that rebooting did NOT fix the problem.
Reply
#3
This is indeed a strange problem, the last 8 digits of the HBS error code are the error code returned by Windows, and the error returned by Windows is indeed 0x00000003 (The system cannot find the path specified.).
[Image: attachment.php?aid=446]


Attached Files Thumbnail(s)
   
Reply
#4
I have only seen this problem this one time. And I was able to fix it. -> No big deal. If it re-occurs, I will tell you.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)