Windows 10: Unable to access other profiles on laptop.

I have a Samsung laptop on which I had three profiles. (my own, my partners and my sons) While signing into my profile after startup I had an error about the login not being recognised and was signed into a temporary user that allowed me very little access and told me that any changes would not be saved on logout. I turned the laptop off and on again to be greeted with only my profile (a lot of visual settings had been changed - background pic, layout of desktop etc).

I thought nothing of it until my partner asked to use the laptop and discovered that she couldn't access her profile. In fact her profile was no longer an option on the sign in screen, just my profile is there. When I access the accounts page it and go into family and other people I can see the the other two profiles in the list and even change the status from standard to administrator but this makes no difference.

I am relatively new to this kind of endeavour so please be gentle with me.

:)

 

Unable to Access Profile

This article looks good for your scenario-

Move Users Folder Location in Windows 10 also

How to Fix a Corrupted User Profile in Windows 8

 

Unable to access other computers on network/Homegroup

Perhaps because the Homegroup expects to be able to see them? Have you been able to "Leave the Homegroup" on all your machines? Related to this I just realized that if you were still connected after deleting that PeerNetworking directory that it would
just get filled in again by the other machines' requests trying to check on what is going on. So, are you deleting it from all of them when none of them are connected or at least when none of them will be trying to Join? Maybe doing something with the Homegroup
services would make this procedure a bit more manageable but I don't have any precise examples about what I mean by that. One would hope that this is something that the troubleshooter would take care of. What is it doing to cover this case? Any hints in
the Detailed report?

Regarding the missing sockets: you say that Kapil's fix only lasts until the next boot? You could try tracing that to find out where it is coming from. It might be necessary to use the ProcMon Boot Logging option. Notice that since you know the Event
class that you would be looking for you could make sure that ProcMon was recording only that (e.g. Operation Is RegSetValue); otherwise you could make sure that recording was going to a file and not just paging space. For another way of looking at the fix
you could use netcfg.exe as I outlined in another thread last night. I may have a go with this myself on my VM (11099)--just to understand why I seem to be working OK with no IPv4 Tunneling or if I should care.

No Internet access after Windows 10 December 22, 2015 Update

Also, I pointed a few other related threads here and that reminds me that I was curious about your Avast and Flash factors. Are you trying to do anything about them?



HTH

Robert

---