Seeing an “Access Denied” message when you try to open or work with a system volume in Windows can be confusing, especially when you are logged in with an administrator account. In many cases, though, Windows is not actually broken. The operating system deliberately protects certain system locations because they contain information required for System Restore, volume management, indexing, recovery, or boot operations.
One of the most common examples is the System Volume Information folder. You may see it on your C: drive, another internal drive, or even an external storage device. Windows normally restricts access to this folder, so simply changing your account to an administrator does not necessarily give you unrestricted access.
There is another situation that produces a similar Access Denied message: running a boot-repair command such as bootrec /fixboot from Windows Recovery Environment.
This is usually related to the EFI System Partition, boot files, or the way Windows Recovery Environment has assigned drive letters.
This guide covers both situations so you can identify the problem first and then apply the appropriate fix.
Access Denied for System Volume [Fixes]
Before changing permissions or partitions, it is important to understand what Windows means by “system volume.” The phrase can refer to different things depending on where you encountered the error.
If File Explorer shows System Volume Information and says access is denied, Windows is protecting a special folder. This folder can contain data associated with System Restore and other volume-level Windows services. Microsoft documentation and support discussions also show that the folder is normally protected from ordinary access.
If the message appears after running bootrec /fixboot, the problem is different. In that situation, Windows Recovery Environment may not be correctly accessing the EFI System Partition. For modern UEFI-based Windows installations, rebuilding the boot files with bcdboot is often more appropriate than repeatedly running bootrec /fixboot.
Microsoft specifically documents using bcdboot to recreate boot files on the system partition.
The steps below start with the safest checks and gradually move toward more advanced repairs.
Step 1: Identify Which System Volume Is Giving You the Error
The first step is to determine exactly where the Access Denied message appears. This matters because you should not modify permissions on a protected Windows folder just because you cannot open it.
If you are in File Explorer, go to File Explorer > This PC > Local Disk (C:) and check whether you are trying to open a folder named System Volume Information. If the error appears specifically when you double-click this folder, you are probably dealing with normal Windows protection rather than a damaged drive.
If the error appears inside Windows Recovery Environment after you run a command such as bootrec /fixboot, you have a boot-repair problem instead.
You can also determine the available volumes from Command Prompt. Open an elevated Command Prompt by going to Start > type Command Prompt > Run as administrator. Then enter diskpart, followed by list volume.
Look at the output carefully. A Windows installation commonly has an NTFS volume containing Windows and, on a UEFI system, a smaller FAT32 system partition. Microsoft uses this distinction when troubleshooting Windows boot problems.
Do not format or delete anything at this stage. The goal is simply to identify the correct volume.
Step 2: Leave System Volume Information Alone If You Only Want to Open It
If your problem is simply that Windows will not let you open C:\System Volume Information, you may not need to fix anything.
This folder is intentionally protected because Windows uses it for system-level information. Seeing Access Denied does not automatically indicate corrupted permissions, malware, or a failing hard drive.
Go to File Explorer > This PC > Local Disk (C:) > System Volume Information and, if Windows displays the Access Denied message, leave the folder alone unless you have a specific administrative task that requires access.
This is particularly important because taking ownership of protected Windows folders and granting yourself full control can interfere with the permissions Windows expects. You should not use commands such as takeown or broad icacls permission changes simply to make a protected folder accessible.
If your actual problem is that an application is trying to copy or synchronize the contents of an entire drive and repeatedly fails on System Volume Information, the better solution is usually to exclude this protected system folder from that operation rather than weakening its permissions.
Step 3: Check the Drive for File-System Errors
If the Access Denied message is accompanied by other symptoms, such as disappearing files, unusual disk behavior, failed updates, or messages indicating that the volume is corrupted, check the file system.
Go to Start > type Command Prompt > Run as administrator. At the Command Prompt, enter:
chkdsk C: /scan
Replace C: with the appropriate drive letter if the affected volume is different.
The /scan option performs an online scan of an NTFS volume without immediately taking the drive offline for repairs. If Windows reports problems that require repair, you can then use an appropriate repair command after making sure your important files are backed up.
If you are running the command from Windows Recovery Environment, remember that drive letters can be different from those you normally see in Windows. Your Windows installation might appear as D: rather than C:.
This is why you should identify the Windows volume with DiskPart or by checking the directory contents before running repair commands against a specific drive.
Step 4: Identify the EFI System Partition
If your particular error says “Access is denied” when you run bootrec /fixboot, move to the boot-repair procedure.
Restart the computer and enter the Windows Recovery Environment. You can generally reach it through Troubleshoot > Advanced options > Command Prompt when Windows cannot boot normally.
At Command Prompt, type:
diskpart
Then type:
list volume
Look for a small FAT32 volume. On a typical UEFI installation, this is the EFI System Partition, which contains the files Windows uses to start the operating system. Microsoft documentation shows the system volume as a separate FAT32 partition in this type of configuration.
Select the appropriate volume with:
select volume X
Replace X with the actual volume number shown on your computer.
Then assign it a temporary drive letter:
assign letter=S
Type:
exit
Now the EFI partition should be accessible as S: within the recovery environment.
Be extremely careful here. Do not select your large Windows partition by mistake, and do not format the EFI partition as part of this basic repair procedure.
Step 5: Find the Correct Windows Drive Letter
The next step is to identify the drive containing your actual Windows installation.
In Windows Recovery Environment, your normal C: drive may have a different letter. Do not assume it is C:.
At Command Prompt, try:
dir C:\Windows
If you see the Windows directory and its contents, C: is probably your Windows installation.
If you receive an error, try:
dir D:\Windows
Then:
dir E:\Windows
Continue until you find the drive containing the Windows folder.
You can also use DiskPart > list volume to compare the volume sizes and file systems. Microsoft recommends checking the volumes before working with the system partition because the drive letters assigned by WinRE may differ from those used during normal Windows operation.
For the next command, suppose your Windows installation is D: and the EFI partition you assigned is S:.
Step 6: Rebuild the Windows Boot Files With BCDBoot
This is one of the most useful fixes when bootrec /fixboot returns Access Denied on a modern UEFI Windows installation.
At Command Prompt, enter:
bcdboot D:\Windows /s S: /f UEFI
Replace D: with your actual Windows drive and S: with the drive letter you assigned to the EFI System Partition.
The BCDBoot utility copies the necessary boot files to the system partition and creates or updates the Boot Configuration Data store. Microsoft documents BCDBoot as a method for recreating boot files when troubleshooting Windows startup problems.
If the command completes successfully, close Command Prompt and restart the computer.
Go to Continue > Exit and continue to Windows.
If Windows starts normally, the boot files were likely the problem.
Step 7: Run Startup Repair if Windows Still Does Not Boot
If rebuilding the boot files does not resolve the startup problem, use Windows’ built-in Startup Repair tool.
Go to Troubleshoot > Advanced options > Startup Repair.
Windows will scan the startup configuration and attempt to repair problems preventing the operating system from loading.
This is worth trying before performing more aggressive partition or boot configuration changes because it is designed specifically for startup-related problems.
If Startup Repair fails, return to Troubleshoot > Advanced options > Command Prompt and verify that the Windows partition and EFI partition are still correctly identified.
Do not repeatedly format the EFI partition just because a boot command failed. Formatting or deleting a system partition without understanding the existing boot configuration can make the situation worse.
Step 8: Restart and Verify the System
After completing the repair, restart your computer and allow Windows to boot from the internal drive.
If Windows loads successfully, open File Explorer > This PC and verify that your normal partitions are present.
If you were originally seeing System Volume Information > Access Denied, remember that the folder may still refuse access. That does not mean the repair failed. The folder is supposed to have restricted permissions.
The important distinction is whether Windows can boot and whether the original operation you were trying to perform now works.
Faqs
Why does System Volume Information say Access Denied?
System Volume Information is a protected Windows folder. Windows restricts ordinary users from accessing its contents because it contains system-managed information. An Access Denied message is therefore often normal rather than an indication of a problem.
Should I take ownership of System Volume Information?
Generally, no. If you do not have a specific administrative reason to access it, changing ownership or permissions can create unnecessary security and system-management problems. It is safer to leave the folder protected.
Why does bootrec /fixboot say Access Denied?
On some modern UEFI Windows installations, bootrec /fixboot can return Access Denied when the EFI System Partition is not properly accessible in the recovery environment. Identifying the EFI partition and rebuilding the boot files with BCDBoot can be a better approach.
Is the EFI System Partition the same as the C: drive?
No. The EFI System Partition is normally a small FAT32 partition that stores boot-related files, while the Windows installation is usually on a much larger NTFS partition.
Can I delete System Volume Information?
You should not manually delete the protected System Volume Information folder from a Windows drive. Windows manages this folder automatically, and deleting or modifying its contents can affect system features.
What if BCDBoot says it cannot copy the boot files?
First verify that you selected the correct Windows partition and EFI System Partition. In WinRE, drive letters can change. Check the Windows directory again with dir C:\Windows, dir D:\Windows, or the appropriate drive letter, then make sure the EFI partition is the small FAT32 volume before running BCDBoot again.
Summary
An Access Denied message involving a system volume does not always mean Windows has a permissions problem. If the message appears when opening System Volume Information, the restriction is usually intentional and the safest approach is to leave the protected folder alone.
If the error appears while repairing Windows boot files, particularly when bootrec /fixboot reports Access Denied, the situation is different. Use DiskPart to identify the EFI System Partition, identify the correct Windows drive letter, assign the EFI partition a temporary drive letter, and use BCDBoot to recreate the boot files.
The most important thing is to identify the exact volume before making changes. Do not format, delete, or change permissions on a system partition unless you are certain which partition you are working with.
This approach gives you a safer path to resolving the error without accidentally damaging your Windows installation.