I have the same problem, with this error appearing for the prorgam install folder, modules folder and program data folder, when not selecting the default.
I believe this problem also shows up when upgrading from an earlier version, with a custom data folder selected. This is what I experienced - a few days ago after I accepted an upgrade from within the program Eset started throwing errors not being able to start up on boot anymore, system being unprotected, etc.
The result is that I had to uninstall Eset and now have to wait -unprotected- until a fix/patch is released (or, if this is not forthcoming, choose an alternative). My default installation location does not have enough free disk space for the programme and the data/modules, so this is not an option for me
Especially when a database update comes in, Eset seems to require a lot of extra free space for the unpacking. It would be a real life-saver if it could be configured in Eset where archives are unpacked before updating/installing (e.g. RAM-disk, temp folder, disk with sufficient free space).
