http://bugs.winehq.org/show_bug.cgi?id=30078
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Installer Status|NEW |RESOLVED Resolution| |WONTFIX Summary|Many installers fail to |Many installers fail to |detect MSXML6 component |detect MSXML6 component |(Wine doesn't advertise its |(MSXML6 is part of OS since |own MSXML6) |Windows XP SP3 and Wine | |doesn't advertise it using | |registry key)
--- Comment #3 from Anastasius Focht focht@gmx.net 2012-03-12 15:38:27 CDT --- Hello Nikolay,
--- quote --- Alexandre suggested to set reported windows version >winxp for such installers. The problem is that this key is not present on native systems that already ship msxml6 (vista and higher). --- quote ---
This Microsoft XML Team's WebLog entry seems to bolster this:
http://blogs.msdn.com/b/xmlteam/archive/2010/07/02/msxml6-is-now-in-band-msi...
--- quote --- In the past several years, we’ve worked to move MSXML6 in-band for all supported releases of Windows. This began with Vista RTM and has remained the practice for all OS releases since then. Specifically, MSXML6 is in-band for XP SP3, Vista and Windows 7 . It should also be noted that the Vista and Windows 7 Server counterparts also contain in-band MSXML6. I.e. Windows Server 2008 and Windows Server 2008 R2 respectively. One caveat, those that are using Windows Server 2003 will still need to install MSXML6 via MSI/KB<number>.exe wrapped MSIs.
So what does all of this mean for you? If your MSXML6 dependent application is supported on XP SP2 and Windows Server 2003, you’ll need to install the OOB package of MSXML6. For all other OSes called out above, your MSXML6 dependent application needn’t worry about installing MSXML6. --- quote ---
So marking as "WONTFIX".
Usually it won't do any harm if installers decide to install native MSXML6 package on their own.
Regards