Unloading registry issue?

I did some research on why I was receiving a warning error in my admin logs, the microsoft article says that something is failing to release the registry at shut down and that a virus scanner maybe to blame, Avast has always shutdown when requested to do so and this warning error is only recently showing up in my logs, do any of you know if the latest Avast program update is to blame and how to check what could be failing to allow the registry to close?

ps the error log also says something about changing how the services are run but I dont understand it

The full text of the errors/admin log entry, etc. might be helpful.

You don’t mention what your OS is and I can’t remember, this might have an impact ?

Not to mention Patch Tuesday has just past, did you install these patches and did these errors occur around about the same time (in the last week) ?

The last program update was a week earlier from 4 Dec 2007.

I have Windows XP SP2 and they started being logged after the .NET framework update I think

Tell me more about the net framework update. What version do we need?

I know this is unrelated, but I’m having issues with Logitech Setpoint software and a possible fix might be the latest version of net framework.

I think that pre-dates the avast program update by quite some time, the .net patch wasn’t in the December Security Updates, so it is a bit of a mystery.

My .net framework is old version 2.0. I started with 1.0 patch to 1.1, then installed 2.0 (uninstalled 1.1 as 2.0 didn’t require it) since then every .net update/patch has failed to install and this is a well know problem.

Currently it is .net 3.5 I believe, unlike the previous 1.1 - 2.0 the older version wasn’t required. However if you wish to install 3.0 it requires that you already have 2.0 installed. The .net framework is a bloody mess, if I didn’t have one program (my drive imaging software) that requires it I wouldn’t have it on my system.

I only applied the Windows update of .NET 1.1 because it was amongst the other critical updates

If you only have .net 1.0 then you would only be offered .net updates for 1.0 not the later versions I guess.