Windows Media Foundation Download Win 10 Media Feature Pack for Windows 10 N and Windows 10 KN Editions
Total Page:16
File Type:pdf, Size:1020Kb
windows media foundation download win 10 Media feature pack for Windows 10 N and Windows 10 KN editions. In Windows 10 1511, this update is superseded by update 3099229 for the November 2015 release of Media Feature Pack. This Media Feature Pack applies to Windows 10 version 1508. If you have a different version of Windows, please go to KB 3145500 to find the appropriate Media Feature Pack for your version of Windows. Introduction. The N and KN editions of Windows 10 include the same functionality as Windows 10, except for media-related technologies (Windows Media Player) and certain preinstalled media apps (Groove Music, Video, Voice Recorder, and Skype). You must install other software from Microsoft or a third-party for this communication functionality and to play or create audio CDs, media files, and video DVDs, to stream music, and to take and store pictures. New features such as Cortana and PDF viewing in the new Edge browser rely on Windows Media files that are not present in these editions. Some websites and software, such as Windows Store apps or Microsoft Office, use Windows Media-related files that are not incorporated into these editions of Windows. Users can make these websites and software work correctly by installing the Media Feature Pack for N and KN editions of Windows 10. More Information. Download information. The following file is available for download from the Microsoft Download Center: Excluded features. The N and KN editions include the same functionality as Windows 10 editions, except for Windows Media Player and related technologies. The excluded technologies include, but are not limited to, the following features: Windows Media Player user experience: Enables Windows Media Player features such as the ability to play media files and audio CDs, manage media in a library, create a playlist, provide metadata (including album art) for media, create an audio CD, transfer music to a portable music player, and play streaming content from a website. Windows Media Player ActiveX control: Exposes methods and properties to manipulate multimedia playback from a webpage or an app. Windows Media Format: Provides support for the Advanced Systems Format (ASF) file container, the Windows Media audio and video codecs, basic network streaming capability, and digital rights management (DRM). Windows Media DRM: Enables the secure delivery of protected content for playback on a computer, portable device, or network device. Media sharing and Play To: Enables music, pictures, and videos on a networked computer to be shared with other computers and devices on the same network. Also enables computers to find those kinds of files on the network. Media Foundation: Provides support for content protection, audio and video quality, and interoperability for DRM. Windows 8.1 Portable Devices (WPD) infrastructure: Communicates with attached media and storage devices, including devices that support the Media Transfer Protocol. MPEG, WMA, AAC, FLAC, ALAC, AMR, and Dolby Digital audio codecs: Enables the playback of digital audio content such as MP3, WMA, MPEG-2 audio, AAC audio, FLAC and ALAC audio, and AC-3 audio. VC-1, MPEG-4, H.264, H.265, and H.263 codecs: "Standards-based codec components" (as they are collectively called) enable Windows 10 program such as Windows Media Player to support activities that include the playback and creation of multimedia files that are encoded with standards-based codecs. Groove Music: A preinstalled app that is used to play digital music. Video: A preinstalled app that is used to play digital video. Voice Recorder: A preinstalled app that is used to record sounds. Skype: A preinstalled app that is used for messaging and communications. Effect on other features. Some features are not removed. However, they are affected by the media technology removal in the N and KN editions. These features include the following: App Sync: This feature does not work. OneDrive and Photos: These apps cannot play videos. Xbox app: Some functionality associated with this app (such as Game DVR) do not work, and Windows Gaming Settings will not be available. HomeGroup: Integrated media sharing through streaming features do not work. Webcam: This feature does not work. Windows Portable Devices: There is no support for media synchronization, image acquisition, or file browsing. Windows 10 camera devices: Cameras that use the picture transfer protocol (PTP) do not work. Sound Recorder: Recordings are limited to the WAV format. Group Policy for removable disks: This feature does not work. Cortana Personal Assistant: Speech interaction with Cortana does not work. Windows Store Media Content: Audio and video content acquired via the Store cannot be played. Also, preview of audio or video content in the Store does not work. What's New for WDF Drivers in Windows 10. This topic summarizes the new features and improvements for Windows Driver Frameworks (WDF) drivers in Windows 10. Windows Server 2022 includes Kernel-Mode Driver Framework (KMDF) version 1.33 and User-Mode Driver Framework (UMDF) version 2.33. You can use these framework versions to build drivers for: Windows 10 (all SKUs) Windows Server 2022. For version history, see KMDF Version History and UMDF Version History. Except where noted, UMDF references on this page describe version 2 functionality that is not available in UMDF version 1. New in WDF for Windows Server 2022. New in WDF for Windows 10, version 2004. New in WDF for Windows 10, version 1903. No functionality added or changed. New in WDF for Windows 10, version 1809. Added new API WdfDriverRetrieveDriverDataDirectoryString. New in WDF for Windows 10, version 1803. New in WDF for Windows 10, version 1709. New in WDF for Windows 10, version 1703. In Windows 10, version 1703, WDF includes the following enhancements: New WDF Verifier settings to detect excessive object creation. In some cases, framework objects are incorrectly parented and not deleted after use. With this feature, you can specify a maximum number of objects and what should happen when this threshold is exceeded. To start monitoring, add the following registry values under: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\<driver service>\Parameters\wdf. Add a DWORD value named ObjectLeakDetectionLimit with the threshold value. This is the maximum number of objects of the types described in the ObjectsForLeakDetection key. Add a new REG_MULTI_SZ value named ObjectsForLeakDetection that lists each type name to verify. For example, you could specify WDFDMATRANSACTION WDFDEVICE . To specify all handle types, use * as the string. To control whether exceeding this threshold should cause a debug break or a bugcheck, set the DbgBreakOnError key. By default, if the ObjectsForLeakDetection key is not specified, the framework monitors WDFREQUEST, WDFWORKITEM, WDFKEY, WDFSTRING, WDFOBJECT, and WDFDEVICE. The limit scales with the number of devices installed, so if the driver creates three WDFDEVICE objects, the WDF Verifier limit is three times the value specified in ObjectLeakDetectionLimit . If you specify WDFREQUEST, the verifier only counts WDFREQUEST objects that the driver creates. This feature does not currently support tracking the WDFMEMORY object type. SleepStudy tool provides info on KMDF drivers. The SleepStudy software tool reports the number of power references that a KMDF driver has that are preventing the system from going to sleep. For more info, see Modern standby SleepStudy. The rest of this page describes functionality that was added in Windows 10, version 1507. WDF source code is publicly available. The WDF source code is now available as open source on GitHub. This is the same source code from which the WDF runtime library that ships in Windows 10 is built. You can debug your driver more effectively when you can follow the interactions between the driver and WDF. Download it from https://github.com/Microsoft/Windows-Driver-Frameworks. The private symbol files for WDF on Windows 10 are now available through the Microsoft Symbol Server. The Windows Driver Kit (WDK) 10 samples are also now published to GitHub. Download them from https://github.com/Microsoft/Windows- Driver-Samples. Automatic Source Level Debugging of Framework Code. When you use WinDbg to debug a WDF driver on Windows 10, WinDbg automatically retrieves the framework source code from Microsoft's public GitHub repository. You can use this feature to step through the WDF source code while debugging, and to learn about framework internals without downloading the source code to a local machine. For more information, see Debugging with WDF Source and Video: Debugging your driver with WDF source code. Universal Driver Compliance. All WDF driver samples and Visual Studio driver templates are Universal Windows driver compliant. All KMDF and UMDF 2 functionality is Universal Windows driver compliant. Note that UMDF 1 drivers run only on Windows 10 for desktop editions and earlier versions of desktop Windows. Want to benefit from the universal capabilities of UMDF 2? To learn how to port your old UMDF 1 driver, see Porting a Driver from UMDF 1 to UMDF 2. Debugging and Diagnosability. All KMDF and UMDF 2 drivers can use an always on, always available Inflight Trace Recorder (IFR). When a driver provides a custom trace, the driver IFR log contains the trace messages. Note that the new driver IFR log is separate from the framework IFR log that WDF creates for each driver. The IFR maintains a circular buffer of WPP traces in non-pageable memory. If a driver crashes, the logs are frequently included in the crash dump file. If you turn on the IFR in your driver binary, the IFR is present and running during the lifetime of your driver. You don't need to start an explicit trace collection session. IFR logs are included in minidump files except when the responsible driver is undetermined or if the crash was a host timeout. If you have a debugger connected, you can access both the driver and framework IFR logs by issuing !wdfkd.wdflogdump .