Microsoft's recent Windows 11 23H2 Moment 4 update, launched last week, introduced an array of new features, with a unified AI Copilot being one of the highlights. However, the aftermath of the update unveils a conflict with AMD graphics cards. Reports suggest that AMD users' overclocking profiles and tunings saved on drivers are being erased after rebooting the system, providing an unexpected impediment to users.
Copilot Unavailable in EU Due to Digital Markets Act
The Copilot feature was not brought to Europe amid the rollout of a fresh Digital Markets Act (DMA) policy. However, the issue that AMD graphics cards users are experiencing may be an unintended positive for European users, given the software is thus far inaccessible in the region. As a silver lining, it has been noticed that this issue is specifically linked with the latest AMD Adrenalin 23.9.3 beta driver. Expectations run high for this problem to be resolved in the next WHQL-signed version.
Workaround Discovered to Circumvent The Issue
A workaround by an AMD community forum user, rawintellect, has been discovered to bypass the glitch. The user suggested using the command-line tool vivetool to disable the Copilot feature, which, according to several user experiences, seems to be the cause of the problem. The following command can be issued from PowerShell or Command Prompt as an administrator for this purpose:
./vivetool /disable /id:44774629,44776738,44850061,42105254,41655236
Alternatively, disabling Copilot through the Group Policy Editor or the Registry Editor also appears to address the profile reset issue. Users should approach these solutions with caution as hasty attempts may lead to unintended consequences.
Previous Windows Updates Also Known to Overwrite GPU Drivers
This is not the first instance of a Windows update causing such glitches. Past updates have been noted to overwrite GPU drivers installed by users, both AMD and Nvidia. A Group Policy edit can serve as a preventive measure against such automatic overwrites. Microsoft is anticipated to troubleshoot these issues and provide a robust solution in its next feature update. As the driver team is currently occupied with the upcoming 23H2 feature compatibility, it remains uncertain when the glitch will be rectified.