With the release of Edge based on Chromium and Edge WebView2 Runtime by Microsoft, Chromium has been playing an increasingly important role on Windows desktops. In daily work, when a user opens Outlook to send and receive emails, uses Teams for meetings, and browses the web with Edge, there are already three instances of Chromium running simultaneously on the operating system. In a corporate environment, configuring the system to use a PAC (Proxy Auto-Configuration) script can place significant request pressure on the servers hosting the PAC script in today's widespread Chromium ecosystem.
With the retirement of IE11, many Windows users find it challenging to determine the Security Zone of a URL by the traditional method of opening a webpage in IE and checking the page properties. This poses a significant inconvenience for system administrators and security analysts since Security Zones are crucial for understanding the safety of URLs and their interaction with the system's security policies.
Recently, I conducted an identification test on WiFi7 wireless network cards and encountered some intriguing issues and solutions that I'd like to share with you all. Previously, when identifying network card properties on Windows, the Win32_NetworkAdapter class was commonly used. If the returned PhysicalAdapter property is true, it signifies that the card is a physical network adapter. However, when conducting the same test on WiFi7 cards, I discovered that all the PhysicalAdapter properties returned by Win32_NetworkAdapter were false. Further research indicated that Win32_NetworkAdapter is now deprecated, with MSFT_NetAdapter class being the recommended replacement.