Hyper-V Server – "Access is denied" on C:\ root for all accounts, including SYSTEM and offline from WinRE

Amanda Poitras Gauthier 0 Reputation points
2026-11-19T04:51:09.6733333+00:00

Hello,

I'm looking for help with a production Hyper-V host where the root of the system volume C:\ has become inaccessible to every account, including SYSTEM, even offline from WinRE. The OS still boots and VMs run normally. We think it happened when the server got no space available (0 bytes free). We resolved the problem of space disk, but we still have the permissions problems (access denied).

We tried many thing :

  • dir C:\ / Get-ChildItem C:\ → Access is denied (PowerShell also says "Cannot find path 'C:' because it does not exist")
  • icacls C:\ (read only) → Access is denied
  • takeown /f C:\ /a → Access is denied
  • fsutil fsinfo ntfsinfo C: → Access is denied
  • Get-Volume and Win32_Volume report Size/Capacity and FreeSpace = 0 for C:
  • Files accessed by full path work normally (e.g. C:\Windows\System32)

-chkdsk (no problems detected)

In WinRE offline:

  • dir D:\ → Access is denied
  • takeown /f D:\ /a → Access is denied
  • icacls D:\ /grant *S-1-5-32-544:F *S-1-5-18:F → Access is denied
  • icacls D:\ /setowner *S-1-5-32-544 → Access is denied
  • icacls D:\ /reset → Access is denied

An idea to how resolve this issue without reinstalling the hosts (vms in production on D: drive)?

Thank you

Windows for business | Windows Server | Storage high availability | Virtualization and Hyper-V
0 comments No comments

2 answers

Sort by: Newest
  1. Amanda Poitras Gauthier 0 Reputation points
    2026-11-19T14:05:28.4066667+00:00

    Hi Domic,

    I'm getting access denied and no problem on the chkdsk :

    User's image

    User's image

    PS C:\Windows\system32> chkdsk C: /scan

    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...

    74752 file records processed.

    File verification completed.

    3979 large file records processed.

    0 bad file records processed.

    Stage 2: Examining file name linkage ...

    135 reparse records processed.

    103560 index entries processed.

    Index verification completed.

    0 unindexed files scanned.

    0 unindexed files recovered to lost and found.

    135 reparse records processed.

    Stage 3: Examining security descriptors ...

    Security descriptor verification completed.

    14405 data files processed.

    CHKDSK is verifying Usn Journal...

    2442400 USN bytes processed.

    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.

    No further action is required.

    124338175 KB total disk space.

    13997552 KB in 52290 files.

     44628 KB in 14406 indexes.
    
         0 KB in bad sectors.
    
    147275 KB in use by the system.
    
     65536 KB occupied by the log file.
    

    110148720 KB available on disk.

      4096 bytes in each allocation unit.
    

    31084543 total allocation units on disk.

    27537180 allocation units available on disk.

    User's image

    Thank you for your answer,

    Was this answer helpful?


  2. Domic Vo 37,655 Reputation points Independent Advisor
    2026-11-19T05:26:15.1566667+00:00

    Hello,

    Based on your symptoms, I would not recommend reinstalling Windows Server yet. The fact thatfiles remainaccessible through their full paths (e.g., C:\Windows\System32), while accessingthe volume root returns**Access Denied**, suggests a possible issue with the root directory's NTFSsecurity descriptor (DACL).

    However, the reported Size = 0 and FreeSpace = 0 also warrant investigating filesystemorstorage metadata.

    Before attempting any permission modifications, please run these commands from anelevatedPowerShell session:

    a) Check volume information:

    powershell

    Get-Volume | Format-List DriveLetter,FileSystem,HealthStatus,Size,SizeRemaining
    

    B) Check the root directory's security descriptor:

    powershell

    Get-Acl -LiteralPath 'C:\' |
    Format-List Owner,AreAccessRulesProtected,Sddl
    

    If this returns Access Denied, please provide the complete error.

    C) Check filesystem information:

    cmd

    fsutil volume diskfree C:
    fsutil fsinfo volumeinfo C:
    chkdsk C: /scan
    

    D) Check relevant system events:

    powershell

    Get-WinEvent -FilterHashtable @{
        LogName='System'
        StartTime=(Get-Date).AddDays(-7)
    } | Where-Object {
        $_.ProviderName -match 'Ntfs|disk|storport'
    } | Select TimeCreated,Id,ProviderName,Message
    

    Do not run icacls /reset /T or recursively change permissions. This could damage Windowssystempermissions and Hyper-V dependencies.

    My initial suspicion is a damaged or incorrectly configured root-directory security descriptor, butweneed to rule out NTFS metadata issues before attempting a targeted repair. There is no reasontoreinstall the host until these possibilities have been investigated.

    I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciatedtoaccept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.