Windows 10: Delay for fist packet on socket for Windows version 1803 build 17134.1

Observing that the first packet on a new socket connection does not reach the application immediately. There is a delay of 11-19 seconds.


Detected this problem when my application stated timing out. Then wrote a simple client server program and observed the same behavior there.

Used wireshark to observed whats happening. From wireshark, it seems the message is transmitted and ACK is sent back immediately. However, the message is not delivered to server app. Server app receives the same message after a delay of 11-19 seconds.


One more observation is, if the client closes the connection immediately after sending the message, server also receives the message immediately.


1- Want to know if this is a known issue?

2 - Anyone else facing this issue or can confirm the root cause.





:)

 

Delay Windows 10 Updates for up to One Year Version 1803 Build 1734?


In some of the older versions of Windows 10 pro/enterprise, you could delay feature updates (specifically disabling feature updates while still getting security updates) in the advanced options of update settings. However, I am on version 1803 Build 17134 right now, and I no longer see this option; I only see the option to "pause" all updates for 35 days.
How can you delay feature updates for up to a year on Windows 10 Version 1803 Build 17134?

 

Should stay Version 1803 build 17133.1 or Go Version 1803 build 17134¿

A serious bug was found in Windows 10 17133 forcing Microsoft to discard it and replace it with Windows 10 build 17134.

You will have to upgrade to it, since Microsoft will not be supporting build 17133 with updates.

 

Should stay Version 1803 build 17133.1 or Go Version 1803 build 17134¿

guys give me some reason to stay or to update "now" on 17134. Your opinion and suggestion are going to be helpful to me