Added support for graphics importer components that could read images from GIF, JPEG, TIFF and other file formats, and video output components which served primarily.

I'm running 64-bit version of Windows 7 via bootcamp. I'm running 64-bit version of Microsoft Office 2010. I have the latest version of Quicktime installed 7.7.3 something. I can play the file on the desktop no problem, but when I try to insert the file into Powerpoint or play a file that I inserted previously into Powerpoint on a different system, it says either Quicktime unavailable or you need a 64-bit version of Quicktime in order to insert the file.

So, exactly where is a 64-bit version of Quicktime for Windows because apparently the one on the Apple website for Windows is not 64-bit. Everyone keeps saying download the 64-bit version of Quicktime. Great, tell me where it is. There is no option for 64-bit on the website. It doesn't even say it is 64-bit. It just says its compatible with Windows 7. Powerpoint 2010 64-bit MUST have a 64-bit version of Quicktime in order to insert or play any Quicktime file.

The OS doesn't give a rats @ss one way or the other. The file I previously inserted was playing on a system that apparently had a 32-bit version of Powerpoint installed. That machine defaults to VLC player on the desktop.

It has no issues with the file. It's the Quicktime Player mismatch on my machine that is giving me grief. If I knew Office was going to be a PITA if I installed the 64-bit version I would have stuck with the 32-bit version. Where is the 64-bit version?

How do you tell it is 64-bit? How do you force the installer to make sure it ONLY installs a 64-bit version of it? Posted on Nov 29, 2012 12:08 PM. It is odd that a 64bit application would ask for a software that doesn't exist.

The idea that you need a 64bit version of quicktime is strange because Adobe Premiere (on windows) is also 64bit and seems to work with the 32bit Implementation of Quicktime. To be honest a lot of software can be messy like this (for example itunes64 on windows is not really 64bit at all but 32bit). So to blame microsoft is incorrect - its not their responsibility to make a 64bit quicktime codec. Apple should really create a 64bit tunnel that interfaces to the 32bit codec. To be honest, Apple are known for their total lack of interoperability and in this case (since I would guess that a lot of their software isn't true 64bit yet - like itunes) - I would blame them.

Adobe had to create their own interface for Premiere and After Effects which are both heavily reliant on Quicktime (if you use Apple format videos). Again, it shouldn't really be there responsibility to work around the deficiencies of Apple's deficient format. Sorry it's not the place to mention how bad quicktime actually is, but then you can always go and find out yourself if you're not totally indoctrinated by the marketing lies. Jan 15, 2014 8:44 AM. I'm sorry, but you are incorrect.

It is not Apple's responsibility to write something that doesn't exist. Microsoft wrote their application to ONLY SUPPORT a version that they KNOW doesn't exist. The fact that other software developers are 'keen' to this fact and write their software to use the 32-bit version because it's the only one that exists doesn't change the fact that this is a Microsoft issue. Microsoft needs to fix their 64-bit version to either use 32-bit Quicktime or not use Quicktime at all. To have Quicktime functionality in their 32-bit version but not in their 64-bit version is absurd when they say it supports the Quicktime codec. Yeah, maybe in some far distant future, but not today. Pinball Pirates Caribbean.

Microsoft owns this one, plain and simple. Jan 15, 2014 11:57 AM. Well, talking in absolutes shows you have very weak reasoning skills. There is not a simple right and wrong but that's fine. Secondly, as I mentioned - the idea that a 64bit software needs 64bit specific versions of plugins is not rocket science - that's computing for you. Microsoft didn't dictate that. Thirdly, as I said - Quicktime is the most incompatible closed piece of **** 'protocol' out there.