@Jim1cor13 This system has no secure boot, TPM, or supported CPU. It didn't have the stated issue on Win 10. Win 11 on this system is a clean install. Since installing Win 11, any bootable USB or boot menu gets stuck on the Windows logo, with the loading circle either spinning or stopping after a few secs. No issue with Windows normal booting.
No secure boot, that is good I think, but have you set your BIOS properly? I assume it is UEFI and GPT disk, do you have legacy mode enabled or disabled for booting USB? In other words, for instance, in my BIOS on my Dell Optiplex 9020, I use UEFI, no secure boot, no legacy it is UEFI non-csm booting. It will only boot a UEFI GPT device, no MBR or legacy devices. It will only boot UEFI supported device. So you are saying your machine does not have supported TPM or CPU for Win 11? I don't use TPM personally, but I run Win 10 Pro. You did a clean install of Win 11, it installed ok did not complain about any hardware issues right? Not sure why your WinPE Hasleo does not boot, especially since you downloaded the WinPE components like I did, that solved my USB flash drive boot errors. Perhaps check your BIOS setting as mentioned, but the success when you tilt or shake the system I suspect is something hardware related, perhaps memory or power supply? I really have no idea.
@Jim1cor13 I installed Win 11 with Rufus-created bootable USB for an unsupported system with no errors or warnings. The BIOS mode is set to UEFI. I'll test reseating RAM. Anyway, this system is old and has problems, and I'll replace it, hopefully soon. Many thanks for your help and time!
@khanyash - from my best understanding, an OFFICIAL Windows 11 ISO from MicroSloth does not allow a clean install on any System without TPM v2 active, Secure BOOT enabled, and 8th gen or higher CPU available. There are many "modified" ISOs in the wild that have attempted to disable those requirements but in that process, MicroSloth has gotten tighter with its normal ongoing update requirements and has disabled some of its ongoing updates for those Systems. If that's the case, you may be a victim of these shenanigans if you're using a modified Windows 11 ISO for your builds. ...and then again, you're hardware may really be flakey Just some food for thought...
The merging forward for the backup chain went well (using my 7-day requirement for Incremental images). Tomorrow, after (2) forward merging events, I'll test restorations for all the images (the original FULL, the interim DIFF and the merged forward INCs)... wish me luck
Great to hear the success up to this point @TheRollbackFrog Looking forward to hearing how the restore tests go. Thanks again for all of your testing!
Probably not a good thing for an unsupported machine. No idea of the side effects of Win 11 with a system that does not support the features and as Froggie mentioned, MS will only get more tighter with their demands especially with no TPM and secure boot. Quite possibly part of the reason for the oddities, not to mention possible hardware issues likely not operating as required for Win 11. Just my thoughts @khanyash I know there were some scripts available to get Win 11 to ignore certain requirements, such as no TPM 2.0 check, etc. At some point those installed in such manner will gradually cease to function properly and cause issues. I have no idea if these things would affect your booting issues, hard to tell with an install to an unsupported system as to the side effects.
Microsoft let you create some registry keys, in order to upgrade to Windows 11 on unsupported hardware. You can do so using the official ISO. You can create these keys easily using AveYo MediaCreationTool. https://github.com/AveYo/MediaCreationTool.bat Doing a clean install requires some changes made to ISO, which can be done using Rufus, or the above mentioned batch files. On unsupported hardware, you get all the regular Windows Updates, but you have to manually upgrade to new builds of Windows 11. On some systems you will get a watermark on your desktop saying that Windows is running on unsupported hardware. But that has not happened in my case. Windows 11 does not need a 8th gen CPU, TPM 2.0 or any of the other new requirements to run. Pretty much any computer with a 64 bit CPU that can run Windows 10, can run Windows 11 too. Microsoft have just decided to limit what computers you can install it on, for better security and stability. But these are just limitations put in place by the installer. Windows 11 itself does not have any of these requirements, so mostly will run well on unsupported hardware. For example, I installed in a 17 year old Core 2 Duo laptop with 2GB of DDR2 RAM and it ran fine.
I use the official ISO from MS to create a bootable USB with Rufus for both supported and unsupported systems. I don't experience this problem on an unsupported system that only lacks the supported CPU requirement. I tested EaseUS on my system and had the same outcome. The problem might be because of the absence of secure boot or TPM on my system. Windows 10 worked well on this system.
From the FWIW dept... I recently obtained a "PC on a Stick" to play with (plug it into the back of any HDMI monitor/TV port and you have a computer). It's a Celeron-based (J4025 <4-core 2ghz-3.5ghz>) machine with 8gB of RAM and 128gB SSD. The HBS suite issued an error when trying to image my final configuration. Sent a configuration/error msg and the LOGs to them last night, woke up this morning and a fix was in my InBox... great service I call that
They sent me an explanation for the failure I received, apparently something broke when they added some features. If you're interested, the repaired BETA is available via their post HERE.
That's great & responsible support. As well as rapid! Anyone else besides myself using Hasleo Backup Suite on Windows 8.1? Maybe even Windows7?
OK, using a 9-day old image chain with 1-FULL, 1-DIFF and 7-INCs (2-days of INCs were merged forward due to my 7-day INC GFS spec), I restored the image to each of the 7-days, also to the DIFF and to the original FULL. All restorations returned the System to the state it was in when imaged at that time... I would say very impressive but I'm not, it's what was expected. What was not expected was the time to do these full image restorations (remember, Hasleo is not a DELTA <difference> restoration imaging application)... they were very fast. This process was much slower a while back so some changes have been made along the way which I'm sure not aware of. Using a NvME to NvME restoration process, the time for Hasleo to do a full restore of 104gB (5-partitions) was 1-min, 21-sec. I then tested that op against the same Macrium REFLECT RDR (delta restore) which had a delta of about 350mB and the Reflect restore took 58-sec... that is pretty damn impressive for a full restore operation comparison. At this point, HBS has become a somewhat robust application in most areas... imaging, restoration, scheduling & retention. The Devs are still tweaking the software (that's what caused my temporary problem mentioned in a previous post), but at this point I would have to give a big to this application, and currently it significantly outshines any other FREE imaging software I have ever played with. I hope they keep up the great work...
@TheRollbackFrog - I don't have an SSD system. Recently, I visited a friend and installed Hasleo on his SSD laptop. I was impressed with the SSD and Hasleo performance. His system partition was 44.5 / 150 GB full. Hasleo took over a minute for a full backup and did incrementals and restores in under a minute. Indeed, great work, Hasleo!
A little more perspective on Post #663 above... With this new noticeable knowledge about restoration speeds between Macrium REFLECT and HBS, I decided to run a quick apples to apples (above comparison was really not proper) test between Hasleo and Reflect. Using the same disk image of appx. 104gB, and creating a current DIFF of a 12-day old FULL, I ran a simple non-Delta (disabled RDR in Reflect) restoration comparison of both apps using only their FULLs and the current DIFF. Macrium REFLECT = 7-min, 37-sec... Hasleo = 1-min, 17-sec. Clearly Hasleo has implemented a very speedy robust input/output pipe between the source and target disks during restoration... limited to disk speeds of course. I remain very impressed...
I think compared to most imaging apps, this speed is extremely competitive and blows away most when tested using standard restores, not Delta, etc. I am definitely impressed. Thank you Froggie for taking the time to test these features. Do you think the latest version they put up to take care of your data issue when trying to restore is stable enough to upgrade to? One of the things that also impresses me is the speed at which they provided you a solution for your problem you found. That is really some great support.
The change for my issue was made in their v4 BETA (the one with their new GFS capability). As soon as their beta makes it through their regression testing, it'll be released as their public v4. I am using their beta full time without issue. Their fix for me was due to a very specialized hardware configuration and a small change they made to the app that really didn't affect normal hardware users. If you're using HBS as your primary imaging solution, I would wait for their public release of v4.
Delta restore is now available! HERE "The delta restore has a faster restore speed than the traditional full restore because it restores only the changed blocks on the disk. This benefits from advanced delta detection technology, which enables Hasleo Backup Suite to quickly and efficiently check for changed blocks on disk." "The delta restore is currently only available when restoring the Windows operating system or a partition to its original location."
But, how to use it?! One can delay up to minutes which seems to defeat the purpose with "faster restore".
It seems you are confusing the new scheduling option under settings for delta restore. This option is for delaying the missed scheduled backup instead of starting it immediately after system startup. The new feature "Delta restore" is available when you perform a restore. You can check or enable it to perform delta restore (instead of normal or full restore). "Delay" restore was a typo from the team. It's "Delta" restore. I changed it in my previous post.
This new DELTA RESTORE feature may have been at play when I was doing my testing above with BETA #1. I just did some brief testing with Beta #2 and found no difference between DELTA and non-DELTA mode (after wiping the partition with ZEROs) as far as speed is concerned. BUT, the test was run on SOURCE and TARGET devices that are NvME SSDs, each running over 3gB/sec in speed. I have some questions in to the developers on this. Anyway, this new feature seems to be the exact approach MACRIUM Reflect took when developing their RDR (Rapid Delta Restore) feature... the approach is the same although I don't know what the mechanisms are. It would be nice if some HDD-based users could try out the feature and comment here in the thread. The feature is automatically invoked when returning a System/Disk or Partition image to its original disk only. @khanyash - I found no place to "check or enable" this feature (could be me, it's early here)... it looks automatic when returning and image to its original disk (and its geometry).
I tested it. A delta restore took approximately 13% of the time compared to a normal restore on my HDD system. Great job, Hasleo!
