This fix a bug I got when I decided to move my VM to a symlink.
It doesn't hurt if we check both paths, it seems that at some point VMWare returned resolved sym-linked paths, but now it doesn't do it anymore and return the path its registered on the config.
Description
This fix a bug I got when I decided to move my VM to a symlink. It doesn't hurt if we check both paths, it seems that at some point VMWare returned resolved sym-linked paths, but now it doesn't do it anymore and return the path its registered on the config.
Related issue(s)
Problem after I moved to a symlink.
After the fix