Wow, not one response from a moderator or anyone else. I really need some help with this, as I did just buy the product. Please help!!!!!!!!!!!!!!!!
Install the update that was made available a few months back that has corrected some crash issues.
Once updated, go to Help > About and confirm that Fw is now version 10.0.3.011.
You also mention 'Task Manager', so I can assume you are on Windows. Ensure you are using Fw with Full Administrator account previleges.
If you are not logged in with admin privileges, log into an account that does and see if Fw runs.
If you have limited account priviledges:
Then right-click on your Fireworks application icon (start menu, desktop, quick launch etc.), select 'Properties', select 'Compatibility' and then under the section 'Privilege Level', put a tick in the box 'Run this program as administrator'.
Nonetheless, definitely apply the new patch.
This fix has helped others in the past - see if it works for you: (in addition to installing the updater).
Restore default preferences
Locate the Fireworks Preferences file on your hard disk and delete it. The exact location of this file varies from system to system.
In Windows, preferences are in your user-specific Fireworks configuration folder.
Windows [Drive]:\Documents and Settings\[UserName]\Application Data\Adobe\Fireworks CS#\English\
In Mac OS, preferences are in the Library/Preferences folder in your user folder. For information about locating your Mac OS user folder, see Apple Help.
Mac [User]/Library/Preferences/Adobe Fireworks CS#/en/Fireworks Preferences
Note: On Mac OS, most Fireworks user-specific configuration files are stored in your user-specific Application Support folder.
The Fireworks CS4 Preferences file is an exception.
Restart Fireworks.The next time Fireworks is launched, a new preferences file will be created that restores Fireworks to its original configuration.
Awesome! Thanks for your suggestions. I'm installing the updates right now, and we'll see what happens. I'll note the result on another reply.
Yea! It seemed to have fixed the problem, and it was a very strange issue. Anyway, THANKS!!!