Recently it was in the news for problems with the Fit as a Fiddle achievement and the fact that users were being stuck in an elevator in Houndfield Electrical Station. While the dust was about to settle down, a new one has already made its way. Various users have voiced their concern that they are unable to get their hands on the Don Quixote trophy. This is happening in spite of the fact that they have check-marked the prerequisite of activating the 17 windmills.
Along with that, some users have also reported issues with two other trophies namely Municipal Services (which you get after assigning all facilities), Ban Hammer (that you get after clearing all bandit camps). So all this begs for an important question- how to fix the issue of being unable to get the Don Quixote trophy in the Dying Light 2? Well, there does exist a workaround that has spelled out success for some users. So without any further ado, let’s check out that method.
How to Fix Cannot Get Don Quixote Trophy in Dying Light 2
Do note that this workaround doesn’t come with a relatively high degree of success. While it has worked for some, a few were still facing this issue even after trying out the below steps. But since this is the only workaround that we have in your hands, it is worth a try. So what you need to do is back up the save file to an external device and then uninstall the game from your console. After that, reinstall the game and import that save game file back to your console. Check if it resolves the underlying issue or not. If we talk about the Play Station console, then you will have to go to Application Data Management in the Settings menu. After that, backup your latest version to the cloud and or exFAT USB storage. Then you delete the game and download it again from the PlayStation store. Check if it rectifies the problem or not.
So with this, we round off the guide on how you could fix the issue of being unable to get the Don Quixote Trophy in Dying Light 2. 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.