BITS / ConfigMgr client install error, no active network connections

Ran into this fun one today, admittedly it was in my dev environment and is not a common scenario for our clients, which usually have much larger networks and network segments.

Trying to install the ConfigMgr client, via client push or manually, fails with the below error repeating in ccmsetup.log

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, Context: The error occurred in the Background Intelligent Transfer Service (BITS) queue manager.

It occurs when no default gateway is configured or pingable, even if the machines are on the same subnet as the server. The workaround is to add a pingable default gateway to the network adapter.

It’s an issue with BITS in Windows 10 1903 and continues to be an issue with 1909, it has already been logged with Microsoft and is supposedly fixed in 20H1.

4 thoughts on “BITS / ConfigMgr client install error, no active network connections

  1. I found your article searching for a solution for this issue. Finally realized you can copy the ccmsetup folder from another machine then run ccmsetup successfully without needing BITS to download the client.

  2. It appears KB4554364 has been superseded by KB4550945 (according to the Microsoft Update Catalog). I installed KB4550945 and restarted, but still get this output from bitsadmin:

    BITSADMIN version 3.0
    BITS administration utility.
    (C) Copyright Microsoft Corp.

    GUID: {DCFBC1DD-4C9C-417B-BDDE-6FA2ED35B1D3} DISPLAY: ‘CCMSETUP DOWNLOAD’
    TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\SYSTEM
    PRIORITY: NORMAL FILES: 0 / 3 BYTES: 0 / UNKNOWN
    CREATION TIME: 5/6/2020 4:27:38 PM MODIFICATION TIME: 5/7/2020 7:58:21 AM
    COMPLETION TIME: UNKNOWN ACL FLAGS:
    NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
    RETRY DELAY: 600 NO PROGRESS TIMEOUT: 86400 ERROR COUNT: 0
    PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
    ERROR FILE: http://:80/SMS_DP_SMSPKG$/ZMS00002/x64/WindowsFir
    ewallConfigurationProvider.msi -> C:\WINDOWS\ccmsetup\WindowsFirewallConfigurati
    onProvider.msi
    ERROR CODE: 0x80200010 – There are currently no active network connections. B
    ackground Intelligent Transfer Service (BITS) will try again when an adapter is
    connected.
    ERROR CONTEXT: 0x00000002 – The error occurred in the Background Intelligent Tra
    nsfer Service (BITS) queue manager.
    DESCRIPTION:
    JOB FILES:
    0 / UNKNOWN WORKING http://:80/SMS_DP_SMSPKG$/ZMS00002/x
    64/WindowsFirewallConfigurationProvider.msi -> C:\WINDOWS\ccmsetup\WindowsFirewa
    llConfigurationProvider.msi
    0 / UNKNOWN WORKING http://:80/SMS_DP_SMSPKG$/ZMS00002/x
    64/client.msi -> C:\WINDOWS\ccmsetup\client.msi
    0 / UNKNOWN WORKING http://:80/SMS_DP_SMSPKG$/ZMS00002/x
    64/ClientUpdate/configmgr1906-client-kb4517869-x64.msp -> C:\WINDOWS\ccmsetup\co
    nfigmgr1906-client-kb4517869-x64.msp
    NOTIFICATION COMMAND LINE: none
    owner MIC integrity level: SYSTEM
    owner elevated ? true

    Peercaching flags
    Enable download from peers :true
    Enable serving to peers :true

    CUSTOM HEADERS: NULL

    Listed 1 job(s).

    C:\temp\Client>

Leave a Reply