In ultra-short summary, I'd distrust Easeus Partition Manager (EPM). See the last two paragraphs for the most relevant part. The computer is very old (no UEFI), with HDD, it currently has Windows 7. Up to v16.0 EPM works well, higher versions don't.
Maybe I can trust the EPM partition recovery feature (specially after seeing it working here) b/c looking for a deleted partition table does only have one correct result (if achieved), say a partition that goes from sector 200,000,000 to sector 500,000,000 ("provided that nothing has been overwritten" what's HDDs logic, not SSDs logic but I'm greatly ignorant about the latter so well, it has worked, it may work yes specially if you don't use the SSD a lot in between, no idea if it should work maybe modern SSDs firmware is partitions aware Idk).
But I'm not trusting EPM versions 16.5 and higher (I trust up to v16.0 included) at doing or resizing partitions.
I have an old Easeus Partition Manager perpetual license in an old desktop with a RAID 0 of HDDs as only internal disk. It's MBR among other reasons b/c the mobo doesn't have UEFI. Windows 7 upgraded from Vista quite after EPM v16.0.
I consider I've got much from this license. And the product is still usable, provided I use v16.0 or lower as summarized. I'm not complaining or anything. I'm describing, a bit imprecisely b/c I don't do say 8 works with internal disk partitions every day or week or month or even software version. Let alone having to manage/fix frequent failures. I use partition managers very sparsely and 100% of the times they work as they should.
Since detecting my (Idk if only "my") issues with version 16.5 and higher, I'm lazy trying newer versions, although I've tried them 3 or 4 times and they look worse in every attempt. In the latter one in April 2025, the version tried 19.6 did not show any info about what the result of my queued actions would be.
I only do an elementary test with partitions managers that doesn't involve actual partition changes. I leave 500 or 1000 MB unallocated at the beginning of the 2nd partition, and extend the first partition to use it. I check with a calculator that the partitions begin/end sectors are divisible by 2048 (correct alignment to MB), if not I try 16065 (correct alignment to cylinder), check gaps and such. I don't launch these operations, I undo them and exit.
v16.5 and all higher ones tried except the latest one tried v19.6, don't allow to precisely set a whole amount of MB except in small partitions, instead they set GB as the unit although the user can set up to 2 decimal places (e.g. 78.23 GB), what gives a kind of "imprecise resolution" or 10 MB. The result, as reported by the "properties" or similar dialog (absent or I couldn't find it in v19.6), isn't correctly aligned to MB (nor to cylinder).
In my latter two attempts (v16.5 doesn't belong here, it has the aforementioned problems but not these) I got the same kind of "strange installation" of EPM. Browsing C:\Program Files (x86)\EaseUS\EaseUS Partition Master\..... had 4 MB or less visible but the C: partition free space had decreased by about 1 GB (I use to watch closely the free space of this partition b/c I like the Windows partitions in HDDs to be small for performance reasons). This partition was already sentenced to be restored with a recent Macrium image (what was flawless), but I still uninstalled EPM to research about the disk occupation, what recovered 800 or 900 MB.
After reading the OP, I'm wondering if the latter did prevent a major disk/partitions problem...
