"Item Not Found ... Verify location and try again."

[Pudding_Man]

Win7-64 Home Premium OEM on a little desktop system at my home.

 

When I rename file XXX, I get the message:

 

Item Not Found. XXX is no longer located in c:\...

Verify location and try again. Date created: xx-xx-xxxx

 

When I click "Try Again" the rename looks complete. But it causes numerous other problems.

 

I checked attributes on the folder, did a "take ownership", etc. UAC has been turned off for months.

 

This is evidently a known problem, possibly connected to KB980408, which I haven't even managed to find on my system.

 

I haven't been able to positively track it down, focus on the exact problem and solution. I need to fix it ASAP.

 

Any help with this would be much appreciated. Someone has nailed it down?

 

Thx,

P

Edited January 25, 2011 by Pudding_Man
add detail

[SYNACK]

Do you have a virus checker on there, if so which one. Had problems with dirty old AV packages locking files like that with on access scanning. Try turning off realtime protection on your AV and see if that fixes it. If it does MS Security Essentials usually works nicely with Windows 7. Edited January 25, 2011 by SYNACK

[Pudding_Man]

There is no (repeat NO) evidence of a malware problem.

 

Take a peek at

[MSUPDATE KB980408]Warning To All Win7 x64 Users. - Overclock.net - Overclocking.net

if you're really interested.

 

P

[SYNACK]

I was not implying that there was malware merely that the Antivirus software itself may be causing problems. Turning off UAC does make some things act a little strangely though and for its features it is best to leave it on anyway.

 

Have not experienced the issue with the above KB on any of our stations so it may be a special set of circunstances that triggers it and as your system does not have the update anyway it is unlikely to be that.

[Pudding_Man]

I was not implying that there was malware merely that the Antivirus software itself may be causing problems. Turning off UAC does make some things act a little strangely though and for its features it is best to leave it on anyway.

 

Have not experienced the issue with the above KB on any of our stations so it may be a special set of circunstances that triggers it and as your system does not have the update anyway it is unlikely to be that.

 

Ahhh. You've got it all figured out perfectly!

 

Thank You! Thank You! Thank You! :-)

 

P