I have never, EVER had a problem with security on my Win box with QT installed... which is what this guy is talking about.
I classify that blog with the alarmist TV shows that say Yellowstone national park is overdue for a cataclysmic eruption and a big object from the Oort cloud could strike the Earth any year now, ending life as we know it.
Just because you haven't had an issue doesn't mean that there won't be one in the future, especially now that they have made the vulnerabilities known to the general public. It is only a matter of time before someone exploits them. Apple has no plans to fix the problem or keep supporting QuickTime.
I came up here trying to find the answer to that question as well. I just saw that all Window users need to uninstall QT because of security concerns. I wonder if Adobe will be making any changes.
2 people found this helpful
You can resolve the QuickTime on Windows security vulnerability by reinstalling QT without the Player.
1. In your add / remove programs, uninstall QT player completely.
2. Go to the apple QT installer download page and grab the latest package for Windows
3. During install, make sure that everything except the "critical components" is NOT installed. (Xed out). Leave the top option for install only (something like "media for third party apps" - this is the codecs only)
4. Install as normal
Probable that you may need to install any third party codecs, like DNxHD/HR, after this.
I deinstalled Quicktime now. But I couldn´t find the Quicktime downloader for windows 10 on the apple page anymore!
What could we do?
There is no quicktime for Windows 10. Just use the latest one they have..I think it's 22.214.171.124
You can remove the player without removing the other stuff by going to the Programs and Features Control Panel (hit the Windows button and type uninstall, and choose "Uninstall a Program"). Then right-click on Quicktime7 and choosing modify, rather than uninstall. Then you can uncheck the quicktime player part.
It would be interesting to know definitively if the problem is with the quicktime framework, or just the quicktime player, and thus if removing just the player is effective. There's a lot of FUD around this issue, but very little substance.