Block Microsoft from running experiments in the Microsoft Edge browser
Browsers like Firefox, Chrome or Microsoft Edge come with built-in functionality to run experiments. Browser makers like Mozilla or Google may enable or disable features or changes in select browsers; this is often used to A-B test features or get early feedback on new implementations. While most users may not even notice that experiments are running in their browsers, it happened in the past that experiments caused issues. The latest case was revealed in November when administrators from around the world reported that a Chrome experiment would crash browsers in organizations worldwide. Negative side-effects of experiments are a problem for home users and business users alike, and it is often desirable to disable or block experiments from being downloaded and run. Microsoft distinguishes between controlled feature rollouts and experiments in the company's new Chromium-based Microsoft Edge web browser. Both are made available to part of the user base when they start to roll out but similarities end here. Microsoft notes: Microsoft Edge builds have features and functionality that are still in development or are experimental. Experiments are like CFR, but the size of the user group is much smaller for testing the new concept. These features are hidden by default until the feature's rolled out or the experiment's finished. Experiment flags are used to enable and disable these features. System administrators may use the "Control communication with the Experimentation and Configuration Service" on pro and Enterprise editions of Windows 7, 8.1 or 10 to prevent experiments in the browser. Here is what is needed for that: Get the latest Microsoft Edge policy file from the Microsoft Edge Insider website. It is likely that the policies will become available natively eventually when Edge is released and integrated in Windows. Extract the file (first a cab, then a zip). Open Windows > Admx. Copy the two .admx template files to C:\Windows\PolicyDefinitions\. Open the language folder that matches the system language and copy the .adml files to the corresponding language folder of C:\Windows\PolicyDefinitions\ Open Start, type gpedit.msc and hit the Enter-key to open the Group Policy Editor. Consult this Docs page on the Microsoft website for additional scenarios, e.g. when domain controllers are used. Open Computer Configuration > Administrative Templates > Microsoft Edge. Open the policy "Control communication with the Experimentation and Configuration Service" policy. Set the policy to Enabled. Set it to either "Retrieve configurations only" or "Disable communication with the Experimentation and Configuration Service". Retrieve will download configuration payloads only, disable won't download or enable them. The behavior of not configuring the policy differs depending on whether it is a managed or unmanaged device. Managed devices will download the configuration only while unmanaged devices will retrieve configurations and experiments. Source
Camera app not wirking
Hello, I am in the Relaese channel, 24H2. I have issues with my camera. Yesterday, Windows Hello and the camera app were not working but Zoom did. Today Windows Hello works but not the camera app. I get the message below. I tried ot unistall/reinstall the camera app and checked fir updates; I also tried to repair Windows with scc/scannow but it did not solve the issue. Would you have ideas? Thanks much
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 UserTouchpad not working after Windows 11 Insider Preview Update
Feature Update: Windows 11 Insider Preview 10.0.26220.6690 (ge_release_upr) Quality Update: Windows 11 Insider Preview Quality Update (26220.7271) Since installing these updates, my laptop’s trackpad (touchpad) has completely stopped working. I tried uninstalling the update, but the issue persists. In Device Manager → Human Interface Devices, the driver (I2C HID Device) shows the following error: Device status: This device cannot start. (Code 10) A request for the HID descriptor failed. I attempted updating/uninstalling the driver, but the error remains. Keyboard shortcut keys to enable/disable the touchpad also do not work. I had contacted Microsoft Support and even allowed remote access, but they were unable to resolve the issue. This problem started months ago after the Insider Preview update and has not been fixed yet. Requesting guidance or a fix for this issue.Feedback on Windows 11 & Vision for Windows 12
Dear Windows Team, As a loyal and long-time Windows user, I am writing to express my hope that Microsoft will take the opportunity with the next version of Windows (what the community calls "Windows 12") to address key usability feedback while making bold, innovative strides. While Windows 11 has made visual improvements, it still feels like a step back in user-friendliness and flexibility in several areas. My primary feedback is this: Please prioritize user control, customization, and a cohesive experience that respects the user's workflow. Based on the feature concepts and leaks circulating online, a "Windows 12" that incorporates the following principles would be a significant step in the right direction: Key Areas for Innovation & Improvement in a Future Windows Release 1. A Truly Flexible and Modern Start Menu The rumored "Windows 12" Start Menu concept is encouraging. Please deliver on this by: Bringing Back Flexibility: A resizable Start Menu/Screen that can function as a compact menu or a full-screen information hub is ideal. Enhanced Live Tiles: The concept of more dynamic and customizable tiles (with sizes, transparency, and animations) would be a welcome return of functionality many users loved. Clear Structure: A logically divided layout (Account, Shortcuts, App List, Pinned Tiles) would greatly improve usability over the current simplified design. 2. A Taskbar and Search That Empower the User Never Limit Functionality: Please restore the ability to never combine taskbar icons and to move the taskbar to other screen edges. User choice is paramount. Prominent, Powerful Search: A larger, rectangular search box that is highly customizable would be a clear improvement, making the primary search entry point more effective. 3. Superior Productivity & Multitasking Enhanced Snap Layouts: Supporting up to 8 snap groups and providing better layouts for ultrawide monitors is a must for power users. Revitalized Virtual Desktops: The ability to drag windows between desktops in Task View and the return of a robust Timeline feature for cross-device history would be a massive productivity win. 4. A Cohesive and Customizable Visual Experience Desktop Widgets: The ability to pin widgets directly to the desktop, rather than being locked to a sidebar, would make them far more useful and integrated into the workflow. Personalization: More lock screen customization (date alignment, photo effects) and the introduction of dynamic wallpapers and glass effects would make the OS feel more personal and modern. 5. Embrace Ecosystem and Compatibility Android Subsystem (WSA): Its return and improvement, especially full-screen landscape support, is critical. Please continue to invest in this. Expanded Controller Support: Native support for PlayStation and Nintendo controllers is a fantastic move for gaming accessibility. Relaxed Hardware Requirements: The rumored tiered approach for "Windows 12e" (low-spec) and mainstream versions without strict TPM mandates would be a welcome change, allowing more users to upgrade. 6. A Balanced Approach to "Classic" Features While the large-scale return of features like Windows Media Center and desktop gadgets is a bold concept, I urge caution. A future OS should look forward, not backward. Instead of re-integrating deprecated features, consider: Modern Replacements: Ensure that new apps (like the new Media Player and Mail/Calendar) are so good that users don't feel the need for old ones. Optional Installation: If classic features must return, make them available through the "Optional Features" menu or the Microsoft Store, keeping the base installation clean and performant. Conclusion My core message is this: We are eager for a version of Windows that feels both modern and powerfully familiar—one that doesn't remove features but enhances them. The concepts outlined for a potential "Windows 12" seem to understand this, aiming to combine the best of Windows 10's productivity with Windows 11's aesthetics, and then pushing further. I sincerely hope Microsoft listens to this feedback and builds a future Windows that is truly user-first, flexible, and a genuine joy to use. Thank you for your time and consideration. Sincerely, A Dedicated Windows User
Unable to Download or Update Apps in Microsoft Store – Error Code 0x800706D9
Hello everyone, I’m facing an issue with the Microsoft Store. I am unable to download new apps or update existing ones. Every time I try, I receive the following error message: Error code: 0x800706D9 I have already tried the following steps: Restarted my PC Signed out and signed back into the Microsoft Store Ran the Windows Store Apps troubleshooter However, the problem still persists. I am currently using Windows 11 Insider Preview Build 26120.6982 and I am part of the Windows Insider Program. Could anyone please help me understand what causes this error and how to fix it? Thank you in advance for your help.
Edge Dev CreateProcess bug
I'm using Edge Dev Version 143.0.3638.1 (Official build) dev (64-bit) downloaded from https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/3b9b41d3-7038-420a-bb07-66fe54926f0f/MicrosoftEdgeDevEnterpriseX64.msi Opening a new Edge instance by using the code: BOOL bRet = ::CreateProcess((LPCTSTR)L"C:\\Program Files (x86)\\Microsoft\\Edge Dev\\Application\\msedge.exe", (LPWSTR)L" --new-window www.bing.com", NULL, NULL, FALSE, CREATE_DEFAULT_ERROR_MODE, NULL, NULL, &si, &pi); is no longer working. I can see the process starting and then terminating quickly. It works though when using Edge Version 141.0.3537.99 (Official build) (64-bit). Is this the correct place to report & track the bug?
