AutoPatcher Forum

Black Ghost, on 18 February 2012 - 05:02 PM, said:

One problem with that is .NET Framework 4 Client and/or Full comes as a combined 32-bit and 64-bit download - I don't think there is a way to separate the versions.

Right but looks like the updates/parches are in separate downloads for 32 bit and 64 bit.

I really know how you feel black ghost... 1 gb of downloads for .net, that is a massive amount to download! I too have crappy slower then normal dsl connection. I had considered it in the past and decided to leave it alone. Now that Click Click is managing that... perhaps he would do that. I leave it up to him.

Ran apup2 today and only found one error...


Missing file C:\APUP\modules\Components\__dotnet\NDP30SP2-KB982524-x64.apm_files\NDP30SP2-KB982524-x64.exe
Item Microsoft .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2 Update for Windows 2003 and Windows XP for x64-based Systems is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://download.micr...82524-x64.exe--
This one seems to be a problem

Known problem and has been reported. The script needs to be updated.

I'd like to report a possible detection error? When running AutoPatcher, I get two .NET entries that are shaded black instead of blue. The first one (unticked) is Security Update for .NET Framework 3.5.1 for Windows 7 SP1 and Windows Server 2008 R2 (KB2572077). The other one (ticked) is Security Update for Microsoft .NET Framework 3.5.1 x64 (KB2633873).

Problem is, I checked my installed Windows updates and found
- Security Update for Microsoft Windows (KB2572077) shows as already installed on my system on 10/22/2011
and
-Security Update for Microsoft .NET Framework 3.5.1 x64 (KB2633873) shows as already installed on my system on 2/14/2012.

Of course, I never thought to check to see if they were already installed until I attempted to let AutoPatcher install KB2633873 and failed .

Just thought I'd share. Any ideas gentlemen?

Edit: I forgot to mention that my system is Windows 7 Pro x64.
Edited by dfdff3000, 26 February 2012 - 01:18 AM.

KB2633873 apm FileName= entry is incorrect it should be
FileName=Package_for_KB2633873~31bf3856ad364e35~x86~~6.1.1.0.cat

KB2572077 is also detecting with FileName=

I don't have x64 so I can't test if the detection is set correctly. The above is for x32.
.NET 3.5.1 detection is done via catroot files.See if you can update the FileName=
with the correct file and report back. Thanks
Edited by click-click, 26 February 2012 - 02:00 AM.

Not sure how to do that. Any instructions?

Something tells me that it will make my head hurt.
Edited by dfdff3000, 26 February 2012 - 02:26 AM.

You need to go into the __dotnet directory from Autopatcher (\modules\Components\__dotnet\)
and change the following files:

KB2633873-NDP35SP1-x64.apm (as above)
Windows6.1-KB2572077-x64.apm (remove the 2nd FileName= entry)
Edited by click-click, 26 February 2012 - 02:34 AM.

Done ... and both KB2633873 and KB2572077 are now showing as installed. The release is unsupported/unofficial now though, lol. I know, I'm sure it's because I manually edited the apm files. Many thanks for your timely assistance.

updated the .net
# 2012-02-25: (ViroMan) +KB961118-x64 +KB2656353 +KB979909-x64 +KB982168-x64 (modified KB979909-x86 KB2468871(x86 and x64) KB2657424-x64)

+ some delete commands

Not signed yet. Need someone else with x64 system to see if they get all the pretty blue words. They are blue to me.
Edited by ViroMan, 26 February 2012 - 07:11 AM.

ViroMan you still need to change KB2633873 for x86 and x64 as mentioned in my post..
Edited by click-click, 26 February 2012 - 12:33 PM.

Confirmed, KB2633873 still not showing pretty blue words.

click-click, on 26 February 2012 - 12:31 PM, said:

damn ... forgot to do that. While looking at those apm's I noticed they were as such... DotNetFramework=4 when in fact they should be DotNetFramework=3.5 corrected.

Try it now.

From what I have been able tell in tests, DotNetFramework= does not affect detection. I don't think it matters what is placed there. I used 4 since 3.5 seemed misleading.
Edited by click-click, 27 February 2012 - 09:42 AM.

hmmm really? Ohh well, best to stick to the truth though as the detections will be much more precise with the new AP that is coming. So might as well start now.

James, on 16 October 2008 - 12:03 PM, said:

I'm new in here. Please have a little patience. Where is the download link? Thanks.

@danieldecarli - the autopatcher download link is in the autopatcher download at the top of the forum.
The file needs to be to your hard drive. and run hit_this_to_generate_a_log_file_for_apup.cmd
This will display the releases and you select what you want from there


The dotnet release is approx 1.05Gb in size now and contains both x86 and x64 releases.
Edited by Whatacrock, 03 March 2012 - 03:18 AM.

Damn you whatacrock... I was just going to post. Anyways here is the link

http://www.autopatch...tcher-download/

As he said... use this program to download

Autopatcher Engine and then .NET. Yes its rather large. Click Click is working to separate the two.
Once the download is complete go to the directory you put apup in and then run autopatcher. Then select the installs you want to run.
Edited by ViroMan, 03 March 2012 - 03:18 AM.

Thanks guys.
I was just wondering for a download with everything included because I saw there is an "AutoPatcher_WinXP_Aug07_x86_ENU_Core.exe" file for upgrading XPs with SP3s. Anyways, I got it. Thanks for sharing it.