[Sync as a service account problem]

4 hours ago, Andy+ said:

Seems also for me, is a bug, but I´m not purely sure. Since in all the past years, it was never a problem. New installation, updates, it runs. Also now on all my computers is v2.7.1 installed. But at timepoint of the updates on all was W10 build 1909 installed and after the Resilio update from v2.6.4 to v2.7.1 the Windows updates installes build 2004. It seems for me, that the problem have also a relation to that build 2004.

It is definitely a bug, confirmed by Resilio support team. The bug is independent on Windows version or build, it is there not only for Windows 10 various builds, but also for Windows Server installations. See my recent posted feedback from support team above.

[Sync as a service account problem]

I have contacted Resilio support for solving this issue. The solution is quite simple but not obvious. See Daria's feedback in this threat, she is with Resilio support center.

 

[Sync as a service account problem]

I face the same issue on Windows Server 2016. Installation as a service is running well with V2.6.3. But with V2.7.1 none of the credentials work at the installation process, neither any of the user accounts nor the "local system" and "local service" accounts. The installation always fails saying either username or password are invalid. No chance to jump over this point. No chance to get this update installed as a service. Seems to be an incorporated issue of the current install file V.2.7.1.1370. It is independent on the Windows version obviously. Resilio moderators, can you please comment?