The recent problems that I and others have had with Q329170 recalls the adage - Do No Harm.
I was under the impression that the point to the auto update feature in added to Win 2000 SP3 and later was to keep your system in tip top shape and hack free. I know MS is running scared and trying to plug all holes like the proverbial Dutch dike but maybe a little more regression testing is needed?
I know no one put a gun to my head to install these updates, but one would like to believe that an official update propagated as widely as these updates would be more thoroughly tested? What's even more annoying is that I had to scrounge around in this newsgroup to confirm what I had just about already deduced by myself using the event log to review what happened on the date right before I started getting "couldn't unload registry" messages in my event log. I never ever ask for anyone's help or support with my computer system as it is hopeless and I can always figure it out myself or use my own research. I do think that MS should post as soon as possible on a known web site when it becomes clear that there is a problem with an update. I may be uninformed but the last google I did of Microsoft.com did not reveal this latest gem of a problem called Q329170. I count at least a dozen or so reports of problems with this update on this board so I extrapolate this is a pretty widespread problem. It would be nice if MS informed users of this issue but I guess this is wishful thinking?
Again - Do No Harm.
A kind soul also posted this workaround (I just uninstalled the patch):
Old bug reintroduced with latest updates.
Here's a fix:
Start > Run > gpedit.msc to open the Group Policy Editor
In the Group Policy Editor: Local Computer Policy > Computer Configuration > Administrative Templates > System > Logon
In the right hand panel, double click on "Maximum retries to unload and update user profile", choose "Enabled" and set the Max. retries value to less than its default of 60. I set it to 5.
Bill Simeon MCSE
No comments:
Post a Comment