When installing Windows from an ISO on a typical Intel-based PC, the process is usually straightforward—create a bootable USB drive, install the OS, and you're good to go. However, installing Windows on an ARM-based device like the Surface Pro X is a whole different story. This is because the standard ISO files don't include the necessary drivers for ARM-based devices. Therefore, you need to manually inject drivers and take additional steps to ensure everything works smoothly. In this guide, I will walk you through the detailed steps I used to successfully install a clean version of Windows 11 on my Surface Pro X.
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.
With the increasing need to support Windows 11 ARM64 cases, I've found myself needing to run this operating system in a virtual machine (VM) through Hyper-V. Although similar, installing a Windows 11 ARM64 VM isn't quite the same as installing a 64-bit Windows version. One of the main differences is that you can't directly use an ISO file for installation. Additionally, you won't be able to enable TPM on a Windows 11 ARM64 Hyper-V. This blog post aims to guide you through the steps to successfully set up your virtual machine.