7826
Tweaking.com Support & Help / Re: Newest All In One Repair Beaten
« on: November 24, 2011, 09:25:38 pm »
I use avast my self. Never seen this problem before but the fact that we have a perfect 16 min window before things work correctly makes me want to check 3 things right off the bat.
1. Since these services seem to be hung up waiting then lets look at what is able to stop programs from running. The Antivirus. Its a long shot, I personally don't think it is avast but we need to cover all bases.
2. Windows has a delayed start set on some of the services. I haven't ever looked yet, but I wonder what the timeout value is for that.
3. You say the windows repair fixed this before. One thing the services need is access to the reg keys and files. If they don't then you are waiting for windows to timeout the service. But the old version didnt have access to all the keys, the new one does. So it should have helped more. Unless this is a new cause for this bug.
I have seen windows hang waiting for a command queue to finish, then everything comes loading up like mad.
So the trick now is to find out if it is a windows service or program, or a 3rd party program or service causing this.
Do the msconfig and disable all non ms services and then all non ms programs at startup. If the problem still happens then we know we need to look at drivers and windows services.
If the problem doesn't happen then we know it is a 3rd party program
Lets go from there
Shane
1. Since these services seem to be hung up waiting then lets look at what is able to stop programs from running. The Antivirus. Its a long shot, I personally don't think it is avast but we need to cover all bases.
2. Windows has a delayed start set on some of the services. I haven't ever looked yet, but I wonder what the timeout value is for that.
3. You say the windows repair fixed this before. One thing the services need is access to the reg keys and files. If they don't then you are waiting for windows to timeout the service. But the old version didnt have access to all the keys, the new one does. So it should have helped more. Unless this is a new cause for this bug.
I have seen windows hang waiting for a command queue to finish, then everything comes loading up like mad.
So the trick now is to find out if it is a windows service or program, or a 3rd party program or service causing this.
Do the msconfig and disable all non ms services and then all non ms programs at startup. If the problem still happens then we know we need to look at drivers and windows services.
If the problem doesn't happen then we know it is a 3rd party program
Lets go from there
Shane