Adobe Creative Cloud

QuickTime on Windows

Recently the United States Computer Emergency Readiness Team issued Alert (TA16105-A), which recommends Windows users uninstall Apple QuickTime from their computers.

Adobe has worked extensively on removing dependencies on QuickTime in its professional video, audio and digital imaging applications and native decoding of many .mov formats is available today (including uncompressed, DV, IMX, MPEG2, XDCAM, h264, JPEG, DNxHD, DNxHR, AVCI and Cineform). Native export support is also possible for DV and Cineform in .mov wrappers.

Unfortunately, there are some codecs which remain dependent on QuickTime being installed on Windows, most notably Apple ProRes. We know how common this format is in many worfklows, and we continue to work hard to improve this situation, but have no estimated timeframe for native decode currently.

Other commonly used QuickTime formats which would be affected by the uninstallation of QuickTime include Animation (import and export), DNxHD/HR (export) as would workflows where growing QuickTime files are being used (although we strongly advise using MXF for this wherever possible).

Adobe’s desire has always been to support everything natively without the need for QuickTime. As a result of the above we intend to increase our efforts to remove these incompatibilities, and provide our customers with a complete native pipeline. We will provide more information on this as we progress.

Motion Graphics & Animation, Video Editing

Join the discussion

  • By pierre antoine - 9:25 AM on April 16, 2016  

    ok

  • By Ernie Pinnock - 11:22 AM on April 16, 2016  

    Please fix my table and all my apps on my table.and when i download apps

  • By manisoft - 11:35 AM on April 16, 2016  

    hi
    please tell us now how what software must install like as quick time?

  • By Chris Dickman - 4:35 AM on April 17, 2016  

    Exactly what Adobe applications are affected by this?

    Thanks

    • By Geoff - 1:27 PM on April 17, 2016  

      After Effects, Premiere Pro, Photoshop, and Lightroom are definitely all affected. Not sure on the others.

      • By Nancy - 3:37 AM on April 22, 2016  

        Are Lightroom, Premier Pro and Photoshop affected for still–e.g. non-video–editing/post processing?

        • By Geoff - 11:06 AM on April 22, 2016  

          Adobe claims their team is undergoing tests. They have been unable to provide any specifics with regards to which codecs are affected in Photoshop and Lightroom. Supposedly this link will be updated with specifics at some point, but they have no time line at present.
          https://helpx.adobe.com/x-productkb/multi/quicktime-uninstallation-impact.html

          • By Nancy - 7:33 AM on April 23, 2016  

            Thank you for the link and information.

  • By AdobeLazy - 12:06 PM on April 17, 2016  

    Not removing Quicktime for Windows dependencies years ago?

    Steve Jobs was right when he said Adobe was LAZY.

    • By JSDibelka - 5:41 PM on April 18, 2016  

      Amen.

    • By gary - 8:33 PM on April 27, 2016  

      meanwhile, macintosh users went without a native 64-bit version of photoshop for over a year because apple was too busy developing i-gadgets to build a true 64-bit version of OSX. 🙂

  • By Geoff - 1:26 PM on April 17, 2016  

    I assume discounts will be provided for all Windows users being put at risk?

    • By Chris Conele - 11:09 AM on April 19, 2016  

      You can send a bill to Apple. Adobe had nothing to do with Apple’s decision.

      • By Geoff - 6:20 PM on April 19, 2016  

        But Adobe’s programs are still dependent on a now obsolete Apple product on the Windows platform. So in order to even be able to use Adobe for Windows, you need to keep Quick Time installed, which means ignoring the warnings from the Dept of Homeland Security.

        • By Manning - 7:36 PM on April 19, 2016  

          Be fair. It is Apple who enforce the link between ProRes and Quicktime. And Prores is certainly not obsolete – it is one of the most common codecs used in broadcast/film.

          • By Geoff - 12:50 PM on April 20, 2016  

            All the same, Adobe Windows subscribers are forced to put their computers at risk (against the advice of the Federal Government & the Department of Homeland Security) if they want full functionality. That’s an Adobe problem any way you slice it, even if you think it isn’t their fault.

  • By Scott - 2:00 PM on April 17, 2016  

    Maybe I’m just really hungover but does this post not contradict itself?

    The second paragraph says “native decoding of many .mov formats is available today (including uncompressed, DV, IMX, MPEG2, XDCAM, h264, JPEG, DNxHD, DNxHR, ProRes, AVCI and Cineform)” — note ProRes in there.

    The 3rd paragraph says “Unfortunately, there are some codecs which remain dependent on QuickTime being installed on Windows, most notably Apple ProRes. We…have no estimated timeframe for native decode currently.”

    ??

    • By Scott - 4:41 PM on April 17, 2016  

      Agreed. The post is very poorly written. It is completely ambiguous about enumerating which codecs Adobe have “worked extensively on removing dependencies on QuickTime” and which are still dependent on QuickTime and thus not available if the recommendation is followed.
      Apple have apparently caught Adobe with their pants down. For the money I pay for my CC subscription, this is pretty shabby treatment. To atone, I think they need to add something nice just for Windows users who will have to suffer on account of this massive monkey wrench they’ve thrown into our workflows.

    • By s - 1:14 AM on April 19, 2016  

      No, DECODING is available since a long time on windows. However, ENCODING is still nowhere to be seen in the Adobe Windows world.

      • By Manning - 7:39 PM on April 19, 2016  

        No, Adobe cannot natively decode or encode ProRes. To decode on Windows you must have Quicktime installed. (Remove QT and try to play a ProRes file if you don’t believe me).

        Encoding is not a technical problem, it is a licensing problem. Apple own the codec and won’t grant permission to anyone to develop a Windows encoder. Cinemartin appear to have reverse engineered their solution, which does not overwhelm me with confidence.

        • By JJ - 4:18 AM on April 20, 2016  

          Nope,
          That is not actually true.
          It’s been already several years since more than several Windows applications have been licensed from Apple allowing the encoding of ProRes files on Windows.
          Assimilate Scratch and DVS Clipster were among the first ones to have that extra, most recently Digital Vision Nucoda family joined as well and there are a lot more, you can check it out here – https://support.apple.com/en-us/HT200321

    • By Scott - 6:04 PM on April 29, 2016  

      apparently they fixed it so it no longer says ProRes in the 2nd paragraph.

  • By Craig - 8:58 AM on April 18, 2016  

    Thanks Adobe, for acknowledgingredients the problem. I was wondering about this and it’s great to see you are working on it. I trust that there will be another blog stating when we can truly get rid of QT when all Creative Cloud apps no longer require it?

  • By Regi E. - 4:19 PM on April 18, 2016  

    Its this all a little over blown? The vulnerability with the web player, no? and given you have the option to only install the essentials; that being the codecs needed, would that not be a work around until Adobe has a solution..

    • By s - 1:14 AM on April 19, 2016  

      I Agree.

      • By Garrett T. - 9:59 AM on April 19, 2016  

        I am trying to figure all this out to support my department which is 95% Apple ProRes for video. If I install just the essentials does that keep my platform secure? Is the vulnerability strictly to the player? I appreciate any help you might offer.

        • By Tony V - 8:59 PM on April 21, 2016  

          Garrett, check out this Forbes article. On page 2 it quotes a strategist for Tenable Network Security who states

          “Since the current version of Quicktime for Windows 7.7.9 removed the browser plugin anyway there is no way for an attack to automatically compromise a system with a simple drive-by exploit. The attacker would have to convince a victim to download a specially crafted file and then get them to open it in Quicktime.”

          http://www.forbes.com/sites/tonybradley/2016/04/19/apple-abruptly-pulls-plug-on-quicktime-for-windows/#1eea3ca8775c

          To me, that means if we only open our own ProRes files, there should be no risk, and it may also mean that if we use a different player, like VLC, there is no risk (not as sure about that one, though). Finally, I don’t see any issue working with our own ProRes files in Adobe CC applications.

          If someone has evidence proving otherwise, please share. Thanks.

  • By Adam - 3:53 AM on April 19, 2016  

    Something just felt odd to me when miraizon prores just stops sales and shuts down and now quicktime is being “asked” to be removed from windows systems. I just want to do my job and not have disruptions in my workflow.

  • By Thomas - 5:20 AM on April 19, 2016  

    I hope Adobes Trades will sink to zero. Lazy money eating company.

    • By Adam - 9:06 AM on April 19, 2016  

      Thomas, this isn’t an Adobe fault, issue, whatever you want to call it… its Apple not supporting quicktime anymore and it’s recommended to uninstall QT. Adobe is doing what they can to help their community.

      • By Geoff - 6:25 PM on April 19, 2016  

        It still is Adobe’s fault for their continued reliance on Quick Time. People subscribed to Adobe Creative Cloud aren’t paying Apple for their subscriptions – they’re paying Adobe.

  • By Bill - 7:50 AM on April 19, 2016  

    It is very simple gentlemen. I.T. has removed Quicktime player from my windows rig. I am an After Effects developer 40 hours a week. No Quicktime, no J O B !! In the casino industry you can very well imagine our extremely tightly wound need to keep the internet foes and uneducated internal users from destruction. I challenge anyone and especially Adobe to save my job and do not put my families short term future at risk. Any more simpler than that? I personally need a solution. NOW and thank you kindly.

    • By Geoff - 6:24 PM on April 19, 2016  

      Unfortunately, it doesn’t seem like this is something that will be resolved quickly. Adobe’s support team has been extremely lackluster with their unsatisfactory responses to inquiries. Their customer service inadequacies now rival those of Verizon.

    • By Pete - 1:18 PM on April 22, 2016  

      Switch to MXF wrappers, (which Apple started supporting for the Macs since Feb this year). Move along.

  • By Bill W - 12:50 PM on April 19, 2016  

    What I see is that the security problems stem from using QT player “legacy QuickTime 7 web plug-in” in a browser or on the web??

    “Uninstalling QuickTime 7 also removes the legacy QuickTime 7 web plug-in, if present. Websites increasingly use the HTML5 web standard for a better video-playback experience across a wide range of browsers and devices, without additional software or plug-ins. Removing legacy browser plug-ins enhances the security of your PC.”

    So buy removing just the legacy plugin solves the problem as long as you don’t already have a infected .mov file on your computer already….

  • By Bill W - 1:01 PM on April 19, 2016  

    I was able to just deactivate the QT plugin 7.7.8 in the plugins section of the add-ons manager for Firefox browser…problem is is that Apple introduces a little anarchy and everyone losses their mind and start running around aimlessly shooting at everything that moves!!

  • By Billc - 6:18 PM on April 19, 2016  

    The vulnerabilities extend to the non-web quicktime codex also. There are 2 newly discovered critical vulnerabilities being left unpatched and any .mov file picked up from outside could compromise your system using these. You may or may not consider this an issue. If you’re still using Windows XP I wouldn’t worry about it.

  • By SparkyJim - 1:09 AM on April 20, 2016  

    I know next to nothing about video editing. Codecs drive me crazy. But I can tell you this about the software development industry:

    Major announcements like this about critical standards and software being deprecated are usually made YEARS in advance.

    I understand that Adobe could have been more proactive, but I place *at least* 80% of the blame for this mess squarely on Apple’s shoulders. Instead of a two-year lead time to root out the last vestiges of QuickTime for Windows, Adobe got a major slap in the face, and now the world expects them to come up wish a solution inside of two weeks.

    It’s unreasonable to think that Adobe could have known that Apple would be such jerks about dropping their support for the product.

  • By LPowell - 12:59 PM on April 20, 2016  

    Quicktime for Windows has long been an obnoxious crash hazard for video editing on Windows. From Windows 7 onward, Apple has demonstrated supreme intransigence in refusing to build a 64-bit Windows compatible version of Quicktime. As a result, the 32-bit Quicktime runtime module can allocate only 8MB of RAM and resorts to buggy virtual memory management to handle larger video files. This impacts every video editor that must use Quicktime to decode MOV files, notably Adobe Premiere Pro and After Effects. It is Standard Operating Procedure to Ctrl-Alt-Del into Task Manager and terminate the QuickTime process anytime Premiere or AE lock up while scrubbing through a video. That fixes the hung user interface and you can save project or even continue editing without problems.

    I’d really like to see a class action suit against Apple, demanding they either commit to maintaining Quicktime on all compatible platforms, or else release it to the public domain as an Open Source project.

    • By Scott - 9:10 AM on April 21, 2016  

      As obnoxious as Apple’s behavior may be, they have no legal duty to you or to me to maintain QuickTime on Windows, nor release it into the public domain after they’ve stopped active development. If you’re a Creative Cloud owner, then it’s Adobe that have the moral, if not legal, obligation to fix this. Their continued reliance on a third party to provide such essential functionality shows them to be lazy, foolish, or both.

  • By Derek - 11:06 PM on April 22, 2016  

    I’ve already uninstalled QuickTime for windows and found that Premiere CC can’t load .MOVs generated off of an iPad. Seeing as they are H264 encoded, I’m wondering if here is something else Premiere doesn’t like, perhaps AAC encoding of the audio. Seeing as a lot of folks shoot video on iPhones and iPads, I hope Adobe is addressing this.

  • By Scott - 5:53 PM on April 29, 2016  

    While I agree that this is a bit overblown, it just makes me angry because I was saying years ago to anyone who would listen that we should avoid ProRes and use something similar (like DnxHD – at the time cineform was still $$) that wasn’t proprietary. At a time Apple was CLEARLY moving away from the professional world (no more x-serve, the mac pro had been stagnant for a while, fcp stagnant etc) major post facilities and related companies all wanted to move to prores. And they did. The vast majority of places I work for want ProRes as the master delivery.

    And now here we are. It’s not just about the security but also the 32-bit nature of Quicktime on Windows (as mentioned by others).

    Adobe, for it’s part, has been somewhat unclear about their ability to ‘natively decode prores’. Can anyone clear this up – does ‘native’ mean I can open and edit ProRes in Premiere/AE without QT installed? I can live with decode only and then encode to mxf…

  • By DrTom - 3:26 PM on May 7, 2016  

    It seems that only Adobe Photoshop CS versions use QT. Ihave Adobe Photoshop Elements 6.0 and Adobe Premier Elemets 4.0, both running on Windows Vista. Am I correct that these do not need QT?

    • By Phyllis Albert - 9:18 PM on May 12, 2016  

      I, too, use Adobe Photoshop Elements 6.0 and need to know if I can eliminate QT without affecting the functioning of Elements 6.