Group Policy processing failed: Unable to apply Folders, Files, Services, Registry settings

I'm encountering multiple Group Policy application issues when running a policy update on a domain-joined computer. The output message shows that computer policy updated successfully, but with warnings and errors in applying specific settings. Here is the exact message:

Computer Policy update has completed successfully.  The following warnings were encountered during computer policy processing:  Windows failed to apply the Group Policy Folders settings. Group Policy Folders settings might have its own log file. Please click on the "More information" link. Windows failed to apply the Group Policy Files settings. Group Policy Files settings might have its own log file. Please click on the "More information" link. Windows failed to apply the Group Policy Services settings. Group Policy Services settings might have its own log file. Please click on the "More information" link. Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.  User Policy could not be updated successfully. The following errors were encountered:  The processing of Group Policy failed. Windows attempted to read the file \\altaiholding.com\SysVol\******\Policies\{9BE363D8-E7C0-45E0-80E9-F113539FCC12}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled. 

So far I have:

Verified network connectivity to the DC

Ensured DNS resolution is working

Checked SYSVOL is accessible manually

Verified DFS client service is running

What else can I check to resolve this issue? Could it be related to replication issues or permissions?