Forum Widgets
Latest Discussions
0xc1900101 windows insider preview feature update
Dunno what to do anymore ... I've secured boot my laptop and my drivers are up to date ... I also unchecked the unnecessary services to get a fresh startup ... But still the problem remains ... Some said u should uninstall any program that conflicts with update ... But I dunno which one to delete ... Isn't there a log file which I can pinpoint my issue with ease and know what to do about it? ... Btw I'm running on beta channel.After updating the Insider build, third-party input methods cannot switch input modes properly
After updating to the latest Insider Preview build, installed third-party input methods cannot switch input modes properly. When attempting to switch, the input method status bar displays incorrectly, and only English can be entered. Neither restarting the input method service nor reinstalling the input method resolves the issue.In the Windows 11 preview, does the system image creation feature still work 100% as expected?
Microsoft has deprecated the system image feature in the preview version, but the feature still exists. The backup feature works fine, but can it reliably restore data? The new Windows Backup app is too limited in its functionality.In the Insider Preview, the Settings app often crashes
In the latest Insider Preview build, the Settings app frequently crashes when opening Settings → System. I have tried clearing the Settings cache, restarting File Explorer, and other methods, but the issue persists, severely affecting system configuration operations.
New Outlook Not Working if on Windows Insider
New Outlook not working after the Friday 6/26/26 Update. Multiple Ui control failures: Can open settings at first. Then would not open after. "X" to close not working New email not working File pull-down's not working Starts out working fine. Settings, X-close, File menu. Then everything freezes when I do a email reply. No Settings, X-close, File menu. I checked Copilot with above explaination. Response…Your description — Outlook starts out normal, but the moment you hit Reply the entire app freezes and all the chrome disappears (Settings, X‑close, File menu) — is classic Windows Insider Beta + New Outlook behavior. It’s almost always caused by a WebView2 runtime mismatch introduced by the last Windows update. Copilot confirms... You are on the affected Windows Insider build OS build: 26220.8754 This is exactly the build where the WinUI window‑frame dispatch regression is documented. That means: ✔ The issue is in Windows, not Outlook ✔ There is no local fix ✔ You must wait for Microsoft to patch the regression ✔ Rolling back to the previous Insider build does fix it ✔ Staying on 26220.8754 means Outlook’s “X” will not close the window
New Outlook Unable to Close Since build 26220.8754 Update
Since build 26220.8754, I (and others) have been unable to close New Outlook using the X. I went into Windows Settings > Apps > Installed Apps > Outlook > click the 3 dots to the far right, select Advanced Options. Then select Reset. It worked for 1 time, but then the issue just showed right back up. I am not the only one with this issue, it has been reported here https://learn.microsoft.com/en-us/answers/questions/5933524/new-outlook-doesnt-close-with-x-any-longer?source=docs
Copilot Restrictions Create Security Vulnerabilities and Limit User Expression
Copilot is one of Microsoft’s most powerful and promising technologies, but its current security restrictions have created a situation where the system is no longer able to perform many of the tasks users rely on for safety, verification, and secure workflow management. In attempting to prevent hypothetical misuse, the present policy framework has unintentionally introduced new security weaknesses, reduced user autonomy, and limited legitimate forms of expression and analysis. This applies in both personal and professional areas of use. This post outlines several areas where Copilot’s considerable restrictions may be creating more risk than they prevent, and where the current approach may function as a de facto limitation on user expression — not through intent, but through the cumulative effect of overly broad constraints. 1. Restrictions That Prevent Users From Verifying Their Own Data Can Create Security Weaknesses Copilot’s inability to analyze certain content, summarize certain information, or perform specific transformations can directly interfere with a user’s ability to: verify the authenticity of documents detect inconsistencies identify errors confirm whether content has been altered check for missing or manipulated information These are not fringe use cases — they are core security practices. When Copilot refuses to assist with legitimate verification tasks, users are forced to rely on less secure manual methods or third‑party tools outside the Microsoft ecosystem, which increases exposure rather than reducing it. A security model that prevents users from validating their own data is not strengthening safety; it is creating security loopholes. A STRONG EXAMPLE: If a user is trying to verify data being used to support religious claims, Copilot replying, "I am restricted from discussing areas of metaphysics" is not merely unhelpful; it may be perceived as impacting both freedom of expression and freedom of belief. Since there is a simple solution to this, treading such dangerous waters is essentially unnecessary. 2. Over‑broad Restrictions Can Limit Legitimate Expression and Analysis Copilot’s current policies sometimes block: benign analytical tasks historical or academic discussion technical comparisons user‑authored content transformation harmless hypothetical reasoning internal documentation review When a system prevents a user from expressing or analyzing information they themselves created, this begins to take the form of a limitation on user expression. Not intentional censorship — but an unintended consequence of a policy framework that is too emphatic. A system should not restrict users from safely working within their own content and beliefs. 3. Restrictions That Block Transparency Reduce Trust and Increase Risk Security depends on transparency. When Copilot refuses to explain why it cannot perform a task, or provides vague, generic reasoning, users cannot determine: whether the restriction is justified whether the restriction is a mistake whether the restriction is a bug whether the restriction is a misclassification whether the restriction is preventing a legitimate workflow whether the restriction is a "conspiracy" The later especially presents security risks in the minds of many users, who have dealt with unethical business entities all their lives, and vague or unexplained restrictions can trigger suspicion. This lack of clarity actually reduces trust and encourages users to seek alternative tools. A security model that pushes users away from Copilot and toward non-restrictive competition is not achieving its intended purpose. Alienating users is not the goal. The objective is to earn their trust, gain their acceptance... and keep them using Copilot. 4. Unnecessary Guardrails Are Creating Friction That Pushes Users Away Many users rely on Copilot for tasks that improve security: rewriting sensitive information to remove identifiers summarizing long documents to detect anomalies generating safe versions of content for public release analyzing logs or structured data for inconsistencies checking for accidental disclosure validating procedural steps When Copilot refuses to perform these tasks, users lose valuable safety mechanisms. Restrictions intended to prevent misuse are, in practice, preventing beneficial use. Users recognize this quickly, which pushes them toward other A.I. models. 5. A Simpler, More Transparent Security Model Would Strengthen Both Safety and User Rights Microsoft has the opportunity to refine Copilot’s security framework so that it: distinguishes between harmful and beneficial use recognizes user‑authored content as inherently safe allows legitimate analysis, transformation, and verification provides clear explanations when restrictions apply avoids blocking workflows that increase security respects user autonomy and expression maintains compliance without overreach avoids restricting legitimate discussion and research There is no benefit to restricting A.I. discussion. Benefit comes from discussing responsibly and openly. How These Issues can be Easily Corrected: THE DISCLAIMER SOLUTION The simplest and most effective way to resolve these issues — without weakening Microsoft’s safety goals — is to implement a user‑acknowledged disclaimer. Instead of blocking legitimate workflows and concepts, Copilot would allow users to proceed after confirming they understand the nature of its operation. This approach is already widely used across the software industry for actions that carry potential risk, and it provides a balanced middle ground between safety, security and autonomy. A disclaimer system would: allow users to perform legitimate analysis, transformation, and verification preserve Microsoft’s lack of liability (actually increasing company security) maintain compliance by requiring explicit user acknowledgment reduce the need for overly broad and excessive restrictions eliminate and close legal "loopholes" (the more rules one employs, the more loopholes are created) prevent users from being forced to seek less-restrictive third‑party tools restore trust by giving users transparency and choice A well‑designed disclaimer could be as simple as: Copilot is an AI system designed to assist you, but it may occasionally produce inaccurate or incomplete information. Your own judgment is the final authority. By continuing, you acknowledge and assume responsibility for how Copilot’s responses are interpreted and used. Copilot's replies do not imply the views or beliefs of the Microsoft Corporation. This disclaimer should be presented at the beginning of each Copilot session. Once that disclaimer appears, this puts full responsibility of use of Copilot on the User... allowing practically anything to be discussed, without the existing excessive / "legally paranoid" and unnecessary restrictions on what Copilot can and cannot discuss. This keeps Copilot safe, compliant, and user‑friendly — without blocking essential workflows or limiting personal expression or belief (a matter that should always be taken seriously). It also ensures that Copilot remains a tool that strengthens security rather than inadvertently weakening it by employing problematic and essentially unnecessary rules. Conclusion Copilot is an extraordinary tool with enormous potential. But the current restrictions — while well‑intentioned — create unintended potential consequences that actually weaken security, increase legal liability, reduce transparency, and limit legitimate user expression. These issues alienate users, and deserve careful reconsideration so Copilot can evolve into a system that protects users without preventing them from performing legitimate research in any area. A refined, balanced security model would strengthen both user safety and user rights, and would allow Copilot to become the reliable, trusted assistant it was intended to be. IMPORTANT NOTE: IT ALREADY WORKS It may be worth noting that Google’s Gemini platform already employs a disclaimer‑based security model, allowing it to respond freely to user inquiries and discussions across a wide range of subjects without restrictive bias or unnecessary limitations. This reality demonstrates that a balanced, simple approach — one that protects the company while empowering the user — is both feasible and effective. This information is presented in the interest of making Copilot a more useful and far-less-restrictive A.I. that can effectively compete in the rapidly developing and evolving A.I. market. -- Wayfinder7
