[2024-11-02 13:46:42] INFO Application launch.
[2024-11-02 13:46:42] DEBUG View MainViewModel has been loaded
[2024-11-02 13:47:08] ERROR System.AggregateException: Retry failed after 6 tries. Retry settings can be adjusted in ClientOptions.Retry or by configuring a custom retry policy in ClientOptions.RetryPolicy. (The requested address is not valid in its context. (homeupdater.patchmypc.com:443)) (The requested address is not valid in its context. (homeupdater.patchmypc.com:443)) (The requested address is not valid in its context. (homeupdater.patchmypc.com:443)) (The requested address is not valid in its context. (homeupdater.patchmypc.com:443)) (The requested address is not valid in its context. (homeupdater.patchmypc.com:443)) (The requested address is not valid in its context. (homeupdater.patchmypc.com:443))
---> Azure.RequestFailedException: The requested address is not valid in its context. (homeupdater.patchmypc.com:443)
---> System.Net.Http.HttpRequestException: The requested address is not valid in its context. (homeupdater.patchmypc.com:443)
---> System.Net.Sockets.SocketException (10049): The requested address is not valid in its context.
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|285_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
Quote from: Omar (Patch My PC) on November 01, 2024, 07:04:08 AMHey there,1920x1080 100%
Thank you for your feedback!
Can you please tell me what resolution are you using? and are you using a higher DPI than 100% or not?
Thank you!
Quote from: JamesRodgers on October 22, 2024, 02:48:44 PMQuote from: Raunak Desai (Patch My PC) on April 02, 2024, 01:53:24 AMHey !
Thank you for reaching out.
Certainly! The situation you described is quite common in environments where software updates are deployed through SCCM (System Center Configuration Manager).
Personaly, I don't think there is anything they can do except reboot the machines. What I can suggest is : Only give a few days restart grace period instead of 14.
You can configure SCCM to automatically schedule reboots after updates are installed. This ensures that systems are rebooted within a reasonable timeframe, minimizing the likelihood of pending reboots causing issues during software installations. And about it and more you can find info online. Here is one article about creating LXP from scratch and it may be useful for you. However, be cautious with this approach, as unexpected reboots can disrupt user workflow.
Regards,
Raunak
Hello, I'm pretty new to everything, but why 14 days are not a good option, and you offer to make this period shorter?