Windows 10: Windows 10 pro local account not able to access resources

Hello,I would like to ask for an advise for the windows 10 pro related issue:I made a new installation, have an admin account and with an admin rights, i am able to access all the network resources. However, when i created a new local account for an employee, when logged in with a new account, the user is not able to see any resources nor is able to ping the server, which was doable with Admin account.any ideas what could cause this issue?thank you very much for any kind of helpLubos

:)

 

Unable to access Local Disks (C, (D, and any programs inside those

Hi,

Thank you for posting in Microsoft Community, we appreciate your interest in Windows 10.

As you are facing issues with privileges to access the local account, I suggest you to try the below and check if it helps.

• Please be informed us the troubleshooting steps you have already tried.

This issue might be due to some error in system settings.

If you have not yet tried the below steps, I suggest you to perform and check if it helps.

Step 1: I suggest you to log out from the current user account, restart the computer and log-in with the administrator account and check if you are able to access the local drivers.

If the issue still persists,

Step 2: I suggest you to place the computer in safe mode, try to log-in with administrator account and check if the issue persists.

Try the above steps and reply to the post with an updated status of this issue, we will be happy to assist you further.

 

How to access Cortana on local account in Windows 10?

Hi,

Do not worry we will help you with this issue.

I would like to inform that when you try to configure the Windows built-in apps on your computer you will have to enter Microsoft account. However, you can use local account to configure Cortana.

As currently you are on Microsoft account, try to log-in to that account, convert Microsoft account to Local account on your computer, configure Cortana and check if it helps.

Step 1: To convert the Microsoft account to local account, you can do the following:

• Sign in to your Microsoft account on Windows 10.
• Click Start and then Settings.
• Click Accounts and Sign in with a local account instead.
• Enter your Microsoft account's password, and click on Next.
• Type in a Username, Password, and Password Hint that you want to set for your Local account and click
  Next. Click on Sign out and Finish button.

Step 2: The below are the steps to setup Cortana on local user account in Windows 10

• 
  Log-in to your computer using local account.
  
• 
  Click on Search bar in the
  Taskbar.
  
• 
  Click on Next button.
  
• 
  Click on Use Cortana.
  
• 
  After agreeing with its privacy terms, Cortana will ask you to sign in with a Microsoft account.
  
• 
  Here, you will be able to set the Microsoft account to be used only with Cortana, not with any other features or apps from Windows 10. Also, it will not replace your local account in Windows 10.
  
• 
  Click on Sign in button.
  
• 
  Enter the details of your Microsoft account and click on
  Sign in.
  
• 
  At this step, click on Sign in to just this app instead
  
• 
  Now Cortana is enabled and working for your local account on your Windows 10 device.
  

Hope it helps. Get back to us with an updates status of accessing Cortana on local account for further assistance.

Thank you.

 

Strange Windows 10 User Account issue.

Unfortunately I had done those steps numerous reboots, it just, reappears for no good reason. The base account isn't even a Microsoft account, it's a local account.

I haven't quite tried the built in administrator account on W10, but so far in my experience on my own computer, the built in account seemed to have absolutely no more control than I did on my own.

It's just strange, I go in, it warns me twice about deleting the account, then it's gone. Reboot, and it's back?

EDIT: Just to specify, both command line and Netplwiz both say only HIS account exists on the computer, it doesn't list this rogue account. This is what I meant in my first post about the fact that even Windows doesn't seem to believe it exists, HALF the time. *Frown