Windows 10 Enterprise LTSC 2021 ESU will cost $61 per device


Microsoft a discrètement supprimé une page conseillant 32 Go de RAM pour les PC gaming, un revirement qui en dit long sur la crise des composants et les difficultés de l’industrie à suivre ses propres recommandations.
L’article Microsoft efface ses propres conseils gaming : la pénurie de RAM change les règles est apparu en premier sur Tom’s Hardware.




Earlier this year, Microsoft announced that it was moving to address Windows 11's biggest issues and criticisms from users in an effort to win back trust from customers and reposition Windows once more as a viable alternative to macOS and Linux, something people actually want to use over the competition.
It was nice to see Microsoft outline its roadmap and plan for Windows 11, but I wasn't prepared for just how fast the company would start delivering on the promises it was making. Since March, Microsoft has previewed and even shipped many improvements to Windows 11 that are the direct result of its Windows K2 initiative, all designed to fix Windows 11.
I've been testing these new Windows 11 builds over the last few months, and there are 5 big changes and improvements that stand out as super exciting. Some of these improvements are already shipping, whereas others are still in preview.

Updates on Windows have always been frustrating, so much so Microsoft made it a point of focus for its Windows K2 effort. In the last few months, Microsoft has shipped multiple changes and improvements to Windows Update which are designed to make it more reliable, and more importantly, less annoying.
The first big change is ensuring driver, framework, and security updates are now all timed to install at the same time. Previously, any update could require the user to restart at any time. Now, Windows Update will only ask you to restart once a month, as the update system now installs those driver and framework updates alongside security patches.
That's in addition to being able to pause updates indefinitely now, so even when the one time a month that Windows asks you to restart finally rolls around, users have the option to say no and postpone the restart for as long as they need. Even when an update is pending restart, the option to shut down or restart without installing said update is now present.
Microsoft has even made it so users can skip installing updates when setting up a PC for the first time, meaning it now takes just a few minutes to get right into using your new PC instead of the 20+ minutes it used to take when installing the latest update was a requirement before reaching the desktop.
All of these Windows Update improvements are already shipping to all Windows 11 users, which is a crazy quick turn around.

People didn't believe they'd do it, but they actually have reduced the ads and AI buttons that are present across the OS. The Widgets board has been updated to replace the MSN feed with the local widgets feature by default, meaning you won't ever see any MSN stories or sponsored content unless you manually go into that section of the OS.
Microsoft is also removing Bing and MSN ads from Windows Search, in preview now. The search pane itself is now a long list or recent search queries and items, with nonsense like the Bing wallpaper of the day and other sponsored content no longer appearing at all. Even search results that reach out to the web no longer include sponsored content.
The Start menu now also has more granular controls over the kind of content that appears in there. The "Recommended" feed has been renamed to the "Recents" feed and no longer shows recommended apps and websites that came across as more advertising. Users even have the option to remove the Recents feed entirely now, which is great.
Copilot used to plague every inbox app and UI surface you could think of on Windows 11, but today it only appears in a few very specific areas. It still exists as a standalone app on Windows 11, but the Copilot button no longer exists in apps like Photos and Notepad. Microsoft has even removed the "Ask Copilot" option in File Explorer.

One big area of focus for Microsoft is the overall performance and reliability of Windows 11, which many agree has slipped over the last few years. The good news is Microsoft has already delivered several improvements on this front, with more to come in the following weeks.
The first big change is the new "Low Latency Profile" feature that shipped just a few weeks ago. It's an invisible change that makes opening apps, context menus, and flyouts from the Taskbar much more responsive by silently increasing CPU frequency when these common actions take place.
This is something other OS platforms do which allows them to remain feeling snappy, even under heavy load, and now Windows 11 has the same behavior. This has outright fixed the issue users sometimes have where things like the Start menu don't always appear immediately when clicked. That's a thing of the past now.
Microsoft is also improving the performance of WinUI interfaces across the system via a new System Compositor which reduces latency and memory overhead across the OS so that these modern interfaces are consistently responsive. There's even a new Run dialog built with WinUI that is faster than the old Win32 version.
Opening and navigating through file trees in File Explorer is faster too, and searching for files and apps on Windows 11 is now more consistent. Two character search is already shipping, which makes finding content a little bit easier.

One of the biggest issues people have with Windows 11 is how it took away customizable options for areas of the system like the Start menu or Taskbar. Microsoft has heard that feedback, and is already publicly testing a new Taskbar and Start menu that can be user customized.
The Taskbar can now be repositioned just like on Windows 10, allowing the user to move it to the left, right and top of the display if that's where they want it. There's also a new resize option letting users make it smaller like the Windows 10 one could.
The Start menu is also getting more customization options. Users can hide entire segments of Start, such as the Recents feed, Pinned apps, or All Apps area. They can toggle on or off the Phone Link companion, and disable Start entirely if they don't ever use it.

Above are all the new improvements that I've tested and are either shipping or in public testing via the Windows Insider Program. These are the real changes and features that can be tried and tested as we speak, not just empty promises or ideas. It's all available to download and try out right now.
There's still more to come too, stuff that isn't yet in public preview testing. Microsoft has confirmed it's working to move more parts of the OS to WinUI for faster performance, such as the Start menu and areas of File Explorer. There's an effort to reduce the footprint of the OS in the works too, which should make the OS less resource intensive at idle.
Other improvements in the works are a redesigned context menu system that is faster and more customizable, more integration across the OS with your smartphone, and dark mode in even more places.
For the features that are yet to ship outside of preview, I understand that Microsoft is aiming to get the bulk of these improvements out of the door before the end of 2026, with some expected in 2027.
SI'm so very impressed with how quickly Microsoft has turned Windows 11 around so far. I haven't felt this positive about the features and changes being actively made to Windows in a really long time, to the point where it feels weird to not have anything to really complain about. All of my biggest issues with Windows 11 have either already been addressed, or are in the process of being addressed.
It's a great time to be a Windows user again.

Join us on Reddit at r/WindowsCentral to share your insights and discuss our latest news, reviews, and more.



Votre PC sous Windows 11/10 n’est plus à la bonne heure ? L’horloge affiche une heure en avance, en retard ou se remet systématiquement à zéro après chaque démarrage ? Ce problème est plus fréquent qu’on ne le pense et peut avoir des conséquences sur le bon fonctionnement de Windows et de certaines applications.
Une heure incorrecte peut empêcher la synchronisation de fichiers, provoquer des erreurs de certificats HTTPS dans les navigateurs Web, perturber Windows Update, empêcher la connexion à certains services en ligne ou encore provoquer des dysfonctionnements avec Outlook, OneDrive, Steam ou Microsoft Store.
Les causes sont nombreuses : mauvais fuseau horaire, échec de la synchronisation avec un serveur de temps (NTP), service Windows Time défaillant, pile CMOS déchargée, problème dans le BIOS/UEFI ou encore dual boot entre Windows et Linux.
Dans ce guide, découvrez toutes les causes possibles d’une mauvaise heure sous Windows 11/10 ainsi que les solutions pour retrouver une horloge parfaitement synchronisée.
Une heure incorrecte sur Windows 11/10 peut avoir plusieurs origines. Dans la plupart des cas, le problème provient d’un mauvais paramétrage de Windows, d’un défaut de synchronisation avec les serveurs de temps ou d’un problème matériel comme une pile CMOS usée.
Le tableau ci-dessous présente les causes les plus fréquentes ainsi que les solutions à envisager.
| Symptôme | Cause probable | Solution |
|---|---|---|
| L’heure est décalée d’une ou plusieurs heures | Fuseau horaire incorrect ou réglage automatique désactivé | Vérifier le fuseau horaire et les paramètres de date et d’heure |
| L’heure avance ou retarde de quelques minutes | Échec de la synchronisation avec un serveur de temps (NTP) | Vérifier la synchronisation automatique et relancer une synchronisation |
| L’heure est remise à zéro après chaque arrêt du PC | Pile CMOS déchargée | Remplacer la pile CR2032 de la carte mère |
| L’heure est déjà incorrecte dès l’écran du BIOS/UEFI | Mauvais réglage de l’horloge du BIOS ou pile CMOS défectueuse | Corriger l’heure dans le BIOS/UEFI et contrôler la pile |
| L’heure devient incorrecte après avoir utilisé Linux en double démarrage | Windows et Linux utilisent des méthodes différentes pour gérer l’horloge matérielle (UTC ou heure locale) | Configurer les deux systèmes pour utiliser le même mode |
| L’heure change régulièrement sur un PC d’entreprise | Synchronisation imposée par un contrôleur de domaine Active Directory | Vérifier la configuration réseau avec l’administrateur informatique |
| L’heure est incorrecte après une sortie de veille ou d’hibernation | Problème de reprise de l’horloge ou de synchronisation | Redémarrer Windows et vérifier le service Windows Time |
| L’heure est incorrecte dans une machine virtuelle | Synchronisation avec l’hôte désactivée ou mal configurée | Vérifier les paramètres de synchronisation de l’hyperviseur |

Un mauvais fuseau horaire est l’une des causes les plus fréquentes d’une heure incorrecte sur Windows 11/10. Dans ce cas, l’horloge est généralement décalée d’une ou plusieurs heures alors que les minutes sont correctes.
Par exemple, si votre PC est configuré sur le fuseau (UTC-05:00) Est (États-Unis et Canada) au lieu de (UTC+01:00) Bruxelles, Copenhague, Madrid, Paris, l’heure affichée sera erronée même si la synchronisation avec les serveurs de temps fonctionne correctement.
Pour vérifier le fuseau horaire :
Une fois le bon fuseau horaire sélectionné, vérifiez si l’heure affichée est désormais correcte. Si ce n’est pas le cas, le problème provient probablement de la synchronisation de l’horloge ou d’un autre dysfonctionnement.
Suivez ce tutoriel :

Windows 11/10 synchronise automatiquement l’horloge avec un serveur de temps (NTP) sur Internet. Cette opération permet de maintenir une heure précise sans intervention de votre part.
Si cette synchronisation échoue, l’horloge peut progressivement prendre de l’avance ou du retard, voire ne plus se mettre à jour du tout. Cela peut être dû à un service Windows désactivé, un serveur de temps indisponible, un pare-feu ou un problème de connexion Internet.
Pour vérifier que la synchronisation automatique est activée :
Si la synchronisation réussit, Windows affiche la date et l’heure de la dernière synchronisation.
En revanche, si un message d’erreur apparaît ou que la synchronisation échoue systématiquement, il est probable que le service Windows Time, le serveur NTP ou un autre composant de Windows soit en cause.
Le guide complet :
Après une synchronisation réussie, vérifiez que l’heure affichée est correcte. Si le problème réapparaît après un redémarrage ou quelques heures d’utilisation, il peut s’agir d’un problème matériel, notamment une pile CMOS déchargée ou une horloge du BIOS/UEFI mal configurée.
Si l’heure de votre PC est incorrecte, vous pouvez lancer une synchronisation manuelle avec un serveur de temps afin de remettre immédiatement l’horloge à l’heure.
Cette opération est utile lorsque la synchronisation automatique ne s’est pas effectuée depuis plusieurs jours ou après avoir corrigé le fuseau horaire.
Pour synchroniser l’heure manuellement :
Si l’opération réussit, Windows met immédiatement à jour la date et l’heure, puis affiche la date de la dernière synchronisation.
En revanche, si la synchronisation échoue ou qu’un message d’erreur s’affiche, cela peut indiquer un problème avec le service Windows Time, le serveur NTP ou votre connexion réseau.
Suivez ce guide pour résoudre ce problème :
Si la synchronisation manuelle ne corrige pas le problème ou si l’heure redevient incorrecte après un redémarrage, poursuivez les vérifications ci-dessous, notamment l’heure du BIOS/UEFI et l’état de la pile CMOS

Le service Windows Time (W32Time) est chargé de synchroniser l’horloge de Windows avec un serveur de temps (NTP). S’il est arrêté, désactivé ou rencontre un dysfonctionnement, votre ordinateur ne pourra plus mettre automatiquement son horloge à jour.
Vous pouvez vérifier son état de la façon suivante :
Si le service est arrêté, cliquez dessus avec le bouton droit de la souris, puis choisissez Démarrer. Vous pouvez ensuite essayer de synchroniser à nouveau l’horloge depuis les paramètres de Windows.
Si le service refuse de démarrer, s’arrête immédiatement ou génère une erreur, cela peut indiquer un problème de configuration, de registre ou de fichiers système.
Le guide :
Si le service Windows Time fonctionne correctement mais que l’heure reste incorrecte, poursuivez les vérifications en contrôlant l’heure enregistrée dans le BIOS/UEFI ainsi que l’état de la pile CMOS.

Si l’heure reste incorrecte malgré une synchronisation réussie dans Windows, il est recommandé de vérifier l’horloge enregistrée dans le BIOS/UEFI. En effet, Windows utilise l’horloge matérielle de la carte mère au démarrage. Si celle-ci est erronée, le système peut afficher une heure incorrecte avant même d’effectuer une synchronisation avec un serveur de temps.
Cette vérification est particulièrement utile si :
Pour vérifier l’heure dans le BIOS/UEFI :
Si l’heure du BIOS est correcte mais que Windows affiche une heure différente, le problème provient probablement de la configuration de Windows ou de la synchronisation avec les serveurs de temps.
En revanche, si l’heure du BIOS est également incorrecte, il est fort probable que le problème soit matériel. La cause la plus fréquente est une pile CMOS déchargée, qui ne parvient plus à conserver les paramètres de la carte mère lorsque l’ordinateur est éteint.
La section suivante explique comment reconnaître les symptômes d’une pile CMOS usée et savoir quand il est nécessaire de la remplacer.
La pile CMOS (généralement une pile bouton CR2032) alimente la mémoire de la carte mère lorsque l’ordinateur est éteint. Elle permet notamment de conserver la date, l’heure et les paramètres du BIOS/UEFI.
Avec le temps, cette pile se décharge naturellement. Lorsqu’elle est usée, l’horloge matérielle ne fonctionne plus correctement et Windows affiche une heure ou une date incorrecte au démarrage.
Les symptômes les plus courants d’une pile CMOS déchargée sont les suivants :
Pour confirmer que la pile est en cause :
Si c’est le cas, il est très probable que la pile CMOS soit déchargée et doive être remplacée.
Le remplacement est généralement simple sur un ordinateur de bureau. Il suffit de remplacer la pile bouton par une CR2032 neuve. Sur certains ordinateurs portables, la pile CMOS peut être intégrée à la carte mère ou reliée par un connecteur, ce qui nécessite un démontage plus important.
Le guide pour vous aider :
Après avoir remplacé la pile :
Si le problème persiste malgré une pile neuve, il est alors conseillé de vérifier la configuration de Windows Time, la synchronisation NTP ou un éventuel problème matériel de la carte mère.
Si l’heure de Windows change régulièrement sans raison apparente, il est possible qu’un logiciel ou un équipement réseau la modifie automatiquement. C’est notamment le cas dans les environnements professionnels, avec certaines machines virtuelles ou des logiciels de synchronisation.
Les cas les plus fréquents sont :
Vous pouvez également vérifier la source de synchronisation utilisée par Windows.
Pour cela :
w32tm /query /source
Si le résultat indique Local CMOS Clock, cela signifie que Windows n’est pas synchronisé avec un serveur de temps et utilise uniquement l’horloge matérielle de l’ordinateur. Cette situation peut expliquer une dérive progressive de l’heure, notamment si la pile CMOS est déchargée.
En revanche, si un serveur NTP ou un contrôleur de domaine est affiché, cela signifie qu’une synchronisation est bien configurée.
Si vous utilisez une machine virtuelle, vérifiez également que les paramètres de l’hyperviseur ne remplacent pas régulièrement l’heure de Windows par celle de l’ordinateur hôte.
Enfin, si votre ordinateur appartient à une entreprise ou à un établissement scolaire, il est normal que l’heure soit imposée par l’administrateur réseau. Dans ce cas, les modifications manuelles sont généralement écrasées lors de la prochaine synchronisation.
Si aucune des vérifications précédentes n’a permis de résoudre le problème, il est possible que des fichiers système de Windows soient corrompus. Cela peut affecter le fonctionnement du service Windows Time ou d’autres composants chargés de la gestion de la date et de l’heure.
Windows intègre deux outils permettant de détecter et de réparer automatiquement ces fichiers : SFC (System File Checker) et DISM (Deployment Image Servicing and Management).
Pour lancer une vérification :
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
Le guide complet :
Ces outils permettent de réparer de nombreux problèmes liés aux fichiers système de Windows, y compris ceux pouvant empêcher certains services de fonctionner correctement.
Le guide complet :
Si l’heure reste incorrecte après ces réparations, il est probable que le problème provienne d’un défaut matériel, d’une configuration du BIOS/UEFI ou d’une synchronisation réseau défaillante.
Si votre ordinateur est configuré en dual boot avec Windows et Linux, il est normal de constater un décalage d’une ou deux heures lorsque vous passez d’un système d’exploitation à l’autre.
Ce problème provient du fait que Windows et Linux n’utilisent pas la même méthode pour interpréter l’horloge matérielle (RTC) :
Par conséquent, lorsque vous redémarrez d’un système vers l’autre, Windows peut afficher une heure décalée d’une ou deux heures, notamment lors des changements d’heure été/hiver.
Ce problème n’est pas lié à une panne de votre ordinateur ni à un dysfonctionnement du service Windows Time. Il s’agit simplement d’une différence de fonctionnement entre les deux systèmes d’exploitation.
La solution consiste à harmoniser la gestion de l’horloge entre Windows et Linux. Il est généralement recommandé de configurer Linux pour utiliser l’heure locale, plutôt que de modifier le fonctionnement de Windows, afin d’éviter d’éventuels problèmes avec certaines applications.
Trouvez la solution dans ce guide :
| Erreur | Cause probable | Solution |
|---|---|---|
| Échec de la synchronisation | Windows Time arrêté | Vérifier le service W32Time |
| Le PC perd l’heure à chaque arrêt | Pile CMOS | Remplacer la pile |
| Vous n’êtes pas autorisé à effectuer cette tâche | Droits insuffisants | Utiliser un compte administrateur |
| Le service Windows Time ne démarre pas | Configuration corrompue | Réenregistrer le service |
| Heure décalée d’une heure | Fuseau horaire incorrect | Corriger le fuseau |
| Heure fausse après Linux | Dual boot | Configurer le RTC |
| Heure incorrecte après sortie de veille | Synchronisation interrompue | Relancer la synchronisation |
| L’heure change toute seule | Hyper-V, VMware, domaine AD | Vérifier la source de synchronisation |
Ressources utiles et articles liés
L’article Mon PC sous Windows 11/10 n’est pas à l’heure : causes et solutions est apparu en premier sur malekal.com.
Windows Insiders need to update their PCs to be on a recent build of Windows within the next week. The latest Windows Insider builds contain a renewed flight certificate, which is important because the current flight certificate is set to expire on August 11, 2026.
Flight certificates are used to encourage people to keep devices up to date and on supported versions of Windows. Microsoft ships renewed certificates on a routine basis.
Microsoft emphasized the importance of a renewed flight certificate because in the past renewal mainly affected those in the Canary Channel. Now, those certificates apply across all Insider channels, including Experimental and Beta.
A brief reminder about the flight certificate appears at the top of the change log for the most recent Insider build:
"Today’s Experimental (Future Platforms) build contains a renewed Windows Insider flight certificate. Windows Insider Preview builds use flight certificates that are renewed periodically to help ensure Insider devices remain on supported builds and continue receiving future Insider Preview updates. The current flight certificate expires on August 11, 2026, so please update your device to a build containing the renewed flight certificate before that date."
A separate document dives into more detail, though the main takeaway is that Insiders should simply update their PCs to a recent build. Microsoft shared the chart below to help Insiders stay up to date.
Channel | Core | Minimum Build |
|---|---|---|
Experimental | Future Platforms | 29634.1000 (available July 27, 2026) |
Experimental | 26H2 | 26300.9032 (available July 31, 2026) |
Experimental | 26H1 | 28120.2630 (available July 31, 2026) |
Beta | 25H2 | 26220.9022 (available July 31, 2026) |
Beta | 26H1 | 28020.2623 (available July 31, 2026) |
Once you've performed this one-time larger update, your PC will go back to receiving regular updates.
If you don't update your PC to a build with a fresh flight certificate, you'll start seeing a warning that says, "This build will expire soon" on your desktop. You will also stop receiving automatic background updates once the flight certificate expires.
You should update your PC to a build with a fresh flight certificate, but if you don't, you can fix the issue by going to Settings > Windows Update and letting your PC install the latest build.
Test builds of Windows 11 are designed to expire relatively quickly, so you should update your PC regularly if you're a Windows Insider. Doing so will ensure your system is running a supported version of Windows.


Join us on Reddit at r/WindowsCentral to share your insights and discuss our latest news, reviews, and more.
In this episode of the Windows Central Podcast, Daniel Rubino and Zac Bowden sit down with Marcus Ash, Corporate Vice President of Design and Research for Windows at Microsoft. The discussion centers on the user experience vision for Windows 11, balancing modernization with legacy app compatibility, and optimizing system efficiency across diverse hardware configurations.
This episode of the Windows Central Podcast is sponsored by Surfshark VPN. Unlimited devices, access your content from anywhere, and auto-block malware on Windows, Edge, and other platforms from $2.50/mo, with 4 months extra FREE. Sign up today!
Have a question you want us to answer on the podcast? Send it to us at [email protected]
If you like the show, please let us know by give us a rating on your podcast platform of choice. It really helps us!
You can watch the live, uncut version of the Windows Central Podcast on our YouTube channel!

Join us on Reddit at r/WindowsCentral to share your insights and discuss our latest news, reviews, and more.
562 researchers across 64 countries were on the receiving end of $20 million of rewards from the Microsoft Bounty Program. That program has researchers work with Microsoft to identify and report vulnerabilities across Microsoft's products and services.
The program has been around for years, but the $20 million in awards is a new record. For context, the Microsoft Bounty Program awarded $17 million to 344 researchers last year.
How much researchers receive depends on the type of vulnerability they report. Cloud programs and Zero Day Quest vulnerabilities are capped at $100,000 per vulnerability. Reporting an Endpoint and On-Premises program vulnerability can be worth up to $250,000.
Of course, those are the maximum payouts per report. Many reported vulnerabilities result in smaller awards.
Microsoft expanded the scope of its researcher awards last year. Now, in addition to flagging traditional bounties, researchers can be rewarded for reporting vulnerabilities in open-source software, third-party components, and Microsoft cloud services.
Microsoft detailed the rewards in a recent blog post.
"Security is a team sport. Every vulnerability reported through our bounty programs represents an opportunity to address risk before it can be exploited against customers," said Microsoft. "The work of the research community plays a critical role in helping Microsoft stay ahead of emerging threats while strengthening the security of cloud services, AI systems, enterprise platforms, and consumer technologies."
Microsoft credited the increase in submissions in part to AI. Increasingly, AI is being used to help security researchers.
Microsoft also uses AI to find and fix vulnerabilities as well. Unfortunately, AI can also be used by hackers to quickly leverage discovered vulnerabilities. As a result, there is an AI arms race happening between malicious actors and security researchers.
Microsoft also recalled the success of the Microsoft Zero Day Quest, which had researchers from 20 countries travel to Microsoft's campus in Redmond, Washington. Over 700 vulnerability reports were filed and over $2.3 million was awarded at that event.


Join us on Reddit at r/WindowsCentral to share your insights and discuss our latest news, reviews, and more.
July has come to an end, and as we start a new month, it's a good time to look at the new features and changes that Microsoft has been working on in the second half of the month for Windows 11.
In the last two weeks of July, the company has delivered several new features, but many of those improvements were features that we have already seen in other builds as Microsoft continues to align each channel more closely together.
As part of the improvements, we have seen new customization options for the Start menu, new gestures for the touchpad, an updated interface for the Account Control menu, and improvements for File Explorer.
In addition, we have seen the company pushing changes to Widgets, Windows Search, and more.
In the Experimental channel, Microsoft released builds 26300.9032, 26300.8935, 28120.2630, and 28120.2546, while the Beta channel introduced builds 26220.9022, 26220.8925, 28020.2623, and 28020.2539 for versions 26H2, 26H1, and 25H2.
In this recap, I'll highlight the latest and most noteworthy changes available through the Windows Insider Program.
These are the most significant changes Microsoft has unveiled since my last roundup.
Starting with the release of build 26300.9032, the operating system ships with an updated version of Windows Search that can now automatically find and search other folder locations based on your activity.
The new feature uses signals, such as files and frequently accessed locations. According to the company, this helps to make relevant files easy to find without requiring manual indexing.
The feature is known as "Automatically find additional relevant locations," and it's located on Settings > Privacy & security > Search.
In addition, Microsoft didn't mention this, but I've noticed a new "Search the contents of online files" on the same page, which allows you to decide whether Windows Search can search online content.
The Phone Link companion flyout that appears in the Start menu is getting an update on build 26300.9032 that allows you to hover over a recent message or notification in the "Recent" section to preview the content without extra steps.
This improvement requires the Phone Link app version 1.26021.3.0 or higher.
In the Experimental channel, build 26300.9032 (version 25H2) also introduces changes for the adaptive hibernate policy to prevent hibernation when the battery is above 80 percent and to hibernate when the battery falls below 10 percent.
Microsoft accomplishes this by increasing instances of instant-on resumes from Modern Standby and increasing battery preservation at the low end of the battery.
This change is also available on builds 28120.2630 and 28020.2623 for version 26H1.
On build 26300.8935, File Explorer received three specific improvements. First, the company made file deletion faster when deleting large and fragmented files.
This update also makes the Home page faster, and finally, the "Recommended" section on the Home page now supports touch scrolling to make it easier to browse files from the carousel.
In addition, starting with build 26220.8925 for version 25H2, the "Details" view now shows file sizes with appropriate units, such as KB, MB, and GB, instead of only showing KB.
Furthermore, on the "Home" page, you can now use a middle mouse click to open folder locations in new tabs.
The preview build 26300.8935 also updates the animated icons for the Widgets entry point in the Taskbar.
First, the icon now matches the system accent color instead of the red color. Also, the animated icons can now show more dynamic content if notifications are enabled in the Widgets dashboard.
On build 28120.2630 (Experimental channel for version 26H1), Microsoft is making system updates less disruptive by reducing the number of restarts users face each month.
This is possible thanks to a new unified update experience that coordinates driver, .NET, and firmware updates with the monthly quality update, consolidating updates into a single monthly reboot instead of multiple interruptions.
The company is also expanding update pause controls, allowing users to extend update pauses as many times as needed.
These improvements are also available for build 28020.2623 in the Beta channel for version 26H1.
Builds 28120.2630 and 28020.2623 for version 26H1 add new gesture controls for Precision Touchpads through the Settings app.
The new options will work across most apps, although apps built with WinUI 3 will require updated WinAppSDK 1.8 or 2.0 support before they can take full advantage of the changes.
The new controls include scroll and zoom speed, which lets you adjust the default speed for scrolling and pinch-to-zoom gestures. Also, accelerated scrolling will allow you to increase scrolling speed the longer you continue scrolling, making it easier to move quickly through long documents and webpages.
These improvements are also available for build 26220.8925 in the Beta channel for version 25H2.
Starting with build 28120.2546, Microsoft is adding support to remove smart card policies in Azure Virtual Desktop (AVD) and Windows 365 sessions that use Microsoft Entra ID authentication.
As a result of this change, administrators can configure remote sessions to automatically disconnect when a redirected smart card is removed, helping improve security and meet compliance requirements.
This improvement is also available for build 29639 in the Experimental channel for version Future Platforms.
Microsoft is making refreshable Braille displays easier to use with Narrator in build 28120.2546.
Windows 11 now supports HID-compatible Braille displays, allowing users to connect supported devices instantly over USB with no additional setup, or wirelessly through Bluetooth. The feature also works during the initial Out-of-Box Experience (OOBE), enabling you to configure a new computer independently.
These improvements are also available for build 28020.2539 in the Beta channel for version 26H1, for build 26220.8925 for version 25H2, and for build 29634 for version Future Platforms.
Starting with build 26220.9022 for version 25H2 in the Beta channel, the operating system introduces the ability to change the position of the Taskbar to the top, left, right, and bottom of the screen.
The new setting is known as "Taskbar positions," and it's available from Settings > Personalization > Taskbar > Taskbar behaviors.
When using this new functionality, Taskbar tooltips, flyouts, and animations continue to work in any of the positions, while most customization options, including never combining Taskbar icons, remain available.
This flight also introduces the ability to make the Taskbar smaller. The option is available from this page. However, in the Beta channel, the option works when configuring the "Show smaller app icons" option. In future releases, the company will add a dedicated button under the "Taskbar behaviors" setting, as it's currently available in the Experimental channel.
It's worth pointing out that these changes are still under development, and they may not work as intended.
On Windows 11 build 26220.8925, Microsoft is rolling out new Start menu customization options, including the ability to choose which sections appear in the menu and adjust its size.
The new customization settings are available on Settings > Personalization > Start. On this page, you can show or hide any of the sections, and you'll also notice that the "Recommended" section has been renamed to "Recent."
In addition, there's a new option to change the Start menu size, which means you can make the menu larger or smaller, or use the automatic option to let the system choose the size based on the configuration.
Finally, at the bottom of the page, under the "Other" section, you can enable the "Hide your name and profile picture on Start" setting to improve your privacy when projecting your screen to other people.
Microsoft is also refreshing the Account Control flyout in the Start menu with a more modern design and clearer Microsoft account information.
The updated interface adds a subscription badge, making it easier to check your account state, view available benefits, and explore upgrade options.
It also surfaces account benefits and storage details, giving users a centralized place to manage their Microsoft account without opening the Settings app.
This improvement is also available for build 29634 in the Experimental channel for version Future Platforms.
On build 29634 in the Experimental channel for version Future Platforms, Windows 11 also introduced Voice Isolation for Voice Access to improve speech recognition in noisy environments and shared spaces.
According to the company, the feature uses on-device processing for filtering background noise and nearby conversations.
In addition, Voice Access now includes three speech recognition models, including "Voice Isolation," "Remove background noise only," and "No filtering."
Looking back at the second half of July, I don't think this was Microsoft's most exciting set of Insider releases. A lot of what landed in the Beta and Experimental channels wasn't entirely new. Instead, it felt like the company was catching those channels up with features that had already appeared in other Insider channels as it continues to align the program.
I don't think that's a bad thing. It suggests Microsoft is getting closer to offering a more consistent experience across the Insider channels while focusing on improvements that people will actually notice.
I'm still waiting to see how quickly these features make it into the stable release. Microsoft has been moving faster recently, but Insider builds are still a preview of what's planned, not a guarantee of what will eventually ship.
What are your thoughts about these latest Windows 11 Insider changes? Let me know in the comments.
Explore more in-depth how-to guides, troubleshooting advice, and essential tips to get the most out of Windows 11 and 10. Start browsing here:

Join us on Reddit at r/WindowsCentral to share your insights and discuss our latest news, reviews, and more.




Your iPhone and your PC are about to get a bit closer. Apple is working on allowing your iPhone's clipboard to connect to your Windows 11 clipboard.
The feature was requested by Microsoft and after review, Apple has agreed to move forward with it. MacRumors first spotted the change and 9to5Mac expanded on that coverage.
Rather than just a friendly note, Microsoft reached out to Apple in the form of an EU Digital Markets Act (DMA) interoperability request.
At the moment, apps can only access an iPhone's clipboard if the app is actively running in the foreground. Apple will need to grant access to Microsoft to make clipboard syncing possible.
Apple already has a Universal Clipboard feature that works across iOS and macOS. That feature is one of many benefits of users being in Apple's ecosystem.
Microsoft argued that “cross-device copy and paste is a foundational productivity interaction that users expect to ‘just work’ across their primary devices."
Microsoft also described the use cases for the interoperability:
On June 26, Apple confirmed that it will make the feature available:
"We will introduce a new solution that will follow similar patterns to the Accessory Notifications and Accessory Live Activities frameworks that were introduced on iOS26.5. It will enable you to create an extension to share and import pasteboard items with paired accessories. The system will notify your extension when items are copied into the clipboard; then your extension can use the Accessory Transport Extension framework to share the contents with your accessory as necessary using available transports."
If the feature does ship, it will rely on Apple’s AccessorySetupKit, which is an API framework that requires authorization from both the connected Windows PC and iOS device.
Unfortunately, there are several caveats to the interoperability. First, it will likely not be ready until at least late 2027. Apple referred to creating the feature as a "significant engineering effort," and noted development will be complete by fall 2027. After that, the feature will enter beta and eventually ship to the public.
Even when the clipboard connection becomes available, it may be limited to users in the European Union (EU). When forced to create features or expand them across platforms, Apple sometimes only rolls out the changes within the EU. In other instances, Apple has released the improvements to everyone, regardless of location.
Microsoft has taken a similar approach when dealing with the EU. I would argue the best version of Windows 11 is limited to EU users because they have greater control over which apps are installed on their PC.


Join us on Reddit at r/WindowsCentral to share your insights and discuss our latest news, reviews, and more.

Microsoft's CVP of Design and Research for Windows and Devices, Marcus Ash sat down with the Windows Central Podcast to discuss ongoing work around Windows 11's UI, and how the company is moving to finally eradicate the OS of legacy cruft while maintaining backward compatibility where possible.
We started with Control Panel, which is everyone's go-to as a measurement for the progress the company has made to modernize Windows. Microsoft first began modernizing the Control Panel with Windows 8 over 13 years ago, and the work still isn't complete over a decade later.
Unsurprisingly, Ash says that the reason this has taken so long is that Microsoft prides itself on compatibility with legacy tooling and workflows, so it can't just rush in and modernize everything without first ensuring the modern replacements maintain functionality with what came before.
"That's why things like Control Panel get tricky, because if a customer has a driver or has something that depends on that legacy functionality, we just have to be careful about not breaking that compatibility promise," Ash said. "When we finally get things in Settings, we will then deprecate places say in Control Panel where we don't need that function anymore, we can carry it forward."

Ash highlights that modernizing legacy interfaces is as much about designing and building the new interface as it is about developing the tooling and UI frameworks to support the functionality required to build that modern interface, all while carrying forward the same capabilities, featureset, and performance.
"It also requires us to do work in WinUI 3 and some of these frameworks so that we can move things over at a rate that we think, one, customers can adopt and not break promises, but also just make sure we can test and we have the framework that supports all the things that our customers need. So we are pushing really hard to try to modernize, but we're also proud of the progress."
Ash says that legacy support in Windows is a strength of the platform, not a weakness. With that said, the company is exploring ways it can modernize legacy apps and interfaces while maintaining that legacy support. "There will be cases where, because of a customer that wants something that's important to them, we'll have some legacy UI, but even there we're trying to look and see: are there ways that through tooling and through better approaches we can just reduce that over time?"
In case you've ever wondered how Microsoft goes about choosing which legacy interfaces to modernize, Ash breaks down the process, confirming that "it's based on usage, telemetry, feedback. It's based on: where do we think the tooling is ready to move that surface forward? ... we just keep going through that and trying to make sure that over time, the amount of legacy UI that a customer would see in their day-to-day experience just gets smaller and smaller."

"We look at user journeys. Like if you were to look at File Explorer and you were to think about all the functions that happen in File Explorer, we then look left-to-right and say, okay, for this particular dialogue, where did the user start and where does the user end? So it's not just pick one dialogue, it's pick the full user journey of the things that the customer is trying to do."
Ash even teases that the company is looking at how it can evolve its tooling that that one day it can tackle modernizing apps like the Registry Editor. "I would say the common things that we look at are the top things that users/customers want: File Explorer and some of the big apps. But even things like Regedit and some of the tooling, we're already starting to take a look at and figure out: how would we attack this problem so that we keep a compatibility promise AND we can modernize these frameworks."
It's clear that Microsoft is eager to move Windows forward with modern designs that are consistent with its current design language, but that the company must ensure that these modernizations don't interrupt workflows or break compatibility. That's ultimately why it's taken so long for Microsoft to modernize legacy UIs across Windows, because the UI frameworks and tooling required to do it need to be built-out to ensure legacy support first.
Our interview dives into more topics, including optimizing the OS for 8GB RAM devices and why Microsoft sometimes chooses WebView2 over WinUI in certain apps and interfaces. Be sure to watch the whole interview on our YouTube!
The Windows Central Podcast is sponsored by Surfshark VPN. Unlimited devices, access your content from anywhere, and auto-block malware on Windows, Edge, and other platforms from $2.50/mo, with 4 months extra FREE. Register today!

Join us on Reddit at r/WindowsCentral to share your insights and discuss our latest news, reviews, and more.