navigation bar left navigation bar right

Secunia CSI7
navigation left tab Advisories navigation right tab
navigation left tab Research navigation right tab
navigation left tab Forums navigation right tab
navigation left tab Create Profile navigation right tab
navigation left tab Our Commitment navigation right tab
PSI
PSI API
CSI
OSI
xSI
Vulnerabilities
Programs
Open Discussions
My Threads
Create Thread
Statistics
About

Forum Thread: MSXML

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:
Programs

Relating to this vendor:
Microsoft
And, this specific program:
Microsoft XML Core Services (MSXML) 4.x

This thread has been marked as resolved.
Theophil MSXML
Member 17th Jul, 2014 21:25
Ranking: 0
Posts: 10
User Since: 24th Apr, 2011
System Score: N/A
Location: DE
Last edited on 17th Jul, 2014 21:28

Hello,
using Windows 8.1 - receiving PSI warning that MSXML 4.30.2117.0 (PSI: shown under details / version 3x) is insecure . The link (*see below) provided in this forum leads to Microsoft Core XML Services (MSXML) 6.0 which I have tried to install, successfully - as I have believed first. But is was only a short flash (popup) telling me that install was successful - which is not shown by the list of the installed programs / system. According to an advice I found in this forum I after that have installed KB2721691, obviously successful as it is duly shown in the list of installed programs on the system (sorry I do not know the term in English).
That list now shows three lines:
1. MSXML 4.0 SP3 Parser (KB2758694) 4.30.2117.0 - installed: 22. 03. 2013, impossible?: This Notebook was bought a couple of weeks ago. If I have understood correctly, that installation must have been requested by an "old" programme - but I have installed my programs only recently...
2. MSXML 4.0 SP3 Parser 4.30.2100.0 - installed 19. 06. 2014, which must have been done automatically by Windows Update as I cannot remember any such action by myself
3. MSXML 4.0 SP3 Parser (KB2721691), 4.30.2114.0 installed 17. 07. 2014 - as advised by PSI Forum.
After reboot PSI has been started afresh and done a full search - no change, still the same warning.
SO FINALLY: What must I do??? To be quite honest: I do not know and in this case PSI has been of no help so far.
So please do not give any explanations - just tell me how to act. Or shall I just tell PSI to ignore this problem / program? In the beginning I had done that, but soon I regretted...
Thank you!
By the way: It has been advised in this forum to upload screenshots - would have been an intelligent method - but I was unable to find how to. - And why version 3 of PSI makes it more difficult to go to details etc. I do not understand either.
Sorry, I should have updated my signature - as I have stated in the beginning, I am using Windows 8.1 now
*http://www.microsoft.com/en-us/download/details.as...

--
Windows 8.1 64 Bit; Windows 7 Home Premium 64 Bit; Windows Vista Business 32 Bit

Post "RE: MSXML" has been selected as an answer.
joelrosenberg RE: MSXML
Member 18th Jul, 2014 04:01
Score: 0
Posts: 1
User Since: 17th Jul 2014
System Score: N/A
Location: US
same problem here..tried everything
Was this reply relevant?
+0
-0
PRSONO9 RE: MSXML
Member 18th Jul, 2014 13:04
Score: -1
Posts: 18
User Since: 7th Jan 2012
System Score: N/A
Location: UK
I received the very same update and clicked on the link to update. However when I clicked download up popped 4 different files to download. I hadn't a clue which ones to download.
msxml 6_msi
msxml 6_ia.64msi
msxml 6_SKD.msi
msxml 6 x64.msi
I suppose the answer is all of them. I have a Windows 8.1 64bit system. Or maybe after reading this thread the answer is none of them. haha
Was this reply relevant?
+0
-0
Theophil RE: MSXML
Member 18th Jul, 2014 13:43
Score: 0
Posts: 10
User Since: 24th Apr 2011
System Score: N/A
Location: DE
As I had mentioned in the beginning I also have Win 8.1 and the installation using the link you quoted failed. Then I tried the link (see hereunder) which added another line to my list of installed programs (see my first entry). But PSI 3 was unimpressed, no change, still red. So after carefully reading all entries here in the forum referring to MSXML I have decided to click "ignore" since to me it seems that PSI in this case is issuing a warning which is unnecessary. It may be advisable, however, to proceed with this link, which was mentioned in this forum, too:
https://www.microsoft.com/en-us/download/details.a...
The execution of it leads to the installation of KB2721691 BUT is does not uninstall the original line in my list of installed programs (version 4.30.2117.0). So maybe somebody with more knowledge can tell me/us, whether THIS one should be uninstalled as it was THIS one marked EOL (nicht mehr verfügbar) in PSI 3. On the other hand if Microsoft had wanted to uninstall that version it would have done so I assume...

--
Windows 8.1 64 Bit; Windows 7 Home Premium 64 Bit; Windows Vista Business 32 Bit
Was this reply relevant?
+0
-0
PRSONO9 RE: MSXML
Member 18th Jul, 2014 14:15
Score: -1
Posts: 18
User Since: 7th Jan 2012
System Score: N/A
Location: UK
Last edited on 18th Jul, 2014 14:27
Many thanks like you I have clicked to ignore this update after reading all the other threads as well. I am only a novice in this but when I clicked to ignore this update I had a look at all the programs in Secunia and Microsoft XML Core Services ( MSXML) 6.30.9600.17041 is listed and no listing for MSXML 4.3. How did this happen. haha Did it update with a Windows Update? The Control Panel shows MSXML 4.0 SP3 Parser and MSXML 4.0 SP3 Parser KB2758694. No mention of MSXML 6
Was this reply relevant?
+0
-0
Anthony Wells RE: MSXML
Expert Contributor 18th Jul, 2014 22:27
Score: 2454
Posts: 3,345
User Since: 19th Dec 2007
System Score: N/A
Location: N/A

Hi ,

In my simple understanding of all the threads is that you need to have installed :-

MSXML 4.0 SP3 Parser (KB2758694) 4.30.2117.0

any/all earlier versions are said to be vulnerable/insecure and should be updated ASAP .

If you do not have MSXML 4.0 SP3 all well and good , I don't have on my newish W8.1.1 64bit .

It is not clear from M$ , Secunia nor even Maurice as to whether the above is really EOL or still has partially/extended support . At this stage it is probably not a good idea to create an ignore rule ; if you cannot make do with less than a 100% score in your PSI then delete it and wait for whichever of your programmes/software calls for it . Then decide or seek furhter advice .

W8.1.(1) comes with MSXML 6 and probably 3 already installed .

You can find them here :-

C:\Windows\WinSxS\wow64_microsoft-windows-msxml30_ 31bf3856ad364e35_6.3.9600.17120_none_83be0ec39f00f cfc\msxml3.dll, version 8.110.9600.17120
C:\Windows\SysWOW64\msxml3.dll, version 8.110.9600.17120

C:\Windows\WinSxS\amd64_microsoft-windows-msxml30_ 31bf3856ad364e35_6.3.9600.17120_none_796964716aa03 b01\msxml3.dll, version 8.110.9600.17120
C:\Windows\System32\msxml3.dll, version 8.110.9600.17120

for the 32 bit and 64 bit installs of 3 and for 6 :-

C:\Windows\SysWOW64\msxml6.dll, version 6.30.9600.17041

C:\Windows\System32\msxml6.dll, version 6.30.9600.17041

My PSI 2.0.0.3003 shows them as such and if you have them as well and your system is working then do not touch them ; they will be updated by M$/Windows when the time comes .

Using the 6 installer(s) that the PSI points to will try to offer a very old version of 6 which may or may not affect the above installs and so it should be avoided ; it has no chance of updating or doing anything else to 4 .

Hope that is clear enuff and non-teccy .

Take care

Anthony


--


It always seems impossible until its done.
Nelson Mandela
Was this reply relevant?
+1
-0
Maurice Joyce RE: MSXML
Handling Contributor 18th Jul, 2014 22:42
Score: 11830
Posts: 9,072
User Since: 4th Jan 2009
System Score: N/A
Location: UK
Last edited on 18th Jul, 2014 23:14
I have made my position crystal clear from the information I received from MS.

https://secunia.com/community/forum/thread/show/15...

--
Maurice

Windows 7 SP1 64 Bit OS
HP Intel Pentium i7
IE 11 for Windows 7 SP1
16GB RAM
Was this reply relevant?
+0
-0
PRSONO9 RE: MSXML
Member 18th Jul, 2014 23:43
Score: -1
Posts: 18
User Since: 7th Jan 2012
System Score: N/A
Location: UK
Yep understood many thanks.
Was this reply relevant?
+0
-0
Theophil RE: MSXML
Member 19th Jul, 2014 00:06
Score: 0
Posts: 10
User Since: 24th Apr 2011
System Score: N/A
Location: DE
Last edited on 19th Jul, 2014 00:08
The list of installed versions on my Windows 8.1:
1. MSXML 4.0 SP3 Parser (KB2758694) 4.30.2117.0
2. MSXML 4.0 SP3 Parser 4.30.2100.0
3. MSXML 4.0 SP3 Parser (KB2721691), 4.30.2114.0

Please, advise: Anything to be uninstalled - or added?

--
Windows 8.1 64 Bit; Windows 7 Home Premium 64 Bit; Windows Vista Business 32 Bit
Was this reply relevant?
+0
-0
muffin1945 RE: MSXML
Member 19th Jul, 2014 00:11
Score: 0
Posts: 6
User Since: 5th Apr 2013
System Score: N/A
Location: US
My Secunia PSI is also showing that I should do a manual update. I subscribe to Windows automatic updates. I'll wait until MS gives me this update. When I click on the link for that manual update, it takes me to a MS page and lists which operating systems it is for. My operating system is not listed. I have Windows 7 Professional, SP 1. The Microsoft website says the latest version for Windows 7 is MSXML 4.0 SP3, which is what I have. As I said, I'll wait for Microsoft Windows update to give me this.


--
muffin
Was this reply relevant?
+0
-0
Theophil RE: MSXML
Member 19th Jul, 2014 00:20
Score: 0
Posts: 10
User Since: 24th Apr 2011
System Score: N/A
Location: DE
@ Maurice Joyce - Sorry I forgot so say that I would like especially YOUR advice:

The list of installed versions on my Windows 8.1:
1. MSXML 4.0 SP3 Parser (KB2758694) 4.30.2117.0
2. MSXML 4.0 SP3 Parser 4.30.2100.0
3. MSXML 4.0 SP3 Parser (KB2721691), 4.30.2114.0

Please, advise: Anything to be uninstalled - or added?


--
Windows 8.1 64 Bit; Windows 7 Home Premium 64 Bit; Windows Vista Business 32 Bit
Was this reply relevant?
+0
-0
Maurice Joyce RE: MSXML
Handling Contributor 19th Jul, 2014 02:13
Score: 11830
Posts: 9,072
User Since: 4th Jan 2009
System Score: N/A
Location: UK
It looks like Secunia are not going to help further.

There are numerous threads running on this fiasco created by Secunia - I will try to cobbled something together tomorrow that hopefully will help you & others who remain confused.

In the meantime I suggest you & others do nothing - some of the advice given by Secunia is misleading & a complete waste of time.

--
Maurice

Windows 7 SP1 64 Bit OS
HP Intel Pentium i7
IE 11 for Windows 7 SP1
16GB RAM
Was this reply relevant?
+9
-0
muffin1945 RE: MSXML
Member 19th Jul, 2014 02:45
Score: 0
Posts: 6
User Since: 5th Apr 2013
System Score: N/A
Location: US
Thank you so much, Maurice. Look forward to your note tomorrow.

--
muffin
Was this reply relevant?
+0
-0
pwillener1 RE: MSXML
Member 19th Jul, 2014 07:15
Score: 0
Posts: 20
User Since: 25th Jul 2012
System Score: N/A
Location: JP
What confuses me most is that
- Microsoft XML Core Services (MSXML) 4.x [4.30.2117.0] is marked as EOL.

However
- Microsoft XML Core Services (MSXML) 3.x [8.110.7601.18431] is OK?
Was this reply relevant?
+0
-0
taffy078 RE: MSXML
Contributor 19th Jul, 2014 08:25
Score: 408
Posts: 1,352
User Since: 26th Feb 2009
System Score: 100%
Location: UK
on 19th Jul, 2014 02:13, Maurice Joyce wrote:
It looks like Secunia are not going to help further.

There are numerous threads running on this fiasco created by Secunia - I will try to cobbled something together tomorrow that hopefully will help you & others who remain confused.

In the meantime I suggest you & others do nothing - some of the advice given by Secunia is misleading & a complete waste of time.


I'm so glad that I'm coming into this late (my scans run on Saturdays) rather than at the start of the many threads on this debacle.
I too have the message that my v4.30.2117.0 is end of life.

I'm looking forward to Maurice's suggestions - thanks, Maurice.

(PS These threads triggered deju vu - I was sure it had happened to me before and so it had. It was Maurice who provided the solutions two years ago:
http://secunia.com/community/forum/thread/show/131...)

--
taffy078, West Yorkshire, UK

Desktop: Compaq Presario (OEM) 32 bit / AMD Athlon / 2 GB RAM
XP Home - SP3/ IE8/ Norton IS - Secunia PSI v2.0.0.3003

Laptop: Win 7 / IE11 / PSI v2.0.0.3003
Was this reply relevant?
+0
-0
qwerty_y2k RE: MSXML
Member 19th Jul, 2014 13:17
Score: 1
Posts: 1
User Since: 19th Jul 2014
System Score: N/A
Location: US
Here's what worked for me.

Since the file PSI is complaining about is a 32 bit file found in C:\Windows\SysWOW64\ I went hunting in the 32-bit uninstall section of the registry. HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\Cur rentVersion\Uninstall\

I then searched for anything that had XML in it. I found five results. I didn't write down what each of them was but if I recall it started with a couple results from the the XML 4.0 SP3 parser and the other results were from the XML 4.0 SP2 parser. I uninstalled them using the uninstall string found in the registry for each item. After the last one was removed the msxml4.dll and msxml4r.dll files were gone from C:\Windows\SysWOW64\.

Here are the 5 items I removed from my system. YMMV

MsiExec.exe /x{196467F1-C11F-4F76-858B-5812ADC83B94}

MsiExec.exe /X{1D95BA90-F4F8-47EC-A882-441C99D30C1E}

MsiExec.exe /X{355B5AC0-CEEE-42C5-AD4D-7F3CFD806C36}

MsiExec.exe /X{86493ADD-824D-4B8E-BD72-8C5DCDC52A71}

MsiExec.exe /X{F662A8E6-F4DC-41A2-901E-8C11F044BDEC}
Was this reply relevant?
+1
-0
Erik M RE: MSXML
Member 19th Jul, 2014 15:19
Score: -2
Posts: 3
User Since: 19th Jul 2014
System Score: N/A
Location: N/A
Last edited on 19th Jul, 2014 15:22
After removing MSXML 4.0 SP3 Parser 4.30.2100.0 and every KB related to it, Secunia still reported
msxml4.dll.
Then decided to remove the file manualy.
Secunia reported file removed succesfully.
I was a little bit concerned why the uninstall didn't remove the file. Was it somehow not related to MSXML4.0?
I think I found the answer after I wanted to scan something with my HP software.
I received errors, but never the less I could finish the scan.
Just out of curiousity I decided to replace the msxml4.dll file. The error went away, so I guess this file is needed for my scanning software.
I realy want to know how dangerous this file is and if there is no other solution.

My HP Officejet J6410 All-in-One which is not supported by HP anymore, but still works perfectly on my Win7 X64 system, except for one stupid error message that doesn't matter, because everything works fine.
Removing this one file just adds another error message, but in the end there is nothing wrong with my scan.
Was this reply relevant?
+0
-0
ddmarshall RE: MSXML
Dedicated Contributor 19th Jul, 2014 17:58
Score: 1212
Posts: 968
User Since: 8th Nov 2008
System Score: 98%
Location: UK
@Erik M

How dangerous is this file?

There are no documented vulnerabilities in the latest version of this file - 4.30.2117.0.

Other versions of MSXML were patched in June 2014.
https://technet.microsoft.com/en-us/library/securi...
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=...

It is possible MSXML 4.0 has the same vulnerability which is an information disclosure.
Victim browses to a malicious webpage or opens a malicious document, inadvertently sending local path name of downloaded file to attacker. Path name by default includes the user’s login name.

--
This answer is provided “as-is.” You bear the risk of using it.
Was this reply relevant?
+2
-0
inahut RE: MSXML
Member 19th Jul, 2014 18:31
Score: 7
Posts: 12
User Since: 19th Jul 2014
System Score: N/A
Location: US
I have researched this problem on my own
I have examined the information MS provides about differing versions of MSXML
MS shows the differing versions are not directly incompatable
MS recommends installation of newest version
Newest version is 6.0
When one finds its exact location within the Windows directory one can see the versions listed in order, in my case as msxml3...4...6
The installation date I find for my msmxml6.dll and msxml6r.dll is 3-26-2014, as a result of MS update itself
I find the information provided by Maurice Joyce in this thread and in the thread titled "MSXML" to be more accurate than any information provided by Secunia voices
My research shows that Maurice Joyce in describing this problem in terms used by MS itself without leaving out any important variable or factor
In these two threads the voices representative of Secunia are not reproducing the information provided by MS in a completely accurate way.
I have followed the links and read the information to the best of my abiltiy
When I encountered Maurice Joyce's synthesis of the information it rang true and help me see the error being produced by Secunia PSI is incorrect, erroneous and at this point in time it is quite aggravating.
I have yet to uninstall Secunia but I must protest to Secunia that they need to stop this now.
Was this reply relevant?
+0
-0
taffy078 RE: MSXML
Contributor 20th Jul, 2014 08:47
Score: 408
Posts: 1,352
User Since: 26th Feb 2009
System Score: 100%
Location: UK
Last edited on 20th Jul, 2014 08:52
in case it's relevant (I haven't got a clue - this is so confusing):

PSI reported Microsoft XML Core Services (MSXML) 4.x as End-of-Life.
Detected version: C:\\Windows|SysWOW\msxml4.dll, version 4.30.2117.0


PSI advises :Latest version - patching one or more vulnerabilities: 6.x

So I looked at where the "rougue/offending file" is and found that I also have the following:

msxml3.dll
msxml3r.dll
msxml4a.dll
msxml6.dll
msxml6r.dll

It would be reasonable, perhaps logical, even, for a layman to presume that
(1) the two v3 and the one v4 files are also End-of-Life. But they've not been detected. Are they EoL?
(2) I don't need to download v6. Should I? Does the latest downloads install two v6 files?

I'm ignoring all the other threads - no disrespect intended, but I'd prefer to wait for Maurice to deliver the solution.

Edits: to tidy up

--
taffy078, West Yorkshire, UK

Desktop: Compaq Presario (OEM) 32 bit / AMD Athlon / 2 GB RAM
XP Home - SP3/ IE8/ Norton IS - Secunia PSI v2.0.0.3003

Laptop: Win 7 / IE11 / PSI v2.0.0.3003
Was this reply relevant?
+0
-0
Maurice Joyce RE: MSXML
Handling Contributor 20th Jul, 2014 09:35
Score: 11830
Posts: 9,072
User Since: 4th Jan 2009
System Score: N/A
Location: UK
Last edited on 20th Jul, 2014 09:38
@taffy078

Your assumption is NOT correct - leave MSXML3 alone - it is a component of all variants of Windows.

I am still trying to put together some ideas that hopefully will help users choose a course of action that best meets there needs.

There is NO SECURITY issue UNLESS someone has MSXML4 SP2 installed.

--
Maurice

Windows 7 SP1 64 Bit OS
HP Intel Pentium i7
IE 11 for Windows 7 SP1
16GB RAM
Was this reply relevant?
+2
-0
Theophil RE: MSXML
Member 20th Jul, 2014 18:00
Score: 0
Posts: 10
User Since: 24th Apr 2011
System Score: N/A
Location: DE
Thank you very much indeed, Maurice, so I feel to be on the safe side - but I am only too keen to read what you will add further to the subject.

--
Windows 8.1 64 Bit; Windows 7 Home Premium 64 Bit; Windows Vista Business 32 Bit
Was this reply relevant?
+0
-0
PRSONO9 RE: MSXML
Member 20th Jul, 2014 18:10
Score: -1
Posts: 18
User Since: 7th Jan 2012
System Score: N/A
Location: UK
It's all been very intersting if confusing to those not so well clued up.
Was this reply relevant?
+0
-0
Maurice Joyce RE: MSXML
Handling Contributor 20th Jul, 2014 21:33
Score: 11830
Posts: 9,072
User Since: 4th Jan 2009
System Score: N/A
Location: UK
@Theophil,
As promised I have created a post that I hope you find helpful - I have posted it to here so that Secunia get all the follow up emails rather than you.

https://secunia.com/community/forum/thread/show/15...

@taffy078
Enjoy the doodle if nothing else - Secunia did not respond!

--
Maurice

Windows 7 SP1 64 Bit OS
HP Intel Pentium i7
IE 11 for Windows 7 SP1
16GB RAM
Was this reply relevant?
+3
-0

PRSONO9

RE: MSXML
[+]
This reply has been deleted
Theophil RE: MSXML
Member 21st Jul, 2014 00:46
Score: 0
Posts: 10
User Since: 24th Apr 2011
System Score: N/A
Location: DE
@Maurice
Thank you for your clarification - but please bear with me, I am still confused.
As mentioned, these are my versions:
The list of installed versions on my Windows 8.1:
1. MSXML 4.0 SP3 Parser (KB2758694) 4.30.2117.0
2. MSXML 4.0 SP3 Parser 4.30.2100.0
3. MSXML 4.0 SP3 Parser (KB2721691), 4.30.2114.0
I only had 1 and 2 until the Secunia mess started.
Then I found this link http://www.microsoft.com/en-us/download/details.as...
saying: A security issue has been identified in Microsoft XML Core Services (MSXML) that could allow an attacker to compromise your Windows-based system and gain control over it.
I was convinced, and after installation line 3 appeared.
Now, here https://secunia.com/community/forum/thread/show/15... you say "If MSXML 4 is also present it MUST show as 4.30.2117.0 to be SECURE."
Please bear with me. Am I right that the statements by MS and yourself somehow are contradicting? Am I right in assuming that version 4.30.2114.0 should be retained - and the other two deleted / uninstalled?
Sorry, I am not experienced in these matters so I do depend on your advice since Secunia is of no help at all. I am just lucky that my Windows 8.1 is still working as I on the advice of Secunia have tried to install version MSXML 6...

--
Windows 8.1 64 Bit; Windows 7 Home Premium 64 Bit; Windows Vista Business 32 Bit
Was this reply relevant?
+0
-0
steffens RE: MSXML
Member 21st Jul, 2014 01:05
Score: 49
Posts: 64
User Since: 25th Jul 2009
System Score: N/A
Location: US
I'll leave it to Maurice to supply the definitive answer. Until then, this might help...

According to https://technet.microsoft.com/library/security/ms1... update KB2757638 replaces (i.e., supersedes) update KB2721691 for systems running MSXML4.

So... If you already have KB2757638 installed, then you do NOT need KB2721691.

(You could remove KB2721691. But leaving it installed probably won't cause any problems.)
Was this reply relevant?
+0
-0
Maurice Joyce RE: MSXML
Handling Contributor 21st Jul, 2014 01:05
Score: 11830
Posts: 9,072
User Since: 4th Jan 2009
System Score: N/A
Location: UK
You are stating MSXML 4.0 SP3 Parser (KB2758694) 4.30.2117.0 is installed so you are OK.

If you intend using MSXML 4 then my advice is to leave everything as it stands at the moment just like I have.

If Windows considers any of those files surplus to requirement it should clean them up the next time you run the Windows Update Clean Up Tool. It has certainly never cleaned up any of them for me & I run the tool nightly by schedule.

As stated if MSXML3 & 6 are showing in PSI as present & up to date you are OK & no harm has been done.

--
Maurice

Windows 7 SP1 64 Bit OS
HP Intel Pentium i7
IE 11 for Windows 7 SP1
16GB RAM
Was this reply relevant?
+1
-0
steffens RE: MSXML
Member 21st Jul, 2014 01:13
Score: 49
Posts: 64
User Since: 25th Jul 2009
System Score: N/A
Location: US
on 21st Jul, 2014 01:05, steffens wrote:
I'll leave it to Maurice to supply the definitive answer. Until then, this might help...

According to https://technet.microsoft.com/library/security/ms1... update KB2757638 replaces (i.e., supersedes) update KB2721691 for systems running MSXML4.

So... If you already have KB2757638 installed, then you do NOT need KB2721691.

(You could remove KB2721691. But leaving it installed probably won't cause any problems.)


Sorry... Copy-and-paste error. "KB2757638" in the above ahould read "KB2758694". [KB2757638 relates to MSXML6.]

(Tried to edit my post inline, but it failed... apparently I waited too long, or perhaps edits aren't permitted after someone else posts to the thread.)
Was this reply relevant?
+0
-0
Theophil RE: MSXML
Member 21st Jul, 2014 03:41
Score: 0
Posts: 10
User Since: 24th Apr 2011
System Score: N/A
Location: DE
Last edited on 21st Jul, 2014 03:45
OK, guys, this is it - thank you so much for your endurance and patience, quite incredible, I really appreciate your assistance!
So I leave it as it is trusting that everything is fine as it stands. I have set PSI 3 to ignore MSXML:

As a matter of interest:
As far as timing is concerned it seems to be impossible to find out which of my programmes is relying on MSXML. When I bought this Laptop MSXML 4.0 SP3 Parser (KB2758694 was already installed. In the middle of June i. e. time of purchase of this machine I obviously had to install all my programs used on the previous Laptop. But at the same time all Windows Updates were installed. Somewhere along this process MSXML 4.0 SP3 Parser / 4.30.2100.0 appears in the list of installed programs. In the end - as reported - I forced KB2721691 - 4.30.2114.0 to be installed.
But as I said this is just for interest sake and according to your statements does cause no concern.

Finally: Do you suggest that I close this thread now?



--
Windows 8.1 64 Bit; Windows 7 Home Premium 64 Bit; Windows Vista Business 32 Bit
Was this reply relevant?
+0
-0
Maurice Joyce RE: MSXML
Handling Contributor 21st Jul, 2014 08:31
Score: 11830
Posts: 9,072
User Since: 4th Jan 2009
System Score: N/A
Location: UK
You should be perfectly OK with your current set up. If you want to stop update emails I would relock the thread or I can do it for you.

@taffy078 can still read all the detail & respond to the other thread if needed.

--
Maurice

Windows 7 SP1 64 Bit OS
HP Intel Pentium i7
IE 11 for Windows 7 SP1
16GB RAM
Was this reply relevant?
+1
-0

This thread has been marked as locked.


 Products Solutions Customers Partner Resources Company
 
 Corporate
Vulnerability Intelligence Manager (VIM)
Corporate Software Inspector (CSI)
Consumer
Personal Software Inspector (PSI)
Online Software Inspector (OSI)
 Industry
Compliance
Technology
Integration
 Customers
Testimonials
 MSSP
Technology Partners
References
 Reports
Webinars
Events
 About us
Careers
Memberships
Newsroom


Secunia is a member of FIRST Secunia is a member of EDUcause Secunia is a member of The Open Group Secunia is a member of FS-ISAC
 
Secunia © 2002-2014 Secunia ApS - Rued Langgaards Vej 8, 4th floor, DK-2300 Copenhagen, Denmark - +45 7020 5144
Terms & Conditions and Copyright - Privacy - Report Vulnerability - Disclaimer
follow Secunia on Facebook follow Secunia on Twitter follow Secunia on LinkedIn follow Secunia on YouTube follow Secunia Xing follow Secunias RSS feed follow Secunia on Google+