Folder Redirection Woes
Today I came across a very interesting problem in regard to Group Policy folder redirection in Windows 7. All folder redirection was failing with reason codes similar to the one below:
Application Source: Microsoft-Windows-Folder Redirection
12:12:58 PM
Event ID: 502
Task Category: None
Level:
Error Keywords:
User: username
Computer: computername
Description: Failed to apply policy and redirect folder "Documents" to "\\server\share$\username\". Redirection options=0x9020. The following error occurred: "Failed to build the list of known sub folders".
Error details: "The system cannot find the file specified. "
This was happening for all redirected folders – Start Menu, Documents, Music, Desktop etc etc. I assumed firstly that this was a permissions issue. I checked and rechecked all permissions. I logged on as a user – saw the redirection fail, and tried to access the “failed” directory as that user. The user could access (and write) to the documents directory without any problems. I sort of already guessed this was the case because XP clients weren’t having any problems. I also knew that I was in a bit of trouble because googling this error returs no results (sigh).
I cast my mind back to a couple of days ago and remembered that I approved a bunch of updates that had been piling up (I know, I shouldn’t let them pile up but I don’t often get time to approve them). Anyway, after a LOT of painful update installs (pretty much one at a time – took me and some colleagues 3 hours), I found the update that broke folder redirection: KB980408
Microsoft’s description of this KB is: Install this update to resolve reliability issues with Windows 7 and Server 2008 R2.
Well, that didn’t work. After some careful googling, I found that other people have had problems with this update too. Not the same problem mind you. There was a fix recommended in this forum. I wasn’t sure that it was going to solve my problem, but it did.
The [temporary] solution I used involved the following: Make a reg File with the following in it:
Windows Registry Editor Version 5.00</code>
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{2112AB0A-C86A-4ffe-A368-0DE96E47012E}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{2112AB0A-C86A-4ffe-A368-0DE96E47012E}\PropertyBag]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{491E922F-5643-4af4-A7EB-4E7A138D8174}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{491E922F-5643-4af4-A7EB-4E7A138D8174}\PropertyBag]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{7b0db17d-9cd2-4a93-9733-46cc89022e7c}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{7b0db17d-9cd2-4a93-9733-46cc89022e7c}\PropertyBag]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{A302545D-DEFF-464b-ABE8-61C8648D939B}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{A302545D-DEFF-464b-ABE8-61C8648D939B}\PropertyBag]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{A990AE9F-A03B-4e80-94BC-9912D7504104}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{A990AE9F-A03B-4e80-94BC-9912D7504104}\PropertyBag]
Run the reg file. It’s important that you reboot after the fix has been applied. I’ve got a friend who is emailing Microsoft about this issue, and hopefully they’ll release a hotfix or something. I’d be interested to know if anyone else has had similar issues (or fixed it using these steps).
EDIT: A side-effect of this fix is that renaming via Windows Explorer sometimes fails. Still… better than having no folder redirection

I have ran into the same exact issue.
Your fix has worked on a couple testers. No explorer failures yet. MS has not been able to duplicate the issue but they are still working on my case.
I’m glad I’m not alone. Interesting that more people haven’t come across this though. We don’t really run anything non-standard. Only thing slightly different is that we’re running both 2003 & 2008 domain controllers. Still, that should be a supported configuration – surely…
At last, I’ve tried everything and no joy. I was starting to go crazy as to what might be causing this! I did the fix and it worked great, no problems. No hotfix from MS yet.
Hahaha!
Applying this fix again, I noticed that the registry keys looked familiar (call me a nerd if you will).
I’m reasonably sure this has something to do with libraries in Windows 7. The first thing I did with all our Windows 7 machines was disable libraries using a registry fix I found on the web. Turns out it modifies quite a few of the same keys as the fix.
All I can hypothesise is that the old redirection went something like this:
My Documents -> \\server\share
and the new one is:
Documents Library -> \\server\share
However, if libraries are disabled, this won’t ever happen. Hence the message “The system cannot find the file specified”.
It’s not a problem with the machine accessing the SERVER, it’s a problem with the machine accessing its own libraries directories!
It seems that the folder renaming via explorer issue you noticed is not a problem with the reg fix. Its another problem caused by KB980408.
Oh great. Another KB “fix”
Tnx Admin
Your solution works great. Always nice the ms hotfixes….
Yes! I fix it with that! Previously I had deleted Common Libraries! FOlder redirection was working before Applying Windows 2008 R2 SP1
Superb. Been pulling my hair out – one particular IT suite, Windows 7 x64 SP1. Nothing would redirect, useless error message in system logs. I have run into this before, but had forgotten the fix. Thanks!
[...] [...]
Thanks. This fix indeed correlates with the removal of the windows libraries in W2008R2 SP1. However the erroronly because visible after i installed hotfix http://support.microsoft.com/kb/2519550/en-us
I have solved the issue by creating a system-based gpp which removed the registry keys.
Thx
[...] [...]
[...] I found a solution on this page – http://www.nebev.net/blog/?p=258 [...]