Problems with Remote Desktop & FileSharing on Windows 11 IoT Enterprise LTSC 2024

Hello Baptiste DEROSIN

I learnt a similar issue from this article and want to share it with you: [https://windowsforum.com/threads/fixing-windows-11-remote-desktop-issues-after-24h2-update.352977/](https://windowsforum.com/threads/fixing-windows-11-remote-desktop-issues-after-24h2-update.352977/

)

In short, Windows 11 IoT Enterprise LTSC 2024 has stricter security defaults. But here’s how you can resolve the “login attempt failed” issue based on the above article:

1. Create matching local user accounts
   • Ensure each PC has a local user account with the same username and password.
   • RDP and SMB often reject credentials if the account doesn’t exist on the target machine.
2. Disable Network Level Authentication (NLA) (for testing)
   • Go to System Properties > Remote tab.
   • Uncheck “Allow connections only from computers running Remote Desktop with Network Level Authentication.”
   • This helps isolate whether NLA is blocking access.
3. Enable “AllowInsecureGuestLogons” for SMB
   • Open Registry Editor and navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
   • Create or set AllowInsecureGuestLogons to DWORD: 1
   • Reboot the system.
4. Ensure correct sharing permissions
   • Share folder with “Everyone” and grant NTFS permissions to the same user account.
   • Use \\IP\folder or \\computername\folder from another PC.
5. Check firewall settings
   • Ensure inbound rules for “Remote Desktop” and “File and Printer Sharing” are enabled in Windows Defender Firewall.
6. Verify SMB protocol is enabled
   • Run Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol
   • If disabled, enable it with: Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

I haven't been able to find a solution yet but uninstalling the recent updates makes the remote desktop & sharing folder available again.

(cumulative update KB5066131 & Safety update KB5068861)
I suppose it might mean that some parameter can be correctly modified to make it work with the most recent update.
I will update this post if I find something.

Feel free to do the same.

Baptiste

Hello,

I managed to understand my issue thanks to these threads :

https://community.spiceworks.com/t/microsoft-updates-break-rdp/1244529
https://support.microsoft.com/en-us/topic/kerberos-and-ntlm-authentication-failures-due-to-duplicate-sids-76f7394d-c460-4882-9ed1-d27e0960f949

I used an image to install my windows quicker but the SID was replicated as well.
I was able to check with the powershell command :

get-localuser | select name, sid

On both PC the SID was for example : S-6-3-54-5879734548-787697-314513545.

I was able to change the SID properly with the CMD (Admin) :

cd %WINDIR%\System32\Sysprep
sysprep.exe /generalize /oobe /shutdown

Some Packages were interfering with the sysprep command but I was able to delete them by checking the log (to know which package to delete) here : C:\Windows\System32\Sysprep\Panther\setuperr.log and deleting them with the powershell command :

Remove-AppxPackage -Package  NotepadPlusPlus_1.0.0.0_neutral__7njy0v32s6xk6 -AllUsers

Note : The SID reattribution will affect some configuration (rename the PC, ...) but will note delete your files or need you to reinstall Windows.

Hello,

I managed to understand my issue thanks to these threads :

https://community.spiceworks.com/t/microsoft-updates-break-rdp/1244529 https://support.microsoft.com/en-us/topic/kerberos-and-ntlm-authentication-failures-due-to-duplicate-sids-76f7394d-c460-4882-9ed1-d27e0960f949

I used an image to install my windows quicker but the SID was replicated as well. I was able to check with the powershell command :

PowerShell

get-localuser | select name, sid

On both PC the SID was for example : S-6-3-54-5879734548-787697-314513545.

I was able to change the SID properly with the CMD (Admin) :

Windows Command Prompt

cd %WINDIR%\System32\Sysprep sysprep.exe /generalize /oobe /shutdown 

Some Packages were interfering with the sysprep command but I was able to delete them by checking the log (to know which package to delete) here : C:\Windows\System32\Sysprep\Panther\setuperr.log and deleting them with the powershell command :

PowerShell

Remove-AppxPackage -Package  NotepadPlusPlus_1.0.0.0_neutral__7njy0v32s6xk6 -AllUsers

Note : The SID reattribution will affect some configuration (rename the PC, ...) but will note delete your files or need you to reinstall Windows.