Windows 10: WS-Management service CIM namespace error

I was try to connect to my windows desktop via server manager. And I have a problem.

:)

 

Windows 10 CIM server connection error. How to solve the error which does not allow to connect internet?

I solved the problem to start Windows 10 afer numerous attemps and using USB Windows 10 both bits installer, but when I try to make internet connection I get answer no hardware connection. I checked status by configip/all on cmd and the internet is in place.
IP routing is disabled. There are also problems with sound configuration. So I went to device manager I looked in help how to connect to internet. In Microsoft Management Console/Contents/Get Connected/ there is Connecting to the Internet procedure. I will
go through it step by step if not there is no other option like to reinstall Window s10 package. So I followed connection description and first command get logical error explanation:

Get connected/Verify and repair network adapters C:>Get-NetAdapter. t-NetAdapter: Cannot connect to CIM server error. The service be started, either because it is disabled or because it has no enabled devices associated with it.So I search google Windows
10 connect to CIM server error.

"Cannot connect the computer to the server" error message after you install the client connect on a client computer

After you start the client connector on client computer, you may receive the following error message: Cannot connect the computer to the server because either another software installation is in progress or, the computer has a restart pending.

Either complete the installation process, or, restart the computer and try to connect it again.

In Windows Registry Editor/Session Manager there are is PendingFileRenameOperations to delete. How to proceed in Windows 10 to correct CIM server connection error?

 

Unable to Connect to Logical Disk Manager Service Error in Computer Management

WELL, I'll be an "S.O.B."! I got it... lol, just now!

Apparently, & I am going to record this & BOOKMARK/FAV it in my webbrowsers as "HOW TO FIX LOGICAL DISK MANAGER HASSLES" (lol), it is SOMETHING in my services!

You need THIS list of them running (provided you have them online that is, some OS won't have SOME of these (this is Windows Server 2003) & some are 3rd party & won't matter):





* NO SAFE MODE REQUIRED - THIS FIXED IT, PURELY SERVICES RELATED... oddly, no "dependencies" other than the ones the services need (RPC & Plug n Play) are listed in the 2 services for Logical Disk Management... it's like MS missed (somehow) the fact that there IS other dependencies on other services than what they list!

That list above is PROBABLY "overkill" & it is only a fraction of that list above, but the point is there... with ALL of those active? Logical Disk Manager "gets its act together" again & works!

APK

P.S.=> BRB, with screenshot of services & their startup status needed for this to work, in case anyone else hits this... it is a real you-know-what if you can't get to a disk to format it, lol... so, recording it for everyone's sake! apk

 

DFS Namespace issue

I've got an issue with network shares containing shortcuts of themselves. This creates and endless loop when searching, among other issues. When attempting to delete the shortcuts, I would receive errors. Using fsutil i was able to find that these shortcuts
are DFS Reparsepoints, and also was able to remove the reparsepoints and delete the folders (article). But they
kept coming back.

It took a really long time, but I finally figured out that each of the shares with this issue has a DFS Namespace set up, and I believe that the issue is how the targets were created. For instance the shares with this problem exist as such: \\Server1\Share1
and \\Server2\Share1 (these are replicated to each other). The namespace is listed as \\DomainName\Share but its namespace path is \\DomainName\Share1\Share1. I believe this is causing the namespace to create this reparsepoint INSIDE the share instead of
AS the share.

I hope this isn't coming across as gibberish. How do I fix this? I can't simply edit the namespace path, and I'm afraid deleting the namespace itself will break everything.