I recently posted about an obvious bug in the Windows 10 DHCP client, showing with Wireshark captures that it is not resilient to hardware clock changes, i.e., you easily lose your IP address for hours.
Most of the responses either said, “you should not be dual booting Linux” or “there is no DHCP client that handles this case. You cannot expect Windows to handle it.”
So I replied with a link to a similar bug report for RHEL, which has been fixed.
It’s been a month since I posted this bug to the Windows Feedback Hub and there is no response. I doubt it will ever be fixed.
Yup. It even extends to superuser.com.
I recently posted about an obvious bug in the Windows 10 DHCP client, showing with Wireshark captures that it is not resilient to hardware clock changes, i.e., you easily lose your IP address for hours.
Most of the responses either said, “you should not be dual booting Linux” or “there is no DHCP client that handles this case. You cannot expect Windows to handle it.”
So I replied with a link to a similar bug report for RHEL, which has been fixed.
It’s been a month since I posted this bug to the Windows Feedback Hub and there is no response. I doubt it will ever be fixed.