Just so I’m clear on this, by machine code you are referring to the MAC address of my Ethernet adaptor (physical address) or presumably WiFi adaptor if I’m wireless?
I rarely to never reset/reformat fully unless like my situation dictates like now with my plex server, under RMA for a hardware change. It will get set up with all the programs I need to get it stable, the server, IP setup, p/w managers firewall rules drivers etc. A bare-metal disk image will then be made once the essentials are on and the OS is setup and saved to a network drive away from the main backup schedule. This will be my worst case scenario nuke revert in the event I need a fresh start, as it will shave off a good 6 hours or so off setting it back up. The separate weekly backup is the next rollback priority fallback and the 6 day incremental are a cushion.
Thank again for the info.
All my household systems have been set up this way it kind of works for me.
Thank you for your post. I think the "Machine Code" is the computer "Hardware ID." I could be mistaken.
Here is an image of my Hasleo Backup Suite Pro "About" screen:
From what I have read, this is tied directly to a specific computer. Each computer has a unique Hardware ID (Machine Code), as do cellphones with their own IMEI number. Please see this link for more information:
But, please do not make any decision based on what I have told you. I am not an expert on software licensing. The Forum Administrator, or one of more knowledgeable colleagues, will be able to confirm or correct what I have told you in the next few hours.
11-04-2026, 09:39 PM (This post was last modified: 11-04-2026, 09:41 PM by garioch7. Edited 1 time in total.
Edit Reason: add PS
)
@TroubledSoul,
It appears that @Froggie and I were posting simultaneously. I cannot provide details as to how Hasleo assigns a "Machine Code" yet, so I am going to be curious about the impending reply of the Forum Administrator, @admin, when s/he comes back online. The Forum Administrator is here every day, weekends and holidays included. The Forum Administrator is also a senior member of the Hasleo Development Team.
It would not make sense that Hasleo would only identify a router because multiple computers could be on that router, and use a paid version of Hasleo exceeding the number of "seats" the customer had purchased.
I await, with great interest, the reply of @admin.
Have a great day.
Regards,
Phil
PS: Thank you for the reputation point. We are all volunteers here, so they are greatly appreciated when we do help someone and they acknowledge it. 👍
That makes perfect sense thanks for the explanation, machine code was a little vague I was just thinking about possible HW-IDs as I have not really checked the about section of the app. The only time I tend to check that section is to find a check for update feature. As Hasleo auto updates and has the check for updates in the drop down box I can't say I’ve felt the need to check about. I did however go through the setting looking for it before posting.
Unlike Mac computers, most personal PCs do not provide a globally unique machine code in their BIOS. Hasleo's machine code is an identifier generated from the current computer's hardware information (including the CPU, MAC address, etc.), so hardware changes may cause the machine code to change. The program already makes every effort to ensure that the license remains activated after hardware changes, but in some cases the license may still become invalid, in which case you will need to contact us to reset the license.
For personal users, we do not impose overly strict restrictions on licenses. After all, purchasing a license is already a great support for Hasleo; we would rather focus our revenue on commercial licensing, even though this is not easy.
If you encounter activation failure due to a machine code change, please contact us at [email protected] and provide your order number or license key.
(11-04-2026, 02:08 PM)TroubledSoul Wrote: Thank you for the responses, after being burned by various backup and password managers to name a few over the past 20/30 years I am somewhat sceptical when it comes to the promises of lifetime licences, these are more often than not, at least in my experience paywalled by additional features and eventually made inoperable all together once the name is established and bought out by private entities the milk the product for all its worth then burning the project down.
Lifetime licences come with there own problems when it comes to sustainable funding as it requires new users to be consistently signing up and purchasing. I'm am not a massive fan of subscription models at all and will actively avoid products that only use that payment model. Maybe its why I’ve been burnt so many times and sceptical, when it comes down to the initial payment.
I appreciate the clarification regarding honouring lifetime licences if you ever went down the subscription route. That went a long way into my decision to buy the family plan just now, I sincerely hope that is the case.
I completely understand your concerns. You are right that lifetime licenses inherently face sustainability challenges: unless a product can continuously attract new users, a one-time payment may not be able to support development forever. For Hasleo, we try to balance this through relatively low product pricing, continued development, and commercial licensing revenue. We cannot predict the future, nor can we promise that any company will exist forever, but I can tell you that we will honor our commitment to the lifetime licenses users have already purchased. If in the future we have to adjust our licensing model, lifetime licenses already purchased will remain usable in the manner we previously described, rather than being silently disabled.
From another perspective, Hasleo's current pricing is already low enough, because at most you only need to pay the equivalent of two years' subscription fee to obtain a lifetime license with free upgrades. In other words, you break even in about two years, and any use beyond that is a bonus.
11-05-2026, 03:30 PM (This post was last modified: 11-05-2026, 05:13 PM by Froggie. Edited 2 times in total.)
Just a mention... don't know what happened. Was doing some testing and decided to RESTORE to an OS partition image about 40-min old. Restore went well after reBOOTing into the Emergency Media. Upon reBOOTing into the restored System, first indication of an issue came from my VPN (Proton) about the System clock being out of sync. A quick look at the time (EST) showed my clock an hour earlier than where it should be (if some sort of DST/STD issue was at play <delayed by 4-days> it would be an hour later than it was).
I reset the clock and things seem fine... have no idea what happened.
I can try it again if you wish...
An additional DataPoint... because the image time and the real time were close to an hour apart, I thought that maybe the restoration was actually restoring the time of the image (have never seen such a thing before)... not happening. The time after the restore is exactly 1-hr earlier than the real time of the restoration itself
Last DataPoint... makes no difference whether I do an OS partition restoration or a FULL Disk restoration.
Edit: the System is a 10th gen i7 with 16gB of RAM running W10 Ent IoT LTSC.
...and lastest most final DataPoint ... this does not happen under v5.9.2.4 restoring the same image.
Thank you very much for such detailed testing and clear feedback.
Hasleo Backup Suite itself does not actively change the system time. The time offset after restoration should originate from how WinPE (or the restored Windows) handles the BIOS clock during Daylight Saving Time (DST).
This phenomenon is not unique to Hasleo, and it is a known architectural limitation of all WinPE-based recovery environments. In the official communities of Macrium Reflect and Acronis, there are numerous user reports of almost exactly the same issue:
At present, the effective solution for this issue is to "rebuild the WinPE environment." We will also investigate whether this can be addressed at the code level.
Understanding Computer IDs: The Complete Guide
![[Image: confused.gif]](https://www.easyuefi.com/forums/images/smilies/confused.gif)
![[Image: rolleyes.gif]](https://www.easyuefi.com/forums/images/smilies/rolleyes.gif)
![[Image: biggrin.gif]](https://www.easyuefi.com/forums/images/smilies/biggrin.gif)
... this does not happen under v5.9.2.4 restoring the same image.
Restoring partition sets my BIOS clock ahead one hour
Restore via Windows PE (standalone restore)
Untitled