The only fully general answer to this question is to write the exact same program yourself but leave out the copy protection. This always works, and technically answers the question. We’ll call this method #1. I call this the “method that requires you to not be lazy.” It is clearly inappropriate.

So let’s talk about method #2, which is usually called “cracking.” Most of the time, you will need to have access to an already-working copy of the software so you can see what is supposed to happen; this might mean you have to buy it. It might be possible without buying it first, but it is much harder.

Firstly, it is important that you understand how computer programs actually work. I don’t mean knowing how to write Java, or Python, or even C. That is knowing how to make a program. Most programmers have a pretty vague understanding of what happens to execute the program after they are done writing it, and that is the area where you have to become an expert.

Eventually, all programs are running machine code, and you need to learn machine code. Consider learning x86 Assembly, at least well enough to write some trivial examples and to read machine code and know what it’s doing. Learn about interrupts, registers, call stacks, conditional jumps, memory layout, memory mapped hardware access, and tracing running binaries.

Next, you need the ability to interrupt, read, and modify a running program; such a tool is called a debugger, because of its intended use. Windbg is the main one that Microsoft uses for debugging their operating system, and it’s free. These days, more elaborate copy protection might try to defeat you by detecting the presence of a debugger, but that just makes it harder, not impossible.

Ultimately, your goal is to skip or modify the piece of the software that’s designed to keep you from using it for free, while leaving all the other bits working. This is surprisingly difficult; some years ago, we heard from a user on our forum who was having problems with our software. It was a very strange bug. It eventually turned out that he had pirated it, but the pirate had done a very bad job and had broken some important things. We suggested he fix the problem by, y’know, purchasing the software maybe? It was a bit baffling, because our copy protection was lame and easy to circumvent, yet somehow the pirate managed to screw it up. You do have to admire the sheer chutzpah of someone trying to get tech support for a pirated version, though.

Unfortunately for you, a lot of modern software has been abandoning local copy protection in favor of putting part of the program on a remote server. Unless you can steal that remote software somehow (difficult/dangerous/may require leaving basement), you are going to have to figure out what it’s doing and emulate that part yourself, from scratch (see method #1). They are betting that will take a while, which is why such software takes so long to crack. If you do try and reverse engineer the online portion, you will need to look up Wireshark, a tool for monitoring network traffic, and learn how to use it.

Of course, given all that work you just did to become an expert on the internals of the computer, you might now be employable writing low-level software, such as device drivers, virus scanners, security monitors, copy protection, debuggers, etc. Such jobs are usually well-paid, which leads to method #3: Just buy the frickin’ software. Seriously.