I've searched Group Policy, but there is not an option that I could find to remove the Search bar from Windows Explorer.
I do not know what else to suggest other than a repair install to see if that may help. However, it seems more like some issue with the video driver and may not help anyway. Perhaps when the 9.3 version comes out it may be resolved. You might send in a report to AMD/ATI about the 9.2 driver and this issue to help make them aware of this issue to.
Alright than. Since I just installed this build, repair install probably won't help. About the driver, I personally would blame the build, due to the fact that the very same driver was performing flawlessly under the 7000. But who knows. Thanks for all the help, and I will post here if I'll find a solution.
Noticed this thread when searching for the same problem. I also use a 30" monitor at 2560x1600 and no matter what I've done I cannot resize the explorer path and search fields.
Here's how I can replicate the bug:
I've tried reinstalling, installing 7000 first and upgrading to 7048, installing with stock clock speeds..no help. I can also resize the fields if I move down to a lower resolution.
- Create a new account
- Log into it
- Open Explorer
- At this point everything works just fine, fields can be resized.
- Resize the window in any way and close the Explorer window
- Open Explorer again
- Problem is there, resizing fields no longer possible
I don't think it's a graphics driver issue either because it happens with the Nvidia 179.something as well as the 181 version available from their website.
I checked with process monitor and it seems that Windows somehow loses the registry key or class that handles this feature, gives some sort of NOT FOUND messages. I don't know enough about the registry to tell which key is the issue.
7000 doesn't have this issue but does have something similar in the Open dialogs, the path bar is really small in those too but you can still resize, the setting just isn't saved.
Last edited by laxu; 10 Mar 2009 at 16:08.
Hello Laxu,
This must be a bug. I would recommend to send feedback to Microsoft on this to help make them aware of this issue. Hopefully with enough feedback they can come up with a fix this in the next release.
Laxu, I'm happy to hear it's working for you in this build. Thank you for posting back your results. :)
Quote