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!