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

Anonymous

This is not the same issue as similar postings that have to do inability to delete folders that contain zero byte files.

If I try to rename any folder in my system, I get "Could not find this item" with the choices "Try Again" and "Cancel". When I click "Try Again", it always succeeds. So - my system isn't crippled - but it is so totally annoying. I can even right-click on my desktop, and choose "New... Folder" and type in a name, and I get "Could not find this item". The interesting thing is that the item's name does change even before I click "Try Again".

If I have a folder named "Folder1" and I rename it to "Folder2", I get the error that "Folder1" Could not be found - which is actually true, as it is already renamed to "Folder2".

Why is Windows 7 looking for the old folder name after renaming? I've also disabled AVG's live scanner to no avail.

Any thoughts or suggestions would be greatly appreciated.

Thanks.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

I finally got it.

I used the same solution for the similar issue in Windows Vista. Once i got to my company laptop, i exported this 2 registry keys.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\FolderDescriptions

Merged into my pc and voilà !!

The 'shell' command also works again (ex: shell:personal brings up the account folder)

I uploaded the reg file and you can get it here http://cid-fb5a28bc4a1cc9b6.skydrive.live.com/self.aspx/Public/Folder%5E_fix%5E_win7%5E_x64/FolderDescriptions.rar

This is for Win7 x64. Use it at your own risk.

0 comments

95 additional answers

Anonymous

2011-08-17T15:28:09+00:00

Hi Revo15,

Since the thread is rather old, I would recommend starting your own question so that the community can best focus on your specific issue.

Thanks for using Microsoft Answers!
Was this answer helpful?

0 comments No comments
Anonymous

2011-08-17T13:18:21+00:00

Looking at varredor's solution (as that I too was aflicted by this bug), I had one system affected and another one not.

I compared both registries at the locations listed and found a minute difference - and this difference works!

faulty registry entry

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions{9E52AB10-F80D-49DF-ACB8-4330F5687855}]

"RelativePath"="CD Burning"

"ParentFolder"="D:\Temp"

working entry

"RelativePath"="Microsoft\Windows\Burn\Burn"

"ParentFolder"="{F1B32785-6FBA-4FCF-9D55-7B8E7F157091}"

faulty registry entry

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\FolderDescriptions{9E52AB10-F80D-49DF-ACB8-4330F5687855}]

"RelativePath"="CD Burning"

"ParentFolder"="D:\Temp"

working entry

"RelativePath"="Microsoft\Windows\Burn\Burn"

"ParentFolder"="{F1B32785-6FBA-4FCF-9D55-7B8E7F157091}"

so this fixed it for me - so take a look at your registry entries for these locations and compare it to the working entries listed and see if there is a difference

Did you delete the Faulty registry ? i tried varreder method but it hasnt solved my problem
Was this answer helpful?

0 comments No comments
Anonymous

2011-08-09T16:47:07+00:00

Finally, this works!!! (tried it on Win7 x32)
Was this answer helpful?

0 comments No comments
Anonymous

2011-06-29T20:17:35+00:00

WOW! I really love when I get a problem and can just go on the inet and find a solution immediately. Thanks a thousand times!!! :D
Was this answer helpful?

0 comments No comments