New Outlook Randomly Assigning/Overriding Categories to Calendar Items
I use Categories to color code and organize my calendar. In the New Outlook, the system is randomly assigning categories to some of my calendar items. For example, I have one item that has no category assigned, but now it uses my "Misc Meeting" category. Another one I'd already labeled with the "Analyst Team" category and now it's added "Phone Call" to the item (which is making the wrong color display). In both of these examples, if I right click to access the categories and correct them (or even just "Clear all categories"), once I submit, after a few seconds the incorrect category labels and colors come back. Help?
Critical Pen Hover & Stray Ink Issue on New Surface Pro 11 for Business with Slim Pen 2
Hello Microsoft Community and Support Staff, I am writing to report a critical and seemingly widespread issue with the pen input on the brand-new Surface Pro for Business, 13-inch (Intel model, often called Surface Pro 11 "Luna Lake"). The Core Problem: Pen Draws Without Touching the Screen When using the Surface Slim Pen 2, the device begins to register ink input while the pen is still hovering a few millimeters above the screen. It does not require any physical contact or pressure. This "hover-inking" makes handwriting completely unusable. As I write, any time I lift the pen to start a new letter or stroke, the pen continues to draw a line as it moves through the air to its next position. This results in messy, connected handwriting with unwanted "tails," completely defeating the purpose of having a premium inking device. This is Not a Defective Unit - It's a Replicable Problem Initially, I thought I had a faulty device. However, to isolate the issue, I have performed extensive testing: I have personally tested this on [3] brand-new Surface Pro 11 (Intel) devices. I have used [4] different Slim Pen 2s. The exact same hover-inking problem occurred on every single combination of device and pen. Furthermore, I have already performed all standard troubleshooting steps, including: Clean OS installation via Surface Recovery Image. Ensuring all Windows, driver, and firmware updates are installed. Running the Surface Diagnostic Toolkit (which reported no errors). However, the same issue continues to occur even after trying these methods. Additionally, it has been reported that the issue also appears on the latest Surface Pro 12-inch model with the Snapdragon X Plus, just like on the Surface Pro 11 that uses the Qualcomm Snapdragon X Elite instead of Intel’s Lunar Lake. (I do not own any Snapdragon devices myself. If you own a Snapdragon device and are experiencing the same issue, please share your feedback.)" Video Evidence: I have recorded a clear video demonstrating the problem. It shows the pen drawing while hovering on the Surface Pro 11 and makes unwanted tails on handwriting letters. Video Link: https://youtube.com/playlist?list=PLG_7BXFA-cL4evqe0RmRz--iFjDC1HVgT&si=EmEypaAqSyRozr67 Questions for Microsoft: Is this a known issue with the new Surface Pro 11 (Intel) model's firmware or drivers? What are the official steps to escalate this issue directly to the Surface engineering team for a fix? This is a major flaw in a flagship product that severely impacts its core functionality. I have submitted a formal bug report through the Feedback Hub, which can be found here: Feedback Hub Link: https://aka.ms/AAxzh27 I urge the Microsoft team to investigate this with high priority and release a firmware or software update to recalibrate the pen's Initial Activation Force (IAF). Thank you for your attention to this serious matter.MS Edge - Sidebar and copilot not working on Linux Ubuntu v24 LTS
Sidebar not syncing or accepting new app additions (+). Copilot button is dead/inactive. Sidebar settings are well configured. Using the latest version of the Ubuntu OS and MS Edge. Functionality appears to be absent as product was released without full functionality....Lame!
Help- When I go onto the chat on a teams call, everything zoom/glitches
Recently, when I've been on a teams video call (on my computer teams app) and I go onto the chat, the whole screen view has changed. It becomes sort of zoomed in and very difficult to navigate. I can only go up and down by trying to click up through the chat messages or by trying to zoom out a lot so that I'm able to see the chat exit sign and I am not able to see any of the people in the call or any of the functions like leave/mute.... If I'm able to reach the exit button, once the chat is left the screen view goes back to normal. It's really annoying, please let me know how to fix this. Thanks[SOLVED] Memory Integrity bounces back to "turned off" state after Windows restart - fast ring 19536
This is an old post and the issue is no longer relevant. This has been happening since a couple of builds ago as well. I turn on the Memory Integrity in Core isolation section of Windows Defender, then after a restart or two, I go check again and see it's turned off. it usually happens when I uninstall a program that needs to be restarted. but it also happens when I uninstall a software that does Not need Windows restart to finish uninstall process. https://aka.ms/AA6xajf[FIXED] Problem: Can't open unsafe ports on Edge insider
UPDATE: Fixed in Edge insider Version 79.0.280.0 (Official build) canary (64-bit) I need to open a custom port for WAC. I can do that with Google Chrome Canary 79 by adding this to the shortcut target: "--explicitly-allowed-ports=6666" and it loads the WAC console just fine. but when I do the same for Edge insider Canary, it won't work and still gives me the unsafe port error. Edge Insider Version 78.0.277.0 (Official build) canary (64-bit) Windows 10 latest ver WAC 1909
[FIXED] Anyone else having OneDrive high CPU usage problem after upgrading to build 19564?
Feedback on Feedback hub app: https://aka.ms/AA7bbm6 please add more details to it. thank you Tried restarting my computer 2 times already with 5/6 hours intervals. I let it run like that for hours, hoping it will finish whatever it is doing but nope, it always stays like that. anyone else having this issue on the same exact build?
