Yes ofcourse, but it's the same as when you release a new version of Hard_Configurator (good tool, by the way). For example, v3 will be different than v4 but all v4 executables will have the same code (with the difference that autoit not compile to machine code - native code -).
Yes, it may seem complicated, but it is because of the way in which things are explained in the MS documentation. In a simple way this is:
If you write an app in .NET which need to connect to a web server, you need to use "System.Net.dll", "System.Net.Http.dll" assembly and probably also "System.Web.dll". These 3 assemblies will refer to anothers (for example, "System.Web.dll" reference to/use "System.dll" and "mscorlib.dll"), so your app need multiple assemblies. The same applies to native images.
This means that if you write a software, depending on the "target framework" ( .NET v4, v4.5) for example, it will use the corresponding assembly versions.
Yes, native imges may be updated (recompiled) if you made changes in your software / system configuration, but the code generated will be the same (if the target framework is the same).
In short, as I said in the previous post, the machine code generated from a certain source code, only depends on the processor. For equal processors, the resulting code (native images in this case) will be the same.
I hope I have explained clearly. Regards