Larry A suggests:
Go into Norton settings, click on transaction security and disable Crimeware Protection. 15 minutes should be enough time. Then you’ll be able to do your captures.
Rick W provides the following fix:
1 Click on the Norton Internet Security tab up top.
2 Click Reports & Statistics at the bottom.
3 Click View Transaction Protection.
4 Enter your password for Norton Internet Security.
4 You’ll see a recent date where CaptureWiz.exe was blocked… highlight that event and click Allow/Block on the lower-right.
5 The “Status” which said “blocked” before should now say “allowed.”
Lance M adds that he had to restart his computer for the changes to become effective.
The simple solution is to use a different browser. Apparently, ZoneAlarm only "protects" Internet Explorer.
I contacted ZoneAlarm and received the following answer:
1 In ForceField's Settings screen
2 Click the Advanced tab across the top
3 Find the 'antispyware' section
4 Check or Select, "Only in allegedly secure sessions (https)"
5 Click Ok and reboot computer to ensure changes take effect
It worked for me.
Alek S. suggests checking Enable virtualization as well.
Arne D. says to wait 10 seconds after turning off Forcefield.
Another customer suggests:
In Program Control, click on "Programs". Then highlight "CaptureWiz Pro Application file". Next click on the "Options" button at bottom right. The Program Options window shown will open up. Check the top box, as shown. CaptureWiz Pro will now work. Doesn't matter if it is set as "Auto" or "Custom" on previous window.
Craig H found this solution..
Screenshots from David L:
John C adds that you must also change the setting below, under PC Security:
Ken B suggests:
Reported by Raymond H.
According to Myra H, here’s how to stop McAfee from blocking CaptureWiz:
1 Choose the PC Security tab, then click Firewall.
2 Click Internet Connections for Programs.
We haven’t received reports of other security programs causing this problem, but if you find differently, please let us know!
A customer by the name of Terminal6 found that choosing a non-Aero theme, in addition to the above fixes, finally solved his problem, perhaps because security programs have lax support for obsolete Windows features…