The fix we released soon after hearing about the first report (which is in Bootstrap version 166 and up) is to delete only the folders that the Launcher knows about, under the Dungeons install location. So the bug would only impact players who had selected a custom install location for Dungeons where other program files also exist, then tried to uninstall the Dungeons Launcher. And unfortunately, we didn't catch that in tests. We didn't consider that the custom location chosen by players could also have files belonging to other programs in it. Thus, when uninstalling the Launcher, the uninstall logic would simply delete that "Install Location" folder, to leave no traces of program files created by the Launcher on disk. When a player selected a custom "Install Location" in the Dungeons installation dialog, the Dungeons Launcher was taking that location and naively considering that only files written by the Dungeons Launcher would live there. So I'd like to clarify what the bug was about in more detail, and what is the fix we released within around 30 minutes after hearing the first report:
I've been reading online that this bug was causing entire disks to be wiped out, which was not necessarily the case.
0 kommentar(er)
