Replies

I am coming back for a second time on this issue. I had this issue when I upgraded my Dell 7510 laptop to Windows 10 2004. I have one NAS drive from Thecus that is older and only supports SMB 1.5. After trying many things, I finally solved this by mapping a folder on the NAS drive and setting the ProviderFlags Dword 1 in the registry under the mapped drive letter. That has worked fine on that computer for several months.

I recently switched to a new Dell 7550 laptop that came with Windows 10 20H2 installed. I had the same problem initially, that I had to reenter the password every time I tried to access the NAS. I have tried enabling the SMB 1.0 services, enabling NetBIOS over TCP/IP, allowing NLTM authentication, making a whole host of Windows services start automatically, and a few other things, including the ProviderFlags in the registry. Now, when my computer boots, the mapped drive shows that it did not connect. When I select it, I get strange error messages like the specified device name no longer exists or I have no permission to access. I am not even give the option to enter credentials. However, if I reboot the computer, the drive connects this time every time using the stored credentials. It then works fine until I shut down over night and reboot the next day. I suspect that, on initial boot, the drive tries to connect. For some reason, the Thecus recognizes the connection, but Windows does not. When I try to access later to establish the connection, the Thecus does not respond because this computer is already using that Thecus account. I understand one cannot have more than one connection to the same NAS from the same computer at the same time. Why it happens only at initial boot I cannot tell unless it has something to do with timing (the Thecus probably responds a bit slower since it has not been accessed in a long time).

I have tried everything I could find on this thread and elsewhere, with no success. The last thing I tried was mapping the drive using its IP address instead of its network name. Same problem. Any advice is appreciated. Thanks.

It is a powered USB hub, and there is nothing plugged in that draws much power.   As I noted, I have used this same hub plugged directly into the computer with all the same devices for more than 2 years with no issues.   I first observed this problem a week or so after I switched the hub to the Thunderbolt docking station, although I cannot be sure that it is related to the problem.  As I noted, all the other devices on that hub (mouse, webcam, printers, etc.) have been working fine.  The fact that it is only the keyboard is what makes it hard for me to track down — unless the keyboard has developed an internal hardware problem.

I use Kaspersky Internet Security for full time protection.  I have it run a full scan every week.  If I suspect something, I run the Kaspersky stand alone scanner from a USB drive.  The stand alone scanner now does only a limited scan by default, but you can set it for a full scan.  Kaspersky has been at or near the top of almost every lab test of protection software for years.  They also provide very good support.

1 user thanked author for this post.

rc primak

I do have version 19041.804.  Thanks.  That gives me more assurance.

I am assuming it is Microsoft servers or a bad update.   As I noted, I was able to get around it by going back and downloading the latest version as if I was installing new and then installing over the old version.   None of the repair options worked for me.  However, the fresh install seemed to work.

I manged to get the Office programs functioning again by downloading and reinstalling over the old versions.  Seems to work for now.   Why does Microsoft allow such things to happen!

I am not sure why I cannot find the post here now, but I did receive a suggestion that seems to have worked.  Apparently, this is an issue with the version of smb network protocol.   I was instructed to run Powershell as administrator with the command Get-SmbConnection.  That gave me a list of all my currently active NAS devices and what version of smb they were using.  It turns out that the Thecus is using smb 1.5.

I was then instructed to run RegEdit, navigate to key HKEY_CURRENT_USER/Network.  I found the letter for the Thecus drive mapping, and I added a DWORD(32-bit) key named ProviderFlags and gave it a value of 1.  The next time I booted up the computer, I had to enter the Thecus password.  However, after that it seems to remember the credentials.

The main reason I have the new Synology NAS is because I was running out of storage and needed to add more disks.  However, the Thecus N7700PRO has not had any firmware updates in many years.   Thecus now has a newer version of the product, and apparently any new software is not compatible – so they are not updating the old systems.  That is why it is stuck on smb 1.5, and I have no options of which I am aware to change that.  I discovered that Synology apparently uses an architecture where all of their devices can run the latest version of their software.   So I elected to purchase a large, fast Synology NAS for my increased needs.  My new Synology NAS is running smb 2.0.2.   I also gets firmware updates regularly.

Interestingly, I also have an even older small Synology 2-drive NAS that was my first NAS but I really don’t use any more.   It was running the latest Synology firmware.  However, it was set to use smb 1 probably as a legacy.  For some reason, while I did have trouble with this NAS automatically connecting at bootup, I was not having the credentials problem with this one — even though it showed using smb 1.5, also.  It must be something in how the Thecus implements smb.   I was able to reconfigure the old Synology to run smb 2.0.2 like the new one.  (I had to unmap and remap the drive, and change the firmware configuration.)

I am not exactly sure what that registry key did, but it seems to be a workaround for my problem.   Thanks again to everyone for the assistance.

I switched to 2004 in November.  I was on 1903, and had to do something — and at that time Susan was saying 2004 is OK.   I wish I had not made the upgrade.  I started seeing a problem with remembering credentials on one of my NAS drives immediately that I have not been able to resolve after much effort and many tries.  Only then did I see the information that others were having similar problems.  Fortunately, my credentials problem only affects the one NAS drive, so I can live with the consequences.  However, it is disheartening when Microsoft cannot get the major bugs out of a feature release before the next one comes up.

As I noted, this work around did not work for me.  Thanks.

Just an update.  I have now tried every workaround I have seen suggested.  I have tried logging into a local account on my computer, rebooting, then switching back to an online account.  I tried the recommendations to make Credentials Manager run in automatic mode, and to enable permissions in the associated folder.  (This seemed to cause permission access problems for a while, but that seems to have gone away.)  I tried deleting the Thecus device entry in Credentials Manager, and setting up a new one.  I tried running sfc /scannow.   I even tried creating a new registry Dword(32) key named ProtectionPolicy at HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb and setting it to 1, which is supposed to fix some problems with saving of credentials.   None of these things helped with my issue.

Interestingly, my issue is still very narrow.  While most people having troubles with Win 10 2004 credentials seem to lose passwords all over the place, I only have a problem with my NAS device made by Thecus.  My other NAS devices made by Synology work fine.  My OneDrive password works fine.   In fact, once I set the password for the Thecus, it does seem to be retained as long as I am logged into the computer (although this may just be that the login to the Thecus is remembered).    However, the first time I try to access the Thecus after a new boot I have to re-enter the password.

Perhaps this is just one example of the error in Win 10 2004 and I will just have to wait for Microsoft to fix it.  Any other ideas are welcome.  Thanks.

Thanks for the suggestion, PaulK.   Since this is my local network, the password for the Thecus device is the same as the one for my main Synology NAS.  And it is fairly simple.   So the problem must not relate to the password form.   It seems like some kind of Windows link or memory related to the Thecus must have been corrupted  when I made the upgrade to Windows 10 2004.   I tried deleting the entry in Windows Credential Manager, and then creating a new one.  That did not fix it.  I am not sure where else to look.  My login account for the Thecus is valid, as it still works when I don’t get the permission error and I manually enter the password.   I am not sure what else would make Windows think it is inaccessible.

Yesterday, I had the problem with permissions again that I noted earlier.  I got the message that the Thecus is not accessible and I might not have permission to access.   I have all my NAS drives mapped to Windows.  However, at that time, I noticed that the mapping for the Thecus did not show in file explorer.   This morning when I booted up, the mapping was back, and I did not get the permission error when I accessed it.  Nevertheless, I still have to enter my password.

I can live with having to enter the password for a while.  However, when I get that permission error I cannot access the device in any way.   Does anyone have any idea what might be causing that, or what I can do trace the problem or repair or work around?  Thanks.

 

Thanks for the advice.  I followed the suggested leads.  I changed the permissions on the Microsoft>Vault file.  I made the Credentials service start on automatic.  I searched for S4U tasks, but found none.   (The problem is with an NAS on the network.)  Right after that, when I tried to access my Thecus drive I got the following message

This was worse.  I could not access the drive at all.  I rebooted the computer, and I seem to be back to where I was — with the same problem.  I tried deleting the device in Windows Credentials and re-establishing it.  This time I also set up an entry for the IP address of the device.  I will have to see what happens.

 

1 user thanked author for this post.

b

I finally managed to get the popup again when I was logged into Word in administrator mode.  I selected the no option.   However, today, when I logged into Word again, I got the popup.  So neither filling out the popup when in admin mode or switching accounts seems to help.  Any other suggestions?  Thanks.

d3nzen,  I have not had any problems with VPNs.  If you suspect Kaspersky is interfering, have you contacted them.   I had an issue with a particular website that I traced to Kaspersky.  They responded immediately, asking me to run software that collected information for them.  They forwarded this information to their developers, who responded with a very clear answer of an issue they were working and also a temporary work around that dealt with the issue.  All that happened across two days.  If you are having any issues with Kaspersky, I suggest you file a ticket and get their help.  I have only rarely gotten such good and timely support from software vendors.

3 users thanked author for this post.

Elly, Trev, Kathy Stevens

While it was not on your list, I have been using Kaspersky Internet Security for many years.  Some people worry because it is a Russian company.  Nevertheless, Kaspersky and his company are very respected by malware professionals.   The software consistently scores among the best in independent lab tests.   The problem with security software is you never know for sure if the software is good or you just have been lucky.  I have gotten great support from them when I had an issue, and it has blocked a number of malware files in my email as well as a few web pages.  It also gives me warnings when I, for example, update a plugin in my browser that monitors the pages.  I have not noticed any drag on resources.  I had a friend a year or so ago with a malware infected computer who could not do anything on his machine.  I downloaded the Kaspersky bootable disk and ran the scanner/cleaner for him.  It cleaned things up completely with no manual intervention.

3 users thanked author for this post.

Alex5723, Trev, Kathy Stevens