I've been chasing the problem of hangs for months, starting with Ghost 14 on XP. Backups are extremely important to me, and I've tried everything from extensive chat sessions to reading every post I can find on the subject here. The problem was important enough to me to solve that it was one of my reasons for moving to Windows 7 and Ghost 15. My thought was that I might be having a software conflict due to build up of years of installs (and attendent freeloaders), and that doing a brand new, clean install of Windows 7 would simplify things. Sadly, despite new Windows and new Ghost, the hangs are still with me.
Right now, I'm looking at a typical hang: the backup is at 5%, which is where it's been for 12 hours. Clicking the "Cancel" button results in the cancel hanging too. These symptoms are completely typical.
I believe VProSVC.exe is a key player. I am looking at that process using WhatsRunning (a wonderful substitute for Windows Task Manager, because WhatsRunning provides lots of details on any given process/service of interest). VProSVC.exe is sporadically taking CPU, but the I/O is totally absent - zero bytes being transferred... forever...until a reboot. It's waiting for something to happen - and whatever it's waiting for isn't happening.
I've followed so many threads pertaining to hangs, have tried any number of suggestions, and none seem to pertain.
What I want to especially give you folks is the following feedback. We all (users and Tech Support) need Ghost to do a much better job of 1) error detection and response, and 2) status reporting, to allow us and Tech Support to more easily diagnose such problems.
Here's an illustrative example: one of the suggestions I've seen several times is to do a Chkdsk on the disks involved in the backup. For heavens sake, if there is a problem with an I/O error or file system structure, Ghost should report that error and not just hang with no indication of why!!! In my opinion, this is just basic programming common sense.
And with all the months/years these problems have been reported, you would think the design/development team would recognize error detection/management/reporting as a key issue with Ghost and take steps to address it.
I'll look back at this to see if there is a meaningful response, but basically, I'm totally through with Ghost. I've spent hours, hours, and hours trying to get around this problem, and I'm done with the product.