defender-control VS x64dbg

Your way did not remove it if it's still running. Defender is a light weight anti-virus why would you want to remove it? It can be disabled with this but I don't recommend doing so unless the computer is only used offline.

Use this to disable it-- https://github.com/qtkite/defender-control

You can disable defender completely from the registry. This GitHub repo works well with Windows 10. https://github.com/qtkite/defender-control

I most definitely would not choose to use a precompiled executable from a shady looking site like that over a GitHub project where you can see, download and edit the code if ever desired. I would definitely rather choose this any day: https://github.com/qtkite/defender-control

Some people are telling you to get an SSD. Yeah, that's cool, but what if you don't want to, can't, etc.? Therefore this is the solution with what you have: disable everything that doesn't serve a purpose. Uninstall all you can. I've had this problem on and off for a year and I've finally fixed it, use these: You need to disable, mainly, three things: Windows Defender and all its secondary stuff (Antimalware Service, etc.). Use this: https://github.com/qtKite/defender-control (disable all you can manually first). Windows Updates: try this: https://github.com/WereDev/Wu10Man if it doesn't work try this: https://www.wintips.org/how-to-turn-off-windows-10-updates-permanently/. Unnecessary Windows Services (look for a list of those in some search engine, you'll get around 20 that are practically useless for everyone). Then, also: Debloat with this: https://github.com/builtbybel/bloatbox (everything you can, Microsoft Store, XBox, all that nonsense, many of those you can uninstall manually). Disable Cortana, Windows Search, all that nonsense.

I have never heard anyone say anything good about the Visual Studio debugger before. Now, I'm not a Windows person but I'm not gonna argue for gdb or lldb here. RemedyBG and x64dbg are the two debuggers I've heard good things about though I've never used them because, again, not a Windows person.

[1] https://remedybg.handmade.network/

[2] https://x64dbg.com/

I'd help you out but because of circumstances I have no laptop with me. You need x86/x64 debugger to do this. This one for example Find a registration procedure and look for possible brenching to other parts of code in assembly. It's probably somewhere in the beginning. Exclude code validation and export new program version.

One interesting thing you can do is download an app like https://x64dbg.com/ or cheat engine, which will let you see the memory. You can look at the process for something you’ve made and explore it. Log a memory address from your app then go find it in the tool and interpret the bytes as an integer. Find a string and see how that works. Find a pointer, read the address it’s pointing then go look at that address. You start to see how different containers store data. I find it fascinating.

If you want to also do dynamic analysis (debugging) you can use https://x64dbg.com.

close origin and download this debugger https://github.com/x64dbg/x64dbg/releases

.exe is a complex format and not something you're going to extract raw instructions from using a hexdump. What you need is a "disassembler". For Windows I'd recommend x64dbg.

Patch the DayZServer_x64.exe, change "test al, al" to "cmp al, 2". i used x64dbg (https://x64dbg.com) a good video for the whole process: https://drive.google.com/file/d/1F1A0lpumREPXtVeoTMq1HiEnvaZp-NUU/view