Jump to content


KB979909, KB982168 shown in black after install


13 replies to this topic

#1 JRosenfeld

    Advanced Member

  • Members
  • PipPipPip
  • 107 posts

Posted 13 June 2010 - 02:36 PM

I used Autopatcher to install the dotnet updates 979909 and 982168. In my temp files I get files showing the install was successful (e.g the htm file shown in pic).

But on opening autopatcher again they still show as black (not installed.

#2 JRosenfeld

    Advanced Member

  • Members
  • PipPipPip
  • 107 posts

Posted 13 June 2010 - 02:42 PM

Tried to edit above to addpic of Autopatcher, but the full editor would not open, so add it here

#3 Cristiano

    Super Helpful Guy

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

Posted 14 June 2010 - 01:29 AM

there are 2 .net updates that doesn't work if not installed in proper order. i don't remember right now the kb numbers, but i will test it as soon as possible

thanks

edit: great... the page of KB979909 states that this one is v2, but it is v1 and the module is looking for the wrong value. for KB982168, it's an similar case. the fact is that this one isn't KB982168, but it's an collection of updates: NDP20SP2-KB976765.msp, NDP20SP2-KB980773.msp, and NDP30SP2-KB976769.msp. so, the detection has to be changed to be multiple. in this case:
KB976765
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 2.0 Service Pack 2\SP2\KB976765v2
PackageVersion=2

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 2.0 Service Pack 2\SP2\KB980773
PackageVersion=1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.0 Service Pack 2\SP2\KB976769v2
PackageVersion=2

i will fix those detections, don't worry. sorry about that, but this month i had to update the scripts from shared computers, without be able to test a lot of things that are required. right now, i'm doing that from a computer that doesn't belong to me, so...

[]s

Edited by Cristiano, 14 June 2010 - 02:03 AM.


#4 Cristiano

    Super Helpful Guy

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

Posted 14 June 2010 - 02:23 AM

fixed. thanks again

[]s

#5 click-click

    I am not young enough to know everything.

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

Posted 15 June 2010 - 09:51 AM

>fixed. thanks again

Hmmm, ran Apup for .NET after your last fix and got a verification error.

Spoiler

If you run it a second time there is no error. You can recreate the error by making a slight change to the 2 APM files so that apup gets a mismatch and downloads them again.

#6 Cristiano

    Super Helpful Guy

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

Posted 15 June 2010 - 11:40 AM

ok, no problem. i will fix that. only one issue: last night, i've notice that at least one of the .nets has changed the detection due an recent update. those are just md5 errors, so they can be fixed in minutes. but the 3 ones that aren't detecting properly is another thing. they could have even replaced...

edit: weird... downloading the script file in here and the compressed modules, the expected hashes match. but i'm behind an webcache right now and sometimes i can reach old files. but ok, i will check it again from another location today

[]s

Edited by Cristiano, 15 June 2010 - 11:46 AM.


#7 click-click

    I am not young enough to know everything.

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

Posted 15 June 2010 - 05:24 PM

>Download Error: Z:\Autopatcher\modules\Components\__dotnet\windows_dotnet.7z
>File size does NOT match. Expecting 6101, but found 6102!!!

Seems rather strange that windows_dotnet.7z happens to be off by one byte.

#8 Cristiano

    Super Helpful Guy

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

Posted 15 June 2010 - 06:14 PM

fixed. but i've already noticed that issue more than one time. i think (but i'm not sure) that this issue is related to the upload process, but the funny thing is that the md5 doesn't change a bit most of the times

by the way: the modules that seems to have something odd are those:
kb974417
kb953297
kb976126v2
kb979909
kb982168

this running the global .net package in a windows xp 1046. but if i run the xp ptb (that has the same modules), then only the first 3 issues happen. since i'm not in the right mood today (seagate has refused the rma for booth of my hds that has smart failures - to say the least), there's a lot of guys around here that think that Africa is in here (they are with that noise stuff), and my pc that should be here already and isn't yet, i will dig into those issues still today to try clear my mind of those issues

[]s

#9 Cristiano

    Super Helpful Guy

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

Posted 15 June 2010 - 08:39 PM

done. i did an consolidation in the .net package and also i've updated several modules to include more detections. i didn't found any info about if the updates was replaced or something, but one fact: some detections was broken after some updates. i think that the changes that i did will detect the updates, but if not, please report

[]s

Edited by Cristiano, 15 June 2010 - 08:40 PM.


#10 JRosenfeld

    Advanced Member

  • Members
  • PipPipPip
  • 107 posts

Posted 15 June 2010 - 09:50 PM

I had updated the NET framework addon pack on 14 June (after your post 4 above) and it was OK, everything true and official in Autopatcher.

I noticed there was a new update (15 June), but selecting that I get the 'one or more files has failed verification' message and the dotnet pack is now false in Autopatcher.
I tried several times, but same error message each time.
I also tried deleting dotnet.rti first. It redownloaded it but still same error message.

Edited by JRosenfeld, 15 June 2010 - 09:53 PM.


#11 Cristiano

    Super Helpful Guy

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

Posted 15 June 2010 - 10:24 PM

my friend, without an log, it's kinda difficult track issues. you was right about an download error. the download size was wrong for windows_dotnet.7z. it's fixed now. but that it just an warning, not an cause of an unofficial version. deleting all .apm files and downloading all them again is still resulting in a official script. as an guess, i've uploaded the rti file again, but without an log, it's only an guess

one thing can speed up things a lot: in the autopatcher root folder, there's an .md5 file. just run it against your system. hksfv helps a lot with that, but if this one doesn't work to you, ilsfv will work. this last one is an tribute to hksfv makers. just don't forget to go to files, preferences, checking and uncheck "rename bad files"

[]s

#12 JRosenfeld

    Advanced Member

  • Members
  • PipPipPip
  • 107 posts

Posted 16 June 2010 - 12:25 AM

Whatever you did, it fixed it :-). All true and official again.
Many thanks.

#13 Cristiano

    Super Helpful Guy

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

Posted 16 June 2010 - 12:41 AM

by the way, and about the detections? they are working ok now? as they are just registry detections, instead do an new one (and possible break the detection for those missing certain updates), i've just added some extra detections for the same thing. one or another will state that the update is already in place, but as those detections aren't the standard ones, they may not be fully ok for all systems. so please, if anything isn't showing as was supposed to, please report

i will re-do my vms soon, but as i will have to add some extra hardware into my new computer and i will loose any warranty due that, i will be forced to do extensive hardware tests before do that (stress tests... basically, days testing over and over the same thing...) and it may take some time. i was supposed to receive it today, but no, they didn't honored... probably due Brazil x North Korea... oh well, live in a country where anything is an excuse to not work sometimes is a problem...

[]s

#14 JRosenfeld

    Advanced Member

  • Members
  • PipPipPip
  • 107 posts

Posted 17 June 2010 - 10:35 PM

Yes, for me at least, the detection of the installed NET framework components and updates now all show correctly.

Edited by JRosenfeld, 17 June 2010 - 10:36 PM.






2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users