Injector v1.1
Being that this is my first injector, I have made it nice to look at without compromising it's performance. The instructions are relatively simple, so please read them before asking a question.
Instructions
Download Information
I have attached the Injector as an Installer package and also as a plain zip package. Each package contains 4 files which all must be in the same directory. The .dll extension files are by a company named DevExpress. Information about them can be found here: DevExpress
Virus Scan Information
Both packages are clean but do come up with false positives. I am currently unsure why the assembly comes up with these false positives but my best guess is that it is because the nature of an injector is usually malicious. (i.e. Injecting viruses into system files.)
MD5: 851ce434666f7abd7508e21c3776adfd
SHA1: 2423751d4fbcc6cc2d2070d338b1c99fc553f8f6
SHA256: 64f53394ae2b45f8371eb1d713c191bedf1cac97fb630dc9b0 0605930e1b81f2
Total Filesize: 4139298
Injector v1.1.ZIP - VirusTotal.com
Injector v1.1.ZIP - VirSCAN.org
Screenshot

Requirements
.NET 4.0 Framework (by Microsoft)
FAQ
Q. The injector will not open.
A. Please be sure you have installed the .NET 4.0 Framework (by Microsoft) and then try opening.
Q. The injector does not inject properly.
A. Ensure you are running the injector as administrator by right clicking the file and clicking "Run as Administrator". If you have disabled UAC, I am unsure if the injector would work on your machine.
A2. Ensure the .dll files you are using are not patched or out of date. Try using an alternate injector to rule out if it is the .dll files or the injector itself.
Q. None of these FAQs answered my question? What do I do now?
A. You can feel free to message me or comment to this thread. Be sure to be as descriptive as possible regarding the problem and give system information such as Operating System, RAM, x32 or x64 bit, and other relevant information towards your problem. This will allow me to answer you quickly.
Update Log
v1.1
Next Update:
Expecting to add functions to auto remember dlls and automatically add dlls if they are in the same directory as the Injector.
And Lastly...
If you are kind, please use the "thanks" button if this Injector has helped you.
Feel free to donate:

@Nico



Instructions
- Run "Injector.exe" as administrator.
- In the "Target Process" field, type in the process name without the ".exe".
- Click the "..." browse button to add a .dll file. Repeat this step for every .dll file you want to inject. V1.1 now supports multiselect!
- Choose either "Auto Inject" or "Manual Inject". I recommend using manual as it works 100% of the time.
- (For Manual Inject only) Click the Inject button when you are ready to inject the .dll's into the process. For Nexon games, this is when the HackShield updater (at the bottom right) shows
Download Information
I have attached the Injector as an Installer package and also as a plain zip package. Each package contains 4 files which all must be in the same directory. The .dll extension files are by a company named DevExpress. Information about them can be found here: DevExpress
Virus Scan Information
Both packages are clean but do come up with false positives. I am currently unsure why the assembly comes up with these false positives but my best guess is that it is because the nature of an injector is usually malicious. (i.e. Injecting viruses into system files.)
Virus Scans
MD5: 851ce434666f7abd7508e21c3776adfd
SHA1: 2423751d4fbcc6cc2d2070d338b1c99fc553f8f6
SHA256: 64f53394ae2b45f8371eb1d713c191bedf1cac97fb630dc9b0 0605930e1b81f2
Total Filesize: 4139298
Injector v1.1.ZIP - VirusTotal.com
Injector v1.1.ZIP - VirSCAN.org
Screenshot

Requirements
.NET 4.0 Framework (by Microsoft)
FAQ
Q. The injector will not open.
A. Please be sure you have installed the .NET 4.0 Framework (by Microsoft) and then try opening.
Q. The injector does not inject properly.
A. Ensure you are running the injector as administrator by right clicking the file and clicking "Run as Administrator". If you have disabled UAC, I am unsure if the injector would work on your machine.
A2. Ensure the .dll files you are using are not patched or out of date. Try using an alternate injector to rule out if it is the .dll files or the injector itself.
Q. None of these FAQs answered my question? What do I do now?
A. You can feel free to message me or comment to this thread. Be sure to be as descriptive as possible regarding the problem and give system information such as Operating System, RAM, x32 or x64 bit, and other relevant information towards your problem. This will allow me to answer you quickly.
Update Log
v1.1
- Added function to remember last process that was injected.
- Added multiselect feature when browsing for dlls
- Fixed bug where "Close on Inject" would not save the setting on Injector's next run.
Next Update:
Expecting to add functions to auto remember dlls and automatically add dlls if they are in the same directory as the Injector.
And Lastly...
If you are kind, please use the "thanks" button if this Injector has helped you.
Feel free to donate:
@Nico



I have no problem with selecting though lol, just thought it was interesting.