Fix the Digital Signature Timestamp Server Error in Office 2010
Question details
Office 2010 users need to resolve an error when adding a timestamp to a digital signature.

- Product
- Microsoft Office 2010
- Device & OS
- not provided
- Scenario
- A user signs an Office document using a timestamp server configured through Group Policy.
- Observed behavior
- Office 2010 reports that a timestamp cannot be added, while Office 2013 and Microsoft 365 work with the same server.
Check which timestamp server URL Office 2010 is configured to use, and confirm that you have permission to edit the applicable Group Policy. If the computer is managed by your organization, ask your administrator to verify the policy.
Restore the Complete Timestamp Server URL in Group Policy
Use this solution when the configured timestamp server address is missing its protocol prefix.
Open Command Prompt and run gpresult /r to identify the Group Policy objects applied to the computer or user. Ask your administrator to check the relevant Office 2010 digital signature timestamp server setting in Group Policy Management.
Open the timestamp server policy setting and inspect its URL. Include the complete protocol prefix, such as http:// or https://, as specified by the timestamp service provider.
Enter the complete, provider-approved URL and save the policy. In the reported case, the missing prefix was restored to make the address http://sha256timestamp.ws.symantec.com/sha256/timestamp; verify that this historical endpoint is still supported before using it.
Run gpupdate /force in Command Prompt, then restart the computer. Open the policy setting again or ask your administrator to confirm that the corrected value remains in effect.
Open the document in Office 2010 and add its digital signature again. Check whether the signature is created without the timestamp error.

Work with Office Documents in WPS Office
WPS Office is a free, lightweight alternative with a familiar interface and Microsoft Office format support, making it easier to move everyday document work to another office suite. It does not repair Office 2010's timestamp server policy.

Frequently Asked Questions
Why does the timestamp work in newer Office versions but fail in Office 2010?
Office versions can behave differently when processing a server address. In the reported case, the Office 2010 Group Policy URL was missing http://. Check the complete configured URL before assuming the server itself is unavailable.
Why did my registry change revert after a restart?
Group Policy may have reapplied the configured value. Run gpresult /r in Command Prompt to identify applied policies, then have an administrator correct the timestamp server setting in the responsible Group Policy object.
Do I have to use the Symantec timestamp URL shown here?
No. That address is the historical value from the reported case. Use the complete URL supplied by your current timestamp service provider and verify that the endpoint is supported.
What should I check if the complete URL does not fix the error?
Confirm that the corrected policy is still applied after restarting, and check with your timestamp service provider that the endpoint is available and supports your signing setup. Office 2010 is out of support, so consider upgrading to a supported Office version.




