20 replies to this topic

[Whatacrock]

Ran apup2 on both my machines today, checked the log files and no errors reported... good news
Went further and ran autopatcher and both machines state the unofficial/unsupported version, checked the release info and both state all releases as true.
Checked the autopatcher log and found a common file so here are the log files.....

Spoiler

AutoPatcher 5.6 loaded the filesystem.

Detected
English (1033) Windows Vista Home Premium 32-bit Service Pack 2
System Components:
Internet Explorer: 8.0.6001.19190
Windows Media Player: 11.0.6002.18311
.NET Framework: 1.1.4322|1.1SP1|2.0.50727.4016|2.0SP2|3.0.30729.4037.4037|3.0SP2|3.5|3.5SP1|4|4SP0|4.0|4.0SP0
Windows Installer: 4.5.6002.18005
DirectX: 4.09.00.0904
MSN/Live Messenger:

Office Components:
Microsoft Word:
Microsoft Excel:
Microsoft PowerPoint:
Microsoft Outlook:
Microsoft Access:
Microsoft Project:
Microsoft Publisher:
Microsoft OneNote:
Microsoft FrontPage:
Microsoft InfoPath:
Microsoft Visio:
Microsoft SharePoint Designer:
Microsoft Groove:

Module 'C:\APUP\modules\Critical\KB2646524_2k8_x86.apm' EXPLICITLY refers to its module folder as 'C:\APUP\modules\Critical\KB2567680_vista_x86.apm_files'. However, such folder does not exist!
Module 'AdbeRdr1012_en_US.apm' uses an unknown/unsupported property called 'Recomended'. Please make sure this is not a mis-spelling!

Log file XP machine

Spoiler

AutoPatcher 5.6 loaded the filesystem.

Detected
English (1033) Windows XP Professional Service Pack 3
System Components:
Internet Explorer: 7.0.6000.17108
Windows Media Player: 11.0.5721.5280
.NET Framework: 1.1.4322|1.1SP1|2.0.50727.3053|2.0SP2|3.2.30729.01|3.2SP2|3.5|3.5SP1|4|4SP0|4.0|4.0SP0
Windows Installer: 4.5.6001.22159
DirectX: 4.09.00.0904
MSN/Live Messenger:

Office Components:
Microsoft Word:
Microsoft Excel:
Microsoft PowerPoint:
Microsoft Outlook:
Microsoft Access:
Microsoft Project:
Microsoft Publisher:
Microsoft OneNote:
Microsoft FrontPage:
Microsoft InfoPath:
Microsoft Visio:
Microsoft SharePoint Designer:
Microsoft Groove:

Module 'C:\APUP\modules\Critical\KB2646524_2k8_x86.apm' EXPLICITLY refers to its module folder as 'C:\APUP\modules\Critical\KB2567680_vista_x86.apm_files'. However, such folder does not exist!
Module 'AdbeRdr1012_en_US.apm' uses an unknown/unsupported property called 'Recomended'. Please make sure this is not a mis-spelling!
Module 'Microsoft .NET Framework 3.5 Family Update for Windows XP x86, and Windows Server 2003 x86 (.Net 3 SP2) (KB958483)' (unique id: 'NDP30SP2-KB958483-x86_ENU') cannot be loaded because it's uniqueID is duplicate (the module named 'Microsoft .NET Framework 3.5 Family Update for Windows XP x86, and Windows Server 2003 x86 (.Net 3 SP2) (KB958483)' also uses it).

[ViroMan]

I will look into the KB2646524_2k8_x86 issue

however the KB958483 duplicate ID should not be there... MY AP is not complaining at all... although I only have the .NET and XP_x86 in that dir. Perhaps the ID is being reused in the vista script which is bad.

[ViroMan]

hmm.. try this. Its a batch file that will delete all APMs. extract it into your apup dir then run it. Run apup again and it will only download the APMs. See if that fixes the wierd double ID issue.

The issue with KB2646524 is a weird one. Im gana have to ask domenico step in on this one. Im a bit busy right now to look into this as far as I would like. There are two files with KB2646524 in them. They BOTH internally refer to KB2567680 not KB2646524. It was created by domenico last month so im sure he knows what it is supposed to be.

Edited by ViroMan, 22 February 2012 - 03:19 AM.

[Whatacrock]

Ran the batch file , then apup2 to redownload the .apm files again, finally ran auto patcher again and status remains unofficial/unsupported version, however the only entry at the end of the autopatcher log refers to KB2646524_2k8_x86.apm.Not had a chance to run on Vista machine as yet as in another part of my residence and not powered up.

[Whatacrock]

Just went the procedure again on the vista machine, it still remains unofficial and the ap log remains unchaged as per original posting.

[ViroMan]

Ok so the double ID problem went away.

ohh something I didn't noticed...

Quote

Module 'AdbeRdr1012_en_US.apm' uses an unknown/unsupported property called 'Recomended'. Please make sure this is not a mis-spelling!

I will check it

edit:
AdbeRdr1012 Should be fixed.

Edited by ViroMan, 22 February 2012 - 04:34 AM.

[Whatacrock]

The double ID went away and the adobe reader is fixed... thanks ViroMan.

The only that remains is the KB2646524_2k8_x86.apm.

Any ideas on why my autopatcher still shows as unofficial even though the release info shows ALL to be TRUE..
All cache files have been run through the file assassin but still the stratus remains as such.

[ViroMan]

It is because the insides of that apm is wrong. Im going to leave it up to domenico to fix that. Its not a simple fix... or rather it might be.. but, it would require some looking around to fix it.

[_def_x_]

Quote

Any ideas on why my autopatcher still shows as unofficial even though the release info shows ALL to be TRUE..

Because you have a stray (extra) file(s) in your releases somewhere, likely an extra apm which is why when you delete them all and rerun APUP nothing changes. It could also be an executable that wasn't deleted. It's harder to locate when multiple releases are in one folder, but not impossible. I would count each folder by highlighting all same release-types, xp_x86, vista_2k8 will have one folder and 2 apm files. See if anything stands out. If XP has 86 folders in critical, you should have 86 apm files.

This isn't perfect but it may cause something to stand out - if you have 100 folders and 102 apm files.

If you could get each release in it's own folder, create an md5sum of the folder contents, someone could run that apm against an official release, your extra file will be flagged as missing. I would first take a quick count, you may find it. Empty folders don't matter.

Quote

The only that remains is the KB2646524_2k8_x86.apm.

If you notice, KB2567680 was deleted tha same day KB2646524 was added - dkdk_it 10.01.2012 Patch Day January 2012, the apm file was renamed but the contents were unchanged, easy mistake to make. It's an easy fix, edit the contents of both apm files, KB2646524_2k8_x86.apm & KB2646524_vista_x86.apm to point to KB2646524_vista_x86.apm_files.

[dkdk_it]

Sorry, I'll fix them tonight.
See you later.

[dkdk_it]

Fixed. New script (date 20120222) released.

[Whatacrock]

Just ran apup2 to download new scripts, then autopatcher and the kb error no longer exists...Thanks dkdk_it.

I took your advice and matched the number of apms to number of folders.....all okay
Went one step further and checked contents of the folders starting with critical and found several folders which contained multiple files

KB2544521 Vista x86
KB2647516 Vista x86
KB2647516 Win 7 x86
KB2647516 Win 7 x64

All other folders contained only one file.........is this correct?

[_def_x_]

Whatacrock, on 22 February 2012 - 09:47 PM, said:

Just ran apup2 to download new scripts, then autopatcher and the kb error no longer exists...Thanks dkdk_it.

I took your advice and matched the number of apms to number of folders.....all okay
Went one step further and checked contents of the folders starting with critical and found several folders which contained multiple files

KB2544521 Vista x86
KB2647516 Vista x86
KB2647516 Win 7 x86
KB2647516 Win 7 x64

All other folders contained only one file.........is this correct?

I don't know if all but most of the Vista updates (.msu) share a single folder with 2K8. A single update will apply to both Vista and 2K8... and in some cases you will have a single folder with 2 executables and 4 apm files pointing to the same folder, in this case 2 for IE7 (Vista, 2K8) and 2 for IE8 (Vista, 2K8)...

Spoiler

DetectFile=autopatcher:\modules\Critical\KB2544521_IE7_2k8_x86.apm
DetectFile=autopatcher:\modules\Critical\KB2544521_IE7_vista_x86.apm
DetectFile=autopatcher:\modules\Critical\KB2544521_vista_x86.apm_files\Windows6.0-KB2544521-x86.msu
__and__
DetectFile=autopatcher:\modules\Critical\KB2544521_IE8_2k8_x86.apm
DetectFile=autopatcher:\modules\Critical\KB2544521_IE8_vista_x86.apm
DetectFile=autopatcher:\modules\Critical\KB2544521_vista_x86.apm_files\IE8-Windows6.0-KB2544521-x86.msu

And it appears the madness continues with Windows 7 2 apm files looking for the same folder, but a different file (.msu)...

Spoiler

DetectFile=autopatcher:\modules\Critical\KB2647516_seven_x86.apm
DetectFile=autopatcher:\modules\Critical\KB2647516_seven_x86.apm_files\Windows6.1-KB2647516-x86.msu
DetectFile=autopatcher:\modules\Critical\KB2647516_IE9_seven_x86.apm
DetectFile=autopatcher:\modules\Critical\KB2647516_seven_x86.apm_files\IE9-Windows6.1-KB2647516-x86.msu

You'll have to dig deep to find your stray(s) in a large multi-release package. You might let someone know exactly what releases you have together, title, date, everything, maybe they can create the package you have but Official and True, you create an md5sum of what you have at your end. They'll run the md5 against the Official/True package - your extra will be flagged as missing - this is the file(s) you need to remove. If you can't locate it by hand this is the next best option outside of downloading from scratch.

[Whatacrock]

Thanks for the advice _def_x_.
Instead of looking for the offending files have erased it from hard drive and starting from scratch.

Just a heads up found the offending release causing my problem.... was the dotnet directory(not found the offending file as yet)
Start afresh and ran ap after each release download and then continued on until all that was left was dotnet...instead of downloading copied from other machine and presto unofficial/unsupported popped up...erased all the dotnet references and it returned as official..
Now the hunt is on to elimanate the offender.

Thanks for all that helped

Edited by Whatacrock, 23 February 2012 - 01:36 AM.

[Whatacrock]

Problem now fixed ..... yippee now official.
Gave up chasing the rampant files but noticed the differences between the 2 machines and their status.
Official version had 126 files in 52 folders for a toal of 952 Mb
Unofficial version had 128 files in 54 folders for a total of 960 Mb

A huge thank you to ViroMan, dkdk_it and _def_x_

Edited by Whatacrock, 23 February 2012 - 06:22 AM.

[dkdk_it]

@_def_x_
Sounds good!!!

[dfdff3000]

Similar problem here with what Whatacrock was experiencing, though it appears he's already good to go. APUP2 downloading with no verification errors .. all releases show as true .. but AutoPatcher showing unofficial/unsupported. I see in post 9 of this thread that _def_x_ mentioned stray files as being the possible culprit. I think I found them. In my dotnet folder I found 6 strays (4 of them .apm files - which Viroman's batch file mentioned in post #3 would have deleted for Whatacrock). I thought this might point others in the right direction without needing to download the entire dotnet folder again - which is fricken huuuuge. I haven't checked out the script, but the script maintainer could possibly make references to delete these files from previous releases when updating. Anyway, these were the stray files I found ...

Spoiler

Apup2\modules\Components\__dotnet\NDP20SP2-KB2478658-x64.apm_files\NDP20SP2-KB2478658-x64.exe
Apup2\modules\Components\__dotnet\NDP20SP2-KB2478658-x86.apm_files\NDP20SP2-KB2478658-x86.exe
Apup2\modules\Components\__dotnet\NDP20SP2-KB958481.apm
Apup2\modules\Components\__dotnet\NDP20SP2-KB2478658-x64.apm
Apup2\modules\Components\__dotnet\NDP20SP2-KB2478658-x86.apm
Apup2\modules\Components\__dotnet\NDP30SP2-KB958483.apm

On a somewhat related note. I found another folder\file that was causing my Apup2 folder to show as unofficial/unsupported. I noticed in the stand_alone folder I was showing an older release of Adobe Reader X along with the most current update. Deleting the folder for the older version - in my case ..

Spoiler

Apup2\modules\stand_alone\AdbeRdr1011_en_US.apm_files

.. made everything official.

I hope this makes sense. I still need to head over to the AutoPatcher Addon & Extras Module Depot to report some other issues I'm having with the .NET Framework Addon Pack .

Edited by dfdff3000, 26 February 2012 - 12:33 AM.

[ViroMan]

Click-Click is working to split the DOTNET script into x64 and x86 scripts.

hmm I will add those files/folders to be delete in current .net script

lol... that Adobe folder is already set to delete .... however its trying to delete from the modules folder instead of stand_alone... DOH!

[Whatacrock]

@dfdff3000 I starting pulling my hair trying to locate(ain't got much to start with) those files but did find the apms and files after comparing the directory from official release to unofficial release. I don't feel like a loner any longer !!!!!!!
Sacrificed some of my monthly cap to redownload the dotnet which took a while.
Glad to sse you got it sorted out

[dfdff3000]

I can relate Whatacrock, I'm follically challenged myself. Might be how we got that way, eh? Too much hair pulling? Well it's the excuse that "I'm" going to use now! I'm just sorry that I finally got around to stray hunting after you had used up some of your bandwidth cap. I updated a USB drive last night too, and found a different stray on that one. Just wanted to report it in case it can help someone else. Looks like it was a typo more than anything else, probably as the script was getting worked out in the past. It was ...

modules\Components\__dotnetNDP30SP2-KB982524-x64.apm_files\NDP30SP2-KB982524-x86x64exe <-- the . between the 64 and exe was missing already.