Fix: User profile Home Folder doesn’t map

Teodor Nechita
by Teodor Nechita
Download PDF
Affiliate Disclosure

windows file server can't map home folder

Windows File Server can be very handy when used accordingly, and can drastically increase the workflow of organizations and individuals.  However, using them requires users to be able to connect, and that isn’t something that always happens.

For example, some users have reported that their user profile home folder is not mapping


Does anyone know why some of my users Home Folder does not map at login? This just started happening a week ago. I have a password policy in place as well and it seems like most of my users passwords are expiring soon.
In Active Directory in the user account under profile, i have a  home folder connecting to the letter z:. I have had a lot of users call and say that there z drive is missing. They log off the computer, log back on and its still missing. The only way i can get it to map is if i have them run a command:  net use z: servershared name

How do I make profile home folders map again?

Disable your Antivirus or Firewall

Check to see whether an antivirus or a firewall client is enabled on the client that has the folder issues. If you find any, simply disable them and try to map out the folder.

Looking for an antivirus for Windows Server? Check this article out for our top picks.

Disable the Fast Logon Optimization feature

  1. Press Windows + R
  2. Type in gpedit.msc
  3. Open the Group Policy Object where you have preference items
  4. Go to Computer Configuration
  5. Select Administrative Tools
  6. Choose System
  7. Select Logon
  8. Enable the Always wait for the network at computer startup and logon’ setting
    1. This will disable the fast logon feature
  9. Reboot the PC

Once the PC has rebooted, try to see if your user’s home folder encounters any more difficulties while mapping.

The fast logon feature may affect the display and drive letter assignment of a mapped network drive. As such, the drive may have been mapped, but the user on the client cannot see it in Windows Explorer.

As with the case at hand, he may even recognize it as a failed network drive mapping. This is why disabling fast logon via the Group Policy Objects is the best solution.

If you know of any other solution to this problem, tell us more about it in the comments section below.

Was this page helpful?
Thanks for letting us know! You can also help us by leaving a review on MyWOT or Trustpillot.
Get the most from your tech with our daily tips
Tell us why!