Fireworks CS5 update has been pulled out temporarily

The recent release of Fireworks CS5 update has been pulled out after multiple user reports of it not getting successfully installed. The Fireworks engineering team is investigating the root cause and identifying how to make it smooth sail the next time. Looking at this situation, the update has been temporarily been turned off from auto update or the manual download of patch from adobe.com. Once the issue is resolved and we have identified with the issue, we will release it again. If you would like to help us in testing in real world scenarios at your machines, just send me a note below and we can work with you. On behalf of the entire team at Adobe, I personally apologize for all the pain this update has caused for your valuable time and efforts. EDIT: The contents of the patch will not be changed and all the bug fixes will remain as-is. The only change will be packaging and delivery mechanism of the update. So people who have been able to successfully install the older patch need not worry when the new patch comes out. UPDATE: The update is back online and can be independently downloaded from the Fireworks support page at adobe.comShare on Facebook

5 Responses to Fireworks CS5 update has been pulled out temporarily

  1. mike susko says:

    Does that mean that the update itself is not good? I managed to install it manually.

    • Sarthak Singhal says:

      Thanks Mike for asking the question. I have updated the blog entry with the clarifications. HTH

  2. Ponyboy says:

    Go test your own updates. As a professional systems administrator, I am absolutely disgusted with Fortune 500 companies like Adobe essentially constantly asking their customer base to work for free by testing updates. So, I’ll say it again: Adobe, go test your own updates.

  3. I get a message saying
    “unexpected exception: c0000006”.
    Is that due to the problem which you are referring to?

    • Sarthak Singhal says:

      @Thomas,
      I think the exception error should not be due to the update issue. Can you explain in a little more detail on what workflow did this error come up?

      Did Fireworks crash after this error message?