Jump to content


.NET Framework Addon Pack


354 replies to this topic

#141 click-click

    I am not young enough to know everything.

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

Posted 10 February 2012 - 12:05 PM

View PostViroMan, on 09 February 2012 - 07:36 PM, said:

bah.. I messed up the 7z file I zipped it into a dir with files in it, instead of a zip with files in it. Try now. I wish I had all the files so I can test the damn things without having to make you guys do the testing.

I'm afraid it's still not right. I'm still getting file verification failed.

#142 click-click

    I am not young enough to know everything.

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

Posted 10 February 2012 - 12:11 PM

View PostViroMan, on 08 February 2012 - 11:45 AM, said:

Click Click, your always on top of this stuff(a compliment), if you ever wanted to help us manage the scripts we would seriously appreciate it. Its hard keeping up with all of this by ourselves. Really, its not hard to modify a script... its hard for me to download all of these updates so I can make the scripts though. (I hate my AT&T DSL it might as well be a 56k modem)

Send me a PM on what needs to be done and I will try and help where I can.

#143 click-click

    I am not young enough to know everything.

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

Posted 10 February 2012 - 03:35 PM

@ViroMan
(DONE) NDP20SP2-KB2478658-x86.apm - replaced by KB2539631 which is missing
You added KB2539631 but forgot to remove KB2478658 which was superseded by the fix you added.

(DONE)NDP35SP1-KB2657424-x86.apm - incorrect title .. (KB2657424_X86 instead of KB2657424_X64)
Still the same as before. The title entry should be:
Title=Security Update for Microsoft .NET Framework 3.5 Service Pack 1 on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 (KB2657424_X6486)

KB2656356 says it doesn't have an registry detection but, they all do... so I created one that 'should' detect it but im not sure if it works yet.
No. This fix is for Win7 and not XP. There is no registry detection. Look at Windows6.1-KB2518869-x86.apm and you will se what I mean. KB2656356 should be done the same way. This is what the .apm should look like:
Spoiler

DONE)NDP40-KB2656351-x86.apm - bad detection .. (DotNetFramework=3)
Same as before. I think you misunderstood. DotNetFramework=3 is incorrect and should be =4

Also, the reg detection is still incorrect. It should be as follows:
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2656351

I only checked the x86 files. Some of the x64 apms may also be messed up. Getting close to all blue Posted Image

.

Edited by click-click, 10 February 2012 - 03:41 PM.


#144 ViroMan

    Just an awesome guy.

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

Posted 10 February 2012 - 05:43 PM

check the other thread... I forgot to upload the newer dotnet zip. this could be solved now.

#145 click-click

    I am not young enough to know everything.

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

Posted 10 February 2012 - 06:57 PM

Still getting verification error. Although some of the stuff above is okay now. Some corrections are still missing
I will post seperately.
Spoiler

Edited by click-click, 10 February 2012 - 07:09 PM.


#146 click-click

    I am not young enough to know everything.

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

Posted 10 February 2012 - 07:30 PM

Windows6.1-KB2656356-x86.apm and NDP40-KB2656351-x86.apm are still not correct. Please review my previous post about those two KBs.

Edited by click-click, 10 February 2012 - 07:30 PM.


#147 ViroMan

    Just an awesome guy.

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

Posted 10 February 2012 - 09:43 PM

Took me long enough but Here we go

Spoiler

At least the files download properly... I will do an AP install now and check back shortly.

Edited by ViroMan, 10 February 2012 - 09:44 PM.


#148 click-click

    I am not young enough to know everything.

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

Posted 11 February 2012 - 02:05 AM

I have just uncovered more problems with dotNET. I will append the apm changes once I'm finished.

#149 ViroMan

    Just an awesome guy.

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

Posted 11 February 2012 - 02:21 AM

I just went through a few of the files myself. I may have fixed what you have found. Try a new download.

#150 Whatacrock

    Lord Of The Scripts: Return Of The Manager

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

Posted 11 February 2012 - 06:47 AM

Tried rerunning apup2 and we have a go.....NO ERRORS.................WOOOORAHHHH

All we need at the moment for scripts to be signed again to make autopatcher display official/supported version.

Edited by Whatacrock, 11 February 2012 - 06:48 AM.


#151 click-click

    I am not young enough to know everything.

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

Posted 11 February 2012 - 05:08 PM

Please don't sign the script yet. there are more changes.

#152 ViroMan

    Just an awesome guy.

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

Posted 11 February 2012 - 05:50 PM

ohh no.. I was waiting to hear your response.

Although I do know there are some problems with the detections... mainly in the area of x86 installs show up in x64 environment.

Edited by ViroMan, 11 February 2012 - 05:51 PM.


#153 click-click

    I am not young enough to know everything.

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

Posted 11 February 2012 - 09:58 PM

Here you go ViroMan. Everything looks good for dotNET on my side as far as 32-bit goes.






#154 ViroMan

    Just an awesome guy.

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

Posted 12 February 2012 - 01:38 AM

Good job
I will check it later today or early tomorrow. (Im not home)

#155 DesertJerry

    AutoPatcher Elite

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

Posted 12 February 2012 - 02:59 AM

XP Pro w/SP3

.NET Framework > Update for .NET Framework 1.1 SP1 (KB925168)

The .APM file is in error:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\.NETFramework\1.1\M925168
KeyName=Installed
KeyValue=1

Should read:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\.NETFramework\1.1\M925168
KeyName=Installed
KeyValue=M2656353

Microsoft .NET Framework 3.0 Service Pack 2 (KB976570)

The .APM file is:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.0 Service Pack 2\SP2\KB976570
KeyName=PackageVersion
KeyValue=1

There is no such key at that location in the registry.

Security Update for Microsoft .NET Framework 1.1 Service Pack 1 on Windows XP, Windows Server 2003 (64-bit), Windows Vista, and Windows Server 2008 (KB2416447)

The .APM file is in error:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\.NETFramework\1.1\M2416447
KeyName=Type
KeyValue=Update

Should read:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\.NETFramework\1.1\M2416447
KeyName=Installed
KeyValue=M2656353

Security Update for Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 2.0 Service Pack 2 on Windows Server 2003 and Windows XP (KB2478658)

The .APM file is in error:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 2.0 Service Pack 2\SP2\KB2478658
KeyName=PackageVersion
KeyValue=1

There is no such key at that location in the registry.

Security Update for Microsoft .NET Framework 3.5 Service Pack 1 on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 (KB2657424_X86)

The .APM file is in error:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 Service Pack 1\SP1\KB2657424
KeyName=ThisVersionInstalled
KeyValue=Y

Should read:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 SP1\SP1\KB2657424
KeyName=ThisVersionInstalled
KeyValue=Y


Reboot

XP Pro x64 w/SP2

Microsoft Windows - Updated Components

.NET Framework

Microsoft .NET Framework 3.5 Family Update for Windows XP x86, and Windows Server 2003 x86 (.Net 2 SP2) (KB958481) <-- This is an x86 item (see NDP20SP2-KB958481.apm) because this is also listed:

Microsoft .NET Framework 3.5 Family Update for Windows XP x64, and Windows Server 2003 x64 (KB958481) (see NDP20SP2-KB958481-x64.apm)

But, the .APM file is invalid:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 2.0 Service Pack 2\SP2\KB958481
KeyName=PackageVersion
KeyValue=1

There is no such registry key at that location.

A check at:
HKLM\SOFTWARE\Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 2.0 Service Pack 2\SP2
does not show such a key.

Security Update for Microsoft .NET Framework 3.5 Service Pack 1 on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 (KB2657424_X64)

The .APM file is in error:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 3.5 Service Pack 1\SP1\KB2657424
KeyName=ThisVersionInstalled
KeyValue=Y

Should read:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 3.5 SP1\SP1\KB2657424
KeyName=ThisVersionInstalled
KeyValue=Y


Reboot

Win7 Ultimate 64-bit w/SP1

Microsoft Widwos - Updated Components

.NET Framework

Security Update for Microsoft .NET Framework 3.5.1(KB2656356_X64)

The .APM file is in error:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 Service Pack 1\SP1\KB2657424
KeyName=ThisVersionInstalled
KeyValue=Y

There is no such key as: HKLM\SOFTWARE\Microsoft\Updates\

But

[DetectionFile]
FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=Package_1_for_KB2656356~31bf3856ad364e35~amd64~~6.1.1.1.cat
FileVersion=ANY
FileMD5=ANY

does work.

Edited by DesertJerry, 12 February 2012 - 04:17 AM.


#156 click-click

    I am not young enough to know everything.

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

Posted 12 February 2012 - 02:03 PM

View PostDesertJerry, on 12 February 2012 - 02:59 AM, said:

XP Pro w/SP3

Microsoft .NET Framework 3.0 Service Pack 2 (KB976570)

The .APM file is:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.0 Service Pack 2\SP2\KB976570
KeyName=PackageVersion
KeyValue=1

There is no such key at that location in the registry.

I cannot say anything about .NET 1.1 or x64 because I don't have them installed. I only did a
screenshot of KB976570. I don't know why you don't have this reg entry. It is there on my system.
Same for the other KBs where you can't find the subject entries.



Can you supply a screenshot so we can compare the diffs? Thanks

Edited by click-click, 12 February 2012 - 02:04 PM.


#157 ViroMan

    Just an awesome guy.

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

Posted 12 February 2012 - 04:59 PM

On some of the X64 things I agree with DesertJerry. I will correct them. I can't agree with any of the x86 because I don't have that OS type.

Quote

The .APM file is in error:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 Service Pack 1\SP1\KB2657424
KeyName=ThisVersionInstalled
KeyValue=Y

Should read:
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 SP1\SP1\KB2657424
KeyName=ThisVersionInstalled
KeyValue=Y

That is strange, are you sure? The MS Security Bulletin tells us that it should be the first one.

Edit: Hmm... just looked at mine... it is shortened to "Microsoft .NET Framework 3.5 SP1" as well.

Edited by ViroMan, 12 February 2012 - 05:01 PM.


#158 click-click

    I am not young enough to know everything.

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

Posted 12 February 2012 - 09:40 PM

View PostViroMan, on 12 February 2012 - 04:59 PM, said:

On some of the X64 things I agree with DesertJerry. I will correct them. I can't agree with any of the x86 because I don't have that OS type.



That is strange, are you sure? The MS Security Bulletin tells us that it should be the first one.

Edit: Hmm... just looked at mine... it is shortened to "Microsoft .NET Framework 3.5 SP1" as well.

The shortened version is correct. I have already fixed this in the files I sent you. Microsoft makes more than
enough mistakes. don't always believe what they write.Posted Image

Edited by click-click, 12 February 2012 - 09:45 PM.


#159 DesertJerry

    AutoPatcher Elite

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

Posted 12 February 2012 - 11:07 PM

Test today 12Feb

XP Pro w/SP3 > AutoPatcher > Microsoft Windows - Updated Components > .Net Framework

Only two items shown in black:
Microsoft .NET Framework 3.0 Service Pack 2 (KB976570)
Security Update for Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 2.0 Service Pack 3 on Windows Server 2003 and Windows XP (KB2478658)

Decided to allow Autopatcher to attempt an installation - that finished - restarted AutoPatcher - same two items still black.

Reboot > Start AutoPatcher > Same two items still listed black.

Did a registry search on KB976570 - stopped on a couple of keys that I had never seen or had no useful information, then I got
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A3051CD0-2F64-3813-A88D-B8DCCDE8F8C7}.KB976570 but in the right pane there was only a listing (Default) REG_SZ KB976570 - so that does not appear to have any helpful information. Search ended.

Did a registry search on KB2478658 - again, stopped on a couple of keys that I had never seen or had no useful information, then I got
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{C09FB3CD-3D0C-3F2D-899A-6A1D67F2073F}.KB2478658 but in the right pane there was only a listing (Default) REG_SZ KB2478658 - so that does not appear to have any helpful information. Search ended.

So I would have to say they are both installed but I did not find a way to edit the appropriate .APM file so that they would be shown as installed.

Also a search of Microsoft and Google indicates others have had problems

#160 ViroMan

    Just an awesome guy.

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

Posted 13 February 2012 - 04:07 PM

im working on those files you gave me click click... since you didn't send me the other parts I need.... the size and md5 of the files(not the apm files the exes that get downloaded)... I need to download them and get that info myself... it takes time since I have such a damn slow internet.

edit: hmm actually I guess that is my fault for not saying I would need that. sorry.

Edited by ViroMan, 13 February 2012 - 04:11 PM.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users