Why do you have these strange relative paths to the libraries? Actually why do you have paths to libraries at all? Usually you just specify search directories and add libraries by name only. Also you link runtime libraries explicit, this should be wrong, at least for the basic libraries, not sure about WinRT and the like. The compiler picks the proper ones itself depending on the used switches, e.g. /MT or /MD.

Why do you have these strange relative paths to the libraries? Actually why do you have paths to libraries at all? Usually you just specify search directories and add libraries by name only. Also you link runtime libraries explicit, this should be wrong, at least for the basic libraries, not sure about WinRT and the like. The compiler picks the proper ones itself depending on the used switches, e.g. /MT or /MD.

You have to differentiate between two types of compiler configuration, the global one and the project specifc one. In the global configuration i put everything that is required to build for a specific target environment, in the project one (which are multiple in fact) i put everything required for the specific project configuration, in my case its Debug and Release.

I dont have Visual Studio 2017 and i dont build for x64, i have Visual Studio 2015 and i build for x32 with the Windows XP toolkit, so my paths are different than yours and i need some extra settings, but this should outline the steps anyway.

This is enough to build simple Hello World console applications. Depending on your project you need to add additional search directories for the compiler and linker and add your libraries to link with, but you only add them by name, e.g. you add under Link libraries kernel32 and uuid without path, they are searched for in the paths you defined in the Global Configuration.