Credential Problem? in Win10 v2004

Topic

New Reply

I am running Win 10 Pro, V 2004 (OS Build 19041.329) with no problems except one: an inability to back up or transfer files to my networked laptop (Dell Inspiron 7591) running on the same OS version. The problem is that when using Alway Sync to transfer files to the Dell-7591 shares I get the message: Provider could not perform the action since the context was acquired as silent.” I’ve submitted the problem to Allway Sync and haven’t heard yet, but I think the problem is in my credentials.

Searching the error msg suggests that the problem is in my Windows credentials, but I see no hotfix or solution on how to fix this. I also cannot access the Dell-7591 with Win Explorer. The error is: Windows cannot access \\Dell-7591. No other information.

How can I fix this problem? Any help appreciated.

Thanks

1 user thanked author for this post.

woody

Reply | Quote

Replies

My bet is on an Allway Sync bug.

Reply | Quote

I also cannot access the Dell-7591 with Win Explorer. The error is: Windows cannot access \\Dell-7591. No other information.

I’d check your network settings and file sharing permissions. Once you can access the system then try your backup program again.

1 user thanked author for this post.

doriel

Reply | Quote

Put both PC into same workgroup. Then check your sharing.
It is located in the old-fashioned control panel. It should look like this:

At home, I use one shared folder for exchanging data between my devices. When accessing that folder, I enter credentials of local user create exactly for this purpose.

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

Reply | Quote

jel wrote:

I also cannot access the Dell-7591 with Win Explorer.

Use IP address and add that address to Quick Access.

Reply | Quote

Windows’ ‘credentials’ are just stored (persistent) authorisations that prevent the need to re-enter username/password combos each time a user or device accesses another resource (local network, internet or even software) that has been configured to ask for authorisation.

Credentials occasionally get corrupted (particularly after Windows updates) so you just remove the credentials using Windows’ Credential Manager (via Control Panel). To access it, in Cortana’s Search panel, begin typing cred and it should appear as the ‘Best match’ automatically.

The thing with credentials is that they can just be removed… usually. The next time you access a resource that needs authorisation then you’ll be asked for a username/password combo. If you are asked whether to save the info then the username/password combo is stored again as a credential.

Note that Credential Manager has 2 areas – Web Credentials (external resources) and Windows Credentials (local resources).

For example, I had two stored/persistent credentials for the now-defunct ‘Windows Secrets Lounge’ website – one as a ‘member’, the other as a ‘forum administrator’. They showed up in Credential Manager under Web Credentials thus:

Similarly, I have stored credentials to allow me to access other devices on my local network.

Note also that – under Windows Credentials – there are 2 Microsoft-created credentials – virtualapp/didlogical (under Generic Credentials) and SSO_POP_Device (under Other Items).

A Google search shows that the former was apparently created by a Microsoft Live product. I don’t use any Microsoft Live product. Ever.

A Google search shows that the latter was apparently created by a MicrosoftAccount resource. I do not use a Microsoft Account. Ever.

I have not yet seen a good explanation of these 2 persistent Microsoft-created credentials (which the former also appears on my last remaining Win 7 devices as well).

I took the screenshot above before I deleted both stored Microsoft-created credentials (with a screenshot of each action) then restarted the device. The restoration of the Windows desktop to a stable state was *much* slower than normal. When it was all stable, Credential Manager showed that Windows had put these 2 Microsoft-created stored credentials back in again. Go figure…

Hope this helps…

1 user thanked author for this post.

Elly

Reply | Quote

As a matter of interest I’ve trawled backwards through various Windows editions and found that Credential Manager was apparently introduced with Windows 8… as was the virtualapp/didlogical credential:

However, I’ve realised that my posts are off-topic to the OP so… my apologies to @jel.

Hope this helps…

Reply | Quote

Have you tried Carbonite or Gs Richcopy 360 before?? I think you will never face issues like that

Reply | Quote