Today I solved my Problem with the Service Plan of my Environment, it always ended up with the following Error in the Patchdownloader.log, this Log usually reside in “C:\Program Files\SMS_CCM\Logs”:
Failed to move C:\Windows\TEMP\CABD212.tmp to \\deheim.hosebei.ch\hosebeiDFSroot\Deployment\Packages\_UpdatePackages\20160116 - Win10x64\9a30f732-4d40-4b56-b86b-8253f80868a1.1\10586.0.160212-2000.th2_refresh_CLIENTENTERPRISE_VOL_x64fre_en-us.esd, error 3 Software Updates Patch Downloader 26.03.2016 19:16:01 7780 (0x1E64)
Will retry in 5000ms Software Updates Patch Downloader 26.03.2016 19:16:01 7780 (0x1E64)
Failed to move C:\Windows\TEMP\CABD212.tmp to \\deheim.hosebei.ch\hosebeiDFSroot\Deployment\Packages\_UpdatePackages\20160116 - Win10x64\9a30f732-4d40-4b56-b86b-8253f80868a1.1\10586.0.160212-2000.th2_refresh_CLIENTENTERPRISE_VOL_x64fre_en-us.esd, error 3 Software Updates Patch Downloader 26.03.2016 19:16:06 7780 (0x1E64)
Will retry in 5000ms Software Updates Patch Downloader 26.03.2016 19:16:06 7780 (0x1E64)
Failed to move C:\Windows\TEMP\CABD212.tmp to \\deheim.hosebei.ch\hosebeiDFSroot\Deployment\Packages\_UpdatePackages\20160116 - Win10x64\9a30f732-4d40-4b56-b86b-8253f80868a1.1\10586.0.160212-2000.th2_refresh_CLIENTENTERPRISE_VOL_x64fre_en-us.esd, error 3 Software Updates Patch Downloader 26.03.2016 19:16:11 7780 (0x1E64)
ERROR: DownloadContentFiles() failed with hr=0x80070003 Software Updates Patch Downloader 26.03.2016 19:16:11 2800 (0x0AF0)
I have configured a Windows 10 Servicing Plan within System Center Configuration Manager 1602 (Current Branch), and everytime I ran the Plan, or the plan was executed based on the schedule, it ended up with the Error:
Failed to move C:\Windows\TEMP\CABD212.tmp to \\deheim.hosebei.ch\hosebeiDFSroot\Deployment\Packages\_UpdatePackages\20160116 – Win10x64\9a30f732-4d40-4b56-b86b-8253f80868a1.1\10586.0.160212-2000.th2_refresh_CLIENTENTERPRISE_VOL_x64fre_en-us.esd, error 3
and
ERROR: DownloadContentFiles() failed with hr=0x80070003
In my case, the error appeared, because my Deployment Package contained the space character twice (once might give the same error): “20160116 – Win10x64”
All other Deployment Packages does have a space character within the Package Source Path, and they are working as expected, but the servicing plan does not work with a deployment Package with a space character in the Package Source path.
Hope this helps
blog.hosebei.ch 
That’s not right at all. I’m getting exactly the same error and I don;t have any white spaces in my Deployment Package.
Have you seen the three words “In my case”? If not, I will show them to you once more “In my case”.