In this guide, we will show the steps to fix the inability to install Nvidia Driver update v531.18. Whether you own a GeForce, TITAN, or RTX, you must also have its associated software installed on your PC. However, that is currently proving to be easier said than done, especially for those set of users who have recently installed the March update. According to the affected users, they are unable to install Nvidia Driver update v531.18 or v531.29.
When they are try to do so, they are greeted with the ‘Installation can’t continue an error has occurred’ error. On the other hand, some users did manage to install it, but their PC is unable to identify it and hence is continually reminding them to reinstall those drivers. Some have even said that their PC is flickering after every few seconds right after they had installed this driver version. If you are in a similar position, then this guide will help you fix this bug. Follow along.
Table of Contents
Fix Cannot Install Nvidia Driver update v531.18
It is recommended that you try out each of the below-mentioned workarounds and then see which one spells out success. So with that in mind, let’s get started.
FIX 1: Uninstall Drivers via DDU and Reinstall Nvidia Drivers
- To begin with, download the latest Nvidia Driver v531.18.
- Then download and install the Display Driver Uninstaller.
- Now turn off the internet on your PC [turn on Airplane Mode].
- Then launch DDU and select NVIDIA Software and drivers.
- After that, select Clean and restart your PC.
- Now install Nvidia Driver by selecting Custom > Clean Install.
- Once done, restart your PC and then connect to the internet.
FIX 2: Downgrade Nvidia Drivers
You could also downgrade the driver to its earlier stable version which is free from this bug. To do so, please check out our guide on How to Downgrade/Rollback Nvidia GPU Drivers on Windows 11.
That’s it. Either of the two methods should fix the inability to install Nvidia Driver update v531.18. As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned workarounds are your best bet.
