[Samba] SAMBA AD DC - Windows explorer.exe crashes on security tab access

[Rowland penny]

On 18/07/2019 23:39, Jeremy Allison wrote:
> On Mon, Jul 15, 2019 at 09:23:57AM +0100, Rowland penny wrote:
>> On 14/07/2019 22:03, Ábrahám Gyula via samba wrote:
>>> I have a Raspberry Pi 3 B+ with Raspbian Buster and a Samba AD DC is running on it. Everything works fine, I use Active Directory Users And Computers and Computer Management on Windows to control the users and the Samba share permissions. Until this point everything works fine, but the following error raised on Windows.
>>>
>>> If there is a shared directory which was made by mkdir command and a UNIX user is the owner and/or a UNIX group is the group owner the following happens in Windows.
>>>
>>> I do right click on the shared directory, select Properties and on the property window I select the Security tab the explorer.exe crashes and the property window being closed.
>>> This phenomenon does not occur if the directory is made on Windows.
>>>
>>> I found a mailing thread about this problem on samba mailing list:
>>>
>>> https://lists.samba.org/archive/samba/2018-August/217676.html
>>>
>>> But the thread ends with no solution unfortunately. The suspect that this is a bug related to Windows OS. Maybe someone who has met this error (bug?) and could help?
>> Ah, that thread, this is a Windows bug and if I remember correctly, they
>> were supposed to be looking into it.
>>
>> Jeremy, did we ever here anything about this ?
> I got sidetracked with other stuff, and didn't
> bug the Microsoft engineers with it whilst I
> was up in Redmond recently, sorry.
>
> Can you write up a method of reproducing
> and I'll see if someone at Microsoft can
> get the client team to take a look ?
>
> Thanks,
>
> Jeremy.

er, no ;-)

Mainly because I cannot get it to crash any more. It used to be that if 
the group on a file was 'root', File Explorer would crash.

Now, for myself, it just works, I have tried Win 7 & 10 against a 
standalone server and a Unix domain member.

Has Microsoft silently fixed it ?

Rowland