up vote 1 down vote favorite
1
share [g+] share [fb]

I get this message when I create a new folder anywhere on the drive. If I hit try again it makes the folder and no additional errors, has anyone seen this behavior before?

It only does it if I change the default name during creation, if I leave it "New folder" it makes it without error. Strange the message says "New folder" when I have named it something else. If I change any folder name it generates a similar message.

System is clean, regular scans both online and offline.

Restarted several times.

Windows 7 64bit Pro.

enter image description here

link|improve this question
100% accept rate
Have you run a disk check to ensure there's no file system corruption? – techie007 Oct 28 '11 at 17:30
Yes, I do regular chkdsk's as part of my maintenance routine. – Moab Oct 28 '11 at 21:10
feedback

1 Answer

up vote 3 down vote accepted

I have run into this issue on Windows 7 x64 as well.

  • Install hotfix KB980408

  • Remove all of the following registry entries:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{2112AB0A-C86A-4ffe-A368-0DE96E47012E}]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{491E922F-5643-4af4-A7EB-4E7A138D8174}]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{7b0db17d-9cd2-4a93-9733-46cc89022e7c}]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{A302545D-DEFF-464b-ABE8-61C8648D939B}]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{A990AE9F-A03B-4e80-94BC-9912D7504104}]
  • Reboot the system

Credits to HellGates of overclockers.net for this fix.

link|improve this answer
Thanks, downloaded the reg file and merged it, rebooted and the problem is gone! no need to install hotfix. – Moab Oct 28 '11 at 21:09
@moab good to know, I will crosspost your comment to overclockers. Thanks! – John T Oct 28 '11 at 22:56
That was an old post on overclockers, seems a hotfix from 2010 caused the issue, not sure what caused mine since it stays up to date on patches and this was a recent problem. – Moab Oct 29 '11 at 14:42
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.