The Perplexing 0x80200010 MECM Client Installation Error

Introduction.

Recently a colleague escalated a MECM client issue to me.  The attempted installation of the client, whether done by a manual install command line or via the client push installation method, would not complete.  The following error was found in the ccmsetup.log file

Download Update: A recoverable error has occurred.  A retry attempt will be made. Error: 0x80200010, Description There are currently no active network connections. Background Intelligent Transfer Service (BITS) will try again when an adapter is connected.

The installation did retry but never did complete.  This was happening on a Windows Server 2022 instance, but it has also been reported on Windows 10 and Windows 11 instances.

Killing the Network Location Awareness Service (nlasvc) process worked for Mr Durning.  This fix can be found at:

https://sccmnotes.wordpress.com/2025/08/08/ccmsetup-the-mysterious-case-of-error-0x80200010-there-are-currently-no-active-network-connections/

Providing a Default Gateway address in the NIC's TCP4 properties tab worked for Mr Desai.  This fix can be found at:

https://www.prajwaldesai.com/sccm-client-agent-install-error-0x80200010/

Neither of these fixes worked or were relevant for the case presented to me.  I had to dig a little deeper.

Fix 1 - Install without using BITS.

One workaround was to install the client manually by using the /SOURCE parameter.  With this method the installation will copy the MECM client files locally into the c:\windows\ccmsetup directory without using BITS.  Here are the required steps: 

1) On the machine with the issue create a directory on the c: drive called client. 

2) Copy the MECM client source files into this directory.  The MECM source files can be found in the Microsoft Configuration Manager directory on the primary site - in my installation this is at: C:\Program Files\Microsoft Configuration Manager\Client.

3) On the machine with the issue, open a command prompt with Administrator permissions and navigate to the c:\client directory.

4) Install the MECM client using the /SOURCE switch.  Here is an example of the command line that worked for me:

ccmsetup.exe /SOURCE "c:\client" SMSMP=<FQDN of the Management Point> SMSSITECODE=<site code of the Primary Site.>

For example: ccmsetup.exe /SOURCE "c:\client" SMSMP=SERVER2.TEST.ORG SMSSITECODE=ABC

5)  After pressing Enter your client installation should complete.  

In my example this did complete however the client would not register - and again this appeared to be related to issues with the network connection.  This then led me to fix 2.

Fix 2 - Reset the TCP/IP stack.

Having installed the client by bypassing the BITS download, I was not yet "out of the woods" as they say.  The client did register with the MECM primary site, however the client was not fully activated.  For instance, if I opened the applet by running control smscfgrc from the command line, clicking on Actions - I could only see two actions:  Machine Policy retrieval & Evaluation and User Policy retrieval & Evaluation.  A fully activated client would have at least 10 actions listed, as shown here.

Resetting the TCP/IP stack did resolve this problem.

Note: If you are using a static IP address, your IP settings will be removed.  You will have to reapply them.  It is recommended that you create a local admin account so you can log back into the device in this scenario.

1) Make a note of the device's IP settings.

2) Open a command prompt with administrator permissions.

2) Type netsh winsock reset and press Enter.

3) Type netsh int ip reset and press Enter.

4) Restart your machine.

5) If using static IP settings, log into the machine and reapply your IP configuration.

Conclusion

I hope you have enjoyed this little blog and I hope it has saved you hours of troubleshooting your mysterious 0x80200010 MECM client installation problem.