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")
Good day Corey
It works 100% in W7 Pro 64-bit, super!
One question, do you have a ‘uninstall’ or revert reg file?
I made a full backup of the registry before running yr folderfix for just in case. Obviously I will not know the impact till after a few days but by then it will be too late to apply the backup.
Again, many thanks for yr efforts. This issue has been killing me slowly for weeks.
PS How come MS not aware???
[Reply]
Corey DeGrandchamp Reply:
August 9th, 2010 at 9:33 PM
I don’t have a backup, but you should be able to open the .reg in wordpad and see the referenced keys!
[Reply]
Thanks Corey for the quick response. I suppose I could fiddle (at my own risk) with the 258 keys, i.e. if they are all newly added keys?
If some are modified keys then it is out of the question. As far as I can detect I could make a new reg file and add a “-” in front of all the HKEY_LOCAL_MACHINE entries and that should do the trick?
Dumb question but you can just say yes or no and I’m still a happy user of yr solution.
[Reply]
Corey Reply:
August 10th, 2010 at 11:17 AM
@Roy, Oh wow, I forgot the .reg files were that large. The only things it should really be affecting are the “Folder Description” entries of the registry.
I’ve noticed one ill effect from this though, if you used a registry hack to disable the “Libraries” feature of Windows 7, this turns it back on, but that’s it. Other than that I’ve had this registry key applied for a long time. I had to recently re-apply it after a Windows Update, but it still works like a charm.
As far as an “undo” .reg key, I do not have one, I apologize. In the the future any .reg fixes I release will be sure to include an undo .reg file to accompany it!
[Reply]
Anonymous Reply:
August 10th, 2010 at 1:40 PM
@Corey,
Now that you mention Libraries, I used another reg hack four months ago to switch those folders off and only noticed now that they are back again. No big deal, I’ll run that reg hack again.
In any case do you confirm that I can make an undo reg of yr hack (the applicable 258 keys) by placing a “-” in front of each HKEY_LOCAL_MACHINE entry?
Later today that large ‘patch Tuesday’ will be coming through and I wonder what impact that have.
[Reply]
Corey DeGrandchamp Reply:
August 10th, 2010 at 2:23 PM
@, I’m not sure if you can just remove the keys or not, this fix was from along time ago. Really the only thing you’d be reverting to is a broken copy of Windows though, so it never occurred to me to produce a reversal reg. I wouldn’t know where to begin to check this out since my system is already modified with the registry keys in question. Sorry Roy.
Anonymous Reply:
August 10th, 2010 at 5:47 PM
@Corey DeGrandchamp,
Thanks Corey, no problem, it is doing its task perfectly and I’m happy.
Corey DeGrandchamp Reply:
August 10th, 2010 at 6:02 PM
@, In fact, thinking about it a bit makes me think that perhaps us using a registry hack to disable “Libraries” may be the actual reason for this issue in the first place?
It may well be but before I applied the ‘Disable Libraries’ script, 11 Feb, I Googled and found quite a few but they were all the same, modifying the identical 9 keys.
I had no side effects till about a month ago when the folder issue started, and as you’ve also said, and that may have been due to a Windows update?
Today you’ll find tons of complaints on the Web regarding this issue and me thinks that many folk applied this remove Libraries hack since Sept 2009 when it became available.
I do have a ‘Restore Default Settings.reg’ (12 keys) to counter the original ‘Disable Libraries’ (9 keys) but doubt if usable at this late stage.
Most probably what is now in big demand, and impossible challenge, is a fix to fix the fix
[Reply]
Worked for me! Thanks, after searching hundreds of pages, you have it!
[Reply]
Works fine!
Thank you!
[Reply]
I found this fix in two separate forums – same file. I backed up my registry and held my breath and – lo and behold! – yup, it worked.
So I’m thanking both contributors. Now my backup application will work . It quit when I couldn’t make folders.
So thanks and have a virtual Molson’s on me!
[Reply]
It worked. I imported it (even forgot to make a backup of the registry) and after a restart there’s no problem with renaming files or folders.
Thanks a lot!
[Reply]
THANK YOU!!
[Reply]
Works. Thank you!
[Reply]
Doesn’t work for me in Windows 7 64bit. Ran the hotfix above and rebooted, still asks to verify location when I try to delete or rename the file … very frustrating. I have a 0kb size file on my desktop I cant get rid of!
[Reply]
Thank you for the fix. This problem has been driving me mad.
[Reply]
It works, thanks alot.
[Reply]
Thanks, it worked unlike everyone else’s methods.
[Reply]
Thank you so much! It works!!
[Reply]
Yup, that fixed it for me too – my thanks!
It’s been driving me nuts since it started a week or so back (and just when I was beginning to think Win 7 was more reliable than any version since Windows 3.11 too!)
[Reply]
Worked for me too. My computer only seemed to get the folder problem when I installed a Windows update just before upgrading to SP1. Thanks!
[Reply]
This also worked fine for me. I’d applied the no libraries hack mentioned earlier, and it must have caused the problem.
[Reply]
Problem gone. Thanks a million.
[Reply]
You are my hero!
[Reply]
Unfortunately it didn’t work for me,.
[Reply]
yup worked for me: Win7 Ultimutt 32. ps I also had killed off the AMSI (another stoopid microsoft idea) Library, done it over a year ago; I was worried this fix would resurrect it as some others have noted but for me thankfully it did not.
.. long live xp ..
[Reply]
Got the .zip file downloaded, see the reg entries. Where do I extract them to in order to solve the problem?
Thanks!
[Reply]
Corey DeGrandchamp Reply:
November 10th, 2011 at 9:05 AM
@CCC, You just simply double click them and confirm you want to add the data to the registry.
[Reply]
Just in case this would help someone: I was applying this brilliant fix quite a long time ago, and it works like a charm, and even stupid Libraries I disabled even earlier didn’t reappear.
But today, on November 11, 2011, this shit starts again! Any folder renaming is interrupted with this stupid message. Only 2 things do change in my system TODAY:
1. I installed MS Office Word 2003
2. I installed automated “Update for Windows 7 (KB2641690)”
I don’t know which action to blame, if any, but the fact is: I checked my registry, and every key now have only a single “/” instead of double “//” in respected places, just as if this reg-fix was never applied by me! So, I run the fix once again, and it is now all back to normal. Thank you! Just keep in mind that MAYBE this update or MS Office installation cause this. And for now I’m saving this page in bookmarks and I’m saving this FolderFix.zip on my PC, just in case this will happen again.
Microsoft, eat shit!!!!
[Reply]
Corey DeGrandchamp Reply:
November 11th, 2011 at 12:51 PM
@Mayhnaus, Its a side-effect of disabling libraries and running certain updates for Windows 7 – so in this case it was the automatic update that killed it.
Just keep the .reg files handy, or revert back to keeping Libraries enabled
[Reply]
Wow…Works like magic..Thanks bro,
You saved my day
[Reply]
thanks a lot!!!
[Reply]
[...] there is a reference to a registry fix Here You may want to check it [...]