System center can not install update 2509 or 2603

For Configuration Manager 2509 or 2603 in-console updates that get through prerequisite checks and database upgrade but fail during file copy, the supported troubleshooting path in the available guidance is to verify whether the required update files are missing or not fully replicated.

1. In the Configuration Manager console, go to Administration > Updates and Servicing and confirm the update is fully downloaded and shows Available.
   • If it stays at Downloading or does not progress correctly, review hman.log and dmpdownloader.log.
   • If dmpdownloader.log shows the downloader is waiting before checking again, restart the SMS_Executive service on the site server to restart download of the update redistribution files.
   • Also verify proxy settings are not blocking downloads from the required internet endpoints.
2. If the environment uses an offline service connection point, use the service connection tool to download and import the update files again.
   • While it runs, review ServiceConnectionTool.log and ConfigMgrSetup.log to confirm the required files download successfully.
   • After download completes, verify the files exist under EasySetupPayload\Offline*PackageGuid\Redists*.
3. If the files exist in EasySetupPayload but are missing from CMUStaging, retrigger update content replication from a PowerShell command prompt on a server hosting the SMS Provider role for the top-level site:

(Get-WmiObject -Namespace "ROOT\SMS\site_<SiteCode>" -Query "select * from SMS_CM_UpdatePackages where PackageGuid = '<PackageGuid>'").RetryContentReplication($true)

• Replace <SiteCode> with the site identifier and <PackageGuid> with the update package GUID.
• After replication finishes, retry the in-console update.
• Warning: run the cmdlet only with the correct site code and package GUID, because it targets update package replication for the site.

4. Since the update already passes prerequisite checks in the reported environment, run the next validation specifically around update payload handling rather than rerunning prerequisites:
   • Check whether the update package content is present in EasySetupPayload.
   • Check whether the same content is present in CMUStaging.
   • If not, use the replication retry step above.
5. If the update package is not appearing correctly or download behavior is inconsistent, confirm the service connection point at the top-level site is functioning correctly, because 2509 and 2603 updates require it to obtain the in-console update package.

This is the most direct supported path from the available guidance for failures during the file-copy stage of 2509 or 2603 installation.

• Checklist for installing update 2509 for Configuration Manager
• Checklist for installing update 2603 for Configuration Manager
• Configuration Manager in-console update fails at the Install Files stage because required files are missing
• Checklist for installing update 2503 for Configuration Manager