Article ID: 836545 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
When streaming some content from a Windows Media Services server, client computers may experience buffering. Network administrators may notice dropped packets at various router hops or switch hops.
This problem occurs because some network hardware may have buffers that can be exceeded by large frames (such as key frames) that have higher bit rate content. The content is served from the server based on the Send Time of the packet as specified in the file itself. When the large frames in the content are all sent at the same time, the buffer limit may be exceeded on the network hardware. This overflow may cause playback problems on the client.
The following file is available for download from the Microsoft Download Center:
Download the WindowsMedia9-KB836545-ENU.exe package now.
Collapse this imageExpand this image
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
(https://support.microsoft.com/kb/119591/ )How to Obtain Microsoft Support Files from Online Services
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 12-Feb-2004 13:34 18.104.22.16825 2,071,288 Wmvcore.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
After you install the hotfix, you have to encode the content again. You can either do this by means of one of the following: