I was unable to reproduce this locally, but a licensee reported having trouble creating a local installed build of the Engine with only Visual Studio 2017 installed. The licensee reported that the StripSymbols function in WinPlatform.Automation.cs looks for the VS 2015 MSBuild version of PDBCopy.exe, and if it can't find the file, it then looks for the VS 2013 version of that file. If neither one of those exist, the build will fail.
This was reported in relation to version 4.17.2, but the code in WinPlatform.Automation.cs appears to be the same in 4.18 and 4.19.
As described in post.
I don't think this bug is worth testing; the repro is long and convoluted, and I'm pretty confident of the fix.
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-51362 in the post.