Sorry you had to learn the hard way, like I did, but value-tier USB scopes are reliably garbage. Hantek is the worst offender. You are guaranteed to spend more time fighting drivers and software than making measurements, and if you do by some chance get it working then the next system update or Hantek update will reset your progress. If you've made any -- the software is buggy, limited, and poorly designed even if you do get it working. To get my old hantek to work, I needed to:
* Discover that "Win XP SP2" requirement meant "Not XP SP1, not XP SP3, and certainly not Win7 or emulation mode"
* Give up on using it from a VM
* Edit the binary to patch references to debug DLLs to point at the non-debug DLLs they actually deployed with the application
* Yes, that means they didn't test it. Yes, I told them. No, they didn't reply. As far as I know, the latest software for my model of hantek is still the broken one with the wrong DLLs.
...and once I got it "working" it had extremely bad (20LSB or so) 10MHz leakage into one channel and triggers were about 100mV off the displayed level.
Return the USB scope if you can. If you're past the return period, like I was, write it off. Don't throw good time/money after bad, like I did. If you're going to buy a cheap scope, it needs to be a standalone. That's the general wisdom on this subject and I wish I'd listened. $60 is nothing in the world of test equipment, and if you make it any distance down the EE path this writeoff will be a tiny fraction of your total equipment spend in no time. It's not too late to save yourself.