MSXML4 is going to be kill bit-ed


Please read the latest entry on this at  http://blogs.msdn.com/xmlteam/archive/2007/09/13/we-are-not-killbit-ing-msxml4.aspx – We are NOT killbiting MSXML4


 


Hi,


 


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.


 


 


We strongly encourage everyone to start using MSXML6 SP1.MSXML6 SP1 is now available for all supported downlevel platforms and can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyID=d21c292c-368b-4ce1-9dab-3e9827b70604&displaylang=en


 


MSXML Supported Versions:


 


We addressed this in a blog entry http://blogs.msdn.com/xmlteam/archive/2006/10/23/using-the-right-version-of-msxml-in-internet-explorer.aspx


 


The  summary is


MSXML6  – Should be your first choice. This is the MSXML version that will be carried forward. MSXML6 shipped with Vista and we are working on getting this in downlevel OS Service Packs


MSXML3 – This has the advantage of having shipped with every supported OS .We are committed to keeping MSXML3 robust and stable but won’t be adding any functional improvements.


MSXML4  – This is in maintenance mode with a very high bar for fixes approaching End of Life.


MSXML 5 –  Exclusively meant for Office. Do not take any dependencies on it.


 


MSXML4 & 6 Differences and Compatibility:


           


Key changes introduced between MSXML4 and MSXML6 and migration are described in the blog entry at http://blogs.msdn.com/xmlteam/archive/2007/03/12/upgrading-to-msxml-6-0.aspx


 


 


Summary:


We believe this is the best plan for MSXML customers going forward – avoids confusion regarding multiple versions, ensures a safe browsing experience when using MSXML and provides a path to use future functional improvements . If you run into issues with the migration or have questions/feedback feel free to contact us at msxml4@microsoft.com . All of the MSXML team is on this alias eager to hear your feedback and assist with the migration.


 


 


Thanks


MSXML Team


Comments (27)

  1. Tim Weaver says:

    According to the XmlTeam blog here MSXML4 is destined for a rather abrupt end. If you are using MSXML4

  2. Data says:

    Our XML team announced this morning that, a s a part of our MSXML4 End of Life plan, we will kill bit

  3. The Microsoft XML team has announced MSXML4 will be kill bit-ed in IE in the October – December 2007

  4. MSXML6 SP1 fails to install on my Windows XP Professional workstation (actually a laptop).  I have installed Windows installer 3.1 and I have stopped all services, including those specific to SQL Server 2005.

    Each time the installation runs, it fails with a popup dialog box indicating "a netwok error occurred while attempting to read from the file <path name to the msi file on my sytstem>"

  5. XmlTeam says:

    Hi Conrad,

    Please try saving the msi to your machine and running it locally. And let us know if you run into any issues with that.

    Thanks

    Nithya

    MSXML Team

  6. Stephen Green says:

    And when might a ‘kill bit’ be applied to MSXML6 so we can decide whether to use it and for what to use it?

  7. Umut Alev says:

    We are not planning to kill-bit Msxml6 at all. Msxml6 is here to stay.

    Regards,

    Umut Alev

    MSXML Team

  8. XmlTeam says:

    To amplify Umut’s point a bit — The point of killbitting MSXML4 is to encourage people to migrate to MSXML6 so that they have a solid foundation going forward. There are no plans for an MSXML7, so this isn’t something we’re going to ask you to do all over again in a couple of years.

  9. According to this post by the Microsoft XML team , MSXML 4.0 is going end of life near the end of 2007

  10. Jane Do says:

    Why is it going end of life near the end of 2007?

  11. XmlTeam says:

    "kill bit-ing" is not "end of life" in Microsoft-ese.   The kill bit prevents a component from running in IE, it does not prevent it from being used in an application. See http://support.microsoft.com/kb/240797 for more information.  The end of life plan is a much longer term process; the kill bit is just a nudge in that direction.

    All this is being done to reduce the cost and confusion for all of us caused by having so many supported versions of MSXML around at once. As of right now, we do need to support MSXML3 and MSXML6, but MSXML4 doesn’t have any significant functionality that one of the others does not.

  12. IEBlog says:

    Jeremy Dallman here with some important information from the MSXML team to the IE development community.

  13. RSS It All says:

    Jeremy Dallman here with some important information from the MSXML team to the IE development community

  14. MS are going to push out an IE specific kill-bit for MSXML4 in October. More information here: http://blogs.msdn.com/xmlteam/archive/2007/03/12/msxml4-is-going-to-be-kill-bit-ed.aspx

  15. Shan McArthur says:

    Please note that MSXML 6 does not have a CAB installer, which makes it impossible to use in a browser application with respect to automatic download and instantiation.  MSXML 4 is the latest XML version that has a CAB installation.  PLEASE do us all a favor and provide a CAB installer so that we can start to use MSXML6, and please do this before you kill-bit MSXML4.  These are important considerations to be made.

  16. Thriol says:

    Will MSXML4 continue to work in applications that host the IE web control?

  17. Daca aveti aplicatii dependente pe versiunea asta, va recomand sa treceti cat de curand la MSXML6, deoarece

  18. While on the subject of XML. I noticed an announcement on the Microsoft XML Team blog that MSXML4 is

  19. MowGreen says:

    Nice. Until then, could you please do something about the MSXML 4.0 SP2 hotfix/patch/update that was issued in November , KB927978 ?

    Thanks.

  20. MowGreen says:

    Nice. Until then, could you please do something about the MSXML 4.0 SP2 hotfix/patch/update that was issued in November , KB927978 ? Folks are still having issues getting it to install and now that issue is spreading to Vista.

    Thanks.

  21. DaveLord says:

    If I have an ActiveX control that runs in IE and uses the SOAP toolkit 3.0 which in turn uses MSXML4, is the kill bit going to break that? I can’t imagine that they will update the SOAP toolkit so we would have to go to a third party SOAP implementation.

  22. Aric opensights@gmail.com says:

    +1 on the MSXML 4.0SP2 issue in Vista. I am a volume license customer and am unable to install Office 2007 on my Vista PCs due to this problem. If XML4 is going to be kill-bit-ed, why does the latest, greatest office suite rely on it so deeply?

    I am seriously re-considering my purchase of a Vista and Office 2007 volume license.

  23. XmlTeam says:

    Shan McArthur:

    We agree that Msxml4 CAB made things real easy for all parties. We are considering solutions for this problem. Stay tuned.

    DaveLord:

    IE Kill-bit only and only affects ActiveX objects that are created by IE ‘object’ tag and JavaScript ‘new ActiveXObject’ method. If you create a object that in turn creates a Msxml4 object and uses that IE kill-bit cannot prevent that. Since your ActiveX object uses SOAP and SOAP in return creates MSXML4, your scenario should not be affected.

    Aric:

    Office 2007 has zero dependencies on Msxml4 as far as I know. Could you please elaborate more on what you are blocked on Office 2007?

    To resolve the Msxml4 KB927978 update issues see http://forums.microsoft.com/msdn/showpost.aspx?postid=1141274&siteid=1&sb=0&d=1&at=7&ft=11&tf=0&pageid=2 ‘Karen G’ and ‘Jim Rhyne’ has resolved this issue. Shortly we will make this a KB article.

    – Umut Alev

  24. Asta dupa caderea de saptamana trecuta: doua discuri crapate simultan, plus backup (numai) din februarie.

  25. Hello All, In March , we posted our intention to killbit MSXML4 and encouraged users to move to MSXML6

  26. Hello All, In March , we posted our intention to killbit MSXML4 and encouraged users to move to MSXML6

  27. Daca aveti aplicatii dependente pe versiunea asta, va recomand sa treceti cat de curand la MSXML6, deoarece