While in general eschewing spaces in file names and paths sounds like a laudable goal from a lazy (Perl?) programmers perspective, in the OP's case the space is in a system provided path and is unavoidable. A far better thing would be for systems to provide the tools to work correctly with the practices people actually use.

Windows has far too many special characters that can't be used in file names and paths and the mixed blessing of a case insensitive but (mostly) case preserving file system. On the other hand, so long as you remember to double quote file names if you are using the command line, it mostly does what people expect. Use of easy to read descriptive file names is the norm and applications generally cope.

*nix on the other hand allows virtually anything in file names and paths, but general practice is to use short lowercase unpunctuated names without spaces. I find it vastly amusing that the file system that allows the greatest freedom in file naming is used in the most constrained fashion. *nix applications I've encountered are much more likely to be fragile in the context of allowed but unexpected file names than Windows applications.