Windows 11 24H2 / Azure file share broken

Question

We've started using Azure Files share with Microsoft Entra Kerberos authentication.

Following the 24H2 update our machines cannot access the Azure file share - if I run the "net use" to connect I am prompted for a username and password - this shouldn't happen.

Any suggestions welcome.

Answer 1

@Bainbridge, James
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer. Accepted answers show up at the top, resulting in improved discoverability for others.

Issue: We've started using Azure Files share with Microsoft Entra Kerberos authentication. Following the 24H2 update our machines cannot access the Azure file share.

Solution: Customers shared the following workarounds:

1. Have the user log out of Windows, and log back in using Password Authentication (the "key" icon) at the login screen. After doing this once, it is OK afterwards for that user/device.
2. Signed out, signed back in with my PIN (Windows Hello), it worked!!

If your issue remains unresolved or have further questions, please let us know in the comments how we can assist. We are here to help you and strive to make your experience better and greatly value your feedback.

Answer 2

I'm writing to seek urgent assistance with a critical issue encountered within an AVD profile utilizing the 24H2 update. Users are experiencing failures when attempting to attach files within the AVD environment.

also when same user accessing from Dc or other server that storage account file share maped drive without any issue

when I tried to map on on AVD session it promting user and password

Troubleshooting Steps Taken (Confidentiality Maintained):

• Kerberos Ticket Verification: Kerberos ticket existence and validity have been confirmed on the server side by executing the klist command.
• AVD Host klist Output: The klist command run on an AVD session host reveals an error message indicating:

<!-- end list -->

Error calling API LsaCallAuthenticationPackage (GetTicket substatus): 0x6fb
klist failed with 0xc000018b/-1073741429: The SAM database on the Windows Server does not have a computer account for this workstation trust relationship.

Request for Assistance:

I would greatly appreciate it if you could provide guidance on the following aspects:

1. Error Analysis: Could you please help interpret the specific error message ("The SAM database on the Windows Server does not have a computer account for this workstation trust relationship") in the context of AVD and file attachment functionality?
2. Troubleshooting Recommendations: Given the error and the troubleshooting steps already taken, what additional steps would you recommend to diagnose and resolve the file attachment issue within the AVD profile?
3. Potential Solutions: Are there any known configuration settings or procedures specific to AVD in 24H2 that might be relevant to this issue and could be explored?I'm writing to seek urgent assistance with a critical issue encountered within an AVD profile utilizing the 24H2 update. Users are experiencing failures when attempting to attach files within the AVD environment.