I am having this same problem. Did you ever find a resolution? Thx.
I installed CS3 (without DW) in Vista Ultimate machine yesterday, and had the same problem. I tried to run the Fireworks as administrator ('Run as administrator' command), and now FW starts without the message. Hope this helps. Thanks.
I'm having the same problem. However, I noticed that if I double-click on the okay button in the popup it goes away and starts correctly. A single click appears to do nothing - double-click is the trick. I've had a case open with adobe support, but they keep pointing me to the "built-in" administrator account - which microsoft doesn't tell you how to access, and adobe can't tell me either!
If you right-click on your Fireworks launch 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'.
This will sort the problem. You will still have a Windows UAC message come up (unless you have turned off UAC) but Fireworks will not load correctly.
Moosehouse - Are you logged into the same User Profile that Fw/Dw was installed under?
Also is it possible it is still running in the background but not closed properly? I had this happen to me on a few occasions. I resolved it by pressing Ctrl + Alt + Del and killed the runnng executable (Fireworks.exe) in the running processes list.
May not be your case, but worth a shot.
I am having this same issue as well on Vista Home Premium 64 bit and CS4.
I only have one account, with full administrator permissions.
Was there a cleaner fix than "run as Administrator" ?
If you are unable/unwilling to allow the user to "run as administrator", there is another way.
A security concern could be that the file->open dialogue retains the given administrative rights of whatever account was used for "run as administrator". This can be exploited by the lesser user to gain access to folders otherwise restricted.
The most hassle free trick is to give the user full rights to the registry key, that Fireworks wants to write to.
(In the future, use ProcessMonitor from Microsoft to detect what a program tries to access and if it is successfull or not. That's how I found this registry key)
Add FULL rights on this registry key to "Everyone"
That fixed the problem nicely for me.
Also new users will not be required to "run as administrator", as this is valid for all users.
True.. it gives the user full access to that specific registry key, but that is at least much less dangerous than giving full access to the entire system.
You can play around with lesser access than Full, but I will not spend more time figuring out the lowest level of access that will permit Fireworks to run.
Hope this trick works for you too
'Eternal Life or your money back'
Thanks heaps! I thought I was in real trouble! worked like a dream
Go legrant! It works now.