G
Guest
Wishful thinking... The error is extremely rare, but still occurs with
887742 update installed. I hadn't seen the error in about 2 weeks and just
saw a machine throw the error up today. I wish I knew which update is
causing this stupid error. It's security update released in feb. causing
this, but which one, I don't know. They released 4 or 5 all at once. The
error actually occurs during shutdown and windows throws a dumprep in the
"run" registry.
Microsoft Please help!!!!
887742 update installed. I hadn't seen the error in about 2 weeks and just
saw a machine throw the error up today. I wish I knew which update is
causing this stupid error. It's security update released in feb. causing
this, but which one, I don't know. They released 4 or 5 all at once. The
error actually occurs during shutdown and windows throws a dumprep in the
"run" registry.
Microsoft Please help!!!!