The system returned: (22) Invalid argument The remote host or network may be down. A lot of PSI users rely on it to guide them when they are not computer gurus, but in this case, Secunia seems to be leading some of these people astray. All rights reserved. It only applies to Windows before XP SP3. Check This Out
Did a normal (re)"Check for Updates" in Windows Update and am getting the normal "Windows is up to date" . . . If you did install this download it would possibly overwrite the Windows 7 version. If MSXML is only for developers, then why do we even have it if we are not developers?
Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it. The purported problem file is: Microsoft XML Core Services (MSXML) 4.x C:\Windows\SysWOW64\msxml4.dll, version 4.30.2117.0 Clicked the "Microsoft Update" at the end of that line in PSI which led to the following ERROR The requested URL could not be retrieved The following error was encountered while trying to retrieve the URL: http://0.0.0.4/ Connection to 0.0.0.4 failed. According to this forum, that version is current.
It appears that something may be missing from the Secunia instructions. This is further supported by the official Microsoft Lifecycle Policy found here: http://support.microsoft.com/lifecycle/search/defa... Windows XP is no longer supported and at EOL also. https://www.microsoft.com/en-us/download/details.aspx?id=15697 This is further supported by the official Microsoft Lifecycle Policy found here: http://support.microsoft.com/lifecycle/search/defa...
I restored the .dll of MSXML 4 and ran the restore of my backup and everything is back to normal. What is the harm in leaving it on our systems? The download is intended for prior systems. (Source: http://msdn.microsoft.com/en-us/library/jj152146(v=vs.85).aspx) I don't know if installing the download would cause any damage but each subsequent version of Windows has a copy of msxml6.dll Several functions may not work.
What does MSXML do to my computer? If you continue using our website, we'll assume that you are happy to receive all cookies on the Secunia website. Stay Connected RSS YouTube Twitter LinkedIn Xing Weibo What We Do Software License Optimization Application Readiness Software Vulnerability Management Installation Software Monetization Company Contact Us About Flexera Software Website Feedback Site It only applies to Windows before XP SP3.
PULL YOUR HEADS OUT OF YOUR ASSES AND ADDRESS THIS SITUATION! Click finish to exit." window. I ran a backup just in case and created a restore point and then went and deleted the MSXML 4 file or .dll and uninstalled it with Revo and rebooted. Clicked the Download button there, selectecd "msxml6_x64.msi", downloaded and installed it and got a "Setup has installed MSXML 6.0 Parser successfully.
Your cache administrator is webmaster. I am not going to spend hours/days reinstalling Windows 7 and all my programs just because Secunia told me to uninstall something that can stay. As a result, all versions of Microsoft XML Core Services (MSXML) 4.x will correctly be flagged as EOL by the Secunia products, recommending an upgrade to Microsoft XML Core Services (MSXML) this contact form The lack of any mention of MSXML 4.0 suggests that Microsoft have abandoned it.
This question is strictly for purposes of updating the application. Look at the system requirements. Why is Secunia routing me to a download page for MSXML 6, but they don't tell me which is appropriate for my system. Was this reply relevant?+1-0 ddmarshall RE: Microsoft Core XML Services (MSXML) 4.X 16th Jul, 2014 11:10 Score: 1250Posts: 992User Since: 8th Nov 2008System Score: 98%Location: UK Thanks for the update.
This is not good. * Is Secunia going to fix this? * Is Secunia going to repeat this sort of dangerous advice with other software? This is similar to the dozens of times that Chrome has renamed its old file with "old" and PSI thinks it is still a working exe file, ignores any new file I too just clicked on the link in Secunia PSI 2.0 for the MSXML 4.x end-of-life and it most certainly does take you to the MS page to download version 6. navigate here The first thing I did was look at the System Requirements.
Windows since XP SP3 contains MSXML 6.0 as part of the OS . Great warning. It is calling for updates to Windows 2000 Service Pack 4, Windows Server 2003, Windows Server 2003 Service Pack 1, Windows XP Service Pack 1, Windows XP Service Pack 2 . I guess what I'm getting at is my machine was broke.
Was this reply relevant?+1-1 ddmarshall RE: Microsoft Core XML Services (MSXML) 4.X 16th Jul, 2014 09:56 Score: 1250Posts: 992User Since: 8th Nov 2008System Score: 98%Location: UK I suspect this has come Please give us more direction to follow that will not harm anyone's systems. The security bulletin refers to MSXML 3.0, 5.0 and 6.0. Now, a few days later, I find this present thread on the Forum, warning me that I could damage my system if I download and install the very update that Secunia
Jump to content FacebookTwitter Geeks to Go Forum Operating Systems Windows XP, 2000, 2003, NT Welcome to Geeks to Go - Register now for FREE Geeks To Go is a helpful 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 locked. Continue Secunia Research Community Products Services Resources Free Trials Purchase Support Company Login VIM 4 CSI 7 Community Self-service Portal Partner Portal Overview Advisories Research Forums Create Profile Advisories Research Forums If the wrong version of msxml6.dll is present, running the System File Checker may restore the correct version.
Seriously. The advice to update to MSXML 6.0 is intended for developers. There were four files --- one didn't work, but the other three did. Was this reply relevant?+0-0 inahut RE: Microsoft Core XML Services (MSXML) 4.X 19th Jul, 2014 19:07 Score: 9Posts: 12User Since: 19th Jul 2014System Score: N/ALocation: US I have researched this problem
End users with applications build to target MSXML 4.0 cannot simply remove MSXML 4.0 and expect the applications to continue working with the built in MSXML 6.0 present in all currently What am I supposed to do about this and if any, which one am I supposed to download for my system to replace the end of life? 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 But why does Secunia still showing the vulnerability after installing v6 and then rebooting?