Yep - it's not a LabVIEW error per se, it's that you've tried to load a file from explorer (double clicked on a VI, project, etc), and Windows has started to launch LabVIEW to handle the file (you'll notice that your explorer window is still locked). Windows waits for LabVIEW to load to amek sure everything happened smoothly, but after a while it gives up with a couldn't-do-it message (LabVIEW continues to load in the background). That's why a faster PC "fixes" the problem - it just means that LabVIEW's got a better chance to load before Windows gives up on it. Another way to avoid seeing this error is launch LabVIEW first and then open your VI from the File menu.
Of course, the other way to get around it is to make LabVIEW load faster, but that's another story