4 replies to this topic

[bagerlk]

Hi, after upgrading my XP release today all went well however although the release shows as True, AutoPatcher deteced and Unofficial release. Upon investigation, it noticed the following stray folders and files:

\modules\Components\__msxml\MSXML3_ptb.apm_files
- WindowsXP-KB955069-x86-ENU.exe

\modules\Components\__msxml\MSXML6SP1_x86_files
- WindowsXP-KB954459-x86-ENU.exe

When I deleted both folders and both files my release showed as True and Official. I think these need to be added to the cleanup routine?

[_def_x_]

I'm not exactly sure what is going on here, but I do know the XP release will be undergoing a few script changes
as it moves around some updates, but you shouldn't need to remove MSXML 6 from the release, and MSXML 3 ptb
I wouldn't figure to see in an ENU release. We will get it sorted out.

Also, after updating XP SP3 ENU, I have an extra file / folder in my release...

\XP.SP3\modules\Components\__msxml\msxml4_sp3_files
...MSXML4SP3_enu.apm_files - another folder of the same name w/ msxml.msi in it
...msxml.msi

Thanks for the report.

Followup:
After removing the extra "MSXML4SP3_enu.apm_files" folder the release is Official.

Also, all users please be aware - we will be moving updates from "Critical" and "NonCritical" folders etc to the appropriate
"Components" folder, as you can see with the _msxml files. It may not be a smooth transition, we will need your feedback
to work out any bugs - thanks in advance for your reports.

Here are a few examples from the log file...

Executing shell command: move /y 
"G:\AP\XP.SP3\modules\Critical\KB954459_xp_sp3_x86_enu.apm_files" "G:\AP\XP.SP3\modules\Components\__msxml\MSXML6SP1_x86_files"

Executing shell command: move /y 
"G:\AP\XP.SP3\modules\Critical\KB955069_xp_x86_enu.apm_files" "G:\AP\XP.SP3\modules\Components\__msxml\MSXML3_ptb.apm_files"

Executing shell command: move /y 
"G:\AP\XP.SP3\modules\Components\__msxml\MSXML4SP3_enu.apm_files" "G:\AP\XP.SP3\modules\Components\__msxml\msxml4_sp3_files"

Mike

[bagerlk]

Before I deleted the folders and their contents, the entire contents of my \modules\Components\__msxml folder was:

\MSXML3_enu.apm_files
\MSXML3_ptb.apm_files
\msxml4_sp3_files
\MSXML6SP1_enu.apm_files
\MSXML6SP1_x86_files
MSXML3_enu.apm
msxml4_sp3_enu.apm
MSXML6SP1_enu.apm

As for the \MSXML3_ptb.apm_files folder, it contained an English installer (WindowsXP-KB955069-x86-ENU.exe) so I'm confused there also.

Additionally, before I ran apup today, my release still showed up as True and Official from my previous apup run late last month. In fact, the date I last ran apup was Friday, 29 May 2009 and both the suspect folders have this same date stamp. The MSXML6SP1_enu.apm_files folder for instance had today Monday, 22 June 2009 as the date stamp.

Anyway, like I said, deleting the two folders and their contents makes the release True and Official so I'm happy for now ;o)

Edited by bagerlk, 22 June 2009 - 03:03 AM.

[_def_x_]

Please see my Followup: comments above. You will want to run apup.exe /log regularly over the next few days and
report errors/mixups etc if you would like to help. If all goes as planned, we will also be moving media player files
around as well, these needed changes are long overdue.

[Cristiano]

issue related to the wrong move fixed. no additional download will be required, just an minor adjust at the name of the module folder

thanks for your report

[]s