SCCM Client Agent Install Error 0x80200010

While installing SCCM client agent, the I encountered error 0x80200010. The SCCM client install failed and seems like this error occurs on Windows 10 version 1903 and 1909.

In most cases one would check the firewall on client machine or assume an anti-virus could be blocking the install. However the error 0x80200010 has a very simple fix.

So in my lab setup, when I started to perform SCCM client push, I noticed that on some computers the client installation did not succeed.

Checking the ccmsetup.log file on the client computer revealed the error 0x80200010. In addition to that I saw the below info in the log file.

  • BG error context is 2
  • BITS error: 0x80200010
  • 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.
SCCM Client Agent Install Error 0x80200010
SCCM Client Agent Install Error 0x80200010

SCCM Client Agent Install Error 0x80200010

If you’re looking to fix the error 0x80200010 during SCCM client agent install, the below steps will help you.

On your Windows 10 computer or client computer, right click Start > Run. Type ncpa.cpl to access Network Connections. Right click Ethernet adapter and click Properties.

Network properties

Select Internet Protocol version 4 TCP/IPv4 item and click Properties.

IPv4 Properties

In my case, the default gateway setting is blank. There was no gateway address specified. Probably that’s why the ccmsetup.log file showed “There are currently no active network connections”.

default gateway empty

Enter the correct default gateway address. Click OK.

default gateway entered

Now, open the ccmsetup.log file and you can see the client agent has successfully download the files via BITS. The client agent installation resumes now.

SCCM Client Agent Install Error 0x80200010

Finally we see the line CcmSetup is exiting with return code 0.

Few minutes later, the SCCM client agent appears to be installed perfectly without any issues.

SCCM client agent installed

If you know any other fix that worked for Error 0x80200010, do let me know in the comments section.

Related Posts
guest
4 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Marko

I’ve tried every fix known to man kind. I’m experiencing this issue in my lab invironment and in my work production environment. I upgraded our production environment with a mixture of Windows OS 1709, 1809 & 1909. We upgraded from SCCM 1902 to SCCM 2002. The new client works on the 1709, 1809 without any issues. Windows 10 1909 is a different beast. Microsoft dropped the ball on this someone mucked up the code. I’m still troubleshooting. If you guys have a fix please post it.

Mike Frazer

I’m having the same symptoms on several clients that are connected by Palo Alto GlobalProtect VPN. Their default gateway is blank by design, and I can’t change it without impacting traffic. Is this a BITS detection issue? Is there a workaround other than changing the default gateway?

David McKee

Great Post Youssef, thanks for the info as I have the exact issue in my Lab which has no gateways set and everything was fine until 1903. Any news from MS on why this has changed?

Youssef Saad

Hi David,
I don’t think if MS has resolved this issue yet, we’re still waiting for that.

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More