You must have installed the CWDIllegalInDllSearch utility prior to using FixIt. In addition to this, if you installed the workaround suggested by Microsoft, you can now use the Microsoft FixIt Tool to further refine settings. I highly recommend looking at that page & implement the workaround (in conjunction with other suggested workarounds, such as disabling Webclient service, blocking outbound smb traffic, blocking propfind method on proxy servers, etc)

You can use the list below to build a GPO / custom adm file /.reg file, and alter the default dll loading behaviour for those applications, as explained here. (after all, if you have to replace a dll, you might as well replace the executable itself)

I do not consider those examples to be valid cases of dll hijacking. Please note that I will not list instances where you have to replace a dll in the application folders. If you have found other applications to be vulnerable and want to add them to the list, send me a mail. Note that I did not test these applications myself. This page hosts an unofficial list of applications that are said to be vulnerable to the dll hijacking flaw (or feature or whatever you want to call it).

Winmerge 2.12.4 setup