This usually happens when your Windows user account has limited permission, so it's effectively another user from the admin, which the installer must run with, otherwise it couldn't create Symlinks.
However, the latest installer was specifically updated to provide for this case, but first we need to be sure you have it, so try the Offline installer first. In theory, if it finds different users with different permissions, it should show a list of community folders founds, in case the one for the admin user doesn't exists.
