Today, 05:27 AM
Thank you, I will save the log file with "Save LOG file" after reproducing the error. Where should I send it - can I attach it here in the thread, or should it go to Hasleo support?
|
Hasleo Backup Suite V6.0.0.0 ALPHA test release
|
|
Today, 05:27 AM
Thank you, I will save the log file with "Save LOG file" after reproducing the error. Where should I send it - can I attach it here in the thread, or should it go to Hasleo support?
Today, 05:58 AM
(Today, 05:27 AM)yastil Wrote: Thank you, I will save the log file with "Save LOG file" after reproducing the error. Where should I send it - can I attach it here in the thread, or should it go to Hasleo support? Send it to [email protected], with a link to your original post describing your issue, and attach your log.
10 hours ago
Hi all,
I just moved all posts related to the new alpha version to this own thread. Hope that helps to better distinguish between the current stable release and this new test build. Happy testing!
10 hours ago
(Today, 03:34 AM)admin Wrote: We’ve narrowed down the scope of driver injection. Please download the updated BuildPE.dll, replace the existing file in the bin folder under the installation directory, and then try creating the WinPE again. I don't really mind this bit of bloat and have made my ISOs and EDs with the original dll. So unless there is really some reason to change .....
9 hours ago
(Today, 05:27 AM)yastil Wrote: Thank you, I will save the log file with "Save LOG file" after reproducing the error. Where should I send it - can I attach it here in the thread, or should it go to Hasleo support? Do you mean that after replacing BuildPE.dll, you still cannot successfully create WinPE?
9 hours ago
(10 hours ago)Epictetus Wrote:(Today, 03:34 AM)admin Wrote: We’ve narrowed down the scope of driver injection. Please download the updated BuildPE.dll, replace the existing file in the bin folder under the installation directory, and then try creating the WinPE again. If the created WinPE is too large, it may cause the creation to fail. In addition, some drivers are indeed not useful in the WinPE environment, so we will try to extract only HID, DISK (NVMe), and network-related OEM drivers.
9 hours ago
(Yesterday, 05:22 AM)n8chavez Wrote: The second issue I came across has to do with the image protection feature. HBS was unable to see the drive I store my backups on, in my case b:\, thus I cannot enable the protection feature. That location is accessible, but the drive letter is hidden using a registry tweak. "Unhiding" the drive letter did not resolve the issue. We’d like to reproduce the issue in our test environment, so could you please share the exact method you used to hide the drive letter? Thanks.
Confirming: after replacing BuildPE.dll with the updated version, "From WinRE" with automatic driver injection and "Windows UEFI CA 2023" enabled now completes successfully on my system (Windows 11, build 26100). Before, it failed at 100% with error 0x011F0015C0AAB132. I wrote the rescue disk to a USB drive and tested booting from it: it boots and starts Hasleo normally (only a brief screen flicker at the start). Thank you for the quick fix!
OK - took the hint and replaced the BuildPE.dll and found that;
With Win11 and all updates including KB5124010, on a DellXPS 9310 (2022 I think), and using the OPE, the created ISO was about a third of the size with the previous dll. The build process - of both ISO-making and stand-alone ED USB-making - was at most half the time with the previous dll. All processes completed without errors or error messages - but then they did with the previous dll for me at least too. Both the ISO and stand alone ED USB boot and work just fine. Hope that is useful.
5 hours ago
(Today, 03:34 AM)admin Wrote: We’ve narrowed down the scope of driver injection. Please download the updated BuildPE.dll, replace the existing file in the bin folder under the installation directory, and then try creating the WinPE again. Much better. The size is now similar to the previous built. This version did experience the Network PE Manager pop-up error, but it started normally the second time. |
|
« Next Oldest | Next Newest »
|