Office Settings & Configuration

Fix the Digital Signature Timestamp Server Error in Office 2010

Algirdas JasaitisAlgirdas Jasaitis Nov 20, 2026 868 views

Question details

Office 2010 users need to resolve an error when adding a timestamp to a digital signature.

Fix the Digital Signature Timestamp Server Error in Office 2010
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.
Before you start

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.

Solution 1Recommended

Restore the Complete Timestamp Server URL in Group Policy

Use this solution when the configured timestamp server address is missing its protocol prefix.

1
Find the applied policy

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.

2
Check the server address

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.

3
Correct the policy value

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.

4
Apply the policy and restart

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.

5
Test the signature

Open the document in Office 2010 and add its digital signature again. Check whether the signature is created without the timestamp error.

Restore the Complete Timestamp Server URL in Group Policy
Use the current server address: The URL above is from the reported case, not a guarantee that the service remains available. Use the address and protocol provided by your current timestamp service.
Free Microsoft Office alternative

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.

Open and edit Microsoft Office formats including DOCX, XLSX, and PPTXUse a familiar interface for everyday document, spreadsheet, and presentation workMove existing Office files into a lightweight suite without recreating themContinue document work in an alternative suite while an administrator investigates the Office 2010 timestamp setting
microsoft office alternative - wps office

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.