![]() This is known to produce this particular error with even the newest TW builds. Host PC is in standby mode – Another possible reason why this issue occurs is that the host pc is currently in standby mode with the screen turned off. ![]() In this case, disabling the conflicting process should resolve the issue. As it turns out, this occurs because both applications will request access to some settings related to the wallpaper. A process is conflicting with TeamViewer – BGInfo (a process belonging to SysInternals) is known to trigger the “Initiating Display Parameters” hang by conflicting with the TW app.If this is applicable, you can revert this setting by taking a trip to the System Properties screen. The PC is not configured for remote control – It’s also possible that TeamViewer doesn’t have the necessary permissions because your computer is not configured to allow remote control access.If this scenario is applicable, you will be able to resolve it by reinstalling TeamViewer with Unattended Remote Access. Unnatended Remove Access is not configured – This error might also occur if the TeamViewer client is not configured to allow connections if someone is not logged in.This is typically reported to be effective in those cases where one of the machines is dealing with an unstable network connection. Display Quality is set to Optimize Quality – Several affected users have reported that the issue was resolved as soon as they changed the Display quality to Optimize Speed.Several users have reported that the connection was initiating without errors once they disabled Remove Remote Wallpaper from the Options menu. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |