It seems pretty spot on to me: there is a good flow in your design which is all you need for this type of design, tho it can be worked upon.
Usually what you want is to have an invisible line that shows the path your average user will take when using your program:
First, i'll look into the info panel on the top left. This is perfect, nothing to change.
Then i'll look into the advanced settings, this isn't perfect but acceptable as i may want to check the "basic" settings first.
This isn't always true tho, as i may know before hand things like the injection method.
Next, i'll take a look into the settings, which is fine.
And lastly, i have the choice to inject, pick a target and pick a library. This could be improved by having the library and target option next to their text fields, with the inject option last.
To improve the design i would:
Keep the information panels at the top.
Put the two settings (library and target) in the middle, with a button near each one which allows me to load the file's path / process name.
Then, advanced options and inject button.
As of now, the design is perfectly fine and no user would complain about it tho. If moving stuff around and resizing more than half the components sounds like a pain in the butt to you, then you shouldn't feel bad for not changing the layout. =)