If you are performing an operation in explorer (like opening a folder or a network share, or doing a search) and exploer decides it's going to take a while, the location bar at the top turns into a green progress bar. It is somewhat rare under normal operation unless you are on a network which can be slow (spun down drives etc). Or you do a search across a large enough area of disk.
Thanx seal for clarification.
Windows 7 Freezing
Explorer SLOW on large folders
http://knowthyanswer.blogspot.com/20...-in-vista.html
I have done a clean prep without applications, but it was added to the domain then taken out with the problem still happening. I also currently have one test machine that is in a container with no group policy enforced, this machine is still having trouble. We do have an IDS and a Firewall, but I do not have anything to do with those and have no access to them. (distributed IT department) I do not believe that it is a hard drive issue since while it is happening I am able to still use the machine. I can even type C: directly into the address bar in Explorer and get to the drive while the My Computer window is green baring, but not always.
Hmmm, there are some network issues that can block explorer for a long time. Poorly performing or missing mounted network shares for example. There may be quite a few more that are domain specific that are probably out of my league. Having a computer connected to a domain then removing the domain could be causing an undue issue even though (or even because of) having BEEN setup to be connected to a domain.
I guess one test is to have a machine setup for everything, all your software and other setup but NO domain or group policy changes, see if it works fine, then add to domain and see if they show up. Just to confirm that it is probably a domain networking issue. But beyond that I can't add anything else...
I just looked at this article: How to prevent Windows Vista's 'green ribbon of death' - Computerworld
Sounds like your baby. Do any of the solutions help?
And Here: green ribbon of death
There are a number of posts in this forum with GRoD in the title.
I have one test machine that is looking promising, it hasn't had a GRoD yet. It is prepped normally and on the domain in a container with no policy and no mapped drives. I have a suspicion that the network drives may be causing the issue, but how can this be corrected? We can't just tell the users that they can't have their network shares. We probaly have 50/50 novell/microsoft shares. The Novell shares use CIFS mapping to map without using the novell client, I'm wondering if this is contributing to my headache also.
Maybe you need to turn off some stuff. Maybe your network is jamb with puters auto searching every other puter.????????????
Turn off auto anything, go manual or on demand only.
Your machine that was added and then removed from the domain is NOT a valid test. That is because the machine will be forever tattooed with some domain information and you can never be sure that all registry changes are change back completely.
You need a machine that has a clean Windows 7 load and has NEVER been added to the domain for the test.
I would take a KNOWN machine that is NOT working, format the drive and load Windows 7 from scratch on it. Test it! If it works then you KNOW it is a domain problem. You need to remove the Domain from the equation to move forward. -WS
Quote