locked
FolderRedirectionWait Registry Key RRS feed

  • Question

  • We use folder redirection to redirect folders to another location on the local hard drive.  We have always had a significant delay during the first logon for each user.  If we redirect the folders to a network share, this delay does not exist.  The delay is always exactly 5 seconds for each redirected folder.  We have done lots of testing and had noticed that if we manually create all of the folders before the user logs in, there is no delay.

    We have pretty much just lived with it but recently used Process Monitor to log everything that happens during boot and logon.  We noticed the following registry value getting read everytime right before the delay occurs:  HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer\FolderRedirectionWait.  Since the value didn't exist, we decided to create the value just to see what would happen.  Set it to 0, no delay.  Set it to 5000, 5 second delay.  Set it to 10000, 10 second delay.  Obviously this key tells windows to wait the specified number of milliseconds when creating the redirected folders and defaults to 5000.

    I can find no documentation on the internet on this particular registry entry and why it exists.  The registry value is not read when the folders are redirected to a network share and there is no delay.  We are considering manually setting this registry entry to eliminate the long logins (13 redirected items * 5 seconds each) but want to see if anyone know why this delay exists.

    Thanks

    Tuesday, March 27, 2012 9:25 PM

Answers

  • Hi,

    The 5 seconds delay is due to the NTFS quota.

    If the server has per-directory auto quota enabled, it might take them a while to apply to the folder we just created. So, if we are query quota too early, we might get the wrong number. It is very hard from client side to know the auto quota applied on the server. So let's just wait a little bit here.

    The solution is to turn off the NTFS quota on the target volume.

    Best regards,

    Denny Zhou


     

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, April 3, 2012 8:39 AM

All replies

  • Ok, it appears that the FolderRedirectionWait key is read anytime the option to "Move the contents of [folder] to the new location." option is selected on the Folder Redirection settings tab.  Manually creating the key and setting it to 0 eliminates the delay during initial folder redirection and we haven't noticed any issues during testing.  Any guesses as to why Microsoft has the undocumented registry setting in the first place?  I can't think of any reason a 5 second delay would be needed after creating the folder.


    Wednesday, March 28, 2012 6:53 PM
  • Hi,

    It will take some time since using folder redirection to redirect folders to another location would modify the folder properties and other settings in Registry during first logon.  Actually,  we cannot test this issue for the FolderRedirectionWait registry key is not exist in Windows 7.


    Thursday, March 29, 2012 8:42 AM
  • Hi,

    It will take some time since using folder redirection to redirect folders to another location would modify the folder properties and other settings in Registry during first logon.  Actually,  we cannot test this issue for the FolderRedirectionWait registry key is not exist in Windows 7.


    The registry key does not exist by default and I can find no documentation about the key anywhere.  I only discovered the key by using Process Monitor to capture all system activity during boot and logon.  Every time the folder redirection delay showed up in the Event Viewer, the FolderRedirectionWait value was being read from the registry (eventhough it doesn't exist).  Some testing showed that the default value for this registry setting was 5000.   Manually creating the key and setting it to 10000 causes a 10 second delay on each redirected folder.  Setting it to 0 eliminates the delay.

    What I am trying to figure out is why this arbitrary 5 second delay exists to begin with.  It almost looks like some kind of debugging setting that was inadvertently left in the code.

    Thursday, March 29, 2012 11:40 AM
  • Hi,

    The 5 seconds delay is due to the NTFS quota.

    If the server has per-directory auto quota enabled, it might take them a while to apply to the folder we just created. So, if we are query quota too early, we might get the wrong number. It is very hard from client side to know the auto quota applied on the server. So let's just wait a little bit here.

    The solution is to turn off the NTFS quota on the target volume.

    Best regards,

    Denny Zhou


     

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, April 3, 2012 8:39 AM