In Windows Server environments and Remote Desktop Protocol (RDP) sessions, administrators often hide local drives such as C: and D: from File Explorer for security, compliance, or user restriction purposes.

However, many IT engineers encounter situations where:

• Drives are visible in Disk Management
• Drives exist in PowerShell or Command Prompt
• Users can technically access the drives
• But File Explorer does not display them

This issue commonly occurs in:

• Windows Server 2016
• Windows Server 2019
• Windows Server 2022
• Windows 10/11 RDP Sessions
• Terminal Servers
• Domain-controlled environments

This guide explains how drive hiding works internally, how to diagnose the issue, and multiple ways to restore visibility safely.

Understanding the Problem

Symptoms

You may notice:

• C: and D: missing from “This PC”
• Only redirected drives visible in RDP
• Drives visible in Disk Management
• Drives accessible through PowerShell
• Users unable to browse normally

Example:

Get-PSDrive -PSProvider FileSystem

Output:

Name Used (GB) Free (GB) Provider Root
---- --------- --------- -------- ----
C    42.45     76.94     FileSystem C:\
D    358.82    291.18    FileSystem D:\

This confirms the drives exist and are accessible.

Common Reasons Drives Are Hidden

1. Group Policy Restrictions

Administrators commonly use:

Policy 1

Hide these specified drives in My Computer

Policy 2

Prevent access to drives from My Computer

Location:

User Configuration
→ Administrative Templates
→ Windows Components
→ File Explorer

2. Registry-Based Restrictions

Windows Explorer uses registry values:

NoDrives
NoViewOnDrive

Registry locations:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer

and

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer

These values use bitmask calculations to hide selected drives.

3. RDP Session Restrictions

In Remote Desktop Services environments:

• Local server drives may be intentionally hidden
• Only redirected client drives appear
• Explorer may run in restricted shell mode
• RemoteApp environments may suppress local disks

4. Domain Group Policies

Even if Local Group Policy shows “Not Configured”, Active Directory Group Policies may still enforce hidden drives.

Check using:

gpresult /r

or

rsop.msc

How to Diagnose the Issue

Step 1 — Check Disk Management

Open:

diskmgmt.msc

Verify:

• Disk online
• Healthy partitions
• Drive letters assigned

If visible here, the problem is not storage-related.

Step 2 — Verify in PowerShell

Run:

Get-PSDrive -PSProvider FileSystem

If drives appear, permissions are usually fine.

Step 3 — Test Manual Access

Run:

explorer.exe C:\

or:

explorer.exe D:\

If the folder opens:

• Explorer hiding policy is active
• Actual drive access still works

Fix Method 1 — Remove Group Policy Restrictions

Open Local Group Policy Editor:

gpedit.msc

Navigate to:

User Configuration
→ Administrative Templates
→ Windows Components
→ File Explorer

Set these policies to:

Not Configured

Policies:

• Hide these specified drives in My Computer
• Prevent access to drives from My Computer

Apply changes:

gpupdate /force

Fix Method 2 — Remove Registry Restrictions

Remove Current User Restrictions

Run PowerShell as Administrator:

reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" /v NoDrives /f

reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" /v NoViewOnDrive /f

Remove Machine-Level Restrictions

reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" /v NoDrives /f

reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" /v NoViewOnDrive /f

Fix Method 3 — Restart Windows Explorer

After removing restrictions:

taskkill /f /im explorer.exe
start explorer.exe

Or reboot the system.

Fix Method 4 — Force Explorer to Show Drives

Run:

explorer.exe shell:MyComputerFolder

This reloads the “This PC” interface.

Fix Method 5 — Access Administrative Shares

If Explorer still hides drives:

\\localhost\c$

or

\\127.0.0.1\d$

This accesses hidden administrative shares directly.

Requirements:

• Administrative permissions
• Admin shares enabled

Understanding NoDrives Bitmask Values

Windows uses binary bitmask values to hide drives.

Examples:

Example:

• Hide C and D
• 4 + 8 = 12

Registry:

NoDrives = 12

Enterprise Environment Considerations

Security Reasons for Hiding Drives

Administrators hide drives to:

• Prevent accidental deletion
• Protect system files
• Restrict malware spread
• Limit user access
• Enforce compliance
• Simplify RDS sessions

Best Practice

Instead of hiding entire drives:

Use:

• NTFS permissions
• Share permissions
• Folder-level ACLs
• AppLocker
• Group Policy Preferences

These methods are more secure and manageable.

PowerShell Script to Fully Restore Drive Visibility

# Remove Explorer restrictions
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" /v NoDrives /f
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" /v NoViewOnDrive /f
reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" /v NoDrives /f
reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" /v NoViewOnDrive /f
# Restart Explorer
taskkill /f /im explorer.exe
start explorer.exe
# Open This PC
explorer.exe shell:MyComputerFolder

Conclusion

Hidden drives in Windows are usually not missing or damaged. In most cases:

• The drives physically exist
• Explorer visibility is restricted
• Group Policy or registry settings are responsible

By understanding:

• Group Policy
• Registry controls
• RDP restrictions
• Explorer behavior

IT administrators can safely restore access and troubleshoot Windows Server environments efficiently.