Matthew BartelsNot your Kaseya working directory, but the system temp directory... I'm not saying this is the case every time but I've seen behavior like that before, and in some cases it's been caused by a system temp directory with hundreds of thousands of files piled up in it, and because of Windows' filesystem inefficiency, it takes forever to parse through the directory listing and run files that are in that directory. If it helps, great, if not, keep searching