Samsung SSD 850 EVO 250GB SATA Device (250 GB, SATA-III)
Internet Speed
VDSL 50 Mbps
Browser
MICROSOFT EDGE
Antivirus
WINDOWS DEFENDER
Other Info
Legacy MBR installation, no TPM, no Secure Boot, no WDDM 2.0 graphics drivers, no SSE4.2, cannot get more unsupported ;) This is only my test laptop. I had installed Windows 11 here before upgrading my main PC. For my main PC I use everyday see my 2nd system specs.
The worst bug so far, has been since sometime with Windows 7, which carried on to 10 and possibly 11 as well, where network discovery is hung when getting a DHCP lease. That's an old bug.
That's the dreaded "hanging at "Identifying" bug". Where I possibly could be connected already with 56K, for the time it hangs just for Ethernet to become ready!
That's the dreaded "hanging at "Identifying" bug". Where I possibly could be connected already with 56K, for the time it hangs just for Ethernet to become ready!
In that case you should first connect the LAN cable and then dialup to connect via your 56K modem. In Greek we say "When many roosters are yelling it takes more time to dawn" when something goes wrong due to many attempting to do it each one in his own different way. In your case the computer hangs because the LAN is trying to establish an internet connection while you are already connected via 56K modem and there is a DHCP and DNS conflict as a result.
Samsung SSD 850 EVO 250GB SATA Device (250 GB, SATA-III)
Internet Speed
VDSL 50 Mbps
Browser
MICROSOFT EDGE
Antivirus
WINDOWS DEFENDER
Other Info
Legacy MBR installation, no TPM, no Secure Boot, no WDDM 2.0 graphics drivers, no SSE4.2, cannot get more unsupported ;) This is only my test laptop. I had installed Windows 11 here before upgrading my main PC. For my main PC I use everyday see my 2nd system specs.
It's just the networking components that hang. I can still use Windows. It seems to be an ongoing thing since some update many moons ago, when I was still using Windows 7. But that issue also occurs with Windows 10 and Windows 11.
