That distinction matters more than a changelog bullet. A one-time privacy configuration is not necessarily permanent on a Windows PC that receives feature updates, cumulative updates, policy changes, new applications and security-platform updates. At the same time, no third-party evidence in the available material establishes how consistently Premium restores settings in real-world conditions. And neither edition should be understood as a way to stop every form of data transmission from Windows, Microsoft services, or separately installed applications.
Build 3.5.1130 was released on September 2, 2026. It is available for Windows 10 and Windows 11 in x86, x64 and ARM64 variants. The update improves how the software applies and reports certain settings, rather than introducing Premium for the first time.
What changes in version 3.5.1130
The most consequential changes are not flashy, but they address a familiar problem with system-tuning utilities: knowing whether a requested change truly took effect.
O&O’s changelog says the update improves handling for settings identified as U004 and U005. Instead of deleting a value when reverting these particular settings, the software now writes the Windows default value. That is an important implementation adjustment. Deleting a registry or policy value can leave Windows to infer a default state, while explicitly restoring the documented default is potentially more predictable. The release also fixes persistence issues related to U004 and U005, suggesting that the older behavior did not always survive as intended.
Build 3.5.1130 also improves voice output and keyboard operation. For a utility with a long list of switches and recommendation levels, accessible navigation is a substantive quality-of-life improvement rather than a cosmetic addition. Users who rely on a screen reader or keyboard-only input should see better interaction with the application, although the supplied material does not detail every interface change.
Another practical addition is clearer reporting when Windows refuses a requested change. That is welcome because privacy tools can otherwise create false confidence: an option may look selected even if a protected system component, a management policy, or the operating system itself prevents the underlying alteration. The new reporting does not mean every denied setting can now be changed; it means the program is better positioned to tell the user that Windows rejected it.
The changelog further includes work involving Premium service behavior and protected settings, plus fixes concerning Secure Boot certificate status and an error associated with a Recall folder. These changes reinforce the picture of 3.5.1130 as a refinement release. They should not be presented as proof that every sensitive Windows privacy setting is controllable or permanently enforceable.
Premium is older than this release
One point needs correcting for anyone encountering announcements that frame version 3.5.1130 as the arrival of O&O ShutUp10 Premium. Premium predated build 3.5.1130: O&O’s May 20, 2026 release record for version 3.0.1076 already listed the Premium Edition, profiles, a background service, and automatic protection. An O&O blog post promoting Premium is dated June 11, 2026.
In other words, 3.5.1130 develops the Premium experience; it does not debut the paid edition.
O&O positions the two editions for different approaches:
- Free Edition: A portable, no-cost tool for manually reviewing and applying privacy-related Windows settings.
- Premium Edition: A paid, installed client and background-service product, listed from $14.90, with profiles and automatic reapplication of selected settings after Windows updates or relevant configuration changes.
For people who configure a personal PC once or twice a year, the portable edition may be the more appropriate model. It keeps the tool available on demand without adding another resident service. Conversely, people administering a machine where chosen privacy settings repeatedly revert may find the Premium proposition easier to understand: it is meant to monitor selected settings and put them back when Windows updates, Group Policy, or other system changes alter them.
That is O&O’s documented product claim, not an independently verified guarantee. The available evidence does not include external testing that measures whether the service catches every update-driven reversal, every policy conflict, or every protected configuration on all Windows editions and builds. Buyers should therefore treat the service as a convenience and enforcement mechanism with limits, not as a bypass for Windows administration or security controls.
The scope is now far larger than “50 tweaks”
Older descriptions of ShutUp10 often characterize it as a small collection of roughly 50 switches. That is no longer a useful description of the current product. O&O says it manages almost 300 privacy-related settings across more than 20 categories.
A larger catalogue can be valuable because Windows privacy, cloud integration, diagnostics, application behavior and account-linked features are not governed by one master switch. But scale also raises the risk of indiscriminate configuration. A list approaching 300 settings is not a checklist where more disabled options automatically equal better privacy or better security.
O&O itself warns that disabling some settings can affect system functionality, and the tool uses recommendation levels to help separate lower-risk changes from choices that deserve greater caution. That makes a measured approach preferable:
- Read the description and recommendation attached to each setting.
- Start with changes whose consequences are clear for the specific PC and user.
- Avoid bulk-applying every available option just because it is categorized as privacy-related.
- Record the changes made, especially on a work, school or shared household machine.
- Revisit the configuration after major Windows releases and after adding software that depends on Microsoft-connected features.
The Free Edition can offer a System Restore point and supports undoing changes, which are useful safeguards. Neither feature removes the need for care. A restore point may help recover system settings, but it is not a substitute for a current backup strategy, and it cannot make a poorly understood configuration decision consequence-free.
Why Windows may reject a setting
The new denied-change reporting is especially relevant in a Windows environment that increasingly defends some security configuration against local alteration. Microsoft states that Defender tamper protection blocks attempts to modify Microsoft Defender Antivirus settings through the registry.
This has two implications. First, a privacy utility should not be judged solely by how many toggles it exposes; it must accurately report the real state after an attempted change. Second, an automatic background service cannot reasonably be assumed to override every protection Windows applies. If the operating system, tamper protection, device management or an organizational policy rejects a modification, the service may be unable to impose the requested setting.
That limitation is desirable in many cases. Corporate PCs, school devices and systems enrolled in management platforms may have policies designed to keep security baselines intact. Trying to fight those policies through a third-party tool can create support problems, configuration drift, or policy violations. On such hardware, users should consult the responsible administrator instead of treating ShutUp10 as an authority over centrally managed settings.
Personal-device users should be similarly cautious around security-related options. The current documentation does not support the claim that ShutUp10 can simply disable Microsoft Defender. Its Defender-related controls concern sample submission and SpyNet or data-sharing behavior. O&O says the core antivirus engine, real-time protection and local signature-based scanning remain functional.
That boundary is significant. Reducing cloud-assisted sharing may be a deliberate privacy choice, but it can also reduce security telemetry or cloud-supported detection benefits. The trade-off is not merely technical: it asks whether the user is comfortable exchanging some data sharing for potentially less responsive protection against emerging threats. A privacy tool can expose the choice; it cannot decide the appropriate balance for every threat model.
Privacy settings are not a total data-flow blocker
The language used around Windows privacy tools often implies that flipping enough switches will stop Windows from communicating with Microsoft. That is too broad.
Microsoft distinguishes required service data from diagnostic data. According to Microsoft’s documentation, privacy choices for required or optional diagnostic data do not determine whether Windows sends required service data. Put simply, a setting that limits diagnostic collection does not necessarily stop all data needed to operate a Windows feature or service.
The same limit applies beyond Windows itself. Applications and services that run on Windows but are not considered part of the operating system manage data collection with their own controls. A browser, game launcher, cloud-storage client, communication platform, OEM utility or Microsoft application can have separate account settings, consent screens, privacy dashboards and network behavior.
This does not make ShutUp10 pointless. It means the tool is best understood as a way to manage a substantial set of Windows-level privacy-related configurations, not as a universal privacy firewall. Users seeking broader control will still need to review Microsoft account settings, settings within installed applications, browser permissions, synchronization features, advertising preferences, and the data policies associated with services they choose to use.
There is also a practical compatibility dimension. Turning off a feature connected to cloud integration, location, diagnostics, suggestions or synchronization can affect how certain Windows experiences behave. The right question is not “can this be disabled?” but “what function will be less capable, unavailable, or harder to troubleshoot if it is disabled?”
A careful deployment plan for Windows 10 and 11
For a typical home PC, the safest way to use version 3.5.1130 is as a review tool rather than a one-click hardening package.
Begin by making sure Windows is otherwise healthy and fully updated. Create a restore point if the application offers it, and ensure important files are backed up separately. Open the utility with sufficient privileges, then focus first on settings that match concrete preferences: whether you want particular diagnostic-sharing behavior, tailored experiences, advertising-related controls, cloud-connected features or location-linked behavior.
Apply a small group of changes, restart if requested, and use the PC normally. Check features that matter to you: Windows Update, Microsoft Store access if used, sign-in, notifications, search, synchronization, printing, games, accessibility tools, corporate VPNs and security software. If an unexpected problem begins after a change, use the program’s undo capability or restore the corresponding default instead of making unrelated changes in an attempt to fix it.
On a device that regularly resets preferred settings, Premium’s background service may be worth considering if the selected configuration has clear value to the owner. Its central promise is automatic reapplication, and that can be more useful than repeatedly reopening a manual utility after major updates. But it should be evaluated as paid software that introduces a persistent service, not as an infallible guard against Windows changes.
For managed devices, the best plan is usually not to deploy either edition without authorization. Settings imposed by Group Policy or device management may be intentional, and local changes can be reversed or denied. In that setting, a visible “denied” status is useful diagnostic information, not an invitation to work around the administrator.
Bottom line
O&O ShutUp10 3.5.1130 makes credible, practical improvements: more reliable default restoration for U004 and U005, better keyboard and screen-reader operation, clearer feedback when Windows blocks a change, and fixes around several protected or sensitive areas. It is a meaningful update for existing users, particularly because truthful status reporting is essential when operating-system protections can prevent a privacy adjustment.
The larger story is the product’s changed identity. ShutUp10 is no longer accurately described as an entirely free, small tweak collection that can disable Defender. The portable Free Edition is still free and manual, while Premium is a paid, installed service product. The documented setting catalogue has grown to almost 300 items, and the Premium service is intended to reapply chosen settings after updates or configuration changes.
Use it as a precise Windows configuration tool, with restore and rollback plans, rather than as a promise of complete anonymity or absolute control over the operating system. Windows can protect some settings, required service data remains outside the scope of diagnostic-data choices, and independently installed software retains its own collection controls. Those constraints are not a flaw unique to ShutUp10; they are the conditions any Windows privacy tool must work within.