Windows 7: Eliminating "This Folder Is Shared With Other People" Message
I had installed Windows 7. Now, when I would try to move or delete some folders, I would get this message:
This folder is shared with other people.That message was correct: I had, in fact, shared the parent folder (and all of its subfolders, including this one) with my other computer. And I wanted existing and newly created subfolders to continue to be shared. I just didn't want to receive this warning.
If you move this folder, it will no longer be shared.
I tried the approach of going into Control Panel > HomeGroup > Leave the homegroup, because someone advised that this was the solution. It wasn't. I tried a search. This led to a thread with some heartwarming rants about what a dumbass feature this was. That thread also contained the suggestion that, at least for purposes of deleting (as distinct from moving) folders, a workaround was to cut and paste files and folders into Recycle Bin, rather than trying to delete them directly. There was also a command line alternative that supposedly worked for wiping out lots of subfolders:
for /D %d in (*) do rmdir /S /Q "%d"My guess was that the command line would also work for moving, in a pinch: type MOVE /? for guidance. But I didn't want a command-line solution. The thread also offered a couple of other complicated workarounds with potential side effects. Before going that route, I tried the suggestion to take ownership of the folder in question. I had already added a Take Ownership context menu (i.e., right-click) option in Windows Explorer, so I used that now. I used it at the level of the entire partition. That didn't solve the problem. I tried it again on the top-level folder. That didn't do it either. I verified that I had already given Full Control to Everyone in the Sharing context menu option, so that wasn't the solution either.
Another thread contained messages repeating the view that, as a deliberate feature of Windows, this couldn't be changed. I took a look in TweakNow PowerPack 2012, in case they had a fix. I hadn't really used TweakNow previously, but now I saw it wasn't really a tweaker in the sense that Ultimate Windows Tweaker (UWT) was. So I ran UWT instead. But no, UWT didn't seem to have a solution either. So far, the only solution I had seen was that some people had repartitioned their drive and reinstalled Windows from scratch. But that was a pretty draconian solution, and it didn't seem to guarantee against a recurrence of the problem.
Back in Windows Explorer, I right-clicked on the drive being shared and selected Properties > Security tab > Edit > Add > Everyone > Check Names > OK > Allow Full Control > OK. That took a while, as it went through the drive, with a message that said, "Setting security information" various files and folders. This was obviously not a very secure solution. Nor was it logically related to sharing. It was just a guess.
In another thread, someone said that they noticed this behavior began when they installed RC-1 (i.e., Windows 7, First Release Candidate). As noted above, people had been saying it was a built-in Windows feature. But there was at least the possibility that some program had triggered it. In that spirit, someone else in that same thread offered the belief that it might be related to Windows Mail. That was a possibility. I had installed Windows Live Mail. I didn't like it much -- it was very slow to start. But I had already uninstalled it. There didn't seem to be much more I could do on that front. I tried running Glary Registry Cleaner, just in case that would make a difference. It identified a lot of problems, but did not fix this particular one. In another thread, someone suggested that the culprit might be the network sharing service in Media Player 11.
I saw recurrent references to the C:\Users\[username]\Appdata\Local\Temp\WPDNSE folder. For username Ray, mine had nothing in it. Evidently they came to that folder because its name was appearing in an error message. I wasn't getting that. The general idea seemed to be that one user might somehow be linked to another user at that folder. That was interesting. I looked into the possibility that this "shared folder" problem might be due to the existence of an unnecessary user account. As described in another post, I pruned out some extraneous user accounts. But that did not resolve this problem.
Over time, the problem appeared less frequently. It seemed that there might have been an ownership or sharing event, occurring at one time, that became less relevant as my folders went through various processes of being renamed, moved, reshared, and so forth. One post gave me the idea that the problem might be in Windows Explorer > select a folder > right-click > Properties > Sharing tab > Advanced Sharing > Permissions. At this moment, the only group or user listed there was Everyone. It seemed that, previously, there might have been additional entries there, for Ray, Administrators, and/or System. The post made me think that, even though all roads seemed like they should lead to Mecca, the mere presence of multiple people here would confuse Windows. Maybe the original warning that "This folder is shared with other people" was Windows' way of telling me that it was going to remove the others and leave only Everyone on the list. I didn't test this; this was just an idea from that post. At the time when I decided to close this post, it's not so much that the problem had disappeared as that it had become more rare.
4 comments:
I spoke too soon. The problem came back later. And then it went away again. This is among the reasons cited in a later post on the option of switching to a Windows Explorer replacement for at least some purposes.
http://support.microsoft.com/kb/2493924/en-us
"HKEY_CLASSES_ROOT\Directory\shellex\CopyHookHandlers\Sharing
Deleting this registry key causes the share enumeration in Explorer to be ignored while creating or renaming a folder."
Don't forget to restart your computer.
Teracopy seems to get past the issue. Integrates with explorer.
Thanks for this - because the standard del command with /y doesn't do the trick.
Post a Comment