Well, after much arguing with my PC I only have to announce that this little update killed my internet. There's no reasoning with my LAN, renewed all the cables, resetted my router several times......... NA-DA. Will try what LINUX has to offer. This is a new LOW, even for MS standards.
Did you check Device Manager to see if your network card fell into the "spoofing driver" syndrome. Microsoft is disabling drivers it considers not properly signed.
JohnD
And how do I do that or check that?
1. Open Device Manager.
2. If your network device is not showing up under the "Network adapters" section, click "View" in the Menu the select "Show hidden devices".
3. Double-click your network device.
4. If it says "The device is working properly" then it is not the "spoofing driver" issue. Your network should be working ok.
5. If it says the following:
"Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)"
"Windows cannot verify the digital signature for this file. The signing certificate for this file has been revoked."
then you have been had by Microsoft trying to disable what it thinks are potentially dangerous drivers.
JohnD
The traditional tried and tested trick of updating the driver by navigating to Browse my computer for drivers > Let me pick from the list of available drivers > Choosing the related inf file should usually make the device spring back to life. How exactly this is different from the traditional install method, I haven't the faintest clue on earth. This is the only way I can continue working with my Bluetooth Mouse. We can only pray MS doesn't perform last rites on the only left workaround, if they haven't already.Code:"Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)"
How they go about dealing with this whole unsigned driver business is a complete joke on us. Spit out some funky Hex code BSOD error and leave you to fend for yourself with no recourse to a resolution on their vast Knowledge Base repository.Code:"Windows cannot verify the digital signature for this file. The signing certificate for this file has been revoked."
If we dare care to get back to the swing of things better learn some driver debugging lessons or hack into the unsigned driver and re write the part of the code which the updated Windows is taking exception to. That's their concept of protecting us from potential mal-drivers.
I am having issues with certain DNS servers. Google ones for instance.
I am now using OpenDNS with no issues. Check your network config.
OpenDNS DNS addresses:
208.67.222.222
208.67.220.220
For family protection:
208.67.222.123
208.67.220.123
For IPv6:
2620:0:ccc::2
2620:0:ccd::2
um Houston, we have various problems with KB5028166
KB5028166 is causing system issues, break Secure Channel, forces Synology to release a patch - Neowin
Isn't that sweet. Thank you Microsoft.
JohnD
Quote