Renaming any folder produces "Could not find this item". Clicking "Try Again" always works. Why?

Thanks, worked for me on my Windows 7 x64 box, much appreciated.

I don't want to downplay varredor's fix. It does work.

However, looking at the supposed fix, which contains 2183 lines btw, I'd be very wary before blindly applying it. Some of this stuff looks horribly wrong.

Shouldn't you MVP guys step in when someone gives bad advice? Better yet, give proper solution?

Cutting your head off when it aches does work.

More on the subject:

http://www.overclock.net/windows/721973-msupdate-kb980408-warning-all-win7-x64.html

http://www.sevenforums.com/general-discussion/81527-need-help-unable-rename-move-folders.html

http://social.answers.microsoft.com/Forums/en-US/w7files/thread/e2cf38c7-9e77-4256-89de-6308df53d5f9

The x86 registry fix works for sure. Many thanks!

I also have this same problem on an up to date system. I am running Windows 7 32-bit.

If you are having/had this problem as well, you have probably come across mention of the kb940408 that seemed to have caused this issue for some in the past. However, on my recent Win 7 build with integrated updates (latest updates of which kb940408 is NOT a part as it has been superseded) I am experiencing the "Item not found" problem. It happens across partitions, and happens when I want to rename a folder, or delete it. Like others have mentioned it will give you the "Try again" option, and when I try again it will work.

One person mentioned that in his case the problem came about because of a registry tweak he applied beforehand that removes the Libraries in Windows 7 (http://social.technet.microsoft.com/Forums/en-CA/w7itproui/thread/2ca522e9-f46c-4e88-9ea0-3c93359e878e), but I did not remove the Libraries so the cause is different. Or is it? I ask that because Varredor's fix did work for me: but it also uses a technique similar to restoring the Libraries that that person in the linked thread mentioned. Namely, "NameSpace" and "FolderDescriptions". So the reason the 'restore Libraries" reg tweak may have worked for that user is for the same reason Varredor's tweaks works, in that it writes FolderDescriptions that are somehow lacking.

About the KB940408 issue, like I said it doesn't apply to my problem directly as I don't have it installed. But, here is the thing. A friend of mine who has in-depth knowledge of updates/hotfixes and compares them against each other and know which ones supersede older ones, etc., told me that the KB940408 update has been superseded. This is what he told me:

"KB980408 is shell32.dll (and LSA component update). So yes shell32.dll can cause this issue; it's not on the [current] list because it's (kinda) very old update and gets superseded by KB981506 and KB982405."

So it stand to reason that one of these 2 updates is causing this issue again. A Win 7 build I did a month before did not have at least 1 of these updates and I did not have this problem. However, my problem has been verified on two different (recent) builds that included these updates. The first time it happened was when I applied (live, from within Windows) a couple of the most recent updates. The latter of the 2 updates mentioned is KB982405, which I applied 'live'. I think it is then that I started experiencing my problem.

So, to summarize, I think KB940408 can still be causing this issue for some (if they have it installed). For people who hunt for the latest updates they may have come across KB981506 and KB982405 which may be causing their issue. The main culprit of these 2, to me, would be KB982405 as it was made available to me on the 29th of April which is around the time I installed it live and my problems began. After this, I made a Win 7 image with integrated updates, including the KB982405. Upon fresh install, I had this "Item not found" problem again. Since this latter update supersedes KB940408 (which already had been superseded but other KB's in the past) , KB940408 was not part of my latest build.

I hope this is clear and may shed some light on this issue. Although I am still in the dark myself having to deal with a crippled build right now. MS, fix this issue please!

By the way, there appears to be yet another 'fix' to this problem posted by a user called "HellGates". Follow the link: http://www.overclock.net/windows/721973-msupdate-kb980408-warning-all-win7-x64-2.html

PS: Some new updates/hotfixes came my way. When I build a new Win7 image I will test and see if this problem has been resolved. I will post there what my findings are.