I see comments in another thread to be wary of mapping network (or other) drives that may be unavailable/inaccessible on the 'X:' drive letter. Apparently some version have a build artifact that will search for files on X: as the original sources were compiled from there. From what I'm reading on that thread, it's only an issue if X: is mapped to something that is inaccessible (e.g. a share that isn't currently connected or on a machine that isn't currently on, or not currently reachable via the network)