SCCM 1702 KB4035759 Client update

SCCM 1702 KB4035759 Client update.

Issues that are fixed

• Software updates cannot be downloaded to a Configuration Manager current branch, version 1702, client if the following conditions are true:
  • The software update contains multiple files.
  • The content for the software update is not available at an accessible distribution point.
  • The download setting If software updates are not available on the distribution point in current, neighbor, or site groups, download content from Microsoft Update is selected for the deployment.
  When these conditions are met, the failure occurs because the software update files are named incorrectly when they have been copied to the client. Additionally, an error resembling the following is recorded in the WUAHandler.log file on the client: Failed to download updates to the WUAgent datastore. Error = 0x80240031
• Content distribution to Configuration Manager version 1702 clients fails if the SMS Agent Host service or the computer is restarted while a required file is being downloaded; that file will not be available after the restart. Additionally, the corresponding Background Intelligent Transfer Service (BITS) directory is removed. This prevents the job from retrying. Additionally, errors resembling the following are recorded in the DataTransferService.log file: CDTSJob::HandleErrors: DTS Job ‘{job_guid}’ BITS Job ‘{bits_job_guid}’ under user ‘S-1-5-18’ OldErrorCount 0 NewErrorCount 5 ErrorCode 0x80070003

This hotfix is available for download from the Microsoft Download Center:

Download this hotfix now.

To use the update registration tool

1. On the computer that hosts the service connection point:
   • Open a command prompt with administrative privileges, and then change directories to the location that contains <Product>-<product version>-<KB article ID>-ConfigMgr.Update.exe
2. Run the following command to start the update registration tool:
   • <Product>-<product version>-<KB article ID>-ConfigMgr.Update.exe
   • Open the Configuration Manager console and go to Administration > Updates and Servicing, and then click Check for Updates. (Prior to version 1702, Updates and Servicing was under Administration\Cloud Services.)
   After the hotfix is registered, it appears as a new update in the console within 24 hours. You can accelerate the process: The update registration tool logs its actions to a .log file on the local computer. The log file has the same name as the hotfix .exe file and is written to the %SystemRoot%/Temp folder. After the update is registered, you can close the update registration tool.
3. Open the Configuration Manager console and navigate to Administration\Updates and Servicing. Hotfixes that were imported are now available to install. (Prior to version 1702, Updates and Servicing was under Administration\Cloud Services.)