AutoPatcher Forum

Please refrain from running the release2 list until I get this sorted out. The scripts are incorrect the way they are now, so there is no need to continue with them. A word of warning. Anyone trying new scripts should keep a copy of the original __dotnet directory before proceeding. This will allow for you to start over if necessary.
Edited by click-click, 01 April 2012 - 12:33 AM.

No, Click Click I will leave the script in your hands. I was just trying a quick patch but, as you wish I will not touche it anymore.

Quote

This is right. If you mess with test scripts you should have backups.
Edited by ViroMan, 01 April 2012 - 12:37 AM.

Any progress with updating of the scripts ??

They are done, but the releases2.list needs to be updated to use the new scripts. It is still pointing to the old scripts.

Okay, nice job there click-click.Please accept my appreciation for the work you done on this, life now seems easier.

The dotNET Addons have been updated and are now available for testing.
Before starting APUP, run Autopatcher to assure your AP status is Official.
This will make it easier to resolve problems if they arise. I also recommend
running APUP twice - once for x86 and once for x64. If you select both in one
pass, APUP will re-download NDP40-KB2600211-x86-x64.exe (67MB) because it is
a new download and common between the scripts. APUP cannot tell that the files
are identical when both scripts are run in a single pass. This is a limitation
of APUP.

Please run apup with the /log and /listing: options when testing.
The same holds true for the Autopatcher options /verbose /nolicense

apup /log /LISTFILE:http://www.autopatcher.com/releases2.list

ap /verbose /nolicense

When running APUP, clear all check-boxes and select only what you want.
After APUP is finished downloading any missing files, you should see a
separate command prompt window asking you what you would like to keep.

Note1: These instructions apply only to the official APUP and not APUP2.
The APUP2 Beta is currently not supported.

Note2: Be sure to make a backup copy of your __dotnet directory before
running APUP in case of any unexpected problems.

This is ViroMan, and I approve of this message.

(lol I don't know why I wanted to say that. Maby Its because of all the campaign ads going on right now.)

I second the motion.....................MOTION CARRIED.

Tested this with click-click and it runs like a dream.

Here's a heads up for April hotfixes for dotnet

Security Update for Microsoft .Net Framework 1.1 SP1 (KB2656370)
Security Update for Microsoft .Net Framework 2.0 SP2 (KB2656369)
Security Update for Microsoft .Net Framework 4 (KB2656368)

Other hotfixes posted in their respective forums

Yes, Windows update is pretty good about reporting new fixes. Vista and Win7 have updates too not only XP.

Instead of listing the .Net hotfixes with each OS I posted in, just inserted it here and these were listed on my vista machine first as my XP was still downloading at the time.
Sorry for not listing them on the OS postings.

No Problem. I was talking about the dotNET updates for the different systems. It would actually be more helpful to list
the security bulletin link if applicable or just the KB article link if there is no security bulletin. For example security bulletin MS12-025 covers dotNET for all systems. http://technet.micro...lletin/ms12-025

FYI: The Official APUP Release List has been updated.

The previous DotNET selection for APUP has been split into x64 and x86 and updated to reflect Microsoft's April Patch Tuesday. If you would like to keep both x64 and x86 versions, it is recommended you select one version at a time. In other words, run APUP once for x64 and then once more for x86. When APUP is finished processing, you will be prompted by a command window asking you what version(s) you would like to keep. If you keep only one version, the other version will be deleted from your hard drive so please be aware of the consequences. This will complete the split and update your dotNET directory structure.

Please verify that your current AP status shows Official before selecting any of the dotNETs.
Please be sure to use APUP V1. APUP2 is not supported for this split.
Edited by click-click, 18 April 2012 - 01:24 AM.

Also note that you will only be asked which one to keep once. After the split has been made on your HD, you may from then on, select both(if you want both).

If you select both in the initial APUP run, the command prompt will appear twice - once for x86 and once for x64. That is one of the reasons we recommend doing the new dotNET for the first time in separate runs.

I think I found a possible detection error with KB2487367. It looks like this update is not for the .NET Framework 4 Client Profile - but that is where the apm is looking. Please correct me if I'm wrong.

Registry detection currently:
RegistryPath=HKLM\SOFTWARE\wow6432node\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2487367

On my Windows 7 pro x64 system - should be?:
RegistryPath=HKLM\SOFTWARE\wow6432node\Microsoft\Updates\Microsoft .NET Framework 4 Extended\KB2487367

My system isn't x86, but the x86 version of this detection appears to be looking in the wrong place as well.
Edited by dfdff3000, 18 April 2012 - 04:54 PM.

Correct. I have already fixed this and changed it so it will not show up in the AP selections if the user only has the Client installed. Thanks for the heads up.

im still trying to get you access to the FTP click click but, frank is always distracted with his job.

No problem. I sent you the updates dated April 18.

ahh yes... I was just telling domenico about putting the .net in the main list and it hit me, that I downloaded those updates to put on the server but, I have not put them up yet. I will do so now.

edit: bah... I got sidetracked again. The changes are in.
Edited by ViroMan, 19 April 2012 - 09:45 AM.