Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, May 22, 2020 8:54 PM
I'm running March 2019 ltsc 1089 and for God knows what reason WU always tries to reach update endpoint s with some proxy setup despite the fact it is stock install
I double checked every default system proxy setting and they all disabled. Needless to say my network works just fine via DHPC setup on a router.
The funny thing if I specify working proxy system-wide --Update can connect to the servers just fine.
Exported log from the event system just has few entries about proxy not responding when it tries to reach WU endpoint. Any idea where can I reset that proxy?
All replies (8)
Saturday, May 23, 2020 12:32 PM
Here is the log:2020/05/22 23:14:28.9211181 5724 6212 ProtocolTalker ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
2020/05/22 23:14:28.9211197 5724 6212 ProtocolTalker OK to reuse existing configuration
2020/05/22 23:14:28.9211227 5724 6212 ProtocolTalker Existing cookie is valid, just use it
2020/05/22 23:14:28.9211359 5724 6212 IdleTimer WU operation (CAgentProtocolTalker::StartCategoryScan_WithRecovery) started; operation # 80; does use network; is at background priority
2020/05/22 23:14:28.9211724 5724 6212 WebServices Auto proxy settings for this web service call.
2020/05/22 23:14:28.9243979 5724 6212 WebServices WS error: There was an error communicating with the endpoint at 'https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx'.
2020/05/22 23:14:28.9243996 5724 6212 WebServices WS error: The given proxy cannot be reached.
2020/05/22 23:14:28.9244459 5724 6212 WebServices *FAILED* [80240438] Web service call
2020/05/22 23:14:28.9244471 5724 6212 WebServices Current service auth scheme=0.
2020/05/22 23:14:28.9244478 5724 6212 WebServices Current Proxy auth scheme=0.
2020/05/22 23:14:30.9381836 5724 6212 WebServices Auto proxy settings for this web service call.
2020/05/22 23:14:30.9446547 5724 6212 WebServices WS error: There was an error communicating with the endpoint at 'https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx'.
2020/05/22 23:14:30.9446585 5724 6212 WebServices WS error: The given proxy cannot be reached.
2020/05/22 23:14:30.9447756 5724 6212 WebServices *FAILED* [80240438] Web service call
2020/05/22 23:14:30.9447781 5724 6212 WebServices Current service auth scheme=0.
2020/05/22 23:14:30.9447799 5724 6212 WebServices Current Proxy auth scheme=0.
2020/05/22 23:14:32.9579492 5724 6212 WebServices Auto proxy settings for this web service call.
2020/05/22 23:14:32.9641835 5724 6212 WebServices WS error: There was an error communicating with the endpoint at 'https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx'.
2020/05/22 23:14:32.9641871 5724 6212 WebServices WS error: The given proxy cannot be reached.
2020/05/22 23:14:32.9643126 5724 6212 WebServices *FAILED* [80240438] Web service call
2020/05/22 23:14:32.9643155 5724 6212 WebServices Current service auth scheme=0.
2020/05/22 23:14:32.9643173 5724 6212 WebServices Current Proxy auth scheme=0.
2020/05/22 23:14:32.9643288 5724 6212 ProtocolTalker *FAILED* [80240438] StartCategoryScan_WithRecovery failed
As you can see WebServices for some reason tries to use proxy. I would kill for knowledge where that proxy is specified.
Monday, May 25, 2020 8:09 AM
Hi,
I noticed your log file shows "There was an error communicating with the endpoint at 'https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx'.". Is it available to access https://fe2.update.microsoft.com ? Try to check firewall if you have configured any related rules to disable it.
" Please note that new questions regarding ‘Windows 10 Installation, Setup, and Deployment’ could NOT be posted in this forum anymore. This thread could be followed up until Mar-30th. We will be moving your thread to Microsoft Q&A if the deadline is missed. Register our new platform Microsoft Q&A (Preview)! for new questions or discussion. Check more details on sticky post.
Monday, May 25, 2020 11:47 PM
Hi,
I noticed your log file shows "There was an error communicating with the endpoint at 'https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx'.".
Yes, that's kinda the point - it is not available to the Updater because he tries to use some weird/unknown proxy for no less weird reason. Direct connection to the said endpoint works just fine. All my network activity is normal.
Wednesday, May 27, 2020 7:21 AM
Hi ,
Where did you configure proxy? Did you configure proxy in the IE LAN settings?
It would be helpful for us to identify your situation if you could upload the screenshots.
Best regards,
Candy
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Wednesday, May 27, 2020 3:31 PM
Hi ,
Where did you configure proxy?
Nowhere, that's the thing. I went through every proxy setting in the system and there is none. I wouldnt be making this thread is the answer was so simple.
Thursday, May 28, 2020 1:42 AM
Hi ,
>>I wouldnt be making this thread is the answer was so simple.
It's just a signature which under each reply in each post.
Based on your situation, we might need to analyze log to find why it always use some weird/unknown proxy. However, analysis of log is beyond our forum support level. If your issue is urgent, I would suggest you open a case with Microsoft Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue.
Here is the link:
https://support.microsoft.com/en-us/gp/customer-service-phone-numbers
In this way , they can have a clear picture about your issue and your environment by phone communication and live share session.
Best Regards,
Candy
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Thursday, May 28, 2020 1:49 AM
Based on your situation, we might need to analyze log to find why it always use some weird/unknown proxy.
I have no issue analyzing logs myself, problem is - WindowsUpdate log has no relevant or useful info besides these lines I've posted that indicate it uses proxy. If you can point me into the direction where can I find better logs - that's be great
Thursday, May 28, 2020 2:10 AM
Hi ,
After discussion with my colleagues, there might be no log will record proxy related information. You might need to trace network monitor to find any clues.
Best Regards,
Candy
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]