Random Clients fail to download content (0x80070003)

******Update July 27 2017:  I have confirmed that the below issue is addressed via: KB4035759.  Thanks to all who helped! ******

This posts outlines an issue that I am seeing in Configuration Manager starting in 1702. I currently have a call open with MS and will update the post once the issue is resolved. I am currently aware of 2 environments with the issue and am posting this in case this is also an issue for others. If you have this issue in your environment, please shoot me a message with any cases you have open so Microsoft can see the commonalities in our environments.

Steps to Reproduce:
1. Issue occurs on newly built computers (this may be for the simple fact as they are installing the most software). We have reproduced the issue on computers built with our current gold image, last December’s gold image as well as using a new task sequence and VLSC ISO. Failure rates are around 20% so a minimum of 5 computers should be built. For our tests we built 15 computers total all in the same subnet.
2. Mass add computers to software deployment collections

A little about the environment
1 Primary Site server
2 Servers with MP/DP/WSUS roles
1 SQL server
Windows 7 clients

1. At the beginning of the issue, the following is logged (this may or may not be related as this error seems to be thrown when the client restarts):
Error retrieving FileBITS global state object from the GOT.
2. The following informational entries appear in the DataTransferService.log
QUEUE: Readded DTS job ‘{4CD5D29F-807A-4069-9D0D-F09301592264}’ in state DownloadingData to the active list.
Restarted DTS job ‘{4CD5D29F-807A-4069-9D0D-F09301592264}’ in state DownloadingData.
Successfully re-synchronized DTS job {4CD5D29F-807A-4069-9D0D-F09301592264} with BITS job {8CCC7CE6-309B-41D6-9F2E-2E61331BCC66}.
3. The following warning entries appear in the DataTransferService.log immediately after the entries in #2. These entries recur indefinitely until a work around is implemented:
CDTSJob::HandleErrors: DTS Job ‘{4CD5D29F-807A-4069-9D0D-F09301592264}’ BITS Job ‘{8CCC7CE6-309B-41D6-9F2E-2E61331BCC66}’ under user ‘S-1-5-18′ OldErrorCount 0 NewErrorCount 4 ErrorCode 0x80070003
CDTSJob::HandleErrors: DTS Job ID='{4CD5D29F-807A-4069-9D0D-F09301592264}’ URL=” ProtType=1
4. Some clients also have the error:
DTSJob {9B839D96-A24A-47AE-8916-03783762EDAB} encountered error while processing completed download (0x80070002).
5. In the Bits-Client Event log:
BITS stopped transferring the CCMDTS Job transfer job that is associated with the URL. The status code is 0x80070003.
6. If you manually navigate to the URL you are able to successfully download the file.


Note: The following are workarounds, but do not prevent the issue from recurring.
1. Resetting client policy will allow content to download
2. Uninstalling and reinstalling the client will allow content to download
3. Updating the distribution point will allow content to download

The issue appears to start immediately after the ConfigMgr client restarts the computer (either as part of an application task sequence or as a program setting “After running: Configuration Manager restarts computer”). It appears that incomplete downloads at the time of the restart are affected.


16 thoughts on “Random Clients fail to download content (0x80070003)

  1. Alexandre Legault July 24, 2017 / 8:07 am

    I seem to have the exact same problem….

    • mdedeboer July 24, 2017 / 8:23 am

      Thanks ☺ I’ll let the MS team know. Do you also have a premier call open on this?

  2. Carlo July 26, 2017 / 3:18 am

    I have the same problem

    • Gabino February 23, 2018 / 5:38 pm

      For my, Updating the distribution point will allow content to download was the solution… thanks!

  3. Carlo July 26, 2017 / 6:03 am

    Do you already have a permanent solution for this issue. We are currently experiencing the exact same issue and our workaround is reset policy.

    • mdedeboer July 26, 2017 / 7:01 am

      Hi Carlo,

      Currently I have no solution to the issue except like you mentioned a policy reset (or reinstalling the client). So far my Premier call has no leads as to the cause. Anecdotally, I am leaning towards Configuration Manager client initiated reboots corrupting the download jobs but do not have any confirmation from MS on this. If you have a ticket open on this please let me know so that we can link our tickets.


      • Carlo July 26, 2017 / 10:08 am

        Hi MDEDEBOER,

        Thanks for your response. I did open a premier call towards Microsoft. I’ll let you know when we find leads.

      • mdedeboer July 26, 2017 / 10:24 am

        Hi Carlo,

        Thanks! If you’d like to reference my call, my ticket # is 117071016014962.


    • mdedeboer July 27, 2017 / 7:25 am

      Thank you very much! I will send this to the staff on my MS call and see what they say. Once I install it I will report back.


      • mdedeboer July 27, 2017 / 11:29 am

        KB4035759 is now installed. Now time to test…

  4. Carlo July 27, 2017 / 12:04 pm


    MS has provided the same fix. I have just informed our infra support team to apply the said patch. Please let me know if it is able to resolve the issue.


  5. mdedeboer July 27, 2017 / 3:01 pm

    Hi All,

    I can confirm that KB4035759 appears to have addressed this issue in my environment. Thanks a bunch @Anthony for pointing us in the right direction!


  6. Anthony July 28, 2017 / 3:45 am

    Glad that it works! Will install it on our side next week, hope it will be working as well for me.

  7. focalguy August 22, 2017 / 11:14 pm

    Thank you SO much for sharing this. Wish it ranked higher on Google for 0x80070003 but I found it this time. Been dealing with this for months and only had discovered the work-around of removing and re-installing the SCCM Client. I don’t have Premier support so I’m fortunate people who do can share what they learn.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s