18 replies to this topic

[ChrisG_UK]

Hi,

Sorry if this is a stupid question, but I have done my best to research this. I have been using AutoPatcher for a while, and it seems to work fine, but I would like to understand this "Unofficial/Unsupported Release" business.

I made a clean install and get exactly the same issue. I'm using XP with SP3. Here is what I just did to reproduce the problem on a brand new install:

Install and run apup and tick the following:
AutoPatcher Updater
AutoPatcher Engine
AutoPatcher Common Modules
AutoPatcher for Windows XP SP3 (x86) English
AutoPatcher for Office XP (English)

Apup downloads about 525Mb of stuff. I don't see any errors in the apup.log file.

I then run AutoPatcher and get the red "Unofficial/Unsupported Release" message. The AutoPatcher.log file contains lots of error messages:

Module 'E:\AutoPatcher2\modules\Critical\WindowsXP-KB2722913-x86-ENU.apm' implicitly refers to its module folder as 'E:\AutoPatcher2\modules\Critical\WindowsXP-KB2722913-x86-ENU.apm_files'. However, such folder does not exist!
Module 'E:\AutoPatcher2\modules\Critical\WindowsXP-KB2722913-x86-ENU.apm' implicitly refers to its module folder as 'E:\AutoPatcher2\modules\Critical\WindowsXP-KB2722913-x86-ENU.apm_files'. However, such folder does not exist!

UNOFFICIAL: File 'E:\AutoPatcher2\modules\Components\UserProfileHiveCleanup.apm' (mentioned by RTI 'C:\#AutoPatcher_Temp#\xp_sp3_enu.rti') does not exist!

Then there are 574 instances of the following message for different files:

UNOFFICIAL: File 'E:\AutoPatcher2\modules\....apm' was found, but not mentioned by any RTI!

and finally:


Module 'Cumulative Security Update for Internet Explorer 8 for Windows XP (KB2722913)' (unique id: 'IE8_KB2722913_XP_SP3_X86_ENU') cannot be loaded because it's uniqueID is duplicate (the module named 'Cumulative Security Update for Internet Explorer 8 for Windows XP (KB2722913)' also uses it).

Am I doing something wrong?

Many thanks.

[Whatacrock]

Welcome to the forums.
The unoffical/Unsupported version is the result of files that have been changed or deleted by Microsoft from their servers, this is typically done with updates that are cumulative as the update has been superseded.
It should be know that the program will install the updates that you have downloaded.
A piece of advice when you download the releases in apup...download the releases twice..this double checks that all downloads are correct and giving a better listing of the log of files which are incorrect

Usually if there is a problem with the downlo0ads you will receive one or more files have failed validation.

[ChrisG_UK]

Thanks for the response, but 574 errors? I have downloaded several times and always get the same errors.

[Whatacrock]

Just how many releases were you downloading to receive that many errors?? Hope you didn't do them all on a single run


A suggestion when downloading releases and this works well for me is that only one or two releases at a time then rerun the updater again,check the log when completed and make a copy of the log for reporting here.
Once clear then move onto the next couple of downloads repaet the process until you get the releases that you require.

@ChrisG_UK.....any chance of which releases you downloaded...

Edited by Whatacrock, 03 October 2012 - 01:38 PM.

[ChrisG_UK]

Hi, sorry for the delay, there doesn't seem to be an option to get emails when the thread is updated.

I just did exactly what I said in my original post:


Install and run apup and tick the following:
AutoPatcher Updater
AutoPatcher Engine
AutoPatcher Common Modules
AutoPatcher for Windows XP SP3 (x86) English
AutoPatcher for Office XP (English)

Apup downloads about 525Mb of stuff. There are no errors in the apup.log file.

I think that possibly one of the problems I am suffering from is that there is no user guide. I'm sure this is all terribly obvious to you but I'm a bit lost without one.

It's ok, it all seems to work fine, I can live with the Unofficial/Unsupported Release message.

[_def_x_]

ChrisG_UK said:

Hi,

Sorry if this is a stupid question, but I have done my best to research this. I have been using AutoPatcher for a while, and it seems to work fine, but I would like to understand this "Unofficial/Unsupported Release" business.

For a brief explanation of the error see this post (the FYI bit mostly) - http://www.autopatch...dpost__p__12663

Also, please follow the link to log file stickies, read both. It is difficult to nail down issues when users edit their log files, the directions in the stickies are clear.

ChrisG_UK said:

I made a clean install and get exactly the same issue. I'm using XP with SP3. Here is what I just did to reproduce the problem on a brand new install:

Install and run apup and tick the following:
AutoPatcher Updater
AutoPatcher Engine
AutoPatcher Common Modules
AutoPatcher for Windows XP SP3 (x86) English
AutoPatcher for Office XP (English)

Apup downloads about 525Mb of stuff. I don't see any errors in the apup.log file.

Good, this means that downloading isn't the issue, or is it

ChrisG_UK said:

I then run AutoPatcher and get the red "Unofficial/Unsupported Release" message. The AutoPatcher.log file contains lots of error messages:

An AutoPatcher team member needs to see the log file - unedited, sorry, only way to fix everything.

ChrisG_UK said:

Module 'E:\AutoPatcher2\modules\Critical\WindowsXP-KB2722913-x86-ENU.apm' implicitly refers to its module folder as 'E:\AutoPatcher2\modules\Critical\WindowsXP-KB2722913-x86-ENU.apm_files'. However, such folder does not exist!
Module 'E:\AutoPatcher2\modules\Critical\WindowsXP-KB2722913-x86-ENU.apm' implicitly refers to its module folder as 'E:\AutoPatcher2\modules\Critical\WindowsXP-KB2722913-x86-ENU.apm_files'. However, such folder does not exist!

This apm file is looking for a folder that doesn't exist, the apm should be gone as well, according to the script,

PreAction.FileDelete=autopatcher:\modules\Critical\WindowsXP-KB2722913-x86-ENU.apm

look in the \modules\Critical\ folder and delete it.

ChrisG_UK said:

UNOFFICIAL: File 'E:\AutoPatcher2\modules\Components\UserProfileHiveCleanup.apm' (mentioned by RTI 'C:\#AutoPatcher_Temp#\xp_sp3_enu.rti') does not exist!

UPHC has been commented out of the script, meaning it wont download, the link to the executable is dead per Microsoft, the problem is someone with the apm file present signed the release yet you don't have it and the RTI file is expecting it.

Spoiler

# Commented out due to broken windows links
#Item=AutoPatcher UPHClean module
#DetectFile=autopatcher:\modules\Components\UserProfileHiveCleanup.apm
#DetectHash=A7F55CAE3FA61331BF27F1D3C5D3BC46
#DownloadFrom=http://www.autopatcher.com/releases/common/UserProfileHiveCleanup.7z
#DownloadTo=autopatcher:\temp_bin\UserProfileHiveCleanup.7z
#ExpectedSize=1244
#ExpectedHash=72582AE4205E20260C9CE8805CC45902
#ActionAfterDownload.Unzip=autopatcher:\temp_bin\UserProfileHiveCleanup.7z :: autopatcher:\modules\Components

# Commented out due to broken windows links
#Item=UPHClean-Setup.msi
#DetectFile=autopatcher:\modules\Components\UserProfileHiveCleanup_files\UPHClean-Setup.msi
#DetectHash=4B18D1395599E85A1007AAF433C7E4C5
#DownloadFrom=http://download.microsoft.com/download/a/8/7/a87b3d05-cd04-4743-a23b-b16645e075ac/UPHClean-Setup.msi
#DownloadTo=autopatcher:\modules\Components\UserProfileHiveCleanup_files\UPHClean-Setup.msi
#ExpectedSize=430080
#ExpectedHash=4B18D1395599E85A1007AAF433C7E4C5

ChrisG_UK said:

Then there are 574 instances of the following message for different files:

UNOFFICIAL: File 'E:\AutoPatcher2\modules\....apm' was found, but not mentioned by any RTI!

not tryin' to pick on you but ....apm doesn't exactly let anyone know what files are the issue

ChrisG_UK said:

and finally:

Module 'Cumulative Security Update for Internet Explorer 8 for Windows XP (KB2722913)' (unique id: 'IE8_KB2722913_XP_SP3_X86_ENU') cannot be loaded because it's uniqueID is duplicate (the module named 'Cumulative Security Update for Internet Explorer 8 for Windows XP (KB2722913)' also uses it).

Am I doing something wrong?

Many thanks.

Notice the KB number - KB2722913 - likely a conflict with the apm file mentioned in quote #4 above, hopefully deleting it will will cause this apm file to load.

You can see exactly which release is the issue by running AutoPatcher, click About - Release Info. The title RED and FALSE is the issue, if all are TRUE there is a stray somewhere, the stray(s) will need to be found and removed.

Once you try these things, rerun AutoPatcher, make sure you get a new (updated error log) and post it, some of these errors should be gone but likely many more to deal with, wont know until the new log file is evaluated.

[_def_x_]

Update:

Downloaded xp_sp3_enu_20120814.script, msie_enu_critical_20120814.7z, and xp_sp3_enu_critical_20120814.7z

After extracting both .7z files, indeed, WindowsXP-KB2722913-x86-ENU.apm & IE8-WindowsXP-KB2722913-x86.apm have the same UniqueID=, as well Title=, and point to the same executable.

WindowsXP-KB2722913-x86-ENU.apm is still in 'xp_sp3_critical...7z' and should be removed.

[ViroMan]

Quote

Downloaded xp_sp3_enu_20120814.script, msie_enu_critical_20120814.7z, and xp_sp3_enu_critical_20120814.7z

After extracting both .7z files, indeed, WindowsXP-KB2722913-x86-ENU.apm & IE8-WindowsXP-KB2722913-x86.apm have the same UniqueID=, as well Title=, and point to the same executable.

WindowsXP-KB2722913-x86-ENU.apm is still in 'xp_sp3_critical...7z' and should be removed.

These should be fixed in the newer script that WAC has. I will edit the fix into the current main script now as a stop gap till WAC's is releases. I may just make WAC's official now since only one person is willing to test the script and it seems to be fine.

Quote

not tryin' to pick on you but ....apm doesn't exactly let anyone know what files are the issue

It does if you run it with the command /verbose . Can be a pretty large log if your missing an rti file though. It will however tell you any reason it went unofficial.

Edited by ViroMan, 08 October 2012 - 09:58 PM.

[_def_x_]

_def_x_ said:

not tryin' to pick on you but ....apm doesn't exactly let anyone know what files are the issue

ViroMan, on 08 October 2012 - 09:31 PM, said:

It does if you run it with the command /verbose . Can be a pretty large log if your missing an rti file though. It will however tell you any reason it went unofficial.

I think you mi33ed my point , anyway.

You might want to add to the XP_SP3_Enu script;

# 2012-10-08: Delete UPHClean APM & Executable until Microsoft restores link...?
PreAction.FileDelete=autopatcher:\modules\Components\UserProfileHiveCleanup.apm
PreAction.FolderDelete=autopatcher:\modules\Components\UserProfileHiveCleanup_files

If for instance I update the release I found on my drive dated Feb 2012 which has this update, it should cause the release to fail should the release get signed minus UPHC. I might have missed it in the latest script, I only did a quick search and didn't find the removal commands.

... Just a suggestion.

[ViroMan]

Changes uploaded. Removed the problem apm from the script.

also...
I just saw your post just now def x. I suppose I could do that since not many people might use it except admins.

edit:I will set to delete all broken file links like these.

UPHClean-Setup.msi (Working again... will reinstate)
Windows-KB909520-v1.000-x86-ENU.exe (Working again... will reinstate)
windowsmedia10-kb892313-x86-intl.exe (Working again... will reinstate)
windowsmedia-kb895181-x86-enu.exe (Still Broken)
windowsmedia10-kb902344-x86-intl.exe (Working again... will reinstate)

Will check links on more time before I do that though.

Edit2: Hey most links work again.

Last edit?:
Script update and signed. Sorry took so long... lots of interruptions...(watching kids).

Edited by ViroMan, 09 October 2012 - 12:26 AM.

[ChrisG_UK]

I didn't understand any of that discussion. What should I do? Can I just ignore the Unofficial/Unsupported message, or am I doing something wrong?

[Whatacrock]

@ChrisG_UK.....you can use autopatcher to install your necessary updates..

YOU CAN IGNORE THE UNOFFICICIAL/UNSUPPORTED VERSION.....this just means that one or more files have changed or been removed from MS servers and the scripts have not been edited to remove the entries from script.

Upkeep on the scripts are done on a voluntary basis and those responsible do have lives outside of the project....Patience is needed

[ViroMan]

I really should create that "Delete All Files Not Listed" function and stuff it in apup after I work out the current bugs in apup.

[OverBrn]

I've had the same question as the OP for some time. I've been ignoring the "Unofficial/Unsupported Release" For me it rarely has ever said Official since it's beginning, never had a actual problem because of it though.

[ViroMan]

overbrn check the dir that your apup is in... does it have "apengine.rti"? better yet... run the attached batch file in your apup dir. It will run Autopatcher in verbose mode. Anything that would make it unofficial would make a report in the log file. The log file is located in your windows dir and it is called... "autopatcher.log"

Attached Files

•  Verbose Autopatcher.7z   171bytes   5 downloads

[_def_x_]

ChrisG_UK, on 20 October 2012 - 08:06 AM, said:

I didn't understand any of that discussion. What should I do? Can I just ignore the Unofficial/Unsupported message, or am I doing something wrong?

I'm sorry Chris, I hope I didn't contribute too much. If you look at my post, #6, as I always do, I offer some FYI (a 50/50 proposition), and I also asked you to do a few things to help fix your issue:

*** Read a thread where another user asked the very question you asked - "what does unofficial / unsupported mean?" - an explanation was given.
*** Read the stickies on posting a log file.
*** Post your log file.
*** Delete an apm file that was associated with an executable (an update) that didn't exist.
*** View the AutoPatcher Release Info tab to determine which release(s) is unofficial, title in RED.

The rest of the conversation was directed (indirectly) to AutoPatcher team members to read, they could take my findings and have a look to confirm, and possibly fix those issues at AutoPatcher's end.

Again, sorry if the confusion scared you off, but it is not easy trying to gather information about a computer you can't see or touch, this is why the details matter, it's all anyone has to go on.

[_def_x_]

OverBrn, on 05 November 2012 - 02:36 AM, said:

I've had the same question as the OP for some time. I've been ignoring the "Unofficial/Unsupported Release" For me it rarely has ever said Official since it's beginning, never had a actual problem because of it though.

I know the feelin', back in the day my Windows 2000 release was unofficial for a very long time until I figured out how to troubleshoot the issue. Some of it was my fault, I was waiting too long between updates and stray files were left behind in the release.

There are staic links in many releases and usually a release can be outdated without posing a problem but - static link files get updated so a release may have been signed with version 2.1 of a given file, a year later the link points to v2.8, due to file size and md5 changes that conflict with the script the new file fails verification.

True, if you know the reason why the Unofficial status exists using AutoPatcher can be harmless - in most cases. It really should be identifed at the very least but until you provide details about what releases you have we'll only be guessing.

[ChrisG_UK]

FIXED!

Sorry, I never did manage to make any sense of this. I tried reading some of the documentation threads but couldn't make any sense of them either. But just recently I noticed the new utility, Sweeper. I ran it and it deleted some stuff and now Autopatcher says it is official. I'm sure I saw somewhere that sweeper was going to run automatically with Apup, but it definitely didn't. This seems like a really good solution. Thank-you.

[ViroMan]

Indeed. I am glad that it solved your problem.

Sweeper is part of the code that is in AP2. I released it as an external app early because I realized it could be of great help now; in clearing out old files that should have been removed by a script. AP2 will no longer use scripts so it will be necessary to be able to detect what isn't needed and remove it without being told to do so.