I have a very simple Task Sequence to capture my Windows 7 Enterprise x64 reference image. 1. Partition & Format Disk 2. Installs Windows 7 Enterprise x64 3. Configure Network - Workgroup 4. Configure Windows & ConfigMgr Client 5. Install Software 6. Install Software Updates - All Software Updates 7. Sysprep 8. Capture Image The client checks and scans for missing updates (ScanAgent.log) against the available updates and finds a heap of them (UpdatesStore.log). It then proceeds to download them (DataTransferService.log) to the CCM Cache. The problem is that the "Downloading Software Updates" progress indicator gets stuck at 0%. All the logs are normal with no errors at all! I cannot find any error to say that there is an issue downloading an update, it is as though the updates were downloaded by the client is unaware and is still waiting for a download complete notification. Leaving the client alone overnight does not time out either. I've also looked at UpdatesDeployment.log, WUAHandler.log, etc. There are about 60 updates but I can only find 50 directories in the cache folder. Weird thing is, if I were to do a "New OS" deployment from a Task Sequence, the software updates download and installs without any issue. Because I am unable to find any errors in any logs, I have run out of ideas on what may be causing this to occur. This is a mixed mode environment and I have tried it with the machine joined to the domain and in a workgroup. The ConfigMgr client has also been configured with SMSMP, SMSFSP and SMSSLP. The Install Software Updates step is also done after installing the latest Windows Update agent 7.4. Please help...

if you disable any apply drivers package step does it work then ? (there have been many postings recently about chipset drivers causing this problem...) if drivers are not applicable to your problem, do you have any proxy setup ? My step by step SCCM Guides I'm on Twitter > ncbrady

I got a similar problem: http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/1a181785-318b-448b-a65d-b41f5e2fbd10 Did you check your WindowsUpdate.Log at the captured client?