Change in Single Program Capture Behavior with SWV 6.1
Since the 6.1 Beta we've made a change with how Single Program Capture behaves in SWV 6.1 that you'll either love or hate depending on how you look at this news. Let me start out by saying that we believe this is how Single Program Capture should behave so this is a bug fix.
Previously with SVS is you tried to capture Adobe CS3 products (not sure about CS4), as well as some other applications, using their Setup.exe installer the capture would end before the actual install actually started, the workaround was to launch a command prompt and then launch Setup.exe from the command line or do a silent install. The issue at hand was certain child processes were being ignored, more on this is a bit, so when Setup.exe actually launched the installer we didn't track that and when Setup.exe exited we'd stop capture because the process we were tracking had ended and we didn't track the child process. With the changes in 6.1 this is no longer the case as we now track all child processes so situations like this should be less common.
The downside is that now we track all processes so any app that launches a background process during, or after an install, will cause Single Program Capture to not end. And example of this is iTunes which launches iTunes_helper.exe after installing, we use to not track this with SVS 2.1 but now we do so an iTunes capture will not end automatically unless you kill all the processes associated with the application you just captured (services shouldn't matter). Another option is to right click the spinning SWV icon in Windows' Notification Area and select "Stop Capture" just as you would a Global Capture.
I'm sure that for those of you that are use to SVS will find this a little jarring in SWV but we think it's the correct behavior, because you never know what that background process is doing during an install, and that you all would prefer Single Program Capture to be as reliable as possible.