Jump to content


Possible errors in listings


3 replies to this topic

#1 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 988 posts
  • Gender:Male
  • Location:Victorville, California

Posted 05 January 2012 - 04:57 AM

Win7 Ultimate 64-bit w/SP1

APUP2 > APUP2.INI includes
[Options]
ReleasePath=http://www.autopatcher.com/releases2.list

Start AutoPatcher

Microsoft Windows - Critical Updates has check mark in box for:
Windows Media Player - Critical Updates

which is in error because no Critical Updates are listed.

A check of __WMP_critical.apm shows
[OperatingSystem]
WindowsVersion=ANY <this is wrong

which is incorrect as there are no Win7 Critical Updates to be found.
Should be edited to correctly reflect the operating system's media player
that has critical updates.

Also > Microsoft Windows - Updated Components > .Net Framework

Security Update for Microsoft .NET Framework 4 (KB2416472-x64)
Security Update for Microsoft .NET Framework 4 (KB2160841-x64)

does not install. Items listed in black after trying to install twice.

Checked the appropriate .APM file and navigated to that registry location to verify,
did not find KB items listed. Have no idea as to why the install fails.

Someone else could verify the .Net Framework on their system; the WMP item should be obvious
to someone running Win7.

#2 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,163 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 05 January 2012 - 06:00 AM

Well first off you shouldn't be using releases2.list unless your testing something or using my XP x64 script. That is our test release area. Things are bound to be messed up and or old in that place.

I don't see a Windows Media Player critical update for windows7 in the normal windows 7 sp1 x64 script but, I have not been making the scripts so im not completely sure where to look. Point it out to me and if it looks like your right I will make the change.

As for the NET updates you mentioned.

KB2416472-x64 Excerpt from MS10-070 Note A registry key does not exist to validate the presence of this update.

KB2160841 Excerpt from MS10-071 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2160841
the APM tries to read HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2160841

We can place in the one from Microsoft but, im not sure how well autopatcher references the wow node. According to Microsoft you shouldn't read the wow node directly. You should instead do a normal read with the 64 bit switch on and you will get auto directed to the proper place.

Modify your APM to use the wow node suggested by Microsoft and see if it works.

#3 dfdff3000

    Advanced Member

  • Members
  • PipPipPip
  • 91 posts
  • Gender:Male
  • Location:Michigan

Posted 08 January 2012 - 08:16 PM

View PostDesertJerry, on 05 January 2012 - 04:57 AM, said:

Microsoft Windows - Critical Updates has check mark in box for:
Windows Media Player - Critical Updates

which is in error because no Critical Updates are listed.

A check of __WMP_critical.apm shows
[OperatingSystem]
WindowsVersion=ANY <this is wrong

which is incorrect as there are no Win7 Critical Updates to be found.
Should be edited to correctly reflect the operating system's media player that has critical updates.

the WMP item should be obvious to someone running Win7.

I believe the script that contains the reference to __WMP_critical.apm is the autopatcher_xp_sp3_enu script. I'd noticed it some time ago when I was keeping separate folders for each release list. After running apup, I'd run AutoPatcher to check to make sure the release was official and saw that there was a check mark for Windows Media Player critical updates on my Windows 7 system.

I saw something similar with Windows Update Agent (back in January 2011) and reported it
http://www.autopatch...4053#entry14053

I never bothered to report this occurrence with Windows Media Player, since I figured it was a different type of the same issue. This doesn't look to be the same though. In that instance, I believe the update still applied to Windows 7. It doesn't look as though that's the case here.

Edited by dfdff3000, 08 January 2012 - 08:19 PM.


#4 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,163 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 09 January 2012 - 12:28 AM

Well from what I can tell, dfdff3000 is correct. The problem IS in the windows xp sp3 x86 script. It has to do with the way auopatcher processes apm's. There is a root apm for each directory created. The root directory for
Windows Media Player - Critical Updates has " Critical=True " This has the side affect of autopatcher automatically selecting what ever it is plus its sub items. That apm also has "WindowsVersion=ANY " meaning it will
show up in all windows. You will have to bear with this unsightly bug until I get around to recompiling autopatcher.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users