New conroe now takes 5 minutes to boot, and I can't access network settings?
Just installed kaspersky, which I have now disabled but it still happens. Had a wireless network on the Asus p5w, and notice that I now cant access any settings on it. Dialogue box comes up say Server busy, then it gave me 60 seconds to shut down because of NT Authority???
Fine before I installed kaspersky. The wireless network disappeared from the taskbar.
Now dialogue box comes up saying SERVER Busy with two options switch task or retry
I switch task and the Start menu pops up, and the Server Busy appears again
lol, help!
any ideas?
Am
edit. Found microsoft page on the problem, but the resolution dont work. Says that a service is busy and has been set to automatic instead of manual and should edit the registry and change a key to "3". Looked in the reg and the key is "3" already - oh-no feel a reinstall coming on
edit just throwing in my findings in case anyone else gets this, seems from event log that DCOM is finding errors in not finding a device so the server is busily searching for it - it may be the Asus solo wireless network.....
Just installed kaspersky, which I have now disabled but it still happens. Had a wireless network on the Asus p5w, and notice that I now cant access any settings on it. Dialogue box comes up say Server busy, then it gave me 60 seconds to shut down because of NT Authority???
Fine before I installed kaspersky. The wireless network disappeared from the taskbar.
Now dialogue box comes up saying SERVER Busy with two options switch task or retry
I switch task and the Start menu pops up, and the Server Busy appears again
lol, help!
any ideas?
Am
edit. Found microsoft page on the problem, but the resolution dont work. Says that a service is busy and has been set to automatic instead of manual and should edit the registry and change a key to "3". Looked in the reg and the key is "3" already - oh-no feel a reinstall coming on
edit just throwing in my findings in case anyone else gets this, seems from event log that DCOM is finding errors in not finding a device so the server is busily searching for it - it may be the Asus solo wireless network.....
Last edited: