ContributionsMost RecentMost LikesSolutionsRe: Remote unattended stopped working as of W10 2004! Sorry, it had not been my intention to take the thread off-topic. Since this isn't a very active forum and it had been three weeks since your post, I thought I'd add to it rather than create a new one in case there was an overlap in our issues. In terms of log files, when I run the .exe version of the unattended installer (downloaded from the console) on a client machine, it generates a file in the same directory called something like UnattendedUpdater.txt. For me, this was useful in determining that the installation hadn't actually been successful because a previous instance was running. Again, I'm not posting this to hijack the thread; rather, I'm hoping that if you also are seeing this error in the log, my suggestion for a "clean" install might help you. Re: Remote unattended stopped working as of W10 2004! I'll be glad to do that once I know which files to provide and where they're located. Should I get in touch with Customer Support directly to find out? Re: Remote unattended stopped working as of W10 2004! I have customers on Windows 10 version 2004 with unattended support working as expected. On the other hand, now and again a customer will appear offline in the console, and having them restart Windows doesn't help. When I try to reinstall the unattended client, it fails with the log file saying it couldn't delete a folder. For want of a better method, I've been fixing this by terminating the processes, deleting the LogMeIn unattended folder from Program Files, then reinstalling the client. This is definitely a recent issue for me, but not limited to 2004.