Windows Archive
WSLg is short for Windows Subsystem for Linux GUI and the purpose of the project is to enable support for running Linux GUI applications (X11 and Wayland) on Windows in a fully integrated desktop experience. WSLg provides an integrated experience for developers, scientists or enthusiasts that prefer or need to run Windows on their PC but also need the ability to run tools or applications which works best, or exclusively, in a Linux environment. While users can accomplish this today using a multiple system setup, with individual PC dedicated to Windows and Linux, virtual machine hosting either Windows or Linux, or an XServer running on Windows and projected into WSL, WSLg provides a more integrated, user friendly and productive alternative. WSLg will ship with Windows 11, but despite it being developed and tested on Windows 10, it won’t become available for Windows 10 users, and is currently only accessible to users of Windows beta builds.
Earlier today, Microsoft pushed a promotional message to early adopters of Windows 11. The promo intended to promote the upcoming operating system’s integration with Microsoft Teams. Instead, it caused Explorer (the Windows desktop shell) to stop responding and left users without a working Start menu and taskbar. Based on the Microsoft-provided workaround, I narrowed the problem down to a registry key that contained a serialized JSON blob. The blob contained an advertisement for Microsoft Teams. The messaging and imagery in the promotion were identical to the panel you get when you press the Windows key + C on a Windows account not already set up with Teams. It’s unclear if it’s this exact promotion, however. Microsoft broke every single Windows 11 computer through an ad. Windows users – you can choose a better way.
Today, we are announcing the general availability of Windows Server 2022. It’s a big step forward for the operating system that is trusted by major corporations and small businesses alike to run their business and mission-critical workloads. It comes with tons of security improvements (of course), SMB compression, support for up to 48TB of memory and 2048 threads running on 64 sockets, and more.
Windows 11 is no longer merely “coming this fall.” Microsoft will begin releasing the new operating system to the public on October 5, starting with newer PCs (and PCs being sold in stores) and then rolling out to other supported systems over the next nine or so months. The company also says that the Amazon-powered Android app support coming to Windows 11 won’t be ready for public consumption at launch; Microsoft will offer “a preview for Windows Insiders over the coming months.” Get your centered taskbar and 12th concurrently used Windows theme October 5.
Just in case you thought the Windows 11 upgrade and hardware compatibility situation couldn’t get any more confusing and complicated, Microsoft decided to do a Microsoft. This morning, Microsoft revealed a change of plan to The Verge: it won’t technically abandon those millions of PCs, because you’ll be able to manually install the downloadable Windows 11 ISO on whatever you want. The company’s also extending its official CPU compatibility list to a bunch of Intel’s most expensive Xeon workstation processors and its most expensive line of Core X desktop CPUs — and, tellingly, the less powerful Intel chip it shipped in its Surface Studio 2, so it no longer has to defend the idea of abandoning a flagship product that it still continues to sell brand-new. That sounds like a nice gesture, since it will enable anyone – even those who do not technically comply with the TPM requirements – to install Windows 11, even if it has to be a fresh installation (which you should probably do with new Windows versions anyway). However, it turns out there’s a major caveat here. While yes, Microsoft will allow you to install Windows 11 on unsupported hardware, these installations might not get updates – not even security updates. First and perhaps most important, Microsoft informed us after we published this story that if your computer doesn’t meet the system requirements, it may not be entitled to get Windows Updates, even security ones. We’re asking Microsoft for clarification on that now. But secondly, it still sounds like Microsoft will be encouraging millions of people to replace their perfectly good Windows PCs. Other than yet another theme third parties aren’t going to adopt, there’s not a whole lot in Windows 11 as it is, and with all this confusion around upgrades, supported hardware, and access to updates, Windows 10 users are probably better off sticking with Windows 10 for a little while longer. Or, you know, switch to an operating system that doesn’t treat its users like garbage.
In Windows 11, Microsoft has changed the way you set default apps. Like Windows 10, there’s a prompt that appears when you install a new browser and open a web link for the first time. It’s the only opportunity to easily switch browsers, though. Unless you tick “always use this app,” the default will never be changed. It’s incredibly easy to forget to toggle the “always use this app” option, and simply launch the browser you want from this prompt and never see this default choice again when you click web links. Microsoft has changed the way default apps are assigned in Windows 11, which means you now have to set defaults by file or link type instead of a single switch. In the case of Chrome, that means changing the default file type for HTM, HTML, PDF, SHTML, SVG, WEBP, XHT, XHTML, FTP, HTTP, and HTTPS. That’s what you get when you use proprietary operating systems. Windows and macOS are not designed for you; they’re designed for Microsoft and Apple, respectively.
Hello Windows Insiders! Today we are rolling out the first set of updates for several apps that come included as part of Windows 11. The following app updates are rolling out to Windows Insiders in the Dev Channel at first. Microsoft has updated some of the default Windows applications – Snipping Tool, Calculator, and Mail & Calendar.
So imagine my surprise when I dug around in a quarter-century-old archive to find a .zip file containing something that purported to be the original executable of Labyrinth. Surely such an ancient piece of code – written for Windows 3.1 – wouldn’t launch? Well, after a bit of fiddling with the Windows compatibility settings, I was shocked – and extremely pleased – to see that, yes, it most certainly did. It shouldn’t be surprising that a piece of good Windows code from 30 years ago still runs on Windows 10 today, and yet, it always is.
After many months of work, Simon and I are pleased to announce the WireGuardNT project, a native port of WireGuard to the Windows kernel. This has been a monumental undertaking, and if you’ve noticed that I haven’t read emails in about two months, now you know why. WireGuardNT, lower-cased as “wireguard-nt” like the other repos, began as a port of the Linux codebase, so that we could benefit from the analysis and scrutiny that that code has already received. After the initial porting efforts there succeeded, the NT codebase quickly diverged to fit well with native NTisms and NDIS (Windows networking stack) APIs. The end result is a deeply integrated and highly performant implementation of WireGuard for the NT kernel, that makes use of the full gamut of NT kernel and NDIS capabilities. That’s an impressive porting job, and further spreads the availability of this protocol to entirely new users and settings.
Last week Microsoft released Windows 11 Insider Preview Build 22000.100 to everyone in the Dev Channel. After no major issues were detected, Microsoft has released the same build to the more stable Beta channel. Microsoft suggests those who would like to test Windows 11 but who are not ready for the wild Dev channel ride may want to switch to the Beta channel now. Microsoft also said they will not be releasing a Dev channel build this week. This is the first what you could call beta release of Windows 11, hinting that Microsoft is well on track to release Windows 11 later this Fall.
When Windows 11 arrives this holiday season, there is going to be a ton of changes. It looks totally different, supports Android apps, and more. There are also changes coming to how Windows 11 is updated and how it’s supported, so just in case you were worried about it, you’ll be pleased to know that there will be a Windows 11 Long-Term Servicing Channel (LTSC) version. Good news for people not interested in Microsoft’s update schedule.
Today we’re excited to announce Windows 365, a cloud service that introduces a new way to experience Windows 10 or Windows 11 (when it’s generally available later this calendar year) for workers from interns and contractors to software developers and industrial designers. Windows 365 takes the operating system to the Microsoft Cloud, securely streaming the full Windows experience—including all your apps, data, and settings—to your personal or corporate devices. This approach creates a fully new personal computing category, specifically for the hybrid world: the Cloud PC. As silly as this sounds, I’m actually somewhat interested in this. I have a Windows 10 VM for some Windows-only translation software I sometimes need to use, but managing and updating Windows is a pain, so the idea of just paying a few euros every month to have a Windows instance on some faraway server actually seems like a much better alternative.
Running Windows on a phone has long been a dream for Microsoft enthusiasts, especially after the company discontinued their Windows Phones. While we may never see Microsoft’s vision for a phone running Windows 11, some young developers have shown us a preview of the operating system running on Android phones. We may end up in a world where Windows 11 will run on old Android phones, but not on computers with 7th gen Intel Core processors. In all seriousness, this is amazing and cool, and shows just how versatile Windows NT really is. Excellent work by these enthousiasts, and it keeps the dream alive.
Microsoft’s free upgrade offer for Windows 7 and Windows 8.1 users ended way back in 2016, but you can still upgrade to Windows 10. As expected, Microsoft says it will continue to support Windows 11 users upgrading from Windows 7 or Windows 8.1 as long as they meet the minimum system requirements. However, there’s a catch – Windows 7 to Windows 11 upgrade could wipe your apps, settings and customizations. That’s because a proper direct upgrade path is not available for Windows 7/8.1 users, according to a support document from Lenovo, which was published on June 24 and spotted by us earlier today. This isn’t entirely unreasonable. Windows 7 was released 12 years ago, and received its last (and only) service pack 10 years ago. Mainstream support ended 2015, six years ago. I think this is a fair point to say – no more in-place upgrades. I mean, I think most people do fresh Windows installations anyway.
We already know that Windows 11 Home will require a Microsoft account (MSA) at the beginning of the installation process. What Microsoft hasn’t publicized is whether it’s possible to log in with just a local account. It is, but only with Windows 11 Pro. A source close to Microsoft has now told us that the only way to avoid using an MSA is with Windows 11 Pro. According to our source, users who buy or own a PC with Windows 11 Pro may choose to use either a local account or an MSA from the very beginning of the installation process. The Windows 11 Home MSA requirement isn’t permanent, just unavoidable. Microsoft will allow the user to transition to a local account once the Windows 11 Home installation process has completed. Retail versions of Windows 11 Home will offer the same experience. So you’re going to need an online account to install Windows 10 Home. If, for some reason, you truly want Windows 11, I’d suggest waiting a few months and get some cheap OEM license for Windows 11 Pro from eBay for a few dollars to save yourself the hassle.
Microsoft gave its digital imprimatur to a rootkit that decrypted encrypted communications and sent them to attacker-controlled servers, the company and outside researchers said. The blunder allowed the malware to be installed on Windows machines without users receiving a security warning or needing to take additional steps. For the past 13 years, Microsoft has required third-party drivers and other code that runs in the Windows kernel to be tested and digitally signed by the OS maker to ensure stability and security. Without a Microsoft certificate, these types of programs can’t be installed by default. One of the reasons Windows 11’s hardware requirements are so stringent is because Microsoft wants to force Trusted Platform Modules and Secure Boot down everyone’s throat, in the name of security. This way, Windows users can feel secure in knowing Microsoft looks out for them, and will prevent malware and viruses from… I can’t keep writing this with a straight face.
ARM64EC is a new application binary interface (ABI) for Windows 11 on ARM that runs with native speed and is interoperable with x64. An app, process, or even a module can freely mix and match ARM64EC and x64 as needed. The ARM64EC code in the app will run natively while any x64 code will run using Windows 11 on ARM’s built-in emulation. The ARM64EC ABI differs slightly from the existing ARM64 ABI in ways that make it binary compatible with x64 code. Specifically, the ARM64EC ABI follows x64 software conventions including calling convention, stack usage, and data alignment, making ARM64EC and x64 interoperable. Apps built as ARM64EC may contain x64 code but do not have to, since ARM64EC is its own complete, first-class ABI for Windows. Another tool in the toolbox for Windows developers who wish to treat ARM64 as a first-class citizen.
Microsoft has published a blog post, trying to dispel some of the confusion around Windows 11’s system requirements. First and foremost, the company makes it clear that TPM 2.0 and 8th generation Intel and 2nd generation Ryzen are hard floors. Microsoft adds that based on the feedback during Windows 11’s testing process, support for 7th generation Intel and 1st generation Ryzen processors might be added. Using the principles above, we are confident that devices running on Intel 8th generation processors and AMD Zen 2 as well as Qualcomm 7 and 8 Series will meet our principles around security and reliability and minimum system requirements for Windows 11. As we release to Windows Insiders and partner with our OEMs, we will test to identify devices running on Intel 7th generation and AMD Zen 1 that may meet our principles. There are ways around these hard floors, through registry hacks and custom Windows 11 ISOs, but updates might break those, and who knows if Microsoft will plug those holes.
In my first story on the unveiling of Windows 11, I remarked that the system requirements remained largely unchanged from Windows 10. Well, as it turns out, I couldn’t have been more wrong. Since the announcement, Microsoft has been incredibly obtuse and back-and-forth about the system requirements for Windows 11, and at this point, it seems like nobody has any clue anymore what’s true and what isn’t. Windows 11 is arriving later this year as a free upgrade for Windows 10 users, but many are discovering that their hardware isn’t compatible. Microsoft has altered its minimum hardware requirements, and it’s the CPU changes that are most surprising here. Windows 11 will only officially support 8th Gen and newer Intel Core processors, alongside Apollo Lake and newer Pentium and Celeron processors. Windows 11 will also only officially support AMD Ryzen 2000 and newer processors, and 2nd Gen or newer EPYC chips. That’s one hell of a hard cutoff, and one that seems entirely arbitrary. There’s nothing in Windows 11 that a first generation Ryzen or 6th or 7th generation Intel Core processor cannot handle, so why rule them out? A lot of people just assume Windows 11 will work on older processors than those listed, but there’s no confirmation from Microsoft that this is the case. Aside from processor support, there’s another aspect that Microsoft is vague about: does Windows 11 require TPM 2.0 or TPM 1.2? Do you need a hardware TPM, or will a firmware TPM, available in about every modern x86 processor but turned off by default, suffice? Nobody seems to have the answers, and it’s leading to a lot of speculation ad uncertainty. The same applies to Secure Boot and UEFI – Microsoft lists both of them as requirements, but most news stories online just assume Microsoft doesn’t truly think of them as requirements, more as suggestions. There’s a lot of uncertainty in the air here for Windows users.
Let’s take a step back from Windows 11 and go back in time – to 22 years ago, to be exact. Alpha on Windows NT is dead. As far as NT goes, it’s an Intel world. Last week, Compaq announced that it was laying off more than 100 of its Alpha/NT employees in its DECwest facility located near the Microsoft campus. This group of developers was tasked with making Alpha on NT a technical reality. Citing Compaq’s decision and the strength of Intel’s architecture and systems, Microsoft says it will discontinue development of future 32-bit and 64-bit Alpha products across its existing product line. Windows NT on PowerPC, Alpha, MIPS, and Itanium have always been deeply fascinating to me, and at some point, I want to get my hands on some supported hardware, just for the fun of it.
