Using 'Inject variables as a build step', either through 'Properties File Path' or 'Properties Content', resets the system Path for subsequent build steps.
Printing out the env before using this step matches the slave's system path variable, but after injecting variables as a build step, the new env printed shows a different path value, unsure where this new value is being set from, i couldn't map it to anything in our env, yet. The new path ofcourse messes with build environment.