Jump to content


AutoPatcher XP x86 Hotfix Depot

Started by Antonis, Jul 02 2007 07:42 PM

887 replies to this topic

#461 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 16 September 2010 - 01:41 AM

no, just bad typo:
Expecting 33238, but found 34238

fixed. thanks

[]s

#462 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 485 posts
  • Gender:Male

Posted 18 September 2010 - 04:58 AM

I believe KB983583 - MS10-060 replaced KB976569 which has not been removed from
Components/__dotnet.

GDR Service Branch version 2.0.50727.3615 replaced 2.0.50727.3607
LDR Service Branch version 2.0.50727.4455 replaced 2.0.50727.4413

mscordacwks.dll
mscorlib.dll
SOS.dll
mscorwks.dll

Edited by click-click, 18 September 2010 - 04:59 AM.

#463 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 18 September 2010 - 12:38 PM

> KB976569
thank you very much :D i was wondering why this one was showing as installed and then again, showing as not installed, but i didn't found more infos about it

[]s

#464 JRosenfeld

    Advanced Member

  • Members
  • PipPipPip
  • 107 posts

Posted 18 September 2010 - 10:04 PM

When I ran apup NET framework (dated 18 September) it actually downloaded NDP20SP2-KB976569-x86.exe and autopatcher showed as unofficial. I removed the folder NDP20SP2-KB976569-x86.apm_files from the modules\Components\__dotnet set, then autopatcher was happy and official :-).

Edited by JRosenfeld, 18 September 2010 - 10:05 PM.

#465 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 18 September 2010 - 11:07 PM

my mistake, sorry. i've added the command to remove the module and forgot about the folder. fixed

thanks

[]s

#466 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 485 posts
  • Gender:Male

Posted 19 September 2010 - 10:18 AM

This is the first time I've seen this. I can't download the SEP18 XP version. I don't see english/win_xp/autopatcher_xp_sp3_enu_20100918.script in the Index of /releases/english/win_xp

Spoiler

Edited by click-click, 19 September 2010 - 10:43 AM.

#467 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 485 posts
  • Gender:Male

Posted 19 September 2010 - 11:00 AM

 Cristiano, on 18 September 2010 - 11:07 PM, said:

my mistake, sorry. i've added the command to remove the module and forgot about the folder. fixed

thanks

[]s

Still downloading.

Spoiler

#468 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 19 September 2010 - 11:18 AM

not anymore. fixed

thanks

[]s

#469 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 485 posts
  • Gender:Male

Posted 19 September 2010 - 11:49 AM

Look at my post #466. I still have a problem getting Sep18 XP SP3 english

Edited by click-click, 19 September 2010 - 11:53 AM.

#470 Whatacrock

    Lord Of The Scripts: Return Of The Manager

  • Release Managers
  • PipPipPipPipPip
  • 801 posts
  • Gender:Male
  • Location:Somewhere near Hell !!!

Posted 19 September 2010 - 12:17 PM

 click-click, on 19 September 2010 - 11:49 AM, said:

Look at my post #466. I still have a problem getting Sep18 XP SP3 english

I second the motion as I've had to download the lot again as this is a new system and me forgot to save the one from the old hard drive(stupid me)
Cheers
Bruce

#471 _def_x_

    audi 5k

  • Veterans
  • PipPipPipPipPipPip
  • 1,466 posts
  • Gender:Male

Posted 19 September 2010 - 01:44 PM

Cristiano might have pulled the script to fix something or maybe it is in the wrong folder - he'll take care of it as soon as he sees this thread I'm sure :) Nothing really to worry about except the strange text in the log - see post #466 - nothing should happen within the release folder.

#472 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 19 September 2010 - 11:09 PM

just an small issue... i've edited the releases.list to look for autopatcher_xp_sp3_enu_20100918.script and i didn't uploaded that file... well, as forrest gump us to say: ... happens

[]s

#473 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 485 posts
  • Gender:Male

Posted 19 September 2010 - 11:54 PM

Thanks Cristiano. Everything looks great. You can go to bed now :D

#474 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 20 September 2010 - 12:13 AM

sorry if i look distracted since some time ago, but i really am. i'm thinking about another thing that is bothering me a lot since some time ago. sorry, but i really can't avoid think on that and it sometimes make me do stupid things, like those

about go to bed, it's the only one thing that i can do by now. my bike is broken and will stay at the garage waiting for some parts for some time... bus, at night, in here? forget. so, some movie or bed...

by the way: the x64 version of Windows Update Agent v7.4.7600.229 has an small glitch: at least under seven, it works as expected, but as the detection is at an protected folder, autopatcher can't reach the files and can't detect it as installed. i will try find an alternative detection for it, but no promises

edit: i may have found something. can someone that is running an x64 OS deploy Windows Update Agent v7.4.7600.229 and check for the presence of this:
[DetectionFile]
FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=WUClient-SelfUpdate-Core~31bf3856ad364e35~amd64~~7.4.7600.229.cat
FileVersion=ANY
FileMD5=ANY

to make the checking easy, attached to this there's an module that checks for that detection. just make an copy of WindowsUpdateAgent_x64.apm that is located at modules\Components and save the attached file in the same location. then, run apup. if works, then this may do the trick

[]s

Edited by Cristiano, 20 September 2010 - 12:32 AM.

#475 DesertJerry

    Lives In AutoPatcher Forum

  • Members
  • PipPipPipPipPipPip
  • 1,040 posts
  • Gender:Male
  • Location:Victorville, California

Posted 20 September 2010 - 08:01 PM

 Cristiano, on 20 September 2010 - 12:13 AM, said:

sorry if i look distracted since some time ago, but i really am. i'm thinking about another thing that is bothering me a lot since some time ago. sorry, but i really can't avoid think on that and it sometimes make me do stupid things, like those

about go to bed, it's the only one thing that i can do by now. my bike is broken and will stay at the garage waiting for some parts for some time... bus, at night, in here? forget. so, some movie or bed...

by the way: the x64 version of Windows Update Agent v7.4.7600.229 has an small glitch: at least under seven, it works as expected, but as the detection is at an protected folder, autopatcher can't reach the files and can't detect it as installed. i will try find an alternative detection for it, but no promises

edit: i may have found something. can someone that is running an x64 OS deploy Windows Update Agent v7.4.7600.229 and check for the presence of this:
[DetectionFile]
FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=WUClient-SelfUpdate-Core~31bf3856ad364e35~amd64~~7.4.7600.229.cat
FileVersion=ANY
FileMD5=ANY

to make the checking easy, attached to this there's an module that checks for that detection. just make an copy of WindowsUpdateAgent_x64.apm that is located at modules\Components and save the attached file in the same location. then, run apup. if works, then this may do the trick

[]s
Booted into XP Pro x64 w/SP2 and opened Explorer 64-bit - found item: FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} but there was no listing for: FileName=WUClient-SelfUpdate-Core~31bf3856ad364e35~amd64~~7.4.7600.229.cat :(

Anything else I can check?

#476 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 20 September 2010 - 08:44 PM

do you have installed WindowsUpdateAgent30-x64.exe in that system? the installer is at modules\Components\windowsupdateagent30_files

[]s

#477 DesertJerry

    Lives In AutoPatcher Forum

  • Members
  • PipPipPipPipPipPip
  • 1,040 posts
  • Gender:Male
  • Location:Victorville, California

Posted 20 September 2010 - 09:57 PM

 Cristiano, on 20 September 2010 - 08:44 PM, said:

do you have installed WindowsUpdateAgent30-x64.exe in that system? the installer is at modules\Components\windowsupdateagent30_files
[]s
Checked - did not have; ran APUP still do not have but there are two similar APM files: WindowsUpdateAgent_x64.apm and WindowsUpdateAgent_x86.apm. There are also two folders: WindowsUpdate_x86_files and windowsupdateagent30_files - is this info correct? :P

XP Pro x64 > started AutoPatcher > Microsoft Windows - Updated Components > Windows Update Agent v7.4.7600.229 (x64) listed in black with check mark > selected Next > AutoPatcher bar showed installtion > Finished. Re-started Autopatcher > item still listed in black so something is wrong; either installation or detection.

Opened Explorer 64-bit > Windows\System32\Catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} - no, repeat no listing WUClient

Opened Explorer 32-bit - no listing for CatRoot at all. :blink:

Edited by DesertJerry, 20 September 2010 - 10:25 PM.

#478 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 20 September 2010 - 10:51 PM

> There are also two folders: WindowsUpdate_x86_files and windowsupdateagent30_files - is this info correct?
no. WindowsUpdate_x86_files should be deleted by ap xp enu script

> installation or detection
the install works. i've tested in my own. but it requires one reboot to complete

at windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} there's any .cat file with 7.4.7600.229 in the name? at seven x64, there's a couple of files. issue: without an registry detection, the file detections doesn't work in OR mode

[]s

#479 _def_x_

    audi 5k

  • Veterans
  • PipPipPipPipPipPip
  • 1,466 posts
  • Gender:Male

Posted 21 September 2010 - 03:04 PM

Something very strange about KB982010 - are you sure this update applies to XP SP3 x86? Microsoft says (see System Tip) this update does not apply to my OS.

I'm using Windows XP SP3 x86 while visiting the site, also, XP is not listed in APPLIES TO, in fact a search of the page - XP is not mentioned at all - this looks to be a Server 2003 / 2008 update?

- http://support.microsoft.com/kb/982010

Spoiler

#480 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 21 September 2010 - 03:27 PM

about windows update agent? it applies to all OS's, since it is an replacement for the .226 version of the same update. i've deployed that into my xp when that update was first reported as missing and, in deed, it works. about that documentation, isn't the first time that ms is wrong about. of course, the issue that is addressed by the update happens only in the OS's in that documentation, despite some reports about the same issue happen under seven that can be found in the web

but for sure, i would like a lot know why that update isn't at WU yet, since it's public since months ago

[]s
Back to AutoPatcher for Windows XP SP3 (x86) · Next Unread Topic →


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

  1. AutoPatcher Forum
  2. → Releases
  3. → AutoPatcher for Windows XP SP3 (x86)