Resolved NET Framework 3.5 updates keep reinstalling

I don't know whether the XP area is the right place for this, but the NET Framework seems to be more like a part of the OS than "Other software ".

Every time I boot up, after a few minutes the computer tells me that five updates are ready to be installed. Regardless of whether I accept or cancel, when I shut down they are again waiting to to be installed. Sometimes I allow installation and sometimes I select "turn off without installing updates ", but either way they are still waiting to be installed next time I run the computer.

For a while I was selecting "turn off without installing updates" every time, and eventually quite a lot of other updates were outstanding, but I then let those install and have just the five problematic ones waiting every time.

I have also tried Settings > Control Panel > System > Automatic Updates tab > Install updates from the Windows Update Web site > "Express Get high-priority updates (recommended) ". That likewise goes through the motions of installing the updates and reports "Successful 5 Failed 0 ".

I don't know whether the installation is actually failing, despite the absence of an error report, or whether the updates HAVE been installed but Windows for some reason thinks they haven't been.

I have even de-installed and re-installed NET Framework 1, 2, 3 and 3.5 plus SPs, and run a Registry cleaner, but still the five updates reappear every day.

Richard

 

Sorry, I should have mentioned that the .NET Framework Cleanup Tool is another of the things that I had already tried before posting here.

A step towards resolving the problem would be to find out whether the installation is actually failing, despite the absence of an error report, or whether the updates have been installed but Windows for some reason thinks they haven't been. Is there a way to investigate that?

Richard

 

Arie,

> Post relevant info here.

To get something clear to work with I've just done a shut down, allowing the updates to be (supposedly) installed, and then rebooted. It's still not easy to see which is the relevant info, as the relevant section of the log file, from initiating shut down until the completion of rebooting (complete with finding the same five updates yet again) is 360 lines. I append what I hope are enough lines to show what is happening. Insofar as I can understand this log (which is not very well) it seems that Windows thinks it has succeeded in installing each update.

Richard
2010-10-26 13:37:31:502 1600 10d0 AU AU found 5 updates for install at shutdown
2010-10-26 13:37:31:502 1128 60c Misc =========== Logging initialized (build: 7.4.7600.226, tz: +0100) ===========
2010-10-26 13:37:31:502 1128 60c Misc = Process: C:\WINDOWS\Explorer.EXE
2010-10-26 13:37:31:502 1128 60c Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2010-10-26 13:37:31:502 1128 60c Shutdwn Install at shutdown: found updates to install
2010-10-26 13:37:37:314 1600 258 AU AU received handle event
2010-10-26 13:37:39:080 1156 1678 Shutdwn WARNING: AU will install 5 updates.
2010-10-26 13:37:39:142 1600 16e8 Agent * Title = Microsoft .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2 Security Update for Windows 2000, Windows Server 2003, and Windows XP x86 (KB979909)
2010-10-26 13:37:39:142 1600 16e8 Agent * UpdateId = {E193311B-1D69-4AEA-BAB5-D736EE07D790}.105
2010-10-26 13:37:39:142 1600 16e8 Agent * Bundles 1 updates:
2010-10-26 13:37:39:142 1600 16e8 Agent * {E2FFF023-3DE5-4587-8972-5CED490443EF}.105

<snip the other four>

2010-10-26 13:37:41:220 1600 16e8 DnldMgr Preparing update for install, updateId = {E2FFF023-3DE5-4587-8972-5CED490443EF}.105.
2010-10-26 13:37:41:236 2956 700 Misc =========== Logging initialized (build: 7.4.7600.226, tz: +0100) ===========
2010-10-26 13:37:41:236 2956 700 Misc = Process: C:\WINDOWS\system32\wuauclt.exe
2010-10-26 13:37:41:236 2956 700 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2010-10-26 13:37:41:236 2956 700 Handler :::::::::::::
2010-10-26 13:37:41:236 2956 700 Handler :: START :: Handler: Command Line Install
2010-10-26 13:37:41:236 2956 700 Handler :::::::::
2010-10-26 13:37:41:236 2956 700 Handler : Updates to install = 1
2010-10-26 13:37:52:314 1600 258 AU WARNING: Pending directive, 'Install Approval', is not applicable
2010-10-26 13:38:38:703 2956 700 Handler : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
2010-10-26 13:38:38:703 2956 700 Handler :::::::::
2010-10-26 13:38:38:703 2956 700 Handler :: END :: Handler: Command Line Install
2010-10-26 13:38:38:703 2956 700 Handler :::::::::::::
2010-10-26 13:38:38:703 1600 1788 AU >>## RESUMED ## AU: Installing update [UpdateId = {E193311B-1D69-4AEA-BAB5-D736EE07D790}, succeeded]
2010-10-26 13:38:38:719 1600 16e8 Report REPORT EVENT: {6CBD996E-B801-4D5B-9A37-BDBC8070F3D2} 2010-10-26 13:38:38:703+0100 1 197 101 {E193311B-1D69-4AEA-BAB5-D736EE07D790} 105 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Microsoft .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2 Security Update for Windows 2000, Windows Server 2003, and Windows XP x86 (KB979909)

<snip the other four except for the end of no. 5>

2010-10-26 13:41:42:232 1600 1788 AU >>## RESUMED ## AU: Installing update [UpdateId = {8328C689-B157-4AFC-B181-915023070C4A}, succeeded]
2010-10-26 13:41:42:232 1600 16e8 Report REPORT EVENT: {AB6D8214-B939-4F53-9A62-6EA07E435D4C} 2010-10-26 13:41:42:232+0100 1 197 101 {8328C689-B157-4AFC-B181-915023070C4A} 101 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Microsoft .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2 Update for Windows Server 2003 and Windows XP x86 (KB982524)
2010-10-26 13:41:42:247 1600 16e8 Agent *********
2010-10-26 13:41:42:247 1600 1788 AU Install call completed.
2010-10-26 13:41:42:247 1600 16e8 Agent ** END ** Agent: Installing updates [CallerId = AutomaticUpdates]
2010-10-26 13:41:42:247 1600 1788 AU # WARNING: Install call completed, reboot required = No, error = 0x00000000
2010-10-26 13:41:42:247 1600 16e8 Agent *************
2010-10-26 13:41:42:247 1600 1788 AU #########
2010-10-26 13:41:42:247 1600 1788 AU ## END ## AU: Installing updates [CallId = {FC214546-3F56-4B8E-BCFC-6AB1A0C44C0C}]
2010-10-26 13:41:42:247 1600 1788 AU #############
2010-10-26 13:41:42:247 1600 1788 AU Install complete for all calls, reboot NOT needed
2010-10-26 13:41:42:247 1600 1788 AU InstallAtShutdown completed.
2010-10-26 13:41:46:076 1156 1678 Shutdwn WARNING: Installation at shutdown completed
2010-10-26 13:41:47:466 1600 258 AU ########### AU: Uninitializing Automatic Updates ###########
2010-10-26 13:41:47:466 1600 258 Service *********
2010-10-26 13:41:47:466 1600 258 Service ** END ** Service: Service exit [Exit code = 0x240001]
2010-10-26 13:41:47:466 1600 258 Service *************

<I think this is where the computer shut down and was awaiting rebooting>

 

> I'm not seeing any error messages in your log....

And yet, next time Windows re-starts, it thinks the same updates need to be installed again.

Could something be happening that is somehow causing Windows to revert to the previous configuration every time it starts up?

 

Hi Arie,

I tried posting here a few minutes ago. Had the same problem. Running XP Home Edition, SP3. Ran the clean-up tool and saved the log file. Rebooted. Problem is resolved. Thanks.

Kurt

 

Arie,

PS. Sorry. I can post my clean-up tool log if you like. It's probably 600 lines.

Kurt

 

As previously mentioned, I have tried the cleanup tool but it hasn't helped.

Arie said
> Check: How to determine which versions and service pack levels of the Microsoft .NET Framework are installed and see if it actually did install or not.

Unfortunately that only goes down to the level of Service Packs. The five updates that keep reinstalling are updates to those. Here's another extract from the log file which lists them conveniently.

Richard

2010-10-26 13:37:39:080 1156 1678 Shutdwn WARNING: AU will install 5 updates.
2010-10-26 13:37:39:142 1600 16e8 Agent * Title = Microsoft .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2 Security Update for Windows 2000, Windows Server 2003, and Windows XP x86 (KB979909)
2010-10-26 13:37:39:142 1600 16e8 Agent * UpdateId = {E193311B-1D69-4AEA-BAB5-D736EE07D790}.105
2010-10-26 13:37:39:142 1600 16e8 Agent * Bundles 1 updates:
2010-10-26 13:37:39:142 1600 16e8 Agent * {E2FFF023-3DE5-4587-8972-5CED490443EF}.105
2010-10-26 13:37:39:142 1600 16e8 Agent * Title = Microsoft .NET Framework 3.5 SP1 Update for Windows Server 2003 and Windows XP x86 (KB982168)
2010-10-26 13:37:39:142 1600 16e8 Agent * UpdateId = {FA6E4025-F239-4137-9FD8-BA1022974754}.103
2010-10-26 13:37:39:142 1600 16e8 Agent * Bundles 2 updates:
2010-10-26 13:37:39:142 1600 16e8 Agent * {26B25ECB-D3DA-4A1F-9897-939A8EB1F502}.103
2010-10-26 13:37:39:142 1600 16e8 Agent * {1C17F60B-2B33-4A68-A95F-5F78A4FDC253}.103
2010-10-26 13:37:39:142 1600 16e8 Agent * Title = Security Update for Microsoft .NET Framework 2.0 SP2 and 3.5 SP1 on Windows Server 2003 and Windows XP x86 (KB2418241)
2010-10-26 13:37:39:142 1600 16e8 Agent * UpdateId = {77490167-DDE8-4726-8DD8-6E6F089A51C7}.102
2010-10-26 13:37:39:142 1600 16e8 Agent * Bundles 2 updates:
2010-10-26 13:37:39:142 1600 16e8 Agent * {E8FFD943-FDDA-4073-A829-7AA36B4C1AF4}.102
2010-10-26 13:37:39:142 1600 16e8 Agent * {259B477A-51D2-40EC-9299-05D282DE7C12}.102
2010-10-26 13:37:39:142 1600 16e8 Agent * Title = Security Update for .NET Framework 2.0 SP2 and 3.5 SP1 on Windows Server 2003 and Windows XP x86 (KB983583)
2010-10-26 13:37:39:142 1600 16e8 Agent * UpdateId = {4C43DB81-F9DF-4E41-A276-B392587515D3}.101
2010-10-26 13:37:39:142 1600 16e8 Agent * Bundles 2 updates:
2010-10-26 13:37:39:142 1600 16e8 Agent * {8A0C7F93-1D27-44E2-9C52-03D5D587A2F8}.101
2010-10-26 13:37:39:142 1600 16e8 Agent * {7CA87CDA-7F4E-4072-9994-BC1923C2AFF5}.101
2010-10-26 13:37:39:142 1600 16e8 Agent * Title = Microsoft .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2 Update for Windows Server 2003 and Windows XP x86 (KB982524)
2010-10-26 13:37:39:142 1600 16e8 Agent * UpdateId = {8328C689-B157-4AFC-B181-915023070C4A}.101
2010-10-26 13:37:39:142 1600 16e8 Agent * Bundles 2 updates:
2010-10-26 13:37:39:142 1600 16e8 Agent * {F1BC5375-8096-4476-A5B6-664C3AAEA739}.101
2010-10-26 13:37:39:142 1600 16e8 Agent * {65726B5A-FE2D-4906-A388-ACCFE9009F9B}.101

 

I don't know whether any of my software requires NET framework, but it seems likely. If I remove it, will any software that does need it give me a suitable error message so that I will know what needs to be reinstalled?

 

I have found one utilility, a manager for my graphics card, that demands NET framework 2. I don't normally use it but it tries to run at startup and complains if NET framework 2 isn't available. For the time being I have therefore re-installed 2 (without any Service Pack) and that seems to be OK.

When prompted that updates are available I am declining them and selecting not to be asked again. I am waiting to see whether this finally gets rid of the updates that keep trying to reinstall, albeit by a workaround rather than actually getting Windows to install the updates and know that it has done so.

If no-one minds too much I'd prefer to keep this thread open for a little while longer, until I can be sure that at least the workaround is effective.

Richard

 

> So I'd 'kill' it from running at startup!

I had hesitated to do that in case I might want to run it, but that seems unlikely. The utility in question is ati2evxx.exe. msconfig didn't show it but I found instructions on how to disable it at
http://process.networktechs.com/ati2evxx.exe.php

Thread drift alert: I did at one time try a utility (name forgotten) that displays things that are started in various ways at boot-up, with a view to killing those that I don't need, but I couldn't tell what most of them were without a lot of research and have therefore, so far, tolerated them.

Richard

 

Hi RMelish,
I'm new here, and not nearly as knowledgeable as Arie, but i have a lot of audacity and sometimes I get lucky.
I've been to hell and back with .NET, so I'll give you a few tools. First, there's a tel. # you can call FREE for assistance at Mr. Gates' home #:
1-866-PCSAFETY in the United States and Canada
or you can lookup http://support.microsoft.com/common/international.aspx
MS offers FREE support for update problems. They're pretty good, but God helps those who help themselves... so...:
http://support.microsoft.com/kb/923100
gives all installation packages including 3. If you get this much to install, complete the updates at MS Update site.
I have found some registry cleaners (and other "helpful" cleanup tools) can remove or damage components necessary for the .msi installer software to run correctly. ANYTHING the least bit questionable breaks the G-**** .NET install. Be EXTREMELY cautious using them.
If your install failure has an error message, write it down and query it on Google and MS KB. With any luck, you'll find an appropriate "dotnetfx.exe" that may also solve the problem.

If the above doesn't work, try the suggestions:
http://support.microsoft.com/kb/824643
for un- re-registering or re-installing the .msi pkg. I'll try to check back to see if you got it fixed. Best of luck!
- jabrwky

 

I think all is now sorted, as I am now not getting the update message every time I shut down.

Consulting the Registry as described at http://support.microsoft.com/kb/318785 shows that I now have just NET framework 2, without any SPs, and NET framework 3, and those don't seem to be doing any harm.

I did one thing that I think may have helped. I failed to document it at the time so I can't describe it exactly, but it went roughly like this.

When computer had been running for a few minutes and I got the notice of updates available, I selected custom (?) then declined the NET updates and ticked a box that said something like "Don't ask me again ".

Anyway, with thanks for the various suggestions, I think we can count this thread as SOLVED (but I can't immediately see what I have to do to effect that).

Richard