All Activity

A second-hand Surface Pro X has completely changed my perspective on ARM64 and the future of Windows on ARM. Having the privilege to work in technology journalism gives me regular access to the latest laptops and PC components, which can be a blessing and a curse. On the positive side, I have hands-on insights with an incredible range of devices, from the ultra-budget to the ridiculously expensive. Plus, not everything on the high-end guarantees satisfaction, as it's easy to become bored with excess once your personal budget isn't involved. My colleagues with significantly more brand-specific insight and knowledge have covered Microsoft's most extravagant and secretive Surface devices, and I'm starting to understand why they're so exciting. After all, taking advantage of everything Windows 11 offers practically requires a laptop, and who should know better how to build the perfect Windows laptop than Microsoft? Besides Xbox consoles and a Lumia Windows Phone, I'd never tried first-party hardware from the company, and the lofty costs were the primary reason I passed. However, although I've had the pleasure of going hands-on with stellar laptops like Lenovo's Slim Pro 9i, rating it as being as close to perfect as possible, I'd never tried any computer with an ARM processor. Rather than settle for an ultra-budget option from the modern era, I set my sights on a second-hand Surface Pro X featuring Microsoft's four-year-old SQ1 ARM chip. Microsoft's first Windows on ARM offering It might be a few years behind Microsoft's Surface Pro 9, but the Pro X still looks sleek and modern. (Image credit: Daniel Rubino | Windows Central) Technically, the Microsoft SQ1 processor was a modified version of Qualcomm's Snapdragon 8cx ARM chip. Still, it was the first customized ARM64-based CPU the company commissioned for its Surface devices, starting with the Surface Pro X. Luckily for me, its age and position behind two ARM successors, the aptly named SQ2 and SQ3, helped bring the cost down, as I found a pre-owned unit in phenomenal condition for only £280 GBP, converting to around $350. That bargain price excludes accessories, as expected, but I'm not complaining. Considering the launch price for the Surface Pro X alone was $999, picking one up for less than half the price feels like an absolute win, even if it doesn't include a Surface Pro Signature Keyboard or compatible Type Cover. Microsoft's pricing habits quickly became apparent when I realized the hands-on experience needed a keyboard and touchpad to feel complete, and, sadly, the market wasn't so kind to official peripherals. A $30 knock-off will suffice, connected via Bluetooth and featuring one of the worst typing experiences (I'm not a keyboard snob, I swear) I've ever had, but it works. The state of ARM-native apps (and if I care) Spotify, Slack, Adobe Photoshop, and Vivaldi browser running on a Surface Pro X don't feel functionally different from desktop x86-64 apps. (Image credit: Ben Wilson | Windows Central) As a tech professional surrounded by the best and worst of practically every category, I've dabbled in various platforms and more Linux distros than I can count. Compatibility is the primary reason that keeps me returning to Windows 11, as everything works as expected without a need to fiddle with custom executable launch options or tinker with flags in config files. I'll admit that I knew little about Windows on ARM before picking up a Surface Pro X, and a small amount of research shows that I held many of the same misconceptions as many others. Windows Central has enthusiastically covered ARM-based Surface devices for a while, and the slew of content helps educate me on a topic I'd previously, and tragically, dismissed. With the imminent arrival of Qualcomm's latest blockbuster Snapdragon X Elite ARM processor and the incredible performance it promises for portable PCs, the timing couldn't be better to determine how my daily routine is (if at all) affected by any forced emulation of traditional x86-64 apps. Native apps are a bonus, but how much could I expect modern developers to care about ARM64? Can I complete a full working day on an ARM device? Almost everything is a PWA these days Carrying the Surface Pro X to any room with or without the keyboard makes idle browsing much more comfortable. (Image credit: Ben Wilson | Windows Central) Digging into the stock apps with a fresh install of Windows 11, I was pleasantly surprised to see a healthy amount of ARM-native versions running in Task Manager. However, after testing Progressive Web Apps (PWAs), I knew I'd be ditching native Windows apps for these lightweight alternatives. PWAs are self-contained web versions of apps that behave like regular desktop software and are generally nearly identical in the overall experience. Knowing I had 7.5 of usable RAM out of the 8GB built into my Surface Pro X, optimizing memory use to extend battery life away from my desk was a priority. Since the Vivaldi web browser came to ARM for testing and its developers hooked me up with a fix for PWA-related crashes (you can download the tech preview here), I switched away from Microsoft Edge to save ~200MB of RAM on average. With access to emails, the Windows Central backend, and Google Sheets covered by the browser, I only need a handful of other apps to complete my arsenal of daily drivers. Adobe supports Photoshop and Lightroom natively on ARM, even though I've never dabbled in the latter, and most of my basic cropping or color correction needs are filled by installing the web version of Photoshop as a PWA. Slack, Telegram, and Discord all function perfectly as web apps and cover instant messaging, with a Spotify ARM app or PWA variant providing a soundtrack to my working day. Will my next laptop run on ARM? The next Surface Pro and Surface Laptop variants will feature ARM processors, and I can't wait to see them. (Image credit: Windows Central) I have two separate Windows 11 experiences in my life. For one, my custom-made desktop PC is geared for gaming first, and everything else is consequential. I pick up affordable graphics cards and pair them with as much RAM as possible to extend the collective component lifespan before eventually upgrading the motherboard with a new processor socket. However, sitting at a desk all day isn't my idea of a good time, so I prefer a comfortable laptop to cover my workload and daily downtime spent browsing the web and consuming other media. That's not to say I don't enjoy light gaming on a laptop. I'll regularly dip into my retro catalog and play titles better suited to a mouse than even a Steam Deck could translate, like the original Fallout or Rollercoaster Tycoon. Still, I'm a realist with integrated graphics and don't expect the same performance as a gaming laptop, despite some incredible advancements in AMD's Radeon 760M and 780M alongside Intel's Arc mobile graphics. However, battery life and a convenient design come first for me when choosing a laptop, and the upcoming Surface Pro 10 could be my new temptation. Microsoft's Surface Pro range isn't famous for affordability, and its ARM variants are the most expensive of all. A more realistic option will likely feature Qualcomm's Snapdragon X Plus platform, a step down from its upcoming high-end X Elite ARM64 processors, set to appear in a massive variety of branded OEMs. Whether I end up with Lenovo or Dell or stick with a Surface device, one thing is for sure: I won't buy a new PC until I see what Windows on ARM has to offer in this exciting next generation of game-changing hardware. Source

Valinet, the maker of ExplorerPatcher, a popular app for tweaking the UI in Windows, has released an update under version 22621.3527.65.1. This version brings one important change: it no longer allows reverting to the old Windows 10 taskbar on systems with Windows 11 version 24H2 and its early builds (build 26002 and hither). Here is the changelog for the latest version: ExplorerPatcher 22621.3527.65.1 was tested on the following Windows builds: 22621.3296, 22621.3447, and 22621.3527 (the latest non-security update). You can download ExplorerPatcher from its official GitHub repository. ExplorerPatcher release notes are available via this link. In case you missed it, Microsoft recently started blocking systems from upgrading to preview Windows 11 version 24H2 builds if they have StartAllBack or ExplorerPatcher installed. Microsoft would flag those apps as potentially insecure or ones causing performance issues. Although you can bypass the block by simply renaming executables, getting the desired result on version 24H2 is now much harder since the latter no longer allows restoring the old Windows 10 taskbar, thus breaking patchers and other apps relying on legacy code. With that in mind, those unhappy with the Start menu situation in Windows 11 (especially in light of Microsoft adding blatant ads) have several options: just deal with it, go back to Windows 10, or use apps that do not rely on patches and legacy code, such as the recently updated Start11 v2 or any other similar app. Source