J
JIRI
Hi thank you for answehr
my problem is http://support.microsoft.com/default.aspx?
kbid=326572
and I dont know haw setup back my windows when is
starting open some software. On error window is not any
number just "explorer.exe error and will be closed" And 3
sec. after windows explorer starting again and is again
closed and again and again. I can operate true Task
Manager.In Processes is many "drwtsn32.exe" . Ihave
Windows 2ooo Profesional Czech Language. I was try
download updates and hotfix true other PC and than instal
in my PC but nothing change. I am sorry for my englich.
Thank you for help.
SYMPTOMS
After you log on, Explorer.exe may repeatedly generate
access violation error messages. The access violation
occurs in the Browseui.dll module. However, this symptom
does not occur when you log on with administrator rights.
CAUSE
This problem may occur if one or more registry keys are
inaccessible. The inability to obtain access to registry
keys would run an errant code path that would always
cause a fault. The fault occurs because the incorrect
release method was being called on the object.
my problem is http://support.microsoft.com/default.aspx?
kbid=326572
and I dont know haw setup back my windows when is
starting open some software. On error window is not any
number just "explorer.exe error and will be closed" And 3
sec. after windows explorer starting again and is again
closed and again and again. I can operate true Task
Manager.In Processes is many "drwtsn32.exe" . Ihave
Windows 2ooo Profesional Czech Language. I was try
download updates and hotfix true other PC and than instal
in my PC but nothing change. I am sorry for my englich.
Thank you for help.
SYMPTOMS
After you log on, Explorer.exe may repeatedly generate
access violation error messages. The access violation
occurs in the Browseui.dll module. However, this symptom
does not occur when you log on with administrator rights.
CAUSE
This problem may occur if one or more registry keys are
inaccessible. The inability to obtain access to registry
keys would run an errant code path that would always
cause a fault. The fault occurs because the incorrect
release method was being called on the object.