Most entries will be marked info but IME with AnyDesk it’s also normal to also see a few warning entries. The trace log file can be opened in any text editor, e.g. If you are using a *portable* version of AnyDesk then you should find an ad.trace log file in the %appdata%\Roaming\AnyDesk folder, e.g.
If you’re using an *installed* version of AnyDesk then you should find an ad_svc.trace log file in the %programdata%\AnyDesk folder, e.g. during the authentication handshake with the AnyDesk relay server or once the relay server drops into monitor mode to allow direct communication between source and destination devices. It may tell you when the issue happens, e.g. This topic was modified 10 months, 2 weeks ago by glnz.ĪnyDesk includes a trace log which shows program usage and includes warnings and errors.Ĭheck the ad.trace (portable version) or ad_svc.trace (installed version) log files on both source and destination devices for errors. Those errors are all like the following: Log Name: Applicationī_config_layer - File config layer update failed. Then starting Aug 11, I start getting HUNDREDS of Event Viewer Errors for my much-loved AnyDesk.
The two new Dell Optiplex 7000s and one Precision 3660 in my wife’s mini-office have Dell Command Update, which updates quickly when updates are available – no AskWoody delay. Is it possible that the August updates to Win 10 Pro 64-bit v 21H2 are causing AnyDesk to go kablooey?
0 kommentar(er)
