Jump to content


.NET Framework Addon Pack

Started by James, Oct 16 2008 12:03 PM

354 replies to this topic

#81 Cristiano

    Super Helpful Guy

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

Posted 15 October 2010 - 10:55 AM

fix done. one command was added into the script to move the file to the proper folder as well

the date of the script was edited into the releases.list due that, but the downloaded script is the same (except for those changes)

[]s

#82 Cristiano

    Super Helpful Guy

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

Posted 18 October 2010 - 09:01 PM

script updated to fix an issue related to KB2416473-x86 module, that was being showed under seven x86 and isn't the case. also, KB2416473-x64 was added. if possible, can someone running XP_x64,2K3_x64,VISTA_x64,LHSERVER_x64 check if the detection is properly set? oh yes, KB2160841-x64 module was also edited due an issue with the detection (was working anyway, but wasn't properly done)

[]s

#83 Cristiano

    Super Helpful Guy

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

Posted 09 November 2010 - 10:11 PM

# 2010-11-09: -KB953297

i'm not sure about the update that has replaced this one, but this one doesn't install anymore. so, gone for good

[]s

#84 leebee

    Newbie

  • Members
  • Pip
  • 6 posts

Posted 24 January 2011 - 07:14 AM

Hi Cristiano.

I opened a .NET related topic in the XP section because I was experiencing this in XP. gUiTaR_mIkE already replied, but maybe you can just look at it, too, above all to see my work-around (which might help for a fix, or might not).

http://www.autopatch...ran/#entry14043

Thanks,
Lee

#85 DesertJerry

    AutoPatcher Elite

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

Posted 09 June 2011 - 04:17 AM

Net Framework 4.0 has had a major update posted at the Microsoft download site:

NDP40-KB2468871-v2-x86.exe MD5 89C68B30D4029D665174C5D647115CAE

NDP40-KB2468871-v2-x64.exe MD5 1C9AA6DAF3DCBFFD1B07C70382223A19

Edited by DesertJerry, 09 June 2011 - 04:17 AM.

#86 _def_x_

    audi 5k

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

Posted 10 June 2011 - 07:40 AM

@DesertJerry

Do you have the direct links to those files, maybe the bulletin if they have one? I will need some help with the .NET, I've never updated the script, there is a bulletin from April that has 4 downloads, about 70+MB.

(+) http://www.microsoft...n/MS11-028.mspx
.......Vulnerability in .NET Framework Could Allow Remote Code Execution. (2446704 (x2) x86:x64;2446708 (x2) x86:x64)

There's 2 x86 and 2 x64 files. Like I said, I will need some help with the .NET script but I'm not gonna worry about it for a bit, got other things to attend to, but will try and get it done, along with 2 Java updates, just in time for June Patch Tuesday.

Any Volunteers :wacko:

:ph34r:

#87 DesertJerry

    AutoPatcher Elite

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

Posted 10 June 2011 - 09:47 PM

The downloads are here: http://www.microsoft...ls.aspx?id=3556

Major pain in the ###### - between my starting my system and going back to check for the information you asked for, about 30 minutes, Microsoft changed the layout completely for the download page and it is now extremely difficult to find anything. :angry:

I told them the new layout was terrible - probably with no possibility of a change. :(

Have fun trying to find anyhting. :P

#88 Cristiano

    Super Helpful Guy

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

Posted 10 June 2011 - 10:54 PM

the major problem that i see with this new .net 4 is the detection for it. to clarify: i've deployed the x64 version for it yesterday and it was the only one update that i did in my system, but according to w7 automatic updates log, i've deployed KB2473228, KB2468871, KB2446708 and KB2160841. also, all the references for KB2416472 (the previews version) has gone. the registry detection for this one seems to be:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}
DisplayVersion
4.0.30319

that is the only one key listed in the uninstall part of the registry for this one. at:
{B7693CDE-074B-301C-9584-FC4343696C8B}
there's the registry detection for the old one. the data are
DisplayVersion
4.0.30319

(yes, the version is the same. they only have changed the registry key)

the funny part: there's no mention to v2 into the registry for this one. so, possible detections are {F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}, but then this one may not show as installed to those that doesn't have v2, but have deployed as standalones. if the version didn't changed, then this v2 is only an compilation of updates, including those 4, that was missing from the script

i've only tested that under seven x64, since i no longer have any x86 OS and to test that, i have to set an vm (that i don't have anymore and has to be fully deployed)

[]s

#89 _def_x_

    audi 5k

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

Posted 11 June 2011 - 01:01 PM

Cristiano said:

the major problem that i see with this new .net 4 is the detection for it.
This is what's dragging me down with the way things are done now - a lot of time consuming work goes into most detections, finding them by first installing the update, whatever, and the file may be removed in a month maybe before you even install it.

I'm not sure exactly but if the new application gets off the ground as we all hope I would like to see a different kind of approach to the displayed updates, how they are listed as ready for installation or how they are removed and moved to a second list of already installed. I wonder if a list file, maybe a database file could be appended when you select a file to be installed.

You start with a full list of all updates available for your system, maybe a tab, once you select a file for installation the database is appended and that file is removed from the 'available' tab and added to the 'installed' tab. The user can re-add a file if they determine the update failed for some reason and they fixed the issue, maybe installed the missing dependency. The user could also move a selected update to a 'bypassed' tab, files are moved here because you don't need the update and you don't want to mistakenly install it.

The goal is to finally get all the updates from 'available' to 'installed'. Green=Ready To Install, Blue=Installed, Orange=On Hold - the user could select the colors they like :)

#90 _def_x_

    audi 5k

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

Posted 11 June 2011 - 09:56 PM

In all my ramblings I failed to mention - it would be nice to devise a 'safe' way to at least get the update in the release, with a bare minimum bit of info so the user can see the update listed - any ideas? All the 'pre' stuff we need to know makes updating the scripts very time consuming.

This was my point about moving an update from one list to another - once you invoke the install command the update is removed from 'ready' to 'installed'. The user needs to confirm the actual installation - WU/MU, a third party tool like WinUpdatesList, SIW, .NET Version Checker, Add/Remove Programs. We provide the update, the install commands, a nice GUI to drive the installation, the user needs to confirm the installation, if failed, check the update log, fix the issue, then move the file back to 'ready' - does any of this make sense or is this a lousy way of doing things?

The way it is now, much time is put into hunting for the correct detections, this may even make Office updates a bit easier to manage.

The big issue still is the proper dependencies, but large corporations manage many systems and they don't spend this kind of time deploying updates - there is a streamlined way, we need to find it.

I remembered what my CompTIA teacher mentioned, he manages 600+ systems for a large corporation, if I remember correctly he said they deployed images, regularly updated, they didn't bother much with single updates.

#91 DesertJerry

    AutoPatcher Elite

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

Posted 11 June 2011 - 10:26 PM

One place that has had discussion on what was updated/replaced is: http://www.ryanvm.ne...opic.php?t=9115

Spoiler
I have no idea if this helps or hinders your efforts - let me know. It will probably be later tonight or tomorrow, my date/time, before I can get to XP Pro x64 w/SP2 to verify as to what was changed/updated there.

Edited by gUiTaR_mIkE, 12 June 2011 - 03:24 AM.
Added Spoiler

#92 DesertJerry

    AutoPatcher Elite

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

Posted 12 June 2011 - 03:46 AM

Booted into XP Pro x64 w/SP2. Did not find a duplicate registry listing but similar.

HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{8E34682C-8118-31F1-BC4C-98CD9675E1C2}.KB2162169
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{8E34682C-8118-31F1-BC4C-98CD9675E1C2}.KB2416472
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{8E34682C-8118-31F1-BC4C-98CD9675E1C2}.KB2468871
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{8E34682C-8118-31F1-BC4C-98CD9675E1C2}.KB2478063
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{8E34682C-8118-31F1-BC4C-98CD9675E1C2}.KB2487367

The above five appeared to be part of Microsoft .NET Framework 4 Extended


HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{CE2CDD62-0124-36CA-84D3-9F4DCF5C5BD9}.KB2416473
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{CE2CDD62-0124-36CA-84D3-9F4DCF5C5BD9}.KB953595
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{CE2CDD62-0124-36CA-84D3-9F4DCF5C5BD9}.KB958484
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{CE2CDD62-0124-36CA-84D3-9F4DCF5C5BD9}.KB963707
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{CE2CDD62-0124-36CA-84D3-9F4DCF5C5BD9}.KB982306

These five are for Microsoft .NET Framework 3.5 SP1


HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}.KB2028562
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}.KB2160841
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}.KB2162169
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}.KB2446708
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}.KB2446708v2
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}.KB2468871
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}.KB2473228
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}.KB2478063
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}.KB2478663
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}.KB2514805
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}.KB2518870
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}.KB982638
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}.KB983182
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}.KB983571

The above 14 for Microsoft .NET Framework 4 Client Profile

I noticed you "spoilered" my earlier - I have no idea how that is done or is it something I can't do when I post so it doesn't matter anyway.

#93 netluca

    Newbie

  • Members
  • Pip
  • 2 posts

Posted 21 June 2011 - 02:12 PM

hello i have create net4 for my xpsp3 i have use dotNetFx40_Full_x86.exe and hotfix NDP40-KB2416472-x86.exe at today WU need NDP40-KB2446708-x86.exe i have integrate with mst but always appears in the WU update because?



View PostCristiano, on 10 June 2011 - 10:54 PM, said:

the major problem that i see with this new .net 4 is the detection for it. to clarify: i've deployed the x64 version for it yesterday and it was the only one update that i did in my system, but according to w7 automatic updates log, i've deployed KB2473228, KB2468871, KB2446708 and KB2160841. also, all the references for KB2416472 (the previews version) has gone. the registry detection for this one seems to be:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}
DisplayVersion
4.0.30319

that is the only one key listed in the uninstall part of the registry for this one. at:
{B7693CDE-074B-301C-9584-FC4343696C8B}
there's the registry detection for the old one. the data are
DisplayVersion
4.0.30319

(yes, the version is the same. they only have changed the registry key)

the funny part: there's no mention to v2 into the registry for this one. so, possible detections are {F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}, but then this one may not show as installed to those that doesn't have v2, but have deployed as standalones. if the version didn't changed, then this v2 is only an compilation of updates, including those 4, that was missing from the script

i've only tested that under seven x64, since i no longer have any x86 OS and to test that, i have to set an vm (that i don't have anymore and has to be fully deployed)

[]s

#94 Cristiano

    Super Helpful Guy

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

Posted 21 June 2011 - 04:05 PM

WU doesn't is always in sync with the bulletins. under xp, there's an obsolete update that is showed in that list since 3 years ago or so and doesn't even work anymore. under seven, several times the automatic updates download certain updates that can't be applied due superseed. but the .net script is being reviewed (at least, i've readed about it) to track certain issues. there's not an date to it be ready

[]s

#95 Cristiano

    Super Helpful Guy

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

Posted 25 June 2011 - 07:58 PM

when i've said that the worst thing that could happen to the .net was move it from the main thing to his own script, merging versions for all the OS's, everybody said that it was an good move. but what about issues like the missing updates into this script? all the missing updates will require about 175mb of download. in that are included the .net updates for seven sp1 x86 and x64, vista sp2 sp1 x86 and x64 and xp. for those that with be sure of it:
Spoiler

[]s

#96 Cristiano

    Super Helpful Guy

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

Posted 08 July 2011 - 12:39 AM

finally... detections for KB2478660 and KB2518866 under vista x86:
KB2478660
Package_for_KB2478660~31bf3856ad364e35~x86~~6.0.1.0.cat

KB2518866
Package_for_KB2518866_client~31bf3856ad364e35~x86~~6.0.1.0.cat

those files are located at windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}

[]s

#97 Cristiano

    Super Helpful Guy

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

Posted 08 July 2011 - 10:43 PM

reviewing the detections results for vista x86, i've found an .cat file that isn't restricted to client version. so:
vista x86
KB2478660
Package_for_KB2478660~31bf3856ad364e35~x86~~6.0.1.0.cat

KB2518866
Package_for_KB2518866~31bf3856ad364e35~x86~~6.0.1.0.cat

vista x64
KB2478660
Package_for_KB2478660~31bf3856ad364e35~amd64~~6.0.1.0.cat

KB2518866
Package_for_KB2518866~31bf3856ad364e35~amd64~~6.0.1.0.cat

now that those are done, i'm going to take the xp x86 detections for those:
KB2478663
KB2478658
KB2478656
KB2518864
KB2518870

some of those fits for more than one OS, but shared detections us to be the same for all

[]s

#98 Cristiano

    Super Helpful Guy

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

Posted 08 July 2011 - 11:29 PM

xp detections taken:
KB2478663
HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2478663
PackageVersion
1

KB2478658
HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 2.0 Service Pack 2\SP2\KB2478658
PackageVersion
1

KB2518864
HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 2.0 Service Pack 2\SP2\KB2518864
PackageVersion
1

KB2518870
HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2518870
PackageVersion
1

KB2478656 doesn't apply if the user is running .net 3.5 sp1

now, i'm going back to vista x64 to take detections for
KB2478663

[]s

#99 Cristiano

    Super Helpful Guy

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

Posted 09 July 2011 - 12:23 AM

KB2478663: due some reason, this one has an suitable detection at Wow6432Node, meaning that an autopatcher detection can work like this:

vista x64:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2478663
PackageVersion
1

also, detections taken for seven x64:
KB2518870
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2518870
PackageVersion
1

KB2478662
Package_for_KB2478662~31bf3856ad364e35~amd64~~6.1.1.0.cat

KB2518869
Package_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0.cat

seven x86
KB2478662
Package_for_KB2478662~31bf3856ad364e35~x86~~6.1.1.0.cat

seven x86
KB2518869
Package_for_KB2518869~31bf3856ad364e35~x86~~6.1.1.0.cat

due some reason, KB2478658 and KB2518864 have an suitable detection at Wow6432Node, meaning that an autopatcher detection can work like this, under xp x64:

KB2478658
HKLM\SOFTWARE\Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 2.0 Service Pack 2\SP2\KB2478658
PackageVersion
1

KB251886
HKLM\SOFTWARE\Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 2.0 Service Pack 2\SP2\KB2518864
PackageVersion
1

i think that all the detections are now taken and now the modules can be made, after take some non-english translations for them. the .net package will increase in about 172MB due those updates. if someone can just check if those detections are present in other systems, thanks in advance.

[]s

Edited by Cristiano, 09 July 2011 - 02:08 AM.

#100 Cristiano

    Super Helpful Guy

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

Posted 11 July 2011 - 02:35 PM

done. the 16 missing updates in the .net script:
Spoiler

with the removal of KB983583, the full download size for this package shall be about 631MB. i will work later on the modules

[]s

Edited by Cristiano, 11 July 2011 - 02:36 PM.

Back to AutoPatcher Addon & Extras Module Depot · Next Unread Topic →


2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users

  1. AutoPatcher Forum
  2. → Releases
  3. → AutoPatcher Addon & Extras Module Depot