SharePoint SE: "Copy to" functionality failing after the April 2026 Cumulative Update

Question

The "Copy to" and "Move to" features have completely stopped working across different site collections. 

Even for users with Full Control permission, the operation hangs at 0% before throwing a generic "The file could not be moved" error, which usually points to an underlying OAuth or App-Only policy failure in the latest April 2026 build.

Answer 1

Hi Wang Jun Kai

Because these modern features rely heavily on background OAuth and App-Only principals, the CU likely caused a temporary disconnect or cached a stale STS configuration.

Please perform the following steps on your SharePoint server:

• Open the SharePoint Management Shell as an Administrator and run the following PowerShell commands to refresh the STS service principal:

$sts = Get-SPSecurityTokenServiceConfig
$sts.RefreshServicePrincipal = $true
$sts.Update()

• Once the script completes, flush the web server connections by running:

iisreset

(Note: If you have a multi-server farm, please runiisreset on all other SharePoint servers in the farm as well so they pick up the refreshed token configuration).

Once the servers are back up, please test the "Copy to" / "Move to" functionality again and let me know if it resolves the issue.

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.