The -u in wineboot stands for update. So it will update your current wine prefix if a newer one (or different i guess) is installed. It should also restore any wine dll's that are missing which is why you must delete the dxvk ones first as it won't touch the replaced dll's. If it did it would also screw with any other dll's replaced with native Windows versions trough winetricks as an example.
why you must delete the dxvk ones first as it won't touch the replaced dll's
Thanks!
Note that it also doesn't touch the dll overrides so those also have to be removed. Which can be done through winecfg or through CLI by editing the wine registry
i don't know, this is self-explanitory.
after setting the DLL overrides with
WINEDLLOVERRIDES, and installing the DLLs into the correct directory, testing a application, restoring DLLS withwineboot -u, but dxvk is still there.is this a design decision? does 'restoring DLLs' not remove the original overridden dlls?