Windows 10: IconResource partially works via SMB after Windows update

Hello, After installing the updates KB5018546 and KB5018418 on October 12, the custom icons I use for my shared folders on my Synology NAS are no longer working.I have already contacted Synology technical support and here's what to know :- the problem occurred after installing the cumulative updates KB5018546 .NET Framework for Windows 11 and KB5018418 Windows 11,- the configuration in desktop.ini of an absolute path of a .ico present on C: displays correctly the custom icon for example : IconResource=C:\Users\Tony\Desktop\test.ico,0,- the absolute path of a .ico present on Z: the NAS s

:)

 

How to solve problems with accessing, discovering and connecting to NAS with SMB connection from Windows 10

I am experiencing difficulties with accessing, discovering and connecting to my NAS with SMB connection from Windows 10.

I have tried most of the solutions suggest on the Web, but avail, none of them worked.

• Enabling SMB v2 and restarting
• Checking SMB v1 in Windows components is ticked on
• Etc.

It seems that Microsoft has broken something though their patches

If anyone can supply me with a permanent/ final fix,
not workaround, please post it here.

 

How to solve problems with accessing, discovering and connecting to NAS with SMB connection from Windows 10

I am experiencing difficulties with accessing, discovering and connecting to my NAS with SMB connection from Windows 10.

I have tried most of the solutions suggest on the Web, but avail, none of them worked.

• Enabling SMB v2 and restarting
• Checking SMB v1 in Windows components is ticked on
• Etc.

It seems that Microsoft has broken something though their patches

If anyone can supply me with a permanent/ final fix,
not workaround, please post it here.

 

Safety of Login credentials for SMB...

Ok so similar but slightly different question:

Background:

• Storage hosted by my Linksys WR32X Router (see screenshot) with authentication credentials
• SMB v1, v2, and v3 are all enabled on my Win10 PC via the "Enable Features" window (and I've restarted my PC)
• My Windows 10 account uses my MS Live email address as a username and I have 2-step authentication set up as well

A Timeline:

• The NAS successfully shows up and is accessible from the Network page in Win Explorer
• I've successfully mapped the storage to a Network Drive in Windows using the authentication credentials I set in my router's settings page (again see screenshot)
• When I try to access the SMB share via a separate device on my network (my FireTV device running Kodi 17--which supports up to SMB v3), I get caught in an endless loop of it asking for a username and password.
  • I've tried using the credentials I set in my router settings, which worked when I mapped the share to a network drive in windows, and it didn't work in Kodi
  • I've tried un-mapping and re-mapping the share to a network drive using my windows 10 account username and password instead of the credentials set in my router settings, which did not work for either mapping the drive in windows or for accessing it in Kodi
  • I also tried generating an app-specific password via my Microsoft account settings in case the 2-step authentication set on my account was causing the issue (much like you have to do to add your account to Outlook Desktop App when 2-step is set up)

I just want to access my SMB share from my FireTV device (or any network device for that matter) without having to create a new local user. I saw some responses saying that I need to set up a new local account and use it's credentials to map the drive and
then it should work, but is this REALLY necessary? It seems like a redundant workaround...

So, what if I don't want to create a new local user? I like having jut one account on my Win10 PC and that uses my
MS email address as the Win10 Account username.

Any suggestions? What am I missing here? Thanks in advance MS community!