On 15. 5. 2015 21:08, The General wrote:
> Any feedback is much appreciated, and if anyone needs more information
> please don't hesitate to ask.

Is the error in any way tied to number of previous build invocations?

Not that I have the slightest idea what the problem is, but have you tried comparing ProcMon traces of a successful and an unsuccessful build? Coming at it from another angle, maybe revert to the working snapshot, and get a ProcMon trace (possibly with a reasonably chosen filters and saving to a file instead of memory) of the interval between the working and broken states?

-- 
David Macek