Relating to this vendor:
And, this specific program:
Microsoft XML Core Services (MSXML) 4.x
|woodyleonhard||MSXML 4.0 update|
|17th May, 2014 23:37|
User Since: 17th May, 2014
System Score: N/A
I'm reading the Secunia PSI country vulnerability reports and seeing that, every quarter, a vulnerability in MSXML appears at the top of the US list.
The problem, as best I can tell: MSXML 4 is up to Service Pack 3, but Windows Update no longer scans for the presence of MSXML 4, which hit end of life long ago. Secunia has a note about it here:
Multiple versions of MSXML co-exist on many machines. Unfortunately, because of dependencies hard coded into many third-party programs, you can't just delete older versions.
I'm searching for a simple, cookbook recipe for solving the problem. Here's the best I've been able to come up with:
1. Scan the registry for the key
2. If "4.0" is listed as a Name under that key, then
3. Manually install MSXML 4.0 SP 3 from http://www.microsoft.com/en-us/download/details.as...
Note how that sweeps a whole lot of details under the rug: Whether you have 4.1/SP1 or 4.2/SP2 installed, for example. The only glitch I can see is if the Windows user has the MSXML 4.0 SP3 beta installed; in that case, they need to manually remove the beta. (Not sure how.)
Does anybody know if the steps here will work, and not clobber anything in the process?
|Maurice Joyce||RE: MSXML 4.0 update|
|18th May, 2014 10:52|
User Since: 4th Jan 2009
System Score: N/A
Last edited on 18th May, 2014 12:34
|If you have MSXML4 SP1 or SP2 installed there is a simple tried & tested method to update to a safer version.
Download and install SP3 from here:
Select the msxml.msi - 2.3 MB file.
After the install reboot.
Now run a manual Windows Update scan & any updates for SP3 will be revealed that requires installation.
Once complete run a full PSI scan & you should see this:
Microsoft Surface 4 Intel i7 64Bit
Windows 10 Pro version 1607 Build 14393.321
16 GB RAM
IE & Edge Only