File Explorer crashes on Security Tab viewing Shared Folder Properties

Windows 11 Pro 22000.556 File Explorer still crashes on Security Tab when viewing Shared Folder Properties.
File Explorer crashes, restarts and all icons in Taskbar disappear for a while when this takes place.
The shared folder is hosted on a Windows Server 2016 machine and I can reproduce this on several different machines
all having access to same shared folder on the server.
This crash only happens on the SECURITY TAB when invoking folder properties and only after some time sitting on said tab.

Is that the local machine using the server name, or a physically separate computer that you're looking at?

If it is a separate computer, check your network, it might be resetting / losing connectivity and that might through explorer for a loop, because it is trying to update the view and all of a sudden it cannot (temporarily) see anything....

johnlgalt said:

Is that the local machine using the server name, or a physically separate computer that you're looking at?

If it is a separate computer, check your network, it might be resetting / losing connectivity and that might through explorer for a loop, because it is trying to update the view and all of a sudden it cannot (temporarily) see anything....

Click to expand...

Yes, showing one of the machines accessing the shared folder hosted on a dedicated windows server 2016E over the network.
There are no issues with the network as such. File explorer crashes ONLY on the Security tab, stumbling over the server side SID's.

And only after some time, not immediately, correct?

johnlgalt said:

And only after some time, not immediately, correct?

Click to expand...

Yes, just as I stated in the first post.

Only thing I found resembling that was a bug in SAMBA shares that caused similar symptoms, whereby Explorer crashed if at the main security tab and the user tried to edit settings.

Extremely long shot, but does your Server 2016 have SAMBA enabled?

johnlgalt said:

Only thing I found resembling that was a bug in SAMBA shares that caused similar symptoms, whereby Explorer crashed if at the main security tab and the user tried to edit settings.

Extremely long shot, but does your Server 2016 have SAMBA enabled?

Click to expand...

Yes it has.

PS C:\Windows\system32> get-smbserverconfiguration


AnnounceComment :
AnnounceServer : False
AsynchronousCredits : 64
AuditSmb1Access : False
AutoDisconnectTimeout : 0
AutoShareServer : True
AutoShareWorkstation : True
CachedOpenLimit : 5
DurableHandleV2TimeoutInSeconds : 30
EnableAuthenticateUserSharing : False
EnableDownlevelTimewarp : False
EnableForcedLogoff : True
EnableLeasing : True
EnableMultiChannel : True
EnableOplocks : True
EnableSecuritySignature : True
EnableSMB1Protocol : True
EnableSMB2Protocol : True
EnableStrictNameChecking : True
EncryptData : False
IrpStackSize : 15
KeepAliveTime : 2
MaxChannelPerSession : 32
MaxMpxCount : 50
MaxSessionPerConnection : 16384
MaxThreadsPerQueue : 20
MaxWorkItems : 1
NullSessionPipes : ,netlogon,samr,lsarpc
NullSessionShares :
OplockBreakWait : 35
PendingClientTimeoutInSeconds : 120
RejectUnencryptedAccess : True
RequireSecuritySignature : True
ServerHidden : True
Smb2CreditsMax : 2048
Smb2CreditsMin : 128
SmbServerNameHardeningLevel : 0
TreatHostAsStableStorage : False
ValidateAliasNotCircular : True
ValidateShareScope : True
ValidateShareScopeNotAliased : True
ValidateTargetName : True

Are you actively using it for anything? If not, maybe you could try disabling it on the server and see if it makes a difference.

Again, as mentioned before, it's a long shot, for sure. But since you have your settings for it here, should be (relatively) easy to set back up if it doesn't affect your problem after disabling it.

johnlgalt said:

Are you actively using it for anything? If not, maybe you could try disabling it on the server and see if it makes a difference.

Again, as mentioned before, it's a long shot, for sure. But since you have your settings for it here, should be (relatively) easy to set back up if it doesn't affect your problem after disabling it.

Click to expand...

The point is the BUG, not whether I use it or not. Simply a Windows 11 File Explorer in 2022 should not be crashing on enumerating SID's of a Network Share.

And a longstanding bug at that, if it is because of SAMBA.