I have a Mac running High Sierra -- Windows 7 (fully updated) is my Guest OS. For about two weeks since I became a Parallels user, my vm has worked very well. Quick, intuitive, a real pleasure. Today, my Parallels Desktop app opened much slower than usual, but it did give me the vm pick in the Control Center. When I clicked on the vm pick, not much happened until I got the "Operation timeout" error message as the vm was trying (unsuccessfully) to open. I've read a number of KB articles and a few forum posts all of which discuss "Problem ID:15" There is nothing like this descriptor on my error message -- just "Operation timeout -- The operation could not be completed due to a timeout." The link in that error message takes me to KB116216 (which pre-dates Desktop 13 and was last reviewed 14 months ago. I also appears to be specific to the ID:15 issue.). I followed its instruction re: the Activity Monitor without any result. I believe I am fully backed up with clones of the Mac HD, and my Time Machine is also in good shape. I know I have one snapshot from today (unfortunately made between the error message events described next) made under SmartGuard. I thought I had the problem fixed when I succeeded in getting the vm to open just once after two or three failures before but the next attempt to start was unsuccessful. I also have two snapshots from several days ago before SmartGuard was activated. When I had my one success today, I ran CHKDSK on the vm's Windows but didn't dare open the two Windows apps I maintain on the vm. The next attempt to open Parallels Desktop appeared to be successful but was notably slow. Trying to open my vm, however, once again produced the error message above. I have the .dmg I used to install Parallels on July 7th and could re-install the app from that .dmg. Help please. Terry
Hi Paul Chris, and thanks for responding to my request. No I have not. I had discounted this KB122991 yesterday because of the "Problem ID:15" specific that did not appear in my error message. If it happens again, I'll follow this procedure you recommend. I see the .hdd file in my .pvm file and the steps in the fix look quite straightforward. I've heard "stay away from Terminal (or its Windows counterparts) for years and years, but I think opting to run Parallels constitutes a decision to be willing to deal with those under-the-covers fixes. The good news is that the "Operation timeout" problem was nowhere to be seen today -- it left as suddenly as it had arrived yesterday. When I started the Mac this morning, I decided to see if doing nothing for 12 hours (computer was shut down) might have fixed things. Parallels Desktop started up as usual, and the vm opened as well. I noticed a little later (while running an app in my Windows guest OS) that my desktop widget showed available RAM usage of about 70% vs the 45% for which I'd set the configuration two weeks ago (and had never observed it varying from that range). I re-configured the vm to about about 3 gigs of RAM and that has dropped the usage percentage to about 35% . Don't know if this earlier excursion suggests anything. Anyway, right now I'm attributing the successful start-up to good luck and will keep your response at hand (as well as backups). Thanks again for your response, Paul Chris. Terry2
