A 20-year-old bug in Grand Theft Auto: San Andreas, related to how the game handles specific low-level keyboard input, resurfaced in Windows 11 24H2. This bug, originally present in the 2005 release, causes the game to minimize when certain key combinations are pressed, particularly involving the right Windows key. The issue stemmed from DirectInput, a now-deprecated API used for game controllers, and wasn't previously problematic because older versions of Windows handled the spurious messages differently. Windows 11's updated input stack now surfaces these messages to the game, triggering the minimize behavior. A workaround exists by using a third-party DirectInput wrapper or running the game in compatibility mode for Windows 7.
Windows 11's latest Insider build further cements the requirement of a Microsoft account for Home and Pro edition users during initial setup. While previous workarounds allowed local account creation, this update eliminates those loopholes, forcing users to sign in with a Microsoft account before accessing the desktop. Microsoft claims this provides a consistent experience across Windows 11 features and devices. However, this change limits user choice and potentially raises privacy concerns for those preferring local accounts. Pro users setting up Windows 11 on their workplace network will be exempt from this requirement, allowing them to directly join Azure Active Directory or Active Directory.
Hacker News users largely expressed frustration and cynicism towards Microsoft's increased push for mandatory account sign-ins in Windows 11. Several commenters saw this as a continuation of Microsoft's trend of prioritizing advertising revenue and data collection over user experience and privacy. Some discussed workarounds, like using local accounts during initial setup and disabling connected services later, while others lamented the gradual erosion of local account functionality. A few pointed out the irony of Microsoft's stance on user choice given their past criticisms of similar practices by other tech companies. Several commenters suggested that this move further solidified Linux as a preferable alternative for privacy-conscious users.
Windows 11 Insider Preview Build 22635.4950 (Beta Channel) brings several fixes and improvements. Key changes include resolving an explorer.exe crash, improving Narrator performance with large amounts of text, fixing an issue affecting the reliability of Start menu badges, and addressing problems with app defaults and searchindexer.exe crashes. This build also removes the previously available live captions settings within Quick Settings, directing users to the full settings page instead. While this build doesn't introduce new features, it focuses on stability and bug fixes for a smoother user experience.
Hacker News users discuss the new features in the Windows 11 Insider Preview Build, mostly focusing on practical improvements rather than revolutionary changes. Several commenters express appreciation for the return of ungrouped taskbar icons, viewing it as a positive step back from a less popular design choice. Some discuss the new screen recording feature in Snipping Tool, noting its basic functionality and comparing it to existing third-party options. Others mention the addition of a native VPN status indicator in the system tray, considering it a welcome, if overdue, feature. A few comments also touch on more technical aspects, such as the performance improvements and changes to Windows Ink. Overall, the sentiment seems to be one of cautious optimism, with users appreciating the iterative improvements but remaining somewhat reserved about the overall direction of Windows 11.
This blog post details how to set up a network bootable Windows 11 installation using iSCSI for storage and iPXE for booting. The author outlines the process of preparing a Windows 11 image for iSCSI, configuring an iSCSI target (using TrueNAS in this example), and setting up an iPXE boot environment. The guide covers partitioning the iSCSI disk, injecting necessary drivers, and configuring the boot process to load the Windows 11 installer from the network. This allows for a centralized installation and management of Windows 11 deployments, eliminating the need for physical installation media for each machine.
Hacker News users discuss the practicality and potential benefits of netbooting Windows 11 using iSCSI and iPXE. Some question the real-world use cases, highlighting the complexity and potential performance bottlenecks compared to traditional installations or virtual machines. Others express interest in specific applications, such as creating standardized, easily deployable workstations, or troubleshooting systems with corrupted local storage. Concerns about licensing and Microsoft's stance on this approach are also raised. Several users share alternative solutions and experiences with similar setups involving PXE booting and other network boot methods. The discussion also touches upon the performance implications of iSCSI and the potential advantages of NVMe over iSCSI for netbooting.
Despite Windows 10's approaching end-of-life in October 2025, nearly half of Steam users are still using the operating system, according to the latest Steam Hardware Survey. While Windows 11 adoption is slowly growing, it still sits significantly behind Windows 10, leaving a large portion of PC gamers potentially facing security risks and a lack of support in the near future.
Hacker News users discussed the implications of nearly half of Steam users still running Windows 10, despite its approaching end-of-life. Some questioned the statistic's accuracy, suggesting the data might include Windows Server instances or older, unsupported Windows builds lumped in with Windows 10. Others pointed out the apathy many users feel towards upgrading, especially gamers who prioritize stable systems over new features. Several commenters mentioned the potential security risks of staying on an unsupported OS, while others downplayed this, arguing that games often run in sandboxed environments. The cost of upgrading, both in terms of hardware and software, was also a recurring theme, with some suggesting Microsoft's aggressive upgrade tactics in the past have led to distrust and reluctance to upgrade. Finally, some users speculated that many "Windows 10" users might actually be running Windows 11 but misreported due to Steam's detection methods.
Summary of Comments ( 48 )
https://news.ycombinator.com/item?id=43772311
Commenters on Hacker News discuss the GTA San Andreas bug triggered by Windows 11 24H2, mostly focusing on the technical aspects. Several highlight the likely culprit: a change in how Windows handles thread local storage (TLS) callbacks, specifically the order of execution. One compelling comment notes the difficulty in debugging such issues, as the problem might not lie within the game's code itself, but rather in the interaction with the OS, making it hard to pinpoint and fix. Others mention the impressive longevity of the game and express surprise that such a bug could remain hidden for so long, while some jokingly lament the "progress" of Windows updates. A few commenters share their own experiences with similar obscure bugs and the challenges they posed.
The Hacker News post discussing a 20-year-old bug in GTA San Andreas surfacing in Windows 11 24H2 has several comments exploring the technical aspects and implications of the issue.
One commenter highlights the complexity of software interactions, pointing out how a seemingly unrelated change in the operating system can unexpectedly trigger dormant bugs in older applications. They emphasize the difficulty in predicting such issues, especially in large and intricate systems like Windows and a game as complex as GTA San Andreas.
Another comment delves into the specifics of the bug, explaining how the change in Windows 11's handling of specific instructions, particularly related to floating-point operations and denormalized numbers, led to the game's malfunction. This explanation provides a technical understanding of why the bug only surfaced after the Windows update.
Several commenters discuss the challenges faced by developers in maintaining backward compatibility, especially over such long periods. They note that anticipating all possible interactions between a game and future operating system updates is practically impossible. The idea of "bit rot," where software gradually degrades over time due to changes in the surrounding technological environment, is also mentioned.
One commenter mentions a similar experience with another older game, illustrating that this kind of issue isn't unique to GTA San Andreas and highlighting the broader challenge of preserving software functionality across evolving platforms.
There's a discussion about the nature of denormalized numbers and their impact on performance. One commenter questions the practical necessity of handling denormalized numbers in modern hardware and software, suggesting that their support might be more trouble than it's worth in some contexts.
Finally, a few commenters offer potential workarounds for the issue, such as disabling hardware acceleration or using compatibility modes in Windows 11. These suggestions provide practical solutions for users affected by the bug while waiting for a permanent fix.