All programs "lock up" when selecting file/open (or save)/and select pull down menu from Look in/Save in
I had asked a very similar question a while back: https://www.experts-exchange.com/questions/21825856/Long-delay-when-navigating-folders-in-save-as-or-open-file-boxes-only-occurs-in-Microsoft-products.html
Back then the problem only affected Microsoft programs. I suppose the solution (changing NIC driver) was only a coincidence.... because after a little more than one month....
the problem is mysteriously back and with vengeance!
I have tried a system restore back to a few days ago when I was sure I did not have this problem. Unfortunately even though the system restore was successful, the problem is still evident.
Detailed problem description:
- Occurs in any program;
- When selecting file / open and selecting the pull down menu from Look In (folder listing)
Or when selecting file / save as and selecting the pull down menu from Save In (folder listing)
The program appears to lock up. Actually it begins responding after 1 1/12 minutes.
After this point I can navigate the folders (both local and network) without delay.
If I close the folder browse and go back to the program, I will experience the above delay again and
each time;
Other unusual occurrences
- I have also noted that clicking on my computer from file explorer will display the hour glass for about the same
amount of time as the above described delay. This was absolutely not the case before this problem began
this evening.
Any suggestions leading to a fix will be rewarded 500pts. Please do not suggest reinstalling Windows.
What I have done:
- Restored to an earlier date (system restore point)
After completing this message, I will try restoring to another even earlier date;
- Updated Windows XP Pro and Office 2003 (prior to this, almost everything was already up-to-date.);
- tested for Viruses (Bitdefender), Adware (MS Defender);
- Defragged hd;
- looked for broken network orphans;
- ran Registry Mechanic
- ran Ccleaner
I am out of ideas!
Help please.
Back then the problem only affected Microsoft programs. I suppose the solution (changing NIC driver) was only a coincidence.... because after a little more than one month....
the problem is mysteriously back and with vengeance!
I have tried a system restore back to a few days ago when I was sure I did not have this problem. Unfortunately even though the system restore was successful, the problem is still evident.
Detailed problem description:
- Occurs in any program;
- When selecting file / open and selecting the pull down menu from Look In (folder listing)
Or when selecting file / save as and selecting the pull down menu from Save In (folder listing)
The program appears to lock up. Actually it begins responding after 1 1/12 minutes.
After this point I can navigate the folders (both local and network) without delay.
If I close the folder browse and go back to the program, I will experience the above delay again and
each time;
Other unusual occurrences
- I have also noted that clicking on my computer from file explorer will display the hour glass for about the same
amount of time as the above described delay. This was absolutely not the case before this problem began
this evening.
Any suggestions leading to a fix will be rewarded 500pts. Please do not suggest reinstalling Windows.
What I have done:
- Restored to an earlier date (system restore point)
After completing this message, I will try restoring to another even earlier date;
- Updated Windows XP Pro and Office 2003 (prior to this, almost everything was already up-to-date.);
- tested for Viruses (Bitdefender), Adware (MS Defender);
- Defragged hd;
- looked for broken network orphans;
- ran Registry Mechanic
- ran Ccleaner
I am out of ideas!
Help please.
ASKER
Callrs: Thanks for the input but it is none of those issues either. This is a pretty high end computer with one of the best Zalman power supplies available. Hard drives are all SMART SATAs. Memory is Crucial.
Anyhow, all that was tested. The problem is something in Windows.
I had asked earlier but no one knew the answer.... so I will ask again... the common thread is that there is a long delay which appears as a lock up whenever a folder listing is initiated through a program.
Since this problem began, it also affects the behavior of File Explorer too. Whenever I open file explorer and do the unavoidable expanding of the "My Computer" folder, I see an hour glass for about as long as the aforementioned delays occur. This will happen even if I have already begun navigating "My Computer" in a separate open File Explorer. Once the hour glass has completed its routine, I can explore "My Computer" with no further delays. That is, until I close File Explorer or open a new File Explorer.
Obviously that is a specific Windows call and the problem is caused by something gone amiss.
That is either:
- a bad component such as a dll
- Windows is getting stuck on something (like a network dead network path) that no longer exists.
This may be fixed by:
- replacing a component;
- fixing some bad path
- correcting a registry problem
Someone on EE must know Windows well enough to point me in the right direction!
In the meantime, I will run Filemon from SysInternals and see if there is anything interesting to see.
Anyhow, all that was tested. The problem is something in Windows.
I had asked earlier but no one knew the answer.... so I will ask again... the common thread is that there is a long delay which appears as a lock up whenever a folder listing is initiated through a program.
Since this problem began, it also affects the behavior of File Explorer too. Whenever I open file explorer and do the unavoidable expanding of the "My Computer" folder, I see an hour glass for about as long as the aforementioned delays occur. This will happen even if I have already begun navigating "My Computer" in a separate open File Explorer. Once the hour glass has completed its routine, I can explore "My Computer" with no further delays. That is, until I close File Explorer or open a new File Explorer.
Obviously that is a specific Windows call and the problem is caused by something gone amiss.
That is either:
- a bad component such as a dll
- Windows is getting stuck on something (like a network dead network path) that no longer exists.
This may be fixed by:
- replacing a component;
- fixing some bad path
- correcting a registry problem
Someone on EE must know Windows well enough to point me in the right direction!
In the meantime, I will run Filemon from SysInternals and see if there is anything interesting to see.
ASKER
I must say, Filemon has to be one of the most useful (and free) tools ever invented!
I found the problem thanks to Filemon!
It is a program called uwdf.exe. Whenever it is running it causes the delays. If I remove it via the task manager, it just reappears the next time I initiate a file browse command again! How annoying.
I would say it is acting like a virus except according to several sites, it is supposed to be an important part of Windows, " Windows User-Mode Driver Framework"
It is found in the following folders:
c:\windows\prefetch
c:\windows\system32
c:\windows\RegisteredPacka
All are owned by Microsoft with the version number: 5.2.3790.1230 built by: dnsrv(bld4act)
Now what?
Next, I will search Google to see if anyone else has had similar problems with this file.
I found the problem thanks to Filemon!
It is a program called uwdf.exe. Whenever it is running it causes the delays. If I remove it via the task manager, it just reappears the next time I initiate a file browse command again! How annoying.
I would say it is acting like a virus except according to several sites, it is supposed to be an important part of Windows, " Windows User-Mode Driver Framework"
It is found in the following folders:
c:\windows\prefetch
c:\windows\system32
c:\windows\RegisteredPacka
All are owned by Microsoft with the version number: 5.2.3790.1230 built by: dnsrv(bld4act)
Now what?
Next, I will search Google to see if anyone else has had similar problems with this file.
Try also procexp from sysinternals to see if some app is hogging the CPU
>>it also affects the behavior of File Explorer too
In another thread, the culprit was an IDE device (not channel) that was disabled in the BIOS. Re-enabling the device fixed his Explorer problems..
How about also:
System files check: http://ask-leo.com/what_is_the_system_file_checker_and_how_do_i_run_it.html
And if that fails, a Repair Install: http://www.michaelstevenstech.com/XPrepairinstall.htm
Reduce startup clutter: http://www.nirsoft.net/utils/strun.html http://www.sysinternals.com/Utilities/Autoruns.html
>>it also affects the behavior of File Explorer too
In another thread, the culprit was an IDE device (not channel) that was disabled in the BIOS. Re-enabling the device fixed his Explorer problems..
How about also:
System files check: http://ask-leo.com/what_is_the_system_file_checker_and_how_do_i_run_it.html
And if that fails, a Repair Install: http://www.michaelstevenstech.com/XPrepairinstall.htm
Reduce startup clutter: http://www.nirsoft.net/utils/strun.html http://www.sysinternals.com/Utilities/Autoruns.html
ASKER
callrs: Did you see my last message? I found the problem.
Apparently uwdf.exe is an important Microsoft file but I know for certain I this file has NEVER appeared in the Process list before.
Any thoughts on this?
Apparently uwdf.exe is an important Microsoft file but I know for certain I this file has NEVER appeared in the Process list before.
Any thoughts on this?
ASKER
I should stress the annoyance of this problem. All morning I have had to do a Control-Shift-Escape, sort processes, and End Process on uwdf.exe. Saving a file in Firefox, Opening a document in Dreamweaver, Word, Saving a document... whatever.... each time the application "freezes" and each time I have to shut down uwdf.exe. Unfortunately, the dang thing starts up again the next time I need to save or open a file or browse the my folders.
sconnell can you give the location of this file because one its not a core file two you should not see it running in your process's list so can you find the exact location of the one that is running in your process's. Use hijack this to find the location. Also type type the name exactly are there any capital letters such as uWDF or what??
ASKER
Already did.... and according to many websites it is a core file (I've never seen it before thought).
It is found in the following folders:
c:\windows\prefetch
c:\windows\system32
c:\windows\RegisteredPacka
All are owned by Microsoft with the version number: 5.2.3790.1230 built by: dnsrv(bld4act)
name is uwdf.exe and it appears in processes whenever I initiate any of the aforementioned tasks.
Right now it does not appear in processes.....
Now I will go to File/Open File/ and as soon as I try to click the pull down menu in "Look in", that uwdf.exe suddenly appears and Firefox appears to lockup. Again, it does not matter while program I do this in.
It is found in the following folders:
c:\windows\prefetch
c:\windows\system32
c:\windows\RegisteredPacka
All are owned by Microsoft with the version number: 5.2.3790.1230 built by: dnsrv(bld4act)
name is uwdf.exe and it appears in processes whenever I initiate any of the aforementioned tasks.
Right now it does not appear in processes.....
Now I will go to File/Open File/ and as soon as I try to click the pull down menu in "Look in", that uwdf.exe suddenly appears and Firefox appears to lockup. Again, it does not matter while program I do this in.
>>All morning I have had to do a Control-Shift-Escape, sort processes, and End Process on uwdf.exe
Why not prevent it from starting up? It may be an essential component, but if you want to kill it, you probably can. But I don't know what the result will be. So with that caution, here's how to disable it: just use autoruns (link above)
BTW, I don't have uwdf listed on my XPSp2 machine. Do you venom96737?
Why not prevent it from starting up? It may be an essential component, but if you want to kill it, you probably can. But I don't know what the result will be. So with that caution, here's how to disable it: just use autoruns (link above)
BTW, I don't have uwdf listed on my XPSp2 machine. Do you venom96737?
ASKER
What I don't understand is why I seem to be the only one with this problem.
It is located here (in the registry):
HKEY_CURRENT_USER\Software
HKEY_LOCAL_MACHINE\SOFTWAR
HKEY_USERS\S-1-5-21-164552
My initial guess is that it is added by Windows Media Player 10 or 11.
It is located here (in the registry):
HKEY_CURRENT_USER\Software
HKEY_LOCAL_MACHINE\SOFTWAR
HKEY_USERS\S-1-5-21-164552
My initial guess is that it is added by Windows Media Player 10 or 11.
ASKER
It is also not in the startup.
ASKER
Very interesting!
I found another incidence where uwdf.exe starts up. When I open a winrar.exe compressed file.... it stops because of uwdf.exe. Of course, killing the process allows winrar to function.
Finally, now I understand why I can no longer remote to this computer using Microsoft's Remote Desktop Connection. It is the damn uwdf.exe that is preventing it from starting.
Short of deleting the program.... never mind, I am going to try renaming this program.
I found another incidence where uwdf.exe starts up. When I open a winrar.exe compressed file.... it stops because of uwdf.exe. Of course, killing the process allows winrar to function.
Finally, now I understand why I can no longer remote to this computer using Microsoft's Remote Desktop Connection. It is the damn uwdf.exe that is preventing it from starting.
Short of deleting the program.... never mind, I am going to try renaming this program.
May have to rename from SAFE-MODE with Command Prompt, or just SAFE MODE
If you do it & windows wont start up, then go back into safe mode & name it back...
If you do it & windows wont start up, then go back into safe mode & name it back...
ASKER
Well, renaming the file didn't quite solve the problem!
Now there is a short delay (about 10 seconds) then the program continues.
The problem: The Explorer process now goes to 100% and stays there!
$*%&^%
Now there is a short delay (about 10 seconds) then the program continues.
The problem: The Explorer process now goes to 100% and stays there!
$*%&^%
ASKER
BTW, I was able to rename without difficulties in normal Windows mode. Still, I am not winning this battle.
Wanna do a Repair Install? http://www.michaelstevenstech.com/XPrepairinstall.htm
If that won't work it may be some hardware thing
>>Callrs: Thanks for the input but it is none of those issues either. This is a pretty high end computer with one of the best Zalman power supplies available. Hard drives are all SMART SATAs. Memory is Crucial.
Even a new system can have errors. In fact if a hardware failure is going to occur, it usually occurs at the beginning of its life cycle, or at the end. In between it usually remains stable.
The memory test & hard disk surface scan should be done, as mentioned above...
If that won't work it may be some hardware thing
>>Callrs: Thanks for the input but it is none of those issues either. This is a pretty high end computer with one of the best Zalman power supplies available. Hard drives are all SMART SATAs. Memory is Crucial.
Even a new system can have errors. In fact if a hardware failure is going to occur, it usually occurs at the beginning of its life cycle, or at the end. In between it usually remains stable.
The memory test & hard disk surface scan should be done, as mentioned above...
ASKER
Callrs: this is clearly a code problem.
The computer is over a year old now. It also does a number highly intense (math intense and sometimes hard drive) applications nearly 24/7. None of those applications are failing. The only problem is with what I already mentioned. Suspect program has already been found. Obviously it is going to take more than simply rename this file. Explorer is going 100% because of an inherant weakness in its design. Meaning that Explorer is unhappy because it is looking for a file that "no longer exists".
My next step is to remove references to uwdf.exe from the registry. That should solve the 100% issue.
The computer is over a year old now. It also does a number highly intense (math intense and sometimes hard drive) applications nearly 24/7. None of those applications are failing. The only problem is with what I already mentioned. Suspect program has already been found. Obviously it is going to take more than simply rename this file. Explorer is going 100% because of an inherant weakness in its design. Meaning that Explorer is unhappy because it is looking for a file that "no longer exists".
My next step is to remove references to uwdf.exe from the registry. That should solve the 100% issue.
>>remove references to uwdf.exe from the registry
Create a system restore point first...?
Messing with the registry may cause trouble
Create a system restore point first...?
Messing with the registry may cause trouble
ASKER
After renaming that file, running a registry clean up, and finally rebooting. All is well in my world.
What I would like to know now is what did I just disable?
That problem was nothing but trouble for me so what was its purpose?
What I would like to know now is what did I just disable?
That problem was nothing but trouble for me so what was its purpose?
Look in your event logs for some clues:
http://www.windowsnetworking.com/j_helmig/wxpevent.htm Windows XP Event Viewer
http://www.windowsnetworking.com/j_helmig/wxpevent.htm Windows XP Event Viewer
Problem resolved, but sconnel did it on own.. Good analysis here by sconnell. paq.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
callrs: Thanks callrs.
...and thank you to all those who offered help.
Shawn
...and thank you to all those who offered help.
Shawn
2) Surface Scan the hard disk for bad sectors: http://www.pcstats.com/articleview.cfm?articleid=1583&page=5
I.E. from the command prompt: chkdsk /f /r
3) If memory & hard drive test out OK, then it might be some other hardware problem (motherboard, CPU, PCI slot, ...). Sometimes it's better just to buy a new motherboard than to try to sort out the mess, but you can swap parts with known working parts to locate the defective part.
Special Note: Make sure you have a quality power supply, not a cheap light-weight $20 one. Clean stable power is critical.