I recently started having this issue, and aparrently I’m not alone as others are also complaining of this issue. Some have reported it to be update KB980408, but that uninstalling it won’t fix the issue? I cannot confirm or deny this, as there’s a registry patch/fix instead.

For reference, this is the error in question (when trying to rename a folder).

And here are some hotfix registry patches to apply to fix the issue. I’m sure Microsoft will get enough complaints about this to fix the issue, but in the meantime this should do the trick. As always, use this at your own risk, and don’t touch it if you’re unaware of what the registry is.

FolderFix – Includes both x64 and x86 versions, and should work on Windows 7 and Windows Vista.

Tagged with:  

112 Responses to “Guide: Fix Windows Folder Renaming (Could Not Find This Item)”

  1. - says:

    remove&4301dce8d6147bd39a2d90d22e621ee2_NX

    [Reply]

  2. Lycan says:

    Thanks a lot..works perfect on x64 :)

    [Reply]

  3. Shah says:

    this worked perfectly. Thanks a million.

    [Reply]

  4. VeryHappy says:

    Thanks so much. Worked great.

    [Reply]

    Sand1982 Reply:

    @VeryHappy,

    where we find this (&4301dce8d6147bd39a2d90d22e621ee2_NX)

    [Reply]

  5. Sand1982 says:

    where we find this (&4301dce8d6147bd39a2d90d22e621ee2_NX)

    [Reply]

  6. Nick T says:

    Thanks for this, problem sorted.

    [Reply]

  7. John says:

    works with Windows 8 64

    [Reply]

  8. LafinJack says:

    This also worked for me with Windows 8 x64. Thank you!

    [Reply]

  9. Iraj says:

    Great friend.. It works for me

    [Reply]

  10. avhb says:

    thank you so much!!! I was already worrying that I had to reinstall my laptop
    Anyway Thanks

    [Reply]

  11. Ramtin says:

    thank youuuuuuuuuuuuuuuuuu very muchhhhhhhhhhhhhhhhhhh

    [Reply]

  12. Thanks! After a year of frustration, that finally worked!

    [Reply]

  13. side_control says:

    So I intermittently spent a day fiddling with the same issue on Server 2008, I was unable to get the short name of any of my files, dir /x whatever.. so another resolution is connect using Linux via Samba (Network Share) and you can simply delete the directory.

    Silly silly file system limitations, like 2TB on ext3 and fat32.

    [Reply]

  14. inad says:

    10x for million times.
    It works for me too

    [Reply]

  15. rob says:

    Thank you so much for this fix. I was looking for a fix for this on google and someone on a forum suggested this. I really appreciate it

    [Reply]

  16. Darryl M says:

    Thanks this worked 100% for me…

    windows 7 64 bit

    [Reply]

  17. Ryan says:

    This didn’t work for me, even after a reboot. Plus this just started happening to me recently, not back in 2010 when update KB980408 was released.

    Windows 7 64-bit

    [Reply]

  18. Triple-X says:

    THANKS!

    I had to deal with this once before for a customer, and was forced to manually fix and remove registry keys.
    This quick fix is much easier.
    Now that I had this issue appear just now on my own system, without the update in question even installed, Your quick fix worked immediately, without even rebooting.

    So thanks again!!!

    [Reply]

  19. Malcifar says:

    Thanks! Worked like a charm! I never had this problem until installing updates released from 04/25/13 through 05/27/13. So, it appears that something they did in a newer update apparently brought back the issue? In any case, the fix still worked for me, so I am happy with this, yet disappointed that this is not the first time a microsoft update created a new problem on a smooth running rig.

    Windows 7 Ultimate SP1 x64

    [Reply]

  20. Unfixed says:

    Incidentally the fix no longer works for me on W7 Enterprise SP1, after some update during late May 2013. Really bothersome.

    [Reply]

  21. Jan says:

    Brill. Cheers mate

    [Reply]

  22. Squall says:

    Big THANKS!
    I was waiting for windows update, but now 2013.19.07. and still haven’t got any updates that would fix this annoying issue. So I tested this fix just now and it works for me.How long will it work, who knows, but at least now I can work normally.
    So, thank you!

    [Reply]

  23. Nick T says:

    THanks Using 64 bit WIN 7 – worked perfectly – Many Thanks

    [Reply]

  24. A U says:

    Sorry to sound dumb but where do you place these registry files.

    i checked on my system and i am sunning Windows 7 SP1 32-bit, are these files applicable to me and if so which one do i use.

    I look forward to your replies

    [Reply]

    F Villanueva Reply:

    @A U, Extract the files, then right-click on the file pertaining to your version
    of windows, i.e. 64 bit or 32 bit. select merge and follow through.

    [Reply]

  25. riji says:

    Thanks, 64 bit WIN 7 – worked perfectly

    [Reply]

  26. run says:

    thnx man, very very thnx

    [Reply]

  27. Frank H says:

    Works as a breeze on Windows 7 Ultimate 32bit , wonderfull !!

    [Reply]

  28. Youri says:

    Hero! Even works on Windows 8 :)

    [Reply]

  29. Tijs says:

    Worked for me as well. Windows 8.

    [Reply]

  30. Fred N says:

    After 1 1/2 year problems with this item, one fix and the problems are gone.
    Worked in Windows 7.
    Thank you very much.
    Fred, The Hague, Holland

    [Reply]

  31. Larry says:

    Does not work in Win 8.1. Any more ideas. This did work in Win 7 because I had the same issue with it.

    [Reply]

  32. daniel says:

    wowza…this started happening after i did a windows update run yesterday…and it was driving me mad. this fixed it (w7 enterprise sp 1 64 bit), so thanks a lot.

    [Reply]

  33. Pedro147 says:

    @-, I just used this registry mod for Windows 7 32 bit and it worked a treat. Thanks for providing a fix for this annoying glitch. I had also previously modified the registry to remove the annoying libraries “feature”

    [Reply]

  34. parlance says:

    Works on Windows 8.1. Thanks!

    [Reply]

  35. Drew says:

    Damn, I wish I found this the first time I tracked down the problem instead of doing it the hard way. Today I forgot where I was tinkering to fix it last time so here I am, I guess I’m getting old lol.

    That said, thank you very much. :)

    [Reply]

  36. Linda says:

    These registry hacks worked beautifully for the problem that started occurring immediately after the latest Patch Tuesday application in Windows 7 on my 64-bit machine. It was driving me nuts, and I say thanks a million for this fix!

    [Reply]

  37. El Juan says:

    This is legit!
    Years after posted, still helping folks out.
    Cheers buddy!

    [Reply]

  38. Dan says:

    Did the trick for me as well – Win7 x64… VERY much appreciated!

    [Reply]

  39. Pedro147 says:

    I just used this registry mod for Windows 7 32 bit and it worked a treat. This is the second time that I used this registry edit this year on my two different systems. Thanks for providing a fix for this annoying glitch. I had also previously modified the registry to remove the annoying libraries “feature”

    [Reply]

  40. YR says:

    >Thanks a lot for your fix. In Jun 2014 in France, I executed your fix and my system has been corrected. PB : OEM links registre key was wrong. Why ? I can’t explain. Nevertheless, I can create now a directory (Or rename a directory) without any problem.

    [Reply]

  41. jonc says:

    Excellent – works fine on an old Win7 32 bit (X86) machine

    [Reply]

  42. vic says:

    THANKS!!!!!!!!!!!!!!!!!!!

    [Reply]

  43. Warcher says:

    Thanks a lot!
    6/7/14

    [Reply]

  44. Tamotsu says:

    THANKS!
    it works complete on win7x64

    [Reply]

  45. jonah says:

    THANKS! :D

    [Reply]

  46. John says:

    THANKS!!!

    [Reply]

  47. Fritz says:

    It works! Thanks!

    [Reply]

  48. Omid says:

    works for me thx a lot

    [Reply]

Leave a Reply

WordPress Themes

Calendar

May 2010
M T W T F S S
« Apr   Jun »
 12
3456789
10111213141516
17181920212223
24252627282930
31  

Sponsors

Weboy