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.
If you enjoyed this article, please consider sharing it!
![[Valid Atom 1.0]](http://feed2.w3.org/images/valid-rss-rogers.png "Validate my Atom 1.0 feed")
remove&4301dce8d6147bd39a2d90d22e621ee2_NX
[Reply]
Thanks a lot..works perfect on x64
[Reply]
this worked perfectly. Thanks a million.
[Reply]
Thanks so much. Worked great.
[Reply]
Sand1982 Reply:
February 13th, 2013 at 12:25 AM
@VeryHappy,
where we find this (&4301dce8d6147bd39a2d90d22e621ee2_NX)
[Reply]
where we find this (&4301dce8d6147bd39a2d90d22e621ee2_NX)
[Reply]
Thanks for this, problem sorted.
[Reply]
works with Windows 8 64
[Reply]
Problem solved with this post: http://www.overclock.net/t/721973/msupdate-kb980408-warning-to-all-win7-x64-users/10#post_9211430
[Reply]
This also worked for me with Windows 8 x64. Thank you!
[Reply]
Great friend.. It works for me
[Reply]
thank you so much!!! I was already worrying that I had to reinstall my laptop
Anyway Thanks
[Reply]
thank youuuuuuuuuuuuuuuuuu very muchhhhhhhhhhhhhhhhhhh
[Reply]
Thanks! After a year of frustration, that finally worked!
[Reply]
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]
10x for million times.
It works for me too
[Reply]
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]
Thanks this worked 100% for me…
windows 7 64 bit
[Reply]
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]
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]
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]
Incidentally the fix no longer works for me on W7 Enterprise SP1, after some update during late May 2013. Really bothersome.
[Reply]