Thanks Froggie...will try that...but doubt that will help as the IS has always played nicely with Hasleo updates...at least so far.
@ Baldrick I confirm your "Failed to create (start) process (0x0063001E00000005)" I have this on one of my pcs, but also the boot menu will not load for me plus when I try to do a restore from I get BSOD,.
Hi warrior99 Thanks for the update. I have tried a restore and for me it has work flawlessly...no issue with the Boot Menu & no BSOD. So I count myself lucky. Have still not heard back from Hasleo Support but may I suggest that you contact them directly with your information...that may spur them on to respond/take a look. Although from what I hear they are pretty responsive normally. Cheers, Balders
@EASTER - not to be too concerned . V5.2.2.2 is a level #2 minor release. Almost all of those mentions are extreme edge cases which 99% of users will never see. Two of them came from me, two from others... they just happen to come around the same time. For instance, most of the users here would never have tried the "Rebuild WMI" feature... many probably don't even know what it is . This is what happens when you are finally out in the weeds testing the extremes of an application 'cause the main functions work so well. The fact that the Dev teams responded so well to these types of edge conditions speaks very highly of them. Sit back and enjoy another Margarita with this beautiful Spring Season upon us...
Hi All Have heard back from Hasleo Support (pretty quickly as it happens) with something to try which did not work, and therefore I sent them the latest log file. Further to analysing that they came back as follows: "We have analyzed the log file, Windows returned the error code 0x5 (Access is denied.) when Hasleo Backup Suite tries to run bcdedit.exe to add boot entry, it's clear that there is a program preventing it from executing bcdedit.exe. ... This is a situation we have never encountered before. Please Open an elevated cmd.exe in Windows, then run C:\WINDOWS\System32\bcdedit.exe /enum {bootmgr} to see if it works?" So, I made sure that both the Hasleo Backup-related folders in Program Files and ProgramData have been added to the Exclusions list of my AV/IS application (never had to do that before in all of the time I have been running HBS). Then ran the command provided and whereas previously where I still had the Add Boot Menu option under Tools I am now seeing a Remove Boot Menu option instead...which looks much more normal/as I would expect it. Also tried running a restore under WINPE from the Boot Menu option...and that worked fine (although it did even before undertaking the above). I am therefore guessing that the issue is resolved but will double check again after the next update to see whether the issue is completely resolved or not. Hope that helps? Balders
@Baldrick - I have a similar issue as well, but different than yours... haven't turned it over to Hasleo yet and it started BEFORE the v5.2.2.2 release. When the HBS app is started, under "Tools" the BOOT menu option always says "Remove BOOT menu." I don't use the BOOT menu and there is no entry in the BCD (using BOOTice to manage) for the HBS addition. If I <click> on the "Remove BOOT menu" option, it does something briefly then returns to the "Tools" menu now saying "Add BOOT menu." I then look at my BCD and see that nothing has occurred (as expected). If I just pop back to my "Home" TAB then return back to my "Tools" TAB, the BOOT Menu entry has changed back to "Remove BOOT menu"... having done nothing since the last status change. HBS is interpreting something as having a BOOT entry when the System really doesn't have one... maybe some registry leftover glitch. Since it's never affected my general use of HBS, I have ignored it 'til now. I'll submit it for analysis to see what they find.
Hi Froggie Hope that you are doing well? Thanks for the info. What is strange is that whenever the app has been upgraded I have to go into Tools and 'Add Boot Menu', after which when I look in Tools again the app has a 'Remove Boot Menu' option. This has been my experience ever since I have been using HBS (which is for quite a while now). I did try the 'Remove Boot Menu' option standalone to see if it worked and it did indeed remove the WINPE boot menu option even though HBS has not been installed. What is unusual in my flavour of the issue is that even though post the upgrade to v5.2.2.2 I did run the 'Add Boot Menu' option it ended with the error recorded (which we know is due to "...Hasleo Backup Suite tries to run bcdedit.exe to add boot entry, it's clear that there is a program preventing it from executing bcdedit.exe") yet I still had a WINPE boot menu option on log on but under Tools it was offering the 'Add Boot Menu' option rather than the expected 'Remove Boot Menu' option. Which in my book would support my issue being now when I booted into Windows there was no WINPE Boot Menu option so most likely down to something preventing the excution of bcdedit.exe. All appears to be fixed now but good idea to have logged your 'flavour' of the issue. Will be interesting to see what the HBS support team come back with in your case. Regards, Balders
They responded overnight with a test build and all is now just fine... some fringe area glitch they found and fixed. This team is amazing...
To me, this is the most important, listening to customer and fixing problems fast. So many times we see company that takes ages to fix problems...
These comments are why Wilders needs a thumb up emoji! I completely agree with @Antarctica; caring developers are especially important with imaging applications where failure means loss.
Hi. Anyone experiencing extreme slowdowns when restarting the pc due to HBS? I was and wondered why so i started uninstalling the latest installs, after uninstalling HBS the pc got back to 7-8sec instead of 34-40.
@pb1 - no changes here as well. Best to touch base with their forum HERE... or work directly with them at Support AT EasyUEFI DOT com
No, the change won't be incorporated into the main build until next release. The download link was not available on their Forum since we were doing this interaction via email. See PM for further details...
