no, this is not how it works
AHK_H contains a set of anti-debugging techniques that stop your program from starting/working if it spots itself under debugging.
But as we can see, some of these techniques are screwing up after Windows has been updated.
The impression is being given that you are more interested in AutoHotkey_H's anti-debugging for unknown reasons, in the guise of having a problem running it on Windows 10.
You haven't proven the case that AutoHotkey_H's anti-debugger is causing the claimed problem with the new Windows 10 update. This claim that you are making individually, isn't supported by nor reported by other users, so far. Why haven't other users on this forum complained about not being able to run AutoHotkey_H on Windows 10?
Just saying that "some users" have problems running your programs on Windows 10, doesn't mean the problem is with AutoHotkey_H, as it can be specific to the code of your program. You also haven't given any sample code in which you think might be causing the problem. In fact, you condemned AutoHotkey as a dying language in which you no longer support.
As you gave no sample code for anybody to look at, I referred to the compile and the MD vs MT issues, because that's where many people using AutoHotkey_H have got stuck. Just some possible suggestions, didn't say they were definitive solutions. But as far as suggestions go, don't see why you haven't done the below:
. Compile your program with the latest AutoHotkey_L instead of AutoHotkey_H, since you feel its anti-debugger is in your way.
Note- It's not clear what features that your software is using in AutoHotkey_H, that is not in AutoHotkey_L that your program needs. If it's just the anti-debugger, then using AutoHotkey_L will be fine.
. If you feel AutoHotkey is a dying language not worthy of your support, why not rewrite the program in the other language that you know, then have your users use that version. Personally, that's what I would do.