drtweak :
jimmysmitty :
The older GPUs is a driver side issue. I am surprised AMD didn;t have a driver ready for the launch.
Trend Micro has been known to wait till the last minute to update their software to work.
As for the mapped drives issue, this is nothing new. In fact it has existed since Windows 7 at least and doesn't mean they wont work. You have to just open the drive and it works fine. Another well known issue is the network icon on the start bar shows an exclamation mark and states "No Internet" even though internet works just fine. However I have noticed this less with newer versions of 10 than other older versions of Windows.
I think a lot of this is just trying to find flaws to bolster views and clicks more than anything as I said the mapped drives issue has existed for a very long time but is a very small problem that almost never affects any of my users.
Yea the mapped drive reconnecting on logon has been a LONG time issue and honestly I hate it. Login, no internet, it tired to connect even though it says no connection, map drive failed, stay disconnected till you click on it. Its like this has been an issue since XP. Almost 2 decades now and that isn't fixed till even with windows 10. This is why all my domain clients has netlogon scripts so they remap on every login and it is when there is connection because it can't get the bat file till it connects to the server. But yea annoying issues.
FYI, you can use a GPO to map drives.
Anyways, yes, this "red X" bug has always been there. I suspect there must be a race condition going on in which Explorer.exe attempts to validate SMB connectivity before authentication has cleared. In theory, it shouldn't be possible because you must first authenticate at logon before your own session loads Explorer.exe. Anyways, simply opening up the mapped drive will make the X go away as the resources is in fact there. BTW, this is regardless if your on a LAN or WLAN.