Very slow VS2017 C++ linker speed - c++

Question

We're upgrading our C++ projects from VS2013 to VS2017. But in VS2017 we have very bad linking times also for Debug builds. With such values, it's not possible to do effective development.
When I change the single file in our project, in VS2013 it takes 2.6sec. When I do the same with the same file in VS2017 it takes 30sec.
VS2013
1> 32 ms ComputeCLOutputs 1 calls
1> 199 ms WarnCompileDuplicatedFilename 1 calls
1> 2688 ms Link 1 calls
1> 4073 ms ClCompile 1 calls
VS2017
1> 31 ms ComputeCLOutputs 1 calls
1> 44 ms CustomBuild 1 calls
1> 239 ms WarnCompileDuplicatedFilename 1 calls
1> 8021 ms ClCompile 1 calls
1> 29725 ms Link 1 calls
This is more than 15x slower than in VS2013.
Currently, I have both Visual Studios installed on my PC so I can test it side-by-side. I tried a lot of things as same as a lot of googling but without success.
I tried:
compile the same project in VS2017 but with VS2013 toolset and linking takes 2.6sec. So the problem is with toolset in VS2017 not with VS2017 IDE.
I tried a lot of combinations with DebugInformationFormat like /Zi and /Z7, as same as /DEBUG vs /DEBUG:Fastlink, /INCREMENTAL,... but any other settings is even worse than default one generated by QMake (/Zi + /DEBUG:Fastlink + /INCREMENTAL).
I also tried 32bit and 64bit compiler/linker as same as 32/64bit target. But it doesn't have any impact on performance.
I tried to convert VS2013 project to VS2017 as same as generating new one via Qt Qmake but also without any differences.
During link time CPU isn't used at 100% as same as SSD drive isn't utilized at 100%. I tried to output verbose linking log but there isn't anything special (no foreign temporary files, etc. like mentioned in other answers).
This is complete compiler command line
/Yu"stdafx.h" /MP /GS /analyze- /W3 /wd"4577" /wd"4467" /Zc:wchar_t /I ...INCLUDE FOLDERS... /Zi /Gm- /Od /Fd"objs\Debug32\" /FI"stdafx.h" /fp:precise
/D "_WINDOWS" /D "UNICODE" /D "WIN32" /errorReport:prompt /WX- /Zc:forScope /Gd /Oy- /MDd /Fa"objs\Debug32\" /EHsc /nologo /Fo"objs\Debug32\"
/Fp"Debug32\\App.pch" /diagnostics:classic
-Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew -Zc:referenceBinding -Zm130 -w44996 -w34100 -w34189 -w44996 -w44456 -w44457 -w44458
And linker command line
/OUT:"Debug32\\App.exe" /MANIFEST /NXCOMPAT /PDB:"Debug32\App.pdb" /DYNAMICBASE "Q:\SharedLibraries2017\Qt32\lib\qtmaind.lib" "shell32.lib" ...
/VERSION:"1.0" /DEBUG /MACHINE:X86 /SAFESEH /INCREMENTAL /PGD:"Debug32\App.pgd" /SUBSYSTEM:WINDOWS /MANIFESTUAC:"level='asInvoker' uiAccess='false'"
/ManifestFile:"_App\objs\Debug32\App.exe.intermediate.manifest" /ERRORREPORT:PROMPT /NOLOGO /LIBPATH:"Q:\SharedLibraries2017\Qt32\lib" /TLBID:1
"/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'"
I found few some posts about slow linking but nothing helped for me (64bit, erasing temporary files, turning of synchro/sourcurce control/codelens/diagnostic, clean build in new folders, ... ).
I'm using latest VS2017 version 15.5.6, toolset v141, SDK 10.0.16299.0
Any help will be appreciated.
Added:
My PC setup is:
i7-7700K CPU # 4.2Ghz
16GB Ram
SSD Drive
Latest Win10
Edited:
I tried another (smaller) project.
When I do complete rebuild, I got these results:
VS2013:
1> 2898 ms Link 1 calls
1> 11987 ms CustomBuild 1 calls
1> 68238 ms ClCompile 1 calls
VS2017
1> 2822 ms Link 1 calls
1> 14221 ms CustomBuild 1 calls
1> 67243 ms ClCompile 1 calls
So almost identical results. But, when I change for example main.cpp in both projects and do compilation+link, I got this:
VS2013:
1> 577 ms Link 1 calls
1> 1261 ms ClCompile 1 calls
VS2017
1> 1196 ms ClCompile 1 calls
1> 3145 ms Link 1 calls
So, the problem seems to be that no mather how many files are linked together, in VS2017 the time is still the same.
Edit2:
Based on #seccur idea I installed also VS2015 toolkit
Again, two same projects, both fully compiled & linked and in both I moddified main.cpp file.
VS2015 (2015 v140)
1> 64 ms WarnCompileDuplicatedFilename 1 calls
1> 594 ms Link 1 calls
1> 1312 ms ClCompile 1 calls
VS2017 (2017 v141)
1> 43 ms WarnCompileDuplicatedFilename 1 calls
1> 754 ms ClCompile 1 calls
1> 2082 ms Link 1 calls
Both projects opened in VS2017 IDE, both with same settings, the only difference is toolkit selection. It's more than clear that v141 toolkit is completely bugged.