(12-05-2024, 07:57 AM)stevel Wrote:(12-04-2024, 12:38 PM)admin Wrote: I'm sorry I couldn't reproduce your problem, can you describe your steps in detail, and if you can provide a screenshot. And please click "" > "Save log file" to open the save log file dialog, save the log file and then send it to us via email at [email protected]. Thanks.
So ive tried replicating the error again myself to get a log file out of it but ive now come across another error (Failed to create directory. (0x05420078000000CE), overall system backups seem really unstable for me and I dont know why.
Honestly im tired right now and I dont have the time or energy to deal with this and File backups already seem stable enough so ill just use them since they dont give me these types of errors.
sorry for coming to you guys with this error.
We have analyzed the error code 0x05420078000000CE, Windows returned the error code 0xCE (The filename or extension is too long.) when Hasleo Backup Suite tried to create file in the destination.
Were you trying to restore the entire Windows system backup to a different location in file mode? When restoring in file mode, Hasleo Backup Suite restores the entire file tree at the destination location, which may cause the file name to be too long. For example, there is a very long file path (C:\Test\111...111.txt, which is 250 characters long) in the backup image, and when we try to restore it to destination location (D:\222...222, which is 50 characters long ), the length of the entire path (D:\222...222\C+\Test\111...111.txt , which is 300 characters long ) after the restore will exceed the maximum path length (about 260 characters) allowed by Windows, which leads to the 0xCE problem.
So it's not a backup issue. Also I don't see the point of restoring all files in file mode from a Windows system backup.