Windows became the default recommendation for years because it was the practical, low-friction choice for everyday users. But recent decisions have made that recommendation less automatic. Some of the concerns raised included: Trust in updates and security 🔒 There is growing frustration around Windows updates, including recent issues that caused boot failures and VPN problems on some Windows 11 systems. AI features pushed into the OS Microsoft’s Recall feature drew heavy criticism over privacy concerns because it was designed to capture and store screenshots locally to make on-screen activity searchable. Microsoft paused the rollout after backlash. More friction in the user experience 🧩 The piece also highlights hardware requirements, Microsoft account pressure, deeper OneDrive integration, and preloaded apps as signs that Windows is becoming less user-friendly for ordinary consumers. Windows 10 still held a large share even after support ended, while Windows 11 lost share over the same period. Thus, many users would rather stay with the old system than move to the new one. Microsoft may have a trust and product problem. #Technology #Microsoft #Windows #BillGates #USA #Money #Markets #Stocks #Finance
Multi-Gen Wealth Group’s Post
More Relevant Posts
-
🔥 Windows 11 25H2 Forced Rollout: Because Apparently We Weren’t Stressed Enough Well folks, Microsoft is at it again. They’ve decided that Windows 11 25H2 is happening to us, whether we like it or not. No opt‑out. No “remind me later.” Just a big corporate hand reaching into our environments and flipping the switch. Let’s break down the chaos we’re about to inherit: 1. Deferrals? Cute. Microsoft laughs at your deferrals now. All those carefully crafted WUfB rings and GPO delays? Yeah, 25H2 is about to plow through them like a drunk forklift operator. 2. This update is basically a personality transplant for Windows. New kernel bits, deeper AI hooks, more security enforcement… which is great until your ancient vendor app from 2009 starts screaming because it can’t handle modernity. 3. Drivers are about to expose your deepest sins. If you’ve been ignoring that one “mystery yellow exclamation mark” in Device Manager, congratulations — 25H2 is going to make it your entire personality for the next week. 4. Users will absolutely blame you personally. “Why did my taskbar move?” “Why did my PC reboot?” “Why is Windows different?” Because Microsoft said so, Karen. I’m just the messenger. What we’ll all be doing instead of sleeping: Testing LOB apps that should’ve been retired during the Obama administration Praying our RMM/AV/EDR agents survive the kernel changes Updating Autopilot profiles we swore we’d get to “next quarter” Watching Intune rings deploy like a slow‑motion car crash Writing cheerful comms to users while dying inside The real bottom line Microsoft wants a locked‑down, AI‑ready, one‑version‑to-rule‑them-all Windows ecosystem, and they’re dragging us along like a toddler pulling a dog on a leash. Admins who prep now will survive. Admins who don’t… well, I’ll see you in the trenches with 14 RDP sessions open and a gallon of coffee.
To view or add a comment, sign in
-
-
It’s been a long time coming, but Microsoft says it has some fixes in the pipeline that might make using Windows 11 less of a nightmare—and yes, one of those fixes has to do with scaling back how often Windows shoves Copilot down your throat... https://lnkd.in/gfUuxg54
To view or add a comment, sign in
-
Soon you’ll be able to use Microsoft Entra passkeys on Windows, bringing phishing-resistant, passwordless authentication to both managed and unmanaged Windows devices. The feature is currently entering public preview, and I’ve written a short article explaining what this update is and what you need to verify or configure to enable it in your tenant during the preview phase. Please keep in mind that during the public preview you must configure the AAGUIDs. Read the article here: https://lnkd.in/eaTkvmTA
To view or add a comment, sign in
-
Microsoft has officially begun force-upgrading unmanaged Windows 11 version 24H2 devices to version 25H2, marking the final phase of a staged rollout that relies on machine learning to determine device readiness. https://lnkd.in/gh7hmKT6
To view or add a comment, sign in
-
The future of Windows could include fewer ads and distracting upsells #Technology #SoftwareandApps #OperatingSystems #WindowsUpdates #UserExperience #TechNews Microsoft may finally be addressing one of the most frustrating parts of Windows 11: the constant ads and upsells. According to Scott Hanselman, one of the engineering minds leading the charge for...
To view or add a comment, sign in
-
Microsoft Urges Immediate WinRE & Setup Updates as 2026 Secure Boot Certificate Expiry Source: https://lnkd.in/dmkjs_yC Microsoft has issued an urgent advisory about the impending expiration of Secure Boot certificates, which will begin in June 2026. To help organizations prepare for this critical cryptographic transition, the company has released two essential updates: KB5081494 and KB5083482. Released on March 26, 2026, these dynamic updates target the Windows Recovery Environment (WinRE) and Windows setup binaries for Windows 11 versions 24H2 and 25H2. Failure to apply the necessary certificate updates could prevent devices from booting securely, leading to widespread downtime across enterprise and consumer environments.
To view or add a comment, sign in
-
-
Microsoft published more updates for WinRE. Here are two important takeaways from this article: -Microsoft broke WinRE on the same day Windows 10 reached end of support. The October 14, 2025 update — released on Windows 10's final day of mainstream support — caused the Windows Recovery Environment to stop launching on affected devices, leaving users without a critical last-resort tool for when Windows fails to boot. -The fix took months to arrive and offers little explanation. Microsoft's patch (KB5068164), covering Windows 10 versions 21H2 and 22H2, was eventually released but contains no technical explanation — only a brief note that it "addresses" the issue, raising further concerns about Microsoft's quality control among administrators and end users. If your business is still on Windows 10, for security reasons, we highly recommend migrating to 11 immediately. Reach out to us at Lume for help!
To view or add a comment, sign in
-
Windows 11 users are still encountering that annoying bright white flash when opening File Explorer—an issue Microsoft hasn’t fully squashed yet. Despite multiple updates aiming to fix the glitch, it keeps popping up on certain systems, disrupting the smooth user experience many expect. While the problem doesn't affect all devices, those hit have every reason to feel frustrated. Microsoft has been upfront about the ongoing work to resolve this, but no definitive fix is out just yet. If you’re seeing the flash, keep an eye on Microsoft's official updates for the latest. Find out more: https://lnkd.in/dKvE8sn3 #Windows11 #Microsoft #FileExplorer #TechUpdates #WindowsIssues #MicrosoftSupport
To view or add a comment, sign in
-
-
Microsoft Windows, The Most Insecure Operating System. Just watched a truly horrific video of Microsoft Windows 11 update coming down the pipe to force age verification at 1st time install/config of a new Laptop or Desktop. In a nutshell it is straight up wanting to take a picture of your legally issued ID before you can even sign in and "trust" Microsoft with that information, because they are doing it for the safety of your data. No thank you. I will manage my own data. From an admin point of view, doing IT means your usually the one setting things up for the end users, now your being boxed in to fundamentally associate your personal ID to a computer, that others will be using for whatever they choose to do. Whether for good or bad, this now creates a nightmare scenarios where the IT guy can now be legally tied to systems that he/she had no input on past initial setup, and the burden of legal costs and possible life impacting fallout from just doing your basic IT job. This is crap on a whole other Big Brother level os scary.
To view or add a comment, sign in
-
FORCED UPDATE: Microsoft is moving Windows 11 24H2 into hospice care and forcing all users to update to 25H2. Did you ask for that? No. Does Microsoft care? Hard to tell. Let's dive in.... The company is collapsing its support window early and using a machine‑learning–driven “readiness” model to determine when devices are silently moved forward. What’s missing is transparency: Microsoft offers no insight into the criteria, telemetry, or risk thresholds that govern this automated judgment. Windows is no longer a product you own - it’s a service you’re carried along by. And when the update pipeline becomes opaque, the trust model shifts from “I control my system” to “I hope Microsoft’s heuristics don’t break it.” The comments under the article reflect this tension. Some users fear bricked machines. Others threaten to disable updates entirely (a reaction that is understandable but operationally dangerous.) Forced updates on hardware that may not meet evolving instruction‑set requirements can render systems unbootable. Some may say that's paranoia; but to me it's a supply‑chain reality. The core issue isn’t the update itself. It’s the governance model behind it. When a platform vendor can unilaterally decide timing, eligibility, and delivery without disclosing the logic, the update mechanism becomes a single point of failure. Remember, a faulty preview patch already broke installations last month, requiring an emergency out‑of‑band fix. That’s the cost of opacity: when the system misjudges, the blast radius is global. In short (as Dickens liked to say) Windows is a platform that has outgrown the old social contract. Windows is now an ecosystem governed by telemetry, automation, and risk scoring - not user preference. That may improve security at scale, but it also erodes autonomy at the edge, and makes one wonder whether a system this critical should operate on decision logic no one outside the vendor is allowed to see. https://lnkd.in/gMx5dRnD #AuguryIT #microsoft #forcedreality
To view or add a comment, sign in