I want to believe in the potential of Pavan Davuluri as the new leader of Windows development. His thoughtful approach and intelligence suggest he could be a positive force for change. However, trust is a fragile commodity, easily lost and challenging to restore, especially in light of Microsoft’s history of customer dissatisfaction.
This past week, Microsoft made a significant commitment to enhance the quality of Windows through 2026. This announcement has sparked a mix of skepticism and cautious optimism, echoing sentiments I’ve previously expressed in my writings, both critical and hopeful. While it’s natural to have hope for the future, it’s essential to maintain a clear perspective on the realities at hand and not to overestimate what Microsoft has communicated.
The communication in question—a 2000-word blog post by Davuluri—strikes a curious balance between specificity and ambiguity. Notably, it was directed primarily at participants in the Windows Insider Program rather than the broader customer base. Furthermore, the absence of an apology for past grievances is striking, although it’s important to recognize that these issues stem from the actions of Davuluri’s predecessors and their leadership.
Checking the checklist
Reflecting on the current state of Windows, I often refer to my Windows 11 Enshittification Checklist, which outlines various issues that have escalated to the forefront of my concerns. In fact, I recently published a book titled De-Enshittify Windows 11, where I delve into these specific areas of concern. It’s reasonable to scrutinize whether Microsoft will take meaningful steps to address them.
Forced telemetry
The first item on my checklist is forced telemetry. Since the introduction of Windows 10, Microsoft has made telemetry mandatory, leaving users with no option to disable it through the user interface. Interestingly, the term “telemetry” is absent from Davuluri’s blog post, and there’s no mention of this topic, even indirectly. However, the extensive discussion around reliability suggests that telemetry may remain a key component in Microsoft’s strategy to enhance Windows, a change I don’t anticipate.
Bundled crapware
Next on the checklist is bundled crapware. Microsoft once offered a Signature PC program that allowed customers to purchase third-party PCs free of unwanted software. However, since Windows 10, the company has reversed course, incorporating bundled software directly into Windows and promoting it by default. While I didn’t expect Davuluri to use the term “crapware,” he does mention plans for a more relevant Recommended section in Start, which will surface apps and content tailored to user preferences. Yet, it’s clear that suggestions and recommendations will persist, requiring users to opt-out rather than being disabled by default.
Chaotic updates with new features every single month
Constant, unpredictable feature updates have plagued users since Microsoft adopted a Windows as a Service model with Windows 10. Davuluri does address this issue, but his assurances may be misleading. Microsoft plans to “reduce disruptions from Windows Update” by limiting required reboots to once a month, which is a positive step. However, the specifics around pausing updates remain vague, leaving users uncertain about the new time frames for such options.
Moreover, the recent change in naming conventions for monthly updates, now referred to as Security Updates, adds to the confusion. These updates, which include new features, should ideally be separated from security fixes to provide clarity and transparency—an aspect Davuluri does not touch upon.
Forced Microsoft account sign-ins
The requirement for Microsoft account sign-ins has stirred unnecessary controversy. While it is arguably the best choice for most users, the forced nature of this requirement has raised concerns. Davuluri does not address this issue in his post, leaving many questions unanswered.
Forced Microsoft Edge usage and related harassment
Another significant concern is the forced usage of Microsoft Edge, which has become a source of frustration for many users. Despite the absence of any mention of Edge in Davuluri’s post, he does acknowledge that Windows Search will continue to deliver web-based results, hinting at the ongoing integration of Edge into the Windows experience.
Arbitrary hardware requirements
When Windows 11 was first announced, its arbitrary hardware requirements sparked widespread debate. While these requirements now align with necessary security advancements, they have also been raised further with the introduction of Copilot+ PC. Davuluri’s post only briefly touches on hardware, suggesting that requirements will continue to evolve, which may not sit well with all users.
OneDrive harasses you to enable Folder Backup and then automatically enables it no matter what you decide
Microsoft’s approach to OneDrive Folder Backup has also changed, with the feature being suggested throughout the OS and sometimes enabled automatically. While recent updates have made it easier to manage this feature, Davuluri does not mention OneDrive at all in his post, leaving some users questioning the overall direction of this service.
What Davuluri really says and doesn’t say
A review of the checklist reveals that Microsoft is not reversing any of the problematic behaviors associated with Windows 11. While there are some positive changes regarding Windows Update and OneDrive, many critical issues remain unaddressed. This lack of acknowledgment is a sobering reminder for those who hoped for a more comprehensive overhaul.
However, there are indeed positive changes to note. The distinction between opt-in and opt-out functionalities is crucial, as many of the concerns raised in my checklist relate to default settings. Davuluri briefly mentions this in relation to widgets, but a stronger emphasis on opt-in configurations would be beneficial for users.
CFRs
Another point of contention is the Controlled Feature Release (CFR) system, which allows Microsoft to enable new features randomly after installation. While Davuluri acknowledges the need for easier access to new features for Insider Program participants, he does not address the broader implications of CFRs for all users, which is disappointing.
Copilot
Despite the numerous complaints surrounding Copilot, the term appears only a handful of times in Davuluri’s post. Microsoft’s commitment to integrating Copilot and AI into Windows will continue, albeit with a promise of more intentional implementation. However, the removal of certain entry points for Copilot does not equate to the removal of AI features, which may leave some users feeling frustrated.
Windows Insider Program
Addressing the Windows Insider Program, Davuluri promises improvements in reliability and transparency. However, the lack of a structured approach to feature releases remains a significant concern. The program has faced challenges for years, and while there are promises of reform, the path forward remains unclear.
Refactoring
Performance issues within Windows are a common experience for users, often attributed to the underlying architecture. Davuluri suggests that moving core experiences to the WinUI3 framework will enhance responsiveness, but skepticism remains regarding the effectiveness of this approach.
One step forward, how many steps back?
As we await the tangible outcomes of Microsoft’s commitments, it’s essential to maintain a balanced perspective. While there are positive developments on the horizon, many unresolved issues linger in the shadows. Windows remains a complex entity, and the journey toward improvement is fraught with challenges. Perhaps, with time, it can reclaim some semblance of its former glory.
