Unexpected error 0x8007000D "The data is invalid" when moving or renaming folders in Windows 7

0

A few weeks ago I began seeing this error every time I try to rename or move a folder in Windows 7 SP1:

An unexpected error is keeping you from renaming the folder]

Things I've already tried to resolve this:

  • Remove ALL Explorer addins and shell extensions, using Autoruns
  • Create a new user account (happens there, too)
  • Reboot in safe mode (still happens)
  • Rename/move folders on a different drive (happens even when working with folders on a remote network drive or USB key)
  • Remove the 5 registry keys mentioned under this video
  • Trace the operation with ProcMon (didn't notice anything interesting logged right when the rename happens, but would love to learn more about what internal API's explorer calls and exact steps it takes so I can troubleshoot deeper)
  • sfc /scannow
  • chkdsk
  • various dism commands
  • confirmed I have Full Control over and ownership of the folders in question
  • binary compare of explorer.exe to that of another Windows 7 machine (it matches)
  • Windows 7 repair (tried that on a sacrificial backup image of the machine and couldn't get the repair to work)

The rename or move always works on the second attempt, when I hit "Try Again".

I can rename or move the same folders from a DOS prompt (cmd.exe) or with another program (e.g. Directory Opus) with no problem. I'm fairly certain it's not an NTFS/index/metadata issue on my drive itself, as Explorer on another computer can rename the folders just fine when it connects to my machine over the network. And all sfc, chkdsk, etc. commands pass with no issues. I do see the error when I try to rename folders on the remote machine using my computer's Explorer.

I don't have any restore points to revert to. My most recent backup that is before this began is from months ago and I'm not keen to revert back to that.

I'm not interested in upgrading this machine to Windows 10. I don't care that Microsoft doesn't support it anymore (that's why I'm asking the question here instead of paying them). I'm also not keen to reinstall my OS from scratch (it takes literally months to set up and customize all the software again).

As a last-ditch effort, I tried a Windows 7 in-place upgrade to repair this installation. Unfortunately that failed with different set of errors (and Microsoft's Upgrade Advisor tool no longer works as they broke the URL the software needs to connect with).

Grateful for any ideas to diagnose the cause of this issue. Scalpels preferred over sledgehammers.


EDIT: There were some presumably unrelated issues reported by sfc /scannow but those have been cleared up and the tool gives a clean result now (they were due to some customizations detailed here which I made to shellstyle.dll right after the OS was first installed). I do have some files in C:\Windows\winsxs\Temp\PendingDeletes and PendingRenames, if that matters.

windows-7
windows-explorer
rename
move
asked on Super User Dec 27, 2020 by rkagerer • edited Dec 27, 2020 by rkagerer

2 Answers

1

After days of work on it I finally managed to solve this issue. The discussion here led me to examine this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions

Comparing the tree on my computer to a working one, I discovered I was missing a subkey for {1AC14E77-02E7-4E5D-B744-2EB1AE5198B7} which corresponds to "System".

Merging the following .reg file and restarting explorer.exe fixed the problem:

Windows Registry Editor Version 5.00

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

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{1AC14E77-02E7-4E5D-B744-2EB1AE5198B7}]
"Name"="System"
"Category"=dword:00000002

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{1AC14E77-02E7-4E5D-B744-2EB1AE5198B7}\PropertyBag]
"NoCustomize"=dword:00000001
answered on Super User Dec 28, 2020 by rkagerer
-1

Open Cmd As Admin and type sfc /scannow and press enter

answered on Super User Feb 11, 2021 by EAZY BLACK • edited Feb 11, 2021 by Dave M

User contributions licensed under CC BY-SA 3.0