Feature REQUESTS

[garioch7]

I think it might be a better option to move towards "hot patches" for new versions, if that is feasible.  Macrium does it, and users are notified by Macrium in the Release Notes when they need to create new Emergency Disks.

I don't know if the Hasleo Team has the time to do that now, but I do think that should be in their long-range plans.  The uninstall/reinstall routine is time-consuming, and it has potential pitfalls of the customer no longer being recognized as such.

Easeus also has the uninstall/reinstall routine, but their routine is even worse.  It "forgets" the licensing information, so my ETBH clients call me when their "Trial 30-day" version expires.  The answer is simple -- Go the to the Activation screen, and ETBH pulls up the licensing information from wherever it stores it, and hit the "Activate" button, but that is a pain in the you what, and completely baffles my less computer-literate clients.  Needless to say, I am no longer recommending ETBH.  Guess what I am recommending these days ... 

Just my two cents.  Have a great day.

Regards,
Phil

[admin]

@n8chavez Thanks!

Yes, as n8chavez said. After installing the new version, you need to manually add the WinPE environment to the Windows boot menu.

[admin]

I think it might be a better option to move towards "hot patches" for new versions, if that is feasible.  Macrium does it, and users are notified by Macrium in the Release Notes when they need to create new Emergency Disks.

I don't know if the Hasleo Team has the time to do that now, but I do think that should be in their long-range plans.  The uninstall/reinstall routine is time-consuming, and it has potential pitfalls of the customer no longer being recognized as such.

Easeus also has the uninstall/reinstall routine, but their routine is even worse.  It "forgets" the licensing information, so my ETBH clients call me when their "Trial 30-day" version expires.  The answer is simple -- Go the to the Activation screen, and ETBH pulls up the licensing information from wherever it stores it, and hit the "Activate" button, but that is a pain in the you what, and completely baffles my less computer-literate clients.  Needless to say, I am no longer recommending ETBH.  Guess what I am recommending these days ... 

Just my two cents.  Have a great day.

Regards,
Phil

Dear Phil,

Thank you for such a detailed and sincere suggestion!

The "hot patch" update method you mentioned is indeed very valuable, especially in reducing user steps, preventing license information loss, and improving the experience for less tech-savvy users. Although hot patching may not be feasible in the short term, we will record your suggestion in our long-term planning.

Thank you again for taking the time to share your experience and insights.

Best regards,

[garioch7]

@admin,

Thank you for your reply. I am pleased that it will be in the long-term plans for HBS, which is what I was suggesting.

I am not a programmer, but I can imagine that "hot patching" would indeed be very complicated to program. I know that you have higher short-term priorities, and only limited resources to program, test, and implement them.

Have a great day.

Regards,
Phil

[admin]

Dear Phil,

Thank you very much for your understanding and support. It truly means a lot to us, especially given our limited resources. Your recognition of the challenges we face, such as the complexity of hot patching and the need to balance short-term priorities, is greatly appreciated.

Please rest assured that we will keep your valuable suggestion in mind as we move forward with the long-term plans.

Have a great day as well.

Best regards,