Jeffrey Snover, the driving force behind PowerShell, has retired after a career that reshaped Windows administration. The Register reports: Snover's retirement comes after a brief sojourn at Google as a Distinguished Engineer, following a lengthy stint at Microsoft, during which he pulled the company back from imposing a graphical user interface (GUI) on administrators who really just wanted a command line from which to run their scripts. Snover joined Microsoft as the 20th century drew to a close. The company was all about its Windows operating system and user interface in those days -- great for end users, but not so good for administrators managing fleets of servers. Snover correctly predicted a shift to server datacenters, which would require automated management. A powerful shell... a PowerShell, if you will. [...] Over the years, Snover has dropped the occasional pearl of wisdom or shared memories from his time getting PowerShell off the ground. A recent favorite concerns the naming of Cmdlets and their original name in Monad: Function Units, or FUs. Snover wrote: "This abbreviation reflected the Unix smart-ass culture I was embracing at the time. Plus I was developing this in a hostile environment, and my sense of diplomacy was not yet fully operational." Snover doubtless has many more war stories to share. In the meantime, however, we wish him well. Many admins owe Snover thanks for persuading Microsoft that its GUI obsession did not translate to the datacenter, and for lengthy careers in gluing enterprise systems together with some scripted automation.

Read more of this story at Slashdot.

The senior editor at the blog Windows Central decries two serious Windows issues "that were not spotted by Microsoft during testing, and are so severe that the company has now issued an emergency fix to address the problems." Microsoft's first update for Windows 11 in 2026 has already caused two major issues that saw users unable to fully shutdown their PCs or sign-in into a device when using Remote Desktop... Being unable to shut down your PC due to a recent OS update is a huge oversight on Microsoft's part, but this is the latest in a long list of updates over the last year to cause a major issue like this... Other issues that have cropped up in Windows 11 in the last year include a bug that caused Task Manager to fail to close when the user exited the application, causing system resources to lock up after a prolonged period of time if the user had opened and closed Task Manager multiple times in a session. Another update caused saw File Explorer flashbang users with a white screen when opening it in dark mode, which appeared in an update that was supposed to improve dark mode on Windows 11... For whatever reason, the Windows Insider Program doesn't appear to be working anymore, as severe bugs are somehow making it into shipping versions of the OS. "The out of band updates, KB5077744 and KB5077797, are available now via Windows Update and is rolling out to everybody," they write. "Once installed, your PC should go back to being able to shut down successfully, and signing-in via Remote Desktop should work again." Microsoft has also officially acknowledged a third bug which crashes Outlook Classic when using POP accounts, according to the blog Windows Latest, which adds that that bug has not yet been fixed. They've also identified other minor bugs, including "a black screen problem in Windows 11 KB5074109... either due to the update itself or some compatibility issues with GPU drivers." After you install the January 2026 Update, Windows triggers random black screens where the desktop freezes for a second or two, the display goes black, then everything comes back. I can't pinpoint any specific configuration, but I can confirm the black screen issue has been observed on a small subset of PCs with both Nvidia and AMD GPUs. After you install the January 2026 Update, Windows triggers random black screens where the desktop freezes for a second or two, the display goes black, then everything comes back.

Read more of this story at Slashdot.

A recent Microsoft Patch Tuesday update has introduced a bug in Windows 11 23H2 that causes some PCs to refuse to shut down or hibernate, "no matter how many times you try," reports The Register. From the report: In a notice on its Windows release health dashboard, Microsoft confirmed that some PCs running Windows 11 23H2 might fail to power down properly after installing the latest security updates. Instead of slipping into shutdown or hibernation, affected machines stay stubbornly awake, draining batteries and ignoring shutdown like they have a mind of their own and don't want to experience temporary non-existence. The bug appears to be tied to Secure Launch, a security feature that uses virtualization-based protections to ensure only trusted components load during boot. On systems with Secure Launch enabled, attempts to shut down, restart, or hibernate after applying the January patches may fail to complete. From the user's perspective, everything looks normal -- until the PC keeps running anyway, refusing to be denied life. Microsoft says that entering the command "shutdown /s /t 0" at the command prompt will, in fact, force your PC to turn off, whether it wants to or not. "Until this issue is resolved, please ensure you save all your work, and shut down when you are done working on your device to avoid the device running out of power instead of hibernating," Microsoft said.

Read more of this story at Slashdot.

https://www.youtube.com/watch?v=7VZJO-hOT4c : 6 machines identiques. 6 versions de Windows comparées.
Vous vous doutez du résultat ? Oui Windows 11 est une catastrophe.
(Permalink)

Valve has added the NTSYNC kernel driver to the SteamOS 3.7.20 beta, laying the groundwork for improved Windows game synchronization performance via Wine and Proton. Phoronix reports: For gearing up for that future Proton NTSYNC support, SteamOS 3.7.20 enables the NTSYNC kernel driver and loads the module by default. Most Linux distributions are at least already building the NTSYNC kernel module though there's been different efforts on how to handle ensuring it's loaded when needed. The presence of the NTSYC kernel driver is the main highlight of the SteamOS 3.7.20 beta now available for testing.

Read more of this story at Slashdot.

Des nouvelles de cette saloperie de Windows 11 : Non seulement Microsoft utilise des dark patterns pour inciter les utilisateurs à autoriser Microsoft à récupérer vos fichiers privés, mais en prime si vous supprimez vos fichiers de OneDrive, cela les supprime localement.
C'est en gros le fonctionnement d'un ransomeware: Il utilise de l'ingénierie sociale pour récupérer vos fichiers, et vous les fait perdre si vous essayez de vous échapper du système.
Franchement, si vous le pouvez, virez Windows.
(Permalink)

An anonymous reader shared this report from Neowin: Offline Windows activation has been possible to do using the phone. However, it looks like Microsoft has quietly killed off that method as users online have found that they are no longer able to activate the OS using it... [As documented by Windows user Ben Kleinberg on his YouTube channel], Now when trying to activate the OS by attempting to call the phone number for Microsoft Product Activation, an automated voice response says the following: "Support for product activation has moved online. For the fastest and most convenient way to activate your product, please visit our online product activation portal at aka.ms/aoh" If you are wondering, that link takes users to the Microsoft Product Activation Portal for online activation. Thus it appears that offline ways to activate Windows may no longer be available even though the official support documentation by the company may not reflect it yet.

Read more of this story at Slashdot.

Il n'est plus possible d'activer Windows par téléphone.
(Permalink)

• lien nᵒ 1 : Portail de l'initiative (à ce jour seulement en allemand)
• lien nᵒ 2 : #iDidIt sur Mastodon
• lien nᵒ 3 : La vidéo du 39c3 (+50k vues en 2 jours)
• lien nᵒ 4 : L'appel à ce que La Quadrature du Net et Framasoft rejoignent l'initiative

Commentaires : voir le flux Atom ouvrir dans le navigateur

Windows 10's formal end-of-support arrived in October, and while the operating system is generally remembered as one of the "good" versions of Windows -- the most widely used since XP -- many of the annoyances people complain about in Windows 11 actually started during the Windows 10 era, ArsTechnica writes. Windows 10 earned its positive reputation primarily by not being Windows 8. It restored a version of the traditional Start menu, rolled out as a free upgrade to Windows 7 and 8 users, and ran on virtually all the same hardware as those older versions. Microsoft introduced the Windows Subsystem for Linux during this period and eventually rebuilt Edge on Chromium. The company seemed more willing to meet users where they were rather than forcing them to change their behavior. But Windows 10 also began collecting more information about how users interacted with the operating system, cluttered the lock screen with advertisements and news articles, and added third-party app icons to the Start menu without user consent. The mandatory Microsoft Account sign-in requirement -- one of Windows 11's most frequently complained-about features -- was a Windows 10 innovation, easier to circumvent at the time but clearly a step down the road Windows 11 is currently traveling. To be sure, Windows 11 has made things worse by stacking new irritants on top of old ones. The Microsoft Account requirement expanded to both Home and Pro editions, the SCOOBE screen now regularly nags users to "finish setting up" years-old installations and Microsoft's Copilot push changed the default PC keyboard layout for the first time in 30 years.

Read more of this story at Slashdot.

« Que se passe-t-il en ce moment avec Windows 11 ? Depuis quelques mois, Microsoft semble accumuler les boulettes, dans une avalanche de problèmes techniques, alors même que Windows 10 n’a plus de support. Les annonces sur l'IA et la montée en puissance de Linux sur les jeux n'arrangent pas la situation. »

Voir aussi : https://www.windowscentral.com/microsoft/windows-11/2025-has-been-an-awful-year-for-windows-11-with-infuriating-bugs-and-constant-unwanted-features
(Permalink)

Microsoft has denied any plans to rewrite Windows 11 using AI and Rust after a LinkedIn post from one of its top-level engineers sparked a wave of online backlash by claiming the company's goal was to "eliminate every line of C and C++ from Microsoft by 2030." Galen Hunt, a principal software engineer responsible for several large-scale research projects at Microsoft, made the claim in what was originally a hiring post for his team. His original wording described a "North Star" of "1 engineer, 1 month, 1 million lines of code" and outlined a strategy to "combine AI and Algorithms to rewrite Microsoft's largest codebases." The repeated use of "our" in the post led many to interpret it as an official company direction rather than a personal research ambition. Frank X. Shaw, Microsoft's head of communications, told Windows Latest that the company has no such plans. Hunt subsequently edited his LinkedIn post to clarify that "Windows is NOT being rewritten in Rust with AI" and that his team's work is a research project focused on building technology to enable language-to-language migration. He characterized the reaction as "speculative reading between the lines."

Read more of this story at Slashdot.