Windows explorer delay when openning or changing folder
Hi all, I installed windows 7 professional a few weeks ago. At the beginning, everything's fine. But recently i experience a delay of 2->3 seconds whenever I open a folder/ change to a new folder (even back to previous folder also has the same problem). I used process monitor to see whether windows explorer has anything strange, and I noticed that audiodg.exe is the one that takes 2-3 seconds. Here's the screenshot of process monitor: http://img691.imageshack.us/img691/156/procmon.jpg In this one, audiodg takes 2 seconds for thread exit. I know audiodg is a system process from microsoft. But can anyone explain to me why it takes so long to exit this thread? How to fix the delay problem when openning folder? Thank you very much
November 24th, 2009 5:21am

Hi, This behavior may occur if the sound card driver is not up to date. To troubleshoot this issue, please perform the following steps: Reinstall driver ============== 1. Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Search box and press Enter. 2. Double click to expand "Sound, video and game controllers". 3. Right click your sound card and click Uninstall. 4. Check "Delete driver software for this device" check box, click OK. 5. Restart the computer If the issue persists, test it in Clean Boot mode. If it does not work, you can use the following tool to check the Shell Extensions: Run ShellExView ================= http://www.nirsoft.net/utils/shexview.zip Please Note: The third-party product discussed here is manufactured by a company that is independent of Microsoft. We make no warranty, implied or otherwise, regarding this product's performance or reliability.Hope it helps!Vivian Xing - MSFT
Free Windows Admin Tool Kit Click here and download it now
November 25th, 2009 9:29am

Hi, Many thanks for your answer. I have tried all of your suggestions, even disabling all third-party shell extensions but still no improvements. When I uninstalled sound card driver, I no longer see any "suspicious" process under process monitor, but the delay still remained. This problem only happens to windows explorer, all other programs start quite fast :( . I don't know what's happening here
November 25th, 2009 5:12pm

Hi, How about testing it in new account: Create a new user account ==================== 1. Click the Start Button, type User Accounts in the start search pane and press Enter. 2. Click Manage user accounts. 3. Click Create a new account, and type the name. 4. Choose account type as Computer administrator. 5. Click Create Account. 6. Log off and log on with the new account. If the issue persists, please update your BIOS, chipset and device drivers to the latest version. In addition, if any security program (antivirus, firewall) is installed, please temporarily disable it.Vivian Xing - MSFT
Free Windows Admin Tool Kit Click here and download it now
November 27th, 2009 9:43am

Hi, Many thanks for your answer. I have tried all of your suggestions, even disabling all third-party shell extensions but still no improvements. When I uninstalled sound card driver, I no longer see any "suspicious" process under process monitor, but the delay still remained. This problem only happens to windows explorer, all other programs start quite fast :( . I don't know what's happening here And you won't get a straight answer from Microsoft until they fix this file in how it works period. I have read and reread many blogs and posts in this forum and others about the audiobg.exe file and this problem along with many others ppl were experiencing since Vista was out have not been resolved and Microsoft's answer seems to imply there is something wrong with your computer or drivers or whatnot when the reality is that the audiodg.exe driver is coded poorly to allow for such things to happen. On my computer the audiobg.exe at times exceeds 980mb of commit memory and drags the whole system to a crawl when switching between applications. This process leaks memory and does not release it back to the system and I have to run 3 process memory management utilities to implicitly bar this process from exceeding 100mb period. They are Minimem, Smartram and Cleanmem. I shouldn't have to run three 3rd-party memory utilities to make a core subsystem file behave if it was coded correctly. Maybe its time Microsoft developers investigate this file and why its coded so poorly to bring a system to a crawl in a very fresh OS like Windows 7. Once the process is killed the system responds and acts very snappy at the result of no sound of course since its a core sound subsystem file. Only a reboot fixes the sound issue and then after a time the problem starting amping up all over again. Check this out and tell me if this problem can be encountered in Windows 7 like it was in Vista and some of these problems still are there. Time to do something about this Microsoft. You have waiting over 3 years and not done anything about a seriously degraded core file. http://blogs.msdn.com/larryosterman/archive/2007/01/31/what-is-audiodg-exe.aspx
January 11th, 2010 5:08am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics