Medium bug in Fences 2.0
closing the Windows shell
I don't think Fences 1.x had this one.
The problem is this:
1) Close the Windows 7 shell - click Start, press and hold Ctrl+Shift, then right-click any empty area on the Start menu and choose "Exit Explorer".
2) Now run the shell again - Task Manager (which you can run via Ctrl+Shift-Escape), Run, explorer.exe.
RESULT: Fences won't run again. And it does not appear in the desktop right-click menu. Trying to start it via the Control Panel fails.
EXPECTED: Fences should auto-start along with the restart of the Windows 7 shell. AND/OR, at least be able to run it manually via the Control Panel ---> "Enable Fences".
This is a fairly big bug, not sure how you missed it.
Running Windows 7 64-bit, Ultimate, SP1 with all updates installed.
Please advise if this is a known issue, and suggest a workaround. If not, please tell me when this can be fixed?