MS04-032 problem

[Guest]

Hi,
I have been testing MS04-032 on a few of our workstations in our company via
loading from the windows update site. and after i reboot i am getting a pop
up box with the following message.

One of the files containing the system's Registry data had to be recovered
by use of a log or alternate copy. The recovery was successful.

The error appears in the event viewer but there is no extra information
relating to the problem there.

I would like to release the patch via SUS sometime this week to the rest of
our workstations but am a little nervous about doing that when i am geting
this error.


Has anybody else had this issue or is anyone able to help?

 

[Guest]

Hi Vincent,

I can't help you, but we are experiencing the exact same thing. I'm hoping
someone can provide a fix! Thanks.

 

[Jeremy]

Yes, we are experiencing the same problem at work as well. I posted a
message on microsoft.public.windowsxp.network_web last Friday, but
have yet to hear any solutions for this problem. The one solution
that we have discovered at work is to install SP2, but we are no where
near ready to roll this out yet.

 

[Guest]

We have the same issue with SP2, its just not an option to install at the
moment.
I am wondering if it has something to do with this
area....HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP2.

 

[Guest]

here ya go guys

http://support.microsoft.com/?id=843426

 

[gmiller32]

This kind of tells us what is wrong as I am having the same problem,
but I am still not sure what to do about it. Can't load SP2 yet and
can't distribute a hotfix with SUS. Anybody got any ideas?

Thanks,
Greg

 

[Debbie]

Hi Vincent,
I've been receiving the same error message after installing MS04-032.
It only appears once after the reboot. After looking at the log and
'reporting to M$', I got sent to their support center and it
identified the error as ID 26 and said "The program could not load a
driver because the program user doesn't have sufficient privileges to
access the driver or because the drive is missing or corrupt". Note
the 'drive' (not driver) is missing or corrupt statement in the last
part of the message. Yikes.

This is happening to Dells, one of them right out of the box. I called
Dell about the problem the other day and they hadn't heard of it. My
main concern is that when I did a search on the error msg., discussion
boards mentioned that when they got this message (not because of
installing MS04-032) and their system would eventually fail. I'm sure
you've read some of the stories.

Are you using Dells?

Seems very strange that no information is available about this.

 

[Guest]

Hey Debbie,

Yeah i have seen most of the post's on the web relating to this problem, i
have spent coutless hours searching the web before Microsoft sent me the fix.

The difference we have though is that the error message appeared everytime
after a reboot or log off and on and our pc's are compaq's, not just one
model though, didnt matter what model in fact.

I have applied the fix that Microsoft have sent me and it seems to be
working ok on my test pc's. No more error!, i was happy to see that.

Maybe try getting the fix from Microsoft and load it up?? Can only try ey.

Vincent

 

[Debbie]

Vincent,
Glad to hear the hotfix worked for you! Thanks for the info. Question:
how are you planning to distribute the hotfix after you release
ms04-032?

Thanks & happy Friday!
Debbie

 

[Guest]

I have langaurd so i will probably use it for the rollout. If you dont have
anything like that, maybe try psexec?

 

[Guest]

I too have this problem but it seems only with our Dell computers and not all
models.
I also note that the llink you sent indicates XP and NT4 domain. We're AD
running with Sever 2003. Is this hotfix still applicable?
Thanks

 

[Torgeir Bakken \(MVP\)]

I too have this problem but it seems only with our Dell computers and not all
models.
I also note that the llink you sent indicates XP and NT4 domain. We're AD
running with Sever 2003. Is this hotfix still applicable?

Hi

As I wrote in my first post to you in the other thread, disregard
the NT 4.0 domain reference in that KB article.

Call for the hotfix and test it on a computer that have the problem,
I would think it will solve the problem.

Please post back any result