Microsoft Mkv Codec
Gauthier Zitnik
I hope I'm posting this in the right place. I need help with some vulnerability issues. This is happening for a few things, and I'm at a loss as to what to do next. This example is the Qualys QID 91866 Microsoft Windows Codecs Library HEVC Video and VP9 Extensions Remote Code Execution (RCE) Vulnerability for February 2022.
I have updated all the relevant codecs, checked their current versions in PowerShell and confirmed with the CVE that they are up to date, but the VM keeps retrieving this in its scan. The only place I can find older version remnants is the registry, and I don't particularly want to go in and remove a bunch of keys. I'm also not able uninstall the codecs or the other apps this issue keeps happening on.
Did you ever find a fix for this? We have the same issue and even removed the old version only to find out it still shows as vulnerable. It might be picking it up in user profiles which makes it more difficult to remove.
Hi @Kurt Carpenter , what worked for me was to completely uninstall the package using Powershell and then reinstall it from Microsoft Store. I don't need the app, but that solved the problem. The same thing happened with a variety of other codecs. I don't think the uninstall from Programs and Features is a completely clean one, so Powershell was the way to go. Unfortunately, in all my cases there was only a single profile per machine so I don't know if it's installed in each user profile.
@Kurt Carpenter Ditto. Looks like a reference to the old version is lingering in wmi, which is our problem since the detection logic in our case is querying wmi. I'm waiting on a fix from MS. More broadly, we can't update raw image file, VP9, HEIF, extensions... since we don't use MS Store.
@QulaysUser In addition to pushing latest versions via sccm, we had to deploy a removal package via sccm (powershell scripted repeating loops because multiple old versions on some machines). It was painstaking...
The Windows Media Audio and Video codecs are a collection of objects that you can use to compress and decompress digital media data. Each codec consists of two objects, an encoder and a decoder. This part of the documentation describes how to use the features of the Windows Media Audio and Video codecs to produce and consume compressed data streams.
This documentation is primarily for developers who want to use Windows Media codecs in their C++-based media applications. For a technical overview of the features of the Windows Media codecs, see About the Windows Media Codecs.
The term codec is an amalgamation of the terms compressor and decompressor. A codec is usually implemented as a pair of COM objects: one for encoding content, and another for decoding content. In some cases the COM objects occupy the same dynamically linked library (DLL).
Not only are there different codecs for audio and for video, but also different codecs for different kinds of content that you might want to put into an audio or video file. The algorithms used to compress and decompress data for spoken words differ from the algorithms used to compress and decompress music data.
The most recent versions of the codec objects also enable access to some legacy codecs, including Windows Media Video 7 and 8, Windows Media Screen 7, the older Microsoft MPEG-4 codecs, and the Microsoft ISO MPEG-4 codecs.
Microsoft Scripting Guy, Ed Wilson, is here. WOW, ML, I am sorry you are in trouble. I can imagine that I might have gotten into a similar predicament because I also would not consider watching a DVD on my laptop as a mission-critical use case scenario, and it would have fallen out of the test specs.
To query multiple remote computers, by using the Get-WmiObject cmdlet, you can simply add multiple computer names, and specify the appropriate credentials. This technique is shown here.
After you have the data, you can examine it by piping it to the Format-List cmdlet and selecting all of the properties. You can then peruse the output to see what properties are most useful for you. Here is an example.
ML, that is all there is to using WMI to examine video codecs. Join me tomorrow for the Weekend Scripter, when I will talk about creating test log files on Saturday and about parsing those log files on Sunday. It will be fun, I promise.
I invite you to follow me on Twitter and Facebook. If you have any questions, send email to me at scri...@microsoft.com, or post your questions on the Official Scripting Guys Forum. See you tomorrow. Until then, peace.
If you are still using Windows 10 and want to play different video formats on your computer, you might need this codec pack which will help you with the matter. The Windows 10 Codec Pack is an essential tool for anyone who needs to play different types of video and audio files on their Windows 10 devices. This software helps users play almost any media file, making it perfect for media enthusiasts and professionals.
Windows 10 Codec Pack facilitates the playback of modern video and audio files by incorporating an extensive list of codecs. These codecs handle almost every compression and file type used in today's diverse media landscape. The pack includes options for easy installation for beginners and detailed customization for advanced users, accommodating a broad user base with varying technical expertise.
The codec pack supports a vast range of file types including, but not limited to, MP4, MPEG4, MPEG2, x265, x264, and DivX. It also handles a variety of audio formats such as FLAC, AAC, and OGG, among others. This wide-ranging support ensures that users can play files in formats like .mkv, .avi, and .mp4, covering virtually all resolutions from SD to 4K and beyond, catering to the needs of high-definition video enthusiasts.
The Windows 10 Codec Pack is straightforward to install. You can choose a simple installation for a quick setup or a detailed one if you want to customize settings. This codec pack is made for Windows 10, which guarantees it works smoothly on this operating system. If you use other systems, though, you might need a different solution.
Because the Windows Update was not offering this as update after several update checks, I went online and downloaded the Microsoft Camera Codec Pack (6.3.9721.0) from the download center. I used the 64-bit installer MicrosoftCameraCodecPack-x64.msi to install it on Windows 7 SP1 64-bit and rebooted. Back in Windows Explorer, my CR2 files are still not getting any thumbnail previews.
I chose to do a repair install through the Control Panel. Repaired, requested reboot, grated, rebooted, logged in, the problem remains. I'm not sure where to go from here. Just to make sure that this was not only related to thumbnails, I tried opening one of the files with Windows Photo Viewer. It didn't work.
I have Windows 7 with SP1 integrated. Could this be the problem? It only says "Windows 7". I know it sounds sick, but could it be that Windows 7 is not supported if SP1 is installed? I will try uninstalling and reinstalling back and forth a few times, get the latest updates from Windows Update installed. But beyond that, I'm pretty much lost.
Where do I even begin to troubleshoot this problem, on a low level? Like, where are these "plugins" installed in Windows? And what "bit" version is Windows Explorer in 64-bit Windows? Is it a 32-bit program or a native 64-bit program? I fear that this could be a "bit" compatibility issue, like so many times before with Windows and Microsoft. I know this has worked with Windows Vista 64-bit, I have used it. But then it might have been a different version of the plugin.
Yes, as evident by the file type icons, I do have a program that can open these files for me. I have both Photoshop and Photoshop Lightroom. I just feel like it would be useful to have a small preview of these files in Windows Explorer when I work with them. I don't see the point in bringing out the heavy artillery like Photoshop just to have peek at what photo that file holds, and I don't necessarily want to import all of these files into Lightroom. I think it's a normal, legitimate request, it's just too bad Microsoft can't deliver plugins for proprietary file formats except their own.
Canon does have a Windows plugin for their CR2 files, but it's been last updated 4 years ago, in 2010. It's as old as the first release of Windows 7. And it's interesting that it comes with one particular limitation.
So here they say all of a sudden I must have Window Live Photo Gallery in order to use this Canon plugin. That completely contradicts what Microsoft says. I read that as if it's an option, not a requirement (or it would have said so in the system requirements). I take it that both Window Live Photo Gallery and Windows Explorer use WIC. No?..
Canon RAW Codec is a software plug-in that enables the import and display of Canon RAW image files when installed in Windows 7* / Vista (SP1/SP2) / Windows XP SP2 and Windows XP SP3. Windows Imaging Component (WIC) supported applications (Microsoft Windows Live Photo Gallery etc.) are required.
I used C:\Windows\SysWOW64\explorer.exe /separate as instructed by KB895561. All it does is start a separate 64-bit process under svchost.exe. The main explorer.exe process is still 64-bit on 64-bit Windows 7.
I also installed all the latest updates available on Windows Update, rebooted, but it didn't help. I installed the x86 version of the MS codec pack, rebooted, nothing. Uninstalled x86 version, rebooted, installed x64 version again, rebooted, installed x86 version over that, rebooted, still nothing.
On top of x86 and x64 versions of the damned MS codec pack, I downloaded and installed the Canon RAW codec plugin 1.8 and it worked. Despite the stupid warning messages about 64-bit on the site. My CR2 files got previews, and opening the files in Windows Photo Viewer worked too!!
64591212e2