Is monthly BIOS updates via Intune overkill for enterprise Windows 11
Hey all, Looking for some opinions from others managing BIOS and Drivers on enterprise environments. We’re considering pushing BIOS/firmware updates monthly across our Windows 11 fleet using Intune, but it feels a bit too aggressive. Is anyone actually doing BIOS updates this frequently? Do you see real risk in not updating BIOS regularly? Or do you treat BIOS updates more as “only when needed” (security issue / vendor recommendation)? Any issues you’ve run into pushing BIOS updates at scale via Intune? My concern is stability risk vs actual security benefit — feels like monthly might be overkill unless there’s a critical vulnerability. Keen to hear how others are handling this in production environments.
macOS: SSO no longer fully functional on AVD (Win11 25H2)
Hello everyone, Since updating our Test Azure Virtual Desktop Session Hosts from Windows 11 23h2 to 25H2 (26200.7462) , we've been experiencing an SSO issue that exclusively affects macOS clients. Symptoms For macOS users (Windows App), the following issues occur: Example Teams Teams shows the user as "Unknown User" Chat and collaboration features fail to load Error message: "You need to sign in again. This may be a requirement from your IT department or Teams, or the result of a password update. - Sign in" After clicking "Sign in," only a window appears with "Continue with sign-in" (no PW/MFA prompt) After this, all other applications work without further authentication Technical Details macOS Device: AppleM4 Pro macOS Tahoe 26.2 Installed WindowsApp version: 11.3.2 (2848) dsregcmd /status: No errors detected PRT is active and was updated for sign-in Entra Sign-In Logs: Error code: 9002341 EventLog on Session Host (AAD-Operational): Event ID: 1098 Error: 0xCAA2000C The request requires user interaction. Code: interaction_required Description: AADSTS9002341: User is required to permit SSO. Event ID: 1097 Error: 0xCAA90056 Renew token by the primary refresh token failed. Logged at RefreshTokenRequest.cpp, line: 148, method: RefreshTokenRequest::AcquireToken. Observations Affects: Both managed (internal) and unmanaged (external) macOS devices Does NOT affect: Windows clients connecting via Windows App Interesting: If a macOS user starts the session (with the error) and then reconnects on a Windows device, authentication works automatically there Workaround The issue can be resolved for macOS clients by removing the "DE" flag from "Automatic app sign-in" in the following file: C:\Windows\System32\IntegratedServicesRegionPolicySet.json Questions Is this a known issue? Has anyone experienced similar issues with macOS clients after the 25H2 update? Why does this issue only occur with macOS clients? Why does SSO only work after removing the "DE" flag for macOS devices, and why are Windows devices not affected? I would appreciate any insights or confirmation of this issue! Thank you and greetings FT_1
OneDrive for Business sync client issue - not finishing
Hi all, I’m experiencing an issue where OneDrive does not finish synchronizing. It runs for about an hour. Upload is not starting until download worked fine. Everything seems to set up correctly: Internet connection is working No large file involved (9,9 MB of 10,3 MB) Logged in sucessfully Free space available loacally and in OneDrive No sync conflicts E3 License is active and paid No Windows updates Pending (Windows 11, version 24H2) Tried solutions: Restarted OneDrive Restarted Windows Paused and resumed sync Stopped and restarted sync What i am wondering: My local OneDrive version is not listed in the https://support.microsoft.com/de-de/office/onedrive-versionshinweise-845dcf18-f921-435e-bf28-4e24b95e5fc0 .... How can I identify the specific file causing the issue? I don’t see the filename currently being processed. Help highly appreciated :-) Regards, Eric
Delivery Optimization breaking Windows 11 update downloads?
We started seeing Delivery Optimization–related issues with Windows updates after upgrading devices to Windows 11 24H2. In our SCCM environment, Windows updates begin downloading but consistently fail or stall partway through the download. In many cases, the download restarts multiple times and eventually errors out. This behavior is consistent across multiple devices and different boundaries. These same devices were patching normally prior to the 24H2 upgrade. Since moving to 24H2, patching has become unreliable, especially for larger updates. From what we’re seeing, this doesn’t look like a traditional content or boundary issue. It feels like Delivery Optimization is failing mid-transfer or not resuming downloads correctly after the OS upgrade. So far we’ve checked the following: - Boundaries and boundary groups are unchanged - Content is available and distributed correctly on DPs - No recent SCCM site or infrastructure changes - Network connectivity looks normal On the client side, we’ve been reviewing: - DataTransferService.log (downloads start but fail or restart mid-way) - DeliveryOptimization logs (showing repeated retries / stalled transfers) - CAS.log and LocationServices.log (content location looks normal) - WUAHandler.log (update detection looks fine) Overall, detection and policy seem healthy — the issue appears during the actual download phase. Has anyone else seen Delivery Optimization downloads stall or fail during Windows patching after upgrading to Windows 11 24H2? If so, did you find a specific DO setting, policy change, or workaround that stabilized patching?
Windows 11 system tray on second monitor
can we have the system tray on second monitor option back in Windows11? I never understand why they remove this in the first place. This function has been in the older windows OS and its impactful and useful it comes in handy as well its annoying when I try to reach to the corner and cannot find the system tray on second monitor
Windows 11, version 24H2 known issues and notifications
Find information on known issues and the status of the Windows 11, version 24H2 rollout. For immediate help with Windows update issues, click here if you are using a Windows device to open the Get Help app or go to support.microsoft.com. Follow @WindowsUpdate on X for Windows release health updates. If you are an IT administrator and want to programmatically get information from this page, use the Windows Updates API in Microsoft Graph.
Surface Laptop 7, will not boot after system restore
Brand new Surface 7 13.8", just received the package yesterday. I've set it up for my wife, but shortly after network just started timing out querying the router's DNS server (Router is fine, multiple other phones, windows 10 & 11, linux, mac machines work without a hitch). Tried some fixes to no avail, and decided on a system restore just in case I've messed something up during setup. System restore looked like it worked, but laptop restarted and ended up with a bluescreen (something kernel something). System restore is there just fir that, right? Well, I've started it nine hours ago. Now it's just boot looping with the "preparing" bit and then shuts back down. It's been like that the whole day. I've even tried to get a USB stick to have the requisite livecd/recovery media, but it doesn't the new Surface ARM-based processor. What can we even do at this point?Window10, Update in Setting dont work correctly
The PC Health Check tool showed that my system meets the requirements. However, the Windows 11 Installation Assistant says I need to update to Windows 10 version 2004 or higher before I can upgrade to Windows 11. But when I open Windows Update, the window doesn’t display anything. What should I do to upgrade to Windows 11? I want to keep my software and data, so I don’t want to install from an ISO file.[BUG]Desktop Icon Order and File Explorer Window Size Not Saved
After updating to Build 26200.5661, I found two major issues: 1. The desktop icon order is not retained after reboot or shutdown. Every time the system restarts, icons are randomly rearranged. 2. The File Explorer window size is not remembered. It always resets to the default size after closing and reopening. These issues did not occur in the previous build. Expected behavior: - Desktop icons should retain their order and position. - Explorer windows should remember their last size and position
