It is often recommended that you install the latest Windows Update available to you. Microsoft releases the updates to make your system more safe and secure to operate. However, sometimes some updates may introduce a new issue to your system. In this article, we will talk about one such issue. So after installing the recently released KB5001330, some users reported that they could no longer map drives to the server. This issue just appeared post this update. In case if you also can’t map drive to Windows Server after KB5001330, this article is for you.
Well, recently a user reached in forums with this problem. KB5001330 was released for Windows 10 and Server Version 20H2 and 2004 on 13 April, 2021. According to the user, after installing KB5001330, he couldn’t map drives to his Windows Server. If he remove the update KB5001330, the issue gets resolved. So it seems the update is causing this problem. A workaround for this new issue has been posted to official Microsoft forums. In case if you’re also affected, atm you can try the workaround mentioned below.
Fix: Can’t map drive to Windows Server after KB5001330
According to suggested workaround, this issue may occur if you’ve link local multicast name resolution (LLMNR) turned off or disabled. If you enable this resolution, you can easily fix the problem. Try these steps:
1. Press 
+ R and type gpedit.msc in Run dialog box to open GPO snap-in. Click OK.
2. Next, in the GPO snap-in window, navigate here:
Computer Configuration > Administrative Templates > Network > DNS Client
3. In the right pane of DNS Client, locate the Turn off multicast name resolution policy setting. Double click on the policy setting to modify its status.
4. Make sure the policy status remain set to Not Configured. Click Apply, OK.
5. Close GP Editor and reboot the machine to make changes effective.
After restarting the system, LLMNR should be enabled on all available network adapters and you’ll no longer face the issue.
Hope this helps!
Also check: Can’t Map A Drive In Windows 10 V2004.
