MSXML4 is going to be kill bit-ed

We are going to kill bit MSXML4 in the October - December timeframe of this year. Kill Bit applies to Internet Explorer only. After the kill bit , applications will not be able to create MSXML4 objects in the browser. Other Applications like C++ apps which are not killbit aware will continue to work with […]

We are going to kill bit MSXML4 in the October – December timeframe of this year. Kill Bit applies to Internet Explorer only. After the kill bit , applications will not be able to create MSXML4 objects in the browser. Other Applications like C++ apps which are not killbit aware will continue to work with MSXML4.

We are announcing this in advance so that our customers get sufficient time to try their applications with MSXML6 and give us feedback on their experience. Please email us at msxml4@microsoft.com with feedback/questions/concerns.

Why: We are going to kill-bit MSXML4 to ensure a secure browsing experience for our customers. We are planning to also remove MSXML4 from the Download Center page within the next 12 months. Support for MSXML4 going forward will be restricted to high impact security issues only.

MSXML6 is the latest version available to MSXML customers today. This is where all the functionality, performance and security improvements are going in. In addition MSXML6 provides improved W3C compliance and increased compatibility with System.XML in .Net. The recommendation for MSXML customers is to program using MSXML6 and upgrade apps using older versions to MSXML6.

Continue for more info....

Microsoft, Internet Explorer, IE, MSXML4, MSXML