Jul. 14 – Jul. 20 Hot-Fix KB articles Weekly Release – Windows 6


Hi Everyone,


 


Last week, 9 Windows 6 related hot-fix KB article were released. Below are the details:


 


Windows Vista or Windows Server 2008– 7 KB articles:


·         969512  The MIDI application that uses the inbox USB audio driver crashes after a high rate of MIDI events occurs in Windows Vista or Windows Server 2008


·         971311  After you set the value of the EventMask parameter to WTS_EVENT_FLUSH in the WTSWaitSystemEvent function in Windows Vista or Windows Server 2008, you cannot receive pending WTSWaitSystemEvent function calls if the target server is running Windows XP


·         971330  An application that uses an event log API in legacy Windows does not receive event information in a readable format, on a computer that is running Windows Vista or Windows Server 2008


·         967167  An update is available that enables RRAS servers that are running Windows Server 2008 to use the DH-2048 algorithm together with the AES-256 algorithm to negotiate IKE in the L2TP


·         970964  The Group Policy Management MMC snap-in stops responding on a computer that is running Windows Vista or Windows Server 2008 when you select a Group Policy object in a domain that has lots of organizational units


·         971163  The STDIN, the STDOUT, and the STDERR redirections do not work in a WOW64 child process if the CreateProcessWithTokenW function creates the child process


·         971734  Locale data is missing in the saved event logs if you archive the event logs on a computer that is running Windows Vista or Windows Server 2008 and that has an MUI for a non-English language installed


 


Windows Server 2008 – 2 KB articles:


·         972045  Slow system response together with many other performance issues occur on a virtualization server that is running Windows Server 2008 and that has the Hyper-V role installed


·         970529  The volume GUID may unexpectedly change after a volume is extended on a Windows Server 2008 failover cluster node


 

Regards,


Content Team


Comments (0)