[Request/Suggestion] Suggestions for the September update
To the Microsoft technical team: Microsoft technical team, please don't play dumb; you've made a serious mistake. (Note: I previously posted this issue on multiple community channels and feedback hubs, but only received a few hundred views and a few replies. Since this issue severely affects the daily backups of multiple machines, and the official response has not yet been clear, I would like to request Microsoft to suggest an update in September or October to fix it as soon as possible, because everyone uses the archive history record, and I will go crazy without it.)This is not spam. I and other users have encountered the following issues: KB5120998 currently exhibits abnormal mouse cursor. KB5101684 and KB5120249 currently exhibit the following issues: files can still be backed up to the D: drive normally; the Last Backup time in File History is not updated correctly; newly created or saved Word documents, images, videos, etc., still show No previous version available in Content → Previous Versions. If you encounter the same situation as me, feel free to leave a comment below or post on any forum describing your problem. KB5101684 and KB5120249 update after file history issue screenshot:
Windows 11 Insider Build 26220.9223 fails with 0xC1900101
Hi, I am using Windows 11 Insider Preview and I cannot install Feature Update 26220.9223. The update downloads and starts installing. After the PC restarts, the installation fails and Windows rolls back to the previous build. Windows Update then shows the same update with a Retry option. Error code: 0xC1900101 Failed date: 23-08-2026 I have already restarted the PC and reset Windows Update components. The Windows Update and BITS services are running normally. Could anyone help me identify what is causing this error? Is there a known issue with build 26220.9223, or could a driver be causing the installation to roll back? Thank you.Win 10/11 file history is malfunctioning after an update why hasn't Microsoft fixed this issue yet?
Hello, I would like to ask whether other Windows 10/11 users have experienced the same File History problem. I also hope the Microsoft technical team can seriously investigate this issue. My laptop is running Windows 11 25H2. Before installing KB5101684, File History had always worked normally. In Control Panel → All Control Panel Items → File History, the backup time would update normally whenever files were backed up to my D: drive. Around July 28–29, 2026, at approximately 10:00 AM, before KB5101684 was installed, File History was still working normally. I want to make this very clear: I did not manually change my File History settings, delete Event Viewer entries, or modify or delete relevant registry settings. The problem started after KB5101684 was installed. I have already confirmed the following: File History is still enabled. The D: drive is working normally and can be accessed without any problems. After selecting Control Panel → All Control Panel Items → File History → Run now, files are indeed written to: D:\FileHistory\user\LAPTOP-GJTRIQFJ\Data\C\Users\user However, the "Last backup" time displayed by File History does not update correctly. Even after modifying a document, confirming that it was successfully saved, and then clicking Run now, the latest backup time and file versions do not update as expected. Under File Properties → Previous Versions, it still says: "There are no previous versions available." I also noticed that every time a backup runs, folders such as Desktop and Favorites under the FileHistory folder on the D: drive continue to have their modification dates changed, even when their contents have not actually been modified. What makes this even more concerning is that my Windows 10 22H2 desktop computer also started experiencing File History synchronization problems after installing KB5120249. In other words: Windows 11 25H2 → KB5101684 → File History problem Windows 10 22H2 → KB5120249 → File History problem This makes me seriously concerned that these problems may be related to a recent Windows Update change or regression affecting File History. To be honest, I am extremely frustrated with Microsoft. The problem is not simply that Windows has a bug. Any large operating system can have bugs. The real problem is that users have reported the issue, provided detailed testing results, identified the Windows versions and specific KB updates involved, provided the actual File History paths, and spent considerable time troubleshooting, yet it is already August and there still does not appear to be a clear official confirmation from Microsoft regarding whether these issues are related to KB5101684 or KB5120249. Users should not have to repeatedly troubleshoot the same problem without receiving a clear explanation or effective solution. I would like the Microsoft technical team to seriously investigate the following: Could KB5101684 be causing File History backup timestamps or version information to behave incorrectly on Windows 11 25H2? Could KB5120249 be causing similar File History problems on Windows 10 22H2? Why are files actually being written to the FileHistory directory while the "Last backup" time does not update correctly? Why does "Previous Versions" continue to report that no previous versions are available? Why do folders such as Desktop and Favorites have their modification dates changed during backup even when their contents have not been modified? Could this be a File History regression introduced by a recent Windows Update? Please do not simply ask users to repeatedly reset File History, reselect the backup drive, or recreate the File History configuration without investigating the underlying cause. Microsoft needs to determine what is actually happening. I would also like to ask other Windows 10/11 users who have experienced similar File History problems to leave a comment with the following information: Windows version KB update number Date when the problem started Whether the backup location is a local drive or network drive Whether the "Last backup" time is incorrect Whether "Previous Versions" is unavailable Whether files are still being written to the FileHistory folder Please also consider sharing this post or bringing it to the attention of other Windows users and the Microsoft technical team. The more independent cases Microsoft can compare, the easier it should be to determine whether this is a common problem. I am not asking Microsoft to guarantee that Windows will never have bugs. I am asking Microsoft to properly investigate problems that users have clearly reported, provide an explanation, and deliver an actual fix when appropriate. This issue has now continued into August, and I am extremely disappointed with the way the File History problem has been handled so far. Microsoft, please do not ignore this issue. Please investigate it seriously and provide users with a clear response and an actual solution. Thank you.Windows 11 to KB5101684 File History bug
Hello everyone, I have a question about Windows 11 File History. After updating my laptop to KB5101684, I modified a file today and confirmed that it was successfully saved. However, after enabling "File History" and clicking "Execute Now," the backup time still shows yesterday's date (2026/7/28), not today's. I have confirmed the following: The backup drive D is properly connected. File History is enabled. The File History Service is started and running normally. The backup location is set to drive D. The modified files and images were indeed backed up to:D:\FileHistory\user\LAPTOP-GJTRIQFJ\Data\C\Users\user However, in the "Restore Profile" section of File History, I don't see the new version date after today's modification. Additionally, I found that if I go to: Control Panel → All Console Items → File History → Select Drive → Select D drive again Newly created or saved Word documents, images, videos, etc., will still show "No previous version available" in "Content → Previous Versions". and then re-specify the same backup drive, then perform the backup, the update works normally; unlike before the update, where simply clicking "Execute Now" would create a new backup version. Furthermore, before this problem occurred, I did not change any File History settings, nor did I delete any related files or system folders, so I suspect the problem only started appearing after installing KB5101684. I would like to ask everyone: Is this a normal phenomenon? Could it be related to the Windows 11 update KB5101684? Does this indicate a possible anomaly in the File History database, settings, or related services? Has anyone else encountered the same situation after updating KB5101684? Currently, the original files can be opened, modified, and saved normally, and the backup drive is connected normally. I'm just worried that the File History isn't creating a new version correctly, so I want to confirm if further action is needed. Do you have any suggested troubleshooting methods, such as re-establishing the file history settings, checking related services, or other repair methods? Thank you for your assistance!
CRITICAL REGRESSION: Build 26200 broke Mic, Game FPS & Cursors!
System Specifications: Device: Acer Aspire 5 A515-57 Memory: 16GB RAM Storage: 2x 250GB SSDs OS Build: Windows Insider Preview Build 26200 (KB5120998) Edição Windows 11 Home Single Language Versão 25H2 Instalado em 18/07/2026 Compilação do SO 26200.9278 Pacote de recursos Pacote de Experiência de Recursos do Windows 1000.26100.360.0 Issue 1: Integrated Microphone Failure Immediately after installing this build, the integrated microphone completely stopped working and disappeared from the system inputs. The audio jack still accepts headset microphones, but the internal laptop mic is dead and undetected. Issue 2: Severe Performance/FPS Drop in Gaming Game performance has been severely crippled. In Dragon Quest X S Definitive Edition (Steam), I consistently reached 40 to 50 FPS prior to this update. Post-update, the game is heavily bottlenecked, only reaching 20 to 30 FPS. This feels like a major regression in GPU scheduling, driver compatibility, or background AI/VBS overhead introduced in this preview build. Issue 3: Custom Cursors (.cur, .ani, .ini) Blocked Applying custom cursors manually no longer works. Even after moving the custom cursor files directly into the official C:\Windows\Cursors directory, the system refuses to apply .ini, .ani, or .cur files. This feature worked perfectly prior to the update. Please investigate and fix these regressions in the 26200 flight. Attached are screenshots demonstrating the update build and the issues.
A Vision for Windows 12: Familiar Power Meets Modern Innovation
Dear Microsoft Windows Development Team and Community Hub, With the inevitable speculation around Windows 12, I wanted to share a comprehensive vision for the next iteration of Windows. The goal is to blend the best elements of past versions with modern needs, creating a truly powerful and personalizable operating system. Here’s what many users like myself are hoping to see: 1. A Revitalized Start Menu & Screen Fresh, Resizable Layout: A clearly divided Start Menu with dedicated zones: Account Area (top-left), Shortcut Area (far left for common folders), List Area (pinned, most-used, and suggested apps), and a Pinned Tiles Area (right side, four-column layout). It should be resizable by dragging its edges. Full-Screen Start Screen Option: A return of the full-screen Start that combines the easy-to-browse list from Windows 7 with the dynamic Windows 8.1-style Live Tiles, supporting both horizontal and vertical arrangements. Enhanced Tile Flexibility: Tiles in five sizes (small, medium, long, wide, large, tall) with smooth resizing animations. New customization options should include colorful, gradient, light, dark, transparent, and semi-transparent tones. Migration Friendly: When upgrading from Windows 7, 8.1, 10, or 11, all pinned apps and websites should automatically migrate. Copilot Integration: A dedicated, prominent Copilot Tile to highlight the AI assistant's role, perhaps with a new rainbow effect for visual flair. 2. A More Functional Taskbar & Search Comprehensive Taskbar: Featuring the Cortana icon, mobile devices, Start, Search, Task View, Chat, applications, and the system tray. Prominent Search Box: The search box should be more prominent, changing from a circle to a rectangular shape, serving as a stronger entry point. Flexible Search Menu: The search interface should be highly adjustable and consistent with the new Start menu's style. 3. Personalized User Experience Lock Screen Customization: Options for left or center-aligned date and time. New photo effects that highlight the main subject, allowing it to overlay the time. Windows Hello: Facial recognition that works while wearing a mask. Enhanced Widgets: Desktop Pinning: Widgets should be pinnable anywhere on the desktop, not just in a sidebar. Full-Screen Widgets Board: A full-screen mode with a widget panel on the left and news/feeds on the right, supporting up to six columns. New Widgets: Introduction of a 'Calendar', 'People', 'Microsoft Edge', 'Cortana Suggestions', and a dedicated 'Microsoft Store' widget. 4. Peak Productivity & Multitasking Task View & Virtual Desktops: A return to the mature Windows 10 experience, allowing windows to be dragged directly to other desktops in Task View. Timeline Returns: The Timeline feature should come back, including cross-device history. Classic Alt+Tab: The Windows 10 Alt+Tab window switcher experience should be restored. Supercharged Snap Assist: Enhanced Snap Layouts supporting up to 8 segments for large screens, with specific, intelligent layouts for ultrawide (21:9, 32:9) monitors. 5. Application & Ecosystem Evolution App Updates: New versions of Mail, Calendar, and People. The new Outlook app should fully support popular third-party email services like QQ, 163, and 126. A New Cortana: Multilingual support with the return of consumer skills (music control, smart home, third-party skills). It could be offered in two visual forms and power the 'Cortana Suggestions' widget. Screenshot Tool Upgrade: Should support full-screen recording. Media Player: The return of an appearance selector and support for live tiles. Microsoft Store Revamp: UWP Return: High-quality UWP and classic Metro apps should return to the store, with PWAs transitioning to UWP. Gaming Expansion: Addition of dedicated PlayStation and Nintendo Switch apps, including a Nintendo game section. 6. Visual & Nostalgic Enhancements Refined Aesthetics: Improved window transparency with a new glass effect, rounded rectangle system avatars, and a new top bar (weather, system tray, time). Dynamic wallpaper effects would be a welcome addition. Keep the Win11 Sound: The Windows 11 startup sound is great and should be retained. The "Bold Strategy" – Legacy Feature Return: To satisfy power users and nostalgia, consider the large-scale return of beloved features like MSN apps, Windows 7 Desktop Gadgets, Windows Media Center, Groove Music, HomeGroup, a significantly enhanced Tablet Mode, and Windows Ink Workspace. 7. Hardware, Compatibility & Core System Broad Controller Support: Native compatibility with DualShock 4/5, Joy-Con, and others. Android Subsystem (WSA) Return: WSA should return with a focus on fixing previous pain points, especially full-screen landscape app support. Separated Notification Center: The Notification Center and Calendar quick actions should be separated for a cleaner interface. "Next-Gen PC" Promise: Windows 12 should deliver on larger storage, longer battery life, more power, and enhanced security/stability. Enhanced Backup & Transfer: Windows Backup should expand to more regions and add support for backing up personal files and apps to external drives, including migration from old PCs or to new hard drives. 8. Core Versioning & Hardware Requirements A Fresh Start: Version 26H1, with an internal OS version reset to 12.0.0.0. Tiered Editions: Windows 12e (for education, 2GB RAM), Windows 12 (mainstream, 4GB RAM, removing strict TPM restrictions), and Windows 12 Ultra (flagship, 8GB RAM, unlocking all AI and performance features). Extensive Free Upgrade Path: A critical strategy, offering free upgrades from Windows 11 (including SE), Windows 10 (including S), Windows 8/8.1 (including RT), and Windows 7. Doubled Support Lifecycle: Home/Pro/Workstation: 24 months → 48 months. Enterprise/Education/IoT: 36 months → 72 months. In summary, we envision a Windows 12 that isn't afraid to learn from its rich history while pushing forward with modern innovation. It should be a system that respects user choice, empowers productivity, and welcomes everyone from legacy users to those with the latest hardware. If you like this vision and want to support it, you can upvote it here: https://aka.ms/AAylqhw Thank you for considering this feedback. Sincerely, A Passionate Windows UserImprove Voice Access Accuracy for Atypical Speech
Improve Voice Access Accuracy For Users With Atypical Speech Greetings, First, I would like to say that I appreciate Microsoft's continued investment in accessibility and speech-based computer control. Voice Access has the potential to be an extremely important accessibility tool for people who cannot reliably use a mouse, keyboard, or touchscreen. However, when i have test it on Windows 11 Pro 25h2 last public version update, Voice Access misunderstands a large portion of what I say even when using a good microphone in a silent room. So I recently joined the Windows Insider Program specifically to test the latest improvements to Windows Voice Access, especially the new Voice Isolation feature. I tested the new Voice Isolation feature and successfully completed the voice enrollment process. Voice Access was able to record my voice and create the voice profile without problems. However, after testing Voice Isolation, speech recognition accuracy remained very low, making me be sure to believe there is still an important accessibility gap for users with atypical speech. I have atypical speech due to a health condition and I use a breathing machine. The machine itself is very quiet, but it produces a small amount of airflow while I speak. My voice is also relatively low in volume and does not always follow the speech characteristics that modern speech recognition systems appear to expect. Even when I am in a quiet room with very little background noise, Voice Access misunderstands a large portion of what I say. This suggests that the primary problem in my situation is not simply environmental noise or interference from other speakers. The difficulty appears to be that the speech recognition model itself does not interpret my speech characteristics accurately. I have also noticed an interesting difference between languages. The English version of Voice Access generally understands me better than the Brazilian Portuguese version, despite Brazilian Portuguese being my native language. This suggests that recognition quality may also vary significantly between language models for users whose speech differs from the typical speech patterns represented in the training data. Voice Isolation is useful, but it is not speech training. I believe this distinction is extremely important. Voice Isolation appears to identify the user's voice and separate it from background noise, environmental sounds, or other people speaking nearby. That is valuable. However, identifying which voice belongs to the user is different from teaching the speech recognition system how that user speaks. Generally for someone with typical speech, improving the signal quality may significantly improve recognition. In the other hand for someone with atypical speech, however, the audio can be perfectly clean and still be interpreted incorrectly by the speech recognition model. This means that Voice Isolation can help the system hear my voice instead of the environment, but it does not necessarily help the speech recognizer understand my individual pronunciation and speech patterns. This is why I believe Voice Access would benefit enormously from an optional personalized speech recognition training system. Older Speech Recognition Systems Already Solved Part Of This Problem The application that has worked best for me so far is an accessibility program called Motrix, developed by UFRJ (Federal University of Rio de Janeiro): https://intervox.nce.ufrj.br/motrix/ Motrix is a very old application that uses Microsoft's SAPI 4 speech recognition technology. Despite being based on technology from the Windows XP/Vista era, it provides significantly better results for my speech than many modern recognition systems. One major reason is that it includes a built-in voice training process. The user reads predefined text, and the speech recognition system uses this material to adapt itself to the way that individual user speaks. After training, the system becomes better at interpreting that person's speech. This type of personalization was also available in older speech recognition products such as: * IBM ViaVoice * Dragon NaturallySpeaking * older speech recognition systems based on Microsoft SAPI These systems recognized that one universal speech model would not work equally well for every person. Modern speech recognition models are much more powerful overall, but many modern systems seem to have moved away from explicit per-user acoustic training. For most users, that may be acceptable. For accessibility users with atypical speech, however, personalized training can be essential. Why This Matters For Accessibility For someone using speech recognition primarily for convenience, a recognition error may only be an annoyance. For someone who depends on Voice Access to operate the computer, recognition accuracy can determine whether the computer is independently usable at all. Commands such as: "click" "scroll" "move" "open" "close" or application names must be recognized reliably. If a user has to repeat a command five or ten times, or if Voice Access consistently interprets the same pronunciation incorrectly, speech control becomes exhausting and unreliable. This problem becomes even more significant for users who use Voice Access precisely because conventional input devices are difficult or impossible for them to use. Accessibility software therefore needs to consider not only users with typical speech, but also users with: * atypical speech patterns * dysarthric speech * reduced speech volume * altered articulation * respiratory support * speech affected by physical disabilities *other speech characteristics that differ from the speech patterns commonly represented in large speech recognition datasets Not every user in these groups will have the same needs, and that is exactly why optional personalization would be so valuable. Suggested Feature: Personalized Speech Training I would strongly suggest adding an optional feature such as a personalized speech training and voice adaptation that could work similarly to older speech recognition training systems. For example, a Voice Access personalized speech training would ask the user to read a medium size text (5.000~7.500 character lenght) from a example text list so the system could then build a personalized speech profile that adapts recognition to the user's pronunciation and acoustic characteristics. Training could happen gradually. A basic training session might take only a few minutes, while users who need additional adaptation could optionally provide more speech samples over time. Personalized speech training seems to be the first priority to be implement in a future update. Ideally, this personalization would be stored locally on the device so it can work without internet connection and it could be reset, retrained, exported, or backed up by the user. Voice Isolation And Personalized Training Could Complement Each Other I do not believe Voice Isolation should be replaced. I believe it could become the first stage of a much more powerful accessibility system. For example: Microphone → Voice Isolation → Personalized Speech Model → Voice Access Recognition * Voice Isolation could remove unwanted audio and identify the correct speakers; * Personalized speech training could then adapt the recognition system to the way that specific person speaks. These are two different problems, and solving both would potentially make Voice Access dramatically more accessible. Command-specific Training Could Also Help Even if full personalized speech recognition is technically difficult to implement, a smaller first step could be personalized training for Voice Access commands. A user could record commands several times, such as: "click" "scroll down" "move left" "open Start" "show numbers" and so on. Voice Access could learn how that particular user pronounces those commands. For users who mainly depend on Voice Access for computer control rather than long-form dictation, even this limited form of personalization could make a major difference. Microsoft and Nuance Microsoft now owns Nuance, a company with decades of experience in speech recognition and voice accessibility technologies. Dragon NaturallySpeaking and related technologies demonstrated many years ago that speaker adaptation and personalized voice profiles can significantly improve recognition for individual users. Modern machine learning technologies should make it possible to revisit this concept in a much more advanced way. I hope Microsoft can combine the strengths of modern speech recognition with the personalization capabilities that older systems provided. Why I Am Submitting This Through The Insider Program I joined the Windows Insider Program specifically because I wanted to test these new Voice Access improvements and provide meaningful accessibility feedback before features become widely deployed. Voice Isolation is an interesting and potentially useful improvement, but my testing suggests that voice isolation alone does not address the main recognition problem experienced by some users with atypical speech. The speech recognizer needs a way to adapt to the user, rather than requiring every user to adapt their speech to the recognizer. That distinction is extremely important. Conclusion Please consider adding optional personalized speech recognition training to Voice Access. It could make Voice Access usable for people who are currently poorly understood by generic speech recognition systems. For users with atypical speech, this is not merely a request for slightly better recognition accuracy. It can determine whether voice control is a practical accessibility solution at all. Voice Access already provides an excellent foundation for hands-free Windows control. Adding genuine per-user speech adaptation could make it accessible to a much broader group of people. If other users have similar experiences, please consider supporting or upvoting this feedback so Microsoft can better understand the demand for personalized speech recognition. Please also keep the discussion respectful and constructive. Accessibility needs vary greatly between individuals. A feature that may appear unnecessary to one user can be essential for another. Thank you for considering this feedback and for continuing to improve accessibility in Windows.
