Here's what I have just done (running as a non-admin user):
- shut down ScreenShotCaptor - destroy both C:\Users\sba\AppData\Local\VirtualStore\Program Files (x86)\ScreenshotCaptor and C:\Users\sba\AppData\Local\VirtualStore\Program Files (x86)\DcUpdater directories - launch ScreenShotCaptor -- nothing happens in the virtualstore - perform an update check using ScreenShotCaptor's context menu: this launches DcUpdater which recreates both directories with the following contents:
Could be that DcUpdater attempts to update part of this in the non-virtualized directory (or just opens files in read-write mode even if it just wants to read?), this fails, causing the virtualization to do its magic?
This file was probably created by either: - installing ScreenShotCaptor without using "run as administrator" - running ScreenShotCaptor as a non-admin user just after installation
In either case, the file virtualization mechanism (introduced in Vista) has kicked in and redirected the attempt to write to C:\Program Files (x86)\ScreenshotCaptor (which a non-admin user is not allowed to do).
After I have deleted C:\Users\sba\AppData\Local\VirtualStore\Program Files (x86)\ScreenshotCaptor and relaunched ScreenShotCaptor, DcUpdater reports the correct version, BUT the file C:\Users\sba\AppData\Local\VirtualStore\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor.dcupdate has been recreated.
Unfortunately I fear that at the next update ScreenShotCaptor might update C:\Users\sba\AppData\Local\VirtualStore\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor.dcupdate, leaving C:\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor.dcupdate unchanged, causing another version discrepancy.
Another explanation would be that running ScreenShotCaptor as an admin user will populate C:\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor.dcupdate, whereas running an update check from within ScreenShotCaptor running as non-admin user will cause DcUpdater to look at C:\Users\sba\AppData\Local\VirtualStore\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor.dcupdate.
Get the picture?
IMVHO running an app should not populate a per-user file containing version information. Instead, the app's installer should populate a system-wide file containing version information. But I'm just wearing my software developer hat on here ;-)
P.S. Without Process Monitor I would not have been able to troubleshoot this.
Repro'ed it on my first attempt (dunno if all steps are mandatory):
- took a screenshot of an app on the 1st monitor (actually discarded it in the "what's next" dialog) - took a screenshot of an app on the 2nd monitor (actually discarded it in the "what's next" dialog) - connected to the machine using Remote Desktop from another PC that has only one monitor - closed the Remote Desktop session (not a logoff!) - reconnected to the dual-monitor PC's console - hit Alt+PrtSc - got the error message ==> had to close ScreenShot Captor
While I can understand where this technically comes from, it is rather user-unfriendly to have region screenshots made with Shift+PrtSc tagged with an application name of "Program Manager", resulting in filenames such as "Screenshot of 'Program Manager' on 20091204105334"
I would suggest to change that "Program Manager" to something else, such as "(screen region)"...
d:\private_sba\net\Captures\http___www.donationcoder.com_Forums_bb_index.php_topic=16214.0_Screenshot Captor 2.44.01 hangs when capturing IE window - DonationCoder.com - Windows Internet Explorer - 20090708110844.png
SSC doesn't hang anymore, it's just unable to generate a valid filename.
For instance, if I capture the very IE8 window I'm typing into, I get:
--------------------------- SCREENSHOT CAPTOR - ERROR SAVING FILE --------------------------- Error saving file 'd:\private_sba\net\Captures\http___www.donationcoder.com_Forums_bb_index.php_topic=16214.0 Screenshot Captor 2.44.01 hangs when capturing IE window - DonationCoder.com - Windows Internet Explorer 20090610154818.png'.
Filename or path may be too long or on missing drive letter, etc.
Change filename below or use File->Save As menu to specify filename, or File->Discard File to skip saving this file. --------------------------- OK ---------------------------
It seems SSC generates the following filename:
d:\private_sba\net\Captures\http___www.donationcoder.com_Forums_bb_index.php_topic=16214.0^M Screenshot Captor 2.44.01 hangs when capturing IE window - DonationCoder.com - Windows Internet Explorer 20090610154818.png
IOW the filename contains an embedded newline.
My configuration specifies
as the filename template.
This might be related to %windowtitle% expanding to <URL><newline><page title>...