Server admins suddentl lost access to D and E drives - possible windows update issue?

[PotNoodleTech]

Hey all - got a very weird one. Yesterday noticed that the user account usually log into servers with - could not access the D or E drive (but can C) on Windows 2022 file servers in my computer.

 

Initially though the drives had actually gone down - but no, they're up and service network shares and users are connected fine, but just cant open the drive letters in my computer.

 

Two windows updates went on early yesterday morning - KB5032336 and KB5032198

 

Can you guys check your Windows 2022 file servers for similar behavior especially if they've got those two patches on?

 

I am at a loss as even creating a brand new local admin account on the server, cant browse the D and E drives and used an LA domain admin account and same issue on that too! It's utterly bizzare!!

 

These are all Hyper-V VMs

 

[psydii]

what happens if you try to access them from a shell running as Local System?

[Olliedawg]

Our file server is running Server 2022. Has both of those updates applied. I've not noticed any issues.

 

Everything look ok in server manager > file and storage?

[PotNoodleTech]

At appears to be a file systems permission change on the top level folder of the drive.

 

I.e. D:\ has new permissions, the Owner has been changed from Administrators to SYSTEM

The Permission entries have been reset to only Creator Owner, System and Administrators (all explicate users/groups from our active directory are no longer there e.g. domain admins etc).

 

Yet the subfolders don't have ant changes, still have Administrators as the Owner and still have a couple of our Domain groups intact.

 

Ultra weird. Clearly I could override the top level permissions to add my administrator account or group of domain admins and then I'd be able to view the drive in my computer - but I have not changed anything yet whilst we (and the LA) try to work out what has caused this change on all of our fileservers at the same time?

[psydii]

Random thought: was the drive also mounted at a reparse point?

[PotNoodleTech]

No I don't believe so - it's an NTFS drive which is a separate virtual disk in HyperV

[marc644]

I just had the exact same thing happen. Location not available when using windows desktop on server, able to access everything via command line. Owner changed to SYSTEM.

 

has anyone found the fix to this issue.

 

THanks