I installed windows 10 and everything supposedly went fine.
After logging on, at first, I couldn't access 'Settings' so I couldn't get any updates. I got that sorted by using a microsoft fix, but now find that when I try to run services.msc from the command prompt I get an error message saying "Windows was unable to open the service control manager database on 10.0.3.19" and "Error 1722: The RPC server is unavailable". Eventually the services module does come up, but all the services are missing, its just a blank form.
Also I can run "Computer Management" and click on services there and it comes up fine
The thing is, my pc is on a 192.x.x.x network, why would my pc be trying to open something on this other network? I didn't have any of these problems with win 8.1.
Any help appreciated, thanks in advance.
Could give this a try (NOTE: IT IS VERY IMPORTANT TO READ!!! THE ENTIRE TUTORIAL, AND FOLLOW IT EXACTLY): SFC Command - Run in Windows 10 - Windows 10 blog
Also, check for malware. A great free scanner you could use in addition to your normal antivirus program is widely used here, called Malwarebytes: Malwarebytes | Free Anti-Malware & Internet Security Software
Could give this a try (NOTE: IT IS VERY IMPORTANT TO READ!!! THE ENTIRE TUTORIAL, AND FOLLOW IT EXACTLY): SFC Command - Run in Windows 10 - Windows 10 blog
Also, check for malware. A great free scanner you could use in addition to your normal antivirus program is widely used here, called Malwarebytes: Malwarebytes | Free Anti-Malware & Internet Security Software
Thanks for replying, I've already ran sfc and malwarebytes.
What I really want to find out is how to stop services.msc from attempting to open the services on a remote computer by default and change it to the local computer
OH! I... didn't catch that at all...
Thanks for replying, I've already ran sfc and malwarebytes.
What I really want to find out is how to stop services.msc from attempting to open the services on a remote computer by default and change it to the local computer
That is pretty strange, and it doesn't seem like it should be normal behavior. But alas, I don't think I have an answer for you
Deleting my original post and writing this instead:
You mentioned 10.0.3.19, which isn't your PC. Had you ever used Services to "Connect to another computer," which is under the Actions menu in Services when the console finally comes up? Perhaps when connected up to a VPN and troubleshooting another PC?
Normally, that's not a problem, as the next time you run Services it will forget that you did that and show you services from the local computer. But in our case, perhaps due to a beta bug, Services for whatever reason became fixated on that other PC. I didn't even notice that the name of the PC at the top of the Services console was another one on my LAN (one that I definitely remember connecting to in this way).
To fix, once Services does eventually come up, use its "Connect to another computer" to choose Local Computer. It remembers that.
