XP Pro w/SP3 > AutoPatcher > Microsoft Windows - Updated Components >
Microsoft XML Parser (MSXML) is black with NO submenu and the Item Description says: MSXML component updates. Its recommended that you install all of these updates. What updates?
I ask this because I checked the appropriate APM file and found:
[DetectionRegistry]
RegistryPath=
KeyName=
KeyValue=
[DetectionFile]
FilePath=
FileName=
FileVersion=
[OperatingSystem]
WindowsVersion=2K,XP_SP1,XP_SP2,XP_SP3,XP_MCE2004_X86,XP_MCE2005_X86,2K3,VISTA,LHSERVER
SystemLanguage=ANY
What, if anything, is being checked?
I checked Add or Remove Programs and it lists:
Microsoft XML 4.0 SP3 Parser (KB2721691) - 4.30.2114.0
Microsoft XML 4.0 SP3 Parser (KB973685) - 4.30.2107.0
Microsoft XML 6.0 Parser (KB927977) - 6.00.3890.0
5 replies to this topic
#1
Posted 01 January 2013 - 05:51 AM
#2
Posted 01 January 2013 - 09:02 AM
DesertJerry --- done research regarding the updates Microsoft XML 4.0 SP3 Parser (KB973685), Microsoft XML 6.0 Parser (KB927977) were superseded in July 2012..
They were replaced by Microsoft XML 4.0 SP3 Parser (KB2721691) and Security Update for Windows XP (KB2719985)..
The updates are no longer in Components\__msxml, now placed in Critical as they are Security Updates as described by Microsoft..
Checked in my Windows XP x86 and only KB2721691 is listed in add and remove programs
They were replaced by Microsoft XML 4.0 SP3 Parser (KB2721691) and Security Update for Windows XP (KB2719985)..
The updates are no longer in Components\__msxml, now placed in Critical as they are Security Updates as described by Microsoft..
Checked in my Windows XP x86 and only KB2721691 is listed in add and remove programs
#3
Posted 02 January 2013 - 10:38 PM
OK - I can accept the info above as accurate - but that does not explain why I got what I got when running AutoPatcher and why the APM file had nothing in [Detection***]
#4
Posted 03 January 2013 - 12:37 AM
If you're talking about __msxml.apm...
It's a dummy apm file to create a subcategory (MSXML Parent) in \Components (Components Parent) for display purposes in AutoPatcher. You had nothing to tick because there were no updates, actually no update apm files - they were removed.
A clue is to look under [Behavior] in the apm file:
ParentID=XXX_XXX_PARENT == main_category.
UniqueID=XXX_XXX_PARENT == sub_category.
It's a dummy apm file to create a subcategory (MSXML Parent) in \Components (Components Parent) for display purposes in AutoPatcher. You had nothing to tick because there were no updates, actually no update apm files - they were removed.
A clue is to look under [Behavior] in the apm file:
ParentID=XXX_XXX_PARENT == main_category.
UniqueID=XXX_XXX_PARENT == sub_category.
#5
Posted 03 January 2013 - 06:05 AM
DesertJerry .. it seems your APUP/AP may still have a few rogue files...checked 3 different backups an none of them have __msxml.apm or the msxml folder...theses can be deleted.
Check your APUP directory for modules\Components\__msxml .. delete
For __msxml.apm delete from modules\Components
Check your APUP directory for modules\Components\__msxml .. delete
For __msxml.apm delete from modules\Components
#6
Posted 03 January 2013 - 06:39 AM
Deleted _msxml.apm - will see if it gets re-installed in the future. Started AutoPatcher and it appears to list everything else OK.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users












