I was getting the following error while building on my personal Windows machine, which I've build Chrome on in the past without issue:

[1/2831] LINK genmacro.exe genmacro.exe.pdb
FAILED: genmacro.exe genmacro.exe.pdb
C:/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe ../../build/toolchain/win/tool_wrapper.py link-wrapper environment.x64 False link.exe /nologo /OUT:./genmacro.exe /PDB:./genmacro.exe.pdb @./genmacro.exe.rsp

c:\users\matt : general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified.
LINK : fatal error LNK1327: failure during running mt.exe
ninja: build stopped: subcommand failed.

Depending on the target I tried to build, I'd get the same error, but for a different exe, so the issue is not with a particular gn file, but rather with the build infrastructure. 
 My Windows user directory is "c:\users\matt menke\", so the issue seems to be some tool does no like spaces in paths.

After randomly digging around for a while, I noticed a reference to "environment.x64", and looked at the file.  It has two references to my Windows temp directory.  Updating those paths to just point to d:\temp instead (Leaving other paths with spaces alone, including other references to my user directory) seems to fix the issue.  While I suppose I can just change the location of my temp directory, this no-spaces-in-temp-path requirement seems rather unexpected, and the failure output doesn't exactly make it easy to figure out that moving the temp directory will fix the problem (Moving one's user profile is a bit more involved, but should also fix the issue, I assume).