O&O ShutUp10-free antispy tool for Win 10

ShutUp10 has never claimed to have realtime monitoring. In fact, when you close the program, they say you should rerun it after every windows update in case windows changes back settings.
I have done this and never had problems, but now when I check, Telemetry is enabled again even when I disabled it after the last updates, so it seems windows has changed something. We can only hope a new version of ShutUp10 will be released that can deal with this new behaviour.

 

But this feature request needs more than a set and forget installation, shutup now is portable and will require a setup/uninstall which kills its "auto" feature. I dont want it, dont need it. At least it could become paid.

 

Yes. That's exactly what happened. Since my post #148 now suffers from the ubiquitous forum Previous Page Post Death Syndrome, here again is the link that explains exactly what happened:
https://www.tweakhound.com/2021/03/18/oo-shutup10-issue/

Included in this report is the egregious manner in which MS changed this displeasing telemetry service to "Device Management Wireless Application Protocol (WAP) Push message Routing Service."

As my Uncle Bob used to say, "Those sneaky censored!"

In greater detail: After I toggled Disable telemetry to green, I checked the service and it was disabled. I rebooted and the switch was still green, the service was still disabled. While I didn't take a stop watch to it, in a few minutes, I checked again and the setting was red and the service reverted to its default Manual (Triggered). So if we can't call that realtime monitoring, let's call it Something Else.

According to the posts in Malware Tips and the O&O forum (quoting two O&O Engineers in #148 ): No. But, yes hope. Hope is eternal.

OK. This should alleviate post #148's Previous Page Death Syndrome to some degree. Until this page rolls over to page 8.

Cheers.

 

Thanks for the clarification, apparently I missed part of you post #148.
A workaround to Windows enabling it again is in post #25 here:
https://www.bleepingcomputer.com/fo...pletely-disable-telemetry/page-2#entry5141685

 

I have noticed that after reboot certain settings are either enabled or disabled again, not sure how this is possible. But I think Spybot Anti-Beacon may be a better solution to block telemetry since it blocks communication to certain servers without having to change certain settings in Win 10.

 

Sidebar: I had toggled to green Disable automatic Windows Updates and Disable Windows Updates for other products during my discovery of the Disable telemetry behavior. They had remained green until today. Now they're red. I use hibernation, so it's not restart dependent.

You're welcome. I thought some reiteration was in order as my post with all the nasty details drifted off to the previous page.

I haven't pickeded up on any info as of yet if that workaround, logical as it is, is effective. Windows' OS could just as easily hammer that back into compliance. Even in Pro, admin privs were gutted long ago.

Problem is, Windows requires telemetry to determine a system's readiness for service packs feature updates. Which is why I occasionally enable the telemetry settings in Shutup10 when running Windows Update during 2xHx seasons. The ease at which settings can be toggled, the export/import functions and the Actions menu features made ShutUp10 my choice.

Maybe dmwappushservice telemetry isn't a requirement for any updates, but I'd rather not find out.

As well, I've found over the many years that messing with Windows' exe's or service's inheritance and permissions is often more problematic than it's worth. Especially when it involves svchost.exe.

That's it for me. I'm going to keep an eye on this thread and other forums. As absolutely none of the feedback from O&O technical staff even hints at working on a relevant update for some WIndows' OS manipulation, indeed admitting defeat, I'm convinced this is a wrap.

 

Really? It's done with magic.

The FAQ reports support for Windows... 1809.

And I don't need an app to handle all the non-Windows stuff they list.

I'll pass.

 

Yes, Win 10 needs to respect certain settings, it's crazy. And I didn't encounter any problems with Spybot AB.

 

O&O ShutUp10 1.8.1420 Released (March 30, 2021)
Website
Announcement
Changelog

 

https://www.tweakhound.com/2021/03/30/oo-shutup10-1-8-1420/

Won't have a chance to verify this on my systems until the weekend. But TweakHound has been on the mark in all the years I've been following the site.

 

Upon restart, the "Device Management..." service startup type was Disabled but eventually reverted to Manual (Trigger Start).

Unlike ShutUp10 version 1.8.1419 where the toggle reverted to red, in version 1.8.1420 the toggle remains green:


Worthy of note, when I first examined the service a couple of weeks ago, its status was running. Since then, what ever triggers it to start has not yet occurred. Could be that Windows Update does it as I have Allow Telemetry disabled under Data Collection and Preview Builds and enable it tp level 3 prior to doing Windows Update. I disable it when done but don't check if that stops the service. I'll have to keep an eye on that. It could be that disabling Allow Telemetry prevents the service from running.

And in those two weeks, postings and reports in other arenas have gained momentum (and not only within the context of ShutUp10) evidently concur the unyielding restart reversion arrived with 20H2 along with the ill advised inheritance/permissions workaround and the sadly advised set to zero Allow Telemetry as zero does not disable the telemetry.

 

I have disable Onedrive enabled in Shutup10, but AppGuard still regularly blocks Onedrive related executable launches:

Code:

Prevented process <filecoauth.exe | c:\windows\system32\svchost.exe> from launching from <c:\users\user\appdata\local\microsoft\onedrive\19.033.0218.0011>.
Prevented process <onedrivestandaloneupdater.exe | c:\windows\system32\svchost.exe> from launching from <c:\users\user\appdata\local\microsoft\onedrive>.

I see the same here on Windows 1909 with ShutUp10 1.8.1420

 

ShutUp killed my LAN yesterday, glad i could revert the changes with its own saved settings and switches. But that did not helped for my other computer, i needed to change service settings (comparison). There is more under the hood and combined with its switches, could have been more worse. Be warned to do without backup or a lot of experience.

 

You should try to understand which setting does what first before you apply. Out of curiosity, which setting killed ur LAN?

 

I dont know, i reverted it all on both machines with the config before. Call it luck where experience failed to reset it manually

"killed the LAN" means web access yes, but access to other machines failed, incl. itself. Direct access with IP still working (Remote Admin working)

attachment: b working, c not - but only on one machine, on this one i need also to change service settings - thats curios because it worked before.

 

This, people love to always blame the "tools", when it's not the tool that "killed your thing". ShutUp is basically just hidden GPO registry switches all in once place. If you were using GP, you would say GPO killed your LAN.

 

I haven't experience similar problem with Shutup10 and have almost everything disabled. Maybe it's just that specific system or combination with some other software or other changed setting.

 

idd Shutup is to blame, not because of its existence, because of its poor documentation. Not the first time its switches not only affects a single purpose. Nevertheless, a warning for inexperienced people to stay away from such tools without a backup (image). it could have been more worse with w10privacy - and it was here when i tried it, but that was my beginning with windows 10, so i dont care. Shutup gave me some experience without destroying windows Anyone can check out the cfg files.

 

Got it. Thanks, @stapp.

 

I have also never encountered issues so far on Windows 10 1909, other than Windows Store not being able to install a video game, but it's not clear if it's caused by ShutUp 10 of course. But I was thinking if perhaps SpyBot Anti-Beacon is a better solution since it doesn't change any settings, it simply blocks communication with M$ servers.

LOL, good one.

 

O&O ShutUp10 1.8.1422 Released (June 15, 2021)
Website
Announcement
Changelog

 

News and interests in the task bar were also introduced to Windows 10 1909 with the May update. However, there is no option to disable it in ShutUp10.

 

News and interests is Cortana (SearchApp.exe), so disabling either should do.

Spoiler

Code:

takeown /s %computername% /u %username% /f "%WINDIR%\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe"
icacls "%WINDIR%\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe" /inheritance:r /grant:r %username%:F
taskkill /im SearchApp.exe /f
del "%WINDIR%\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe" /s /f /q

rem News and Interests / 0 - Show icon and text (default) / 1 - Show icon only / 2 - Turn off
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Feeds" /v "ShellFeedsTaskbarViewMode" /t REG_DWORD /d "2" /f

rem News and Interests Reduce taskbar updates / 0 - No / 1 - Yes
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Feeds" /v "ShellFeedsTaskbarContentUpdateMode" /t REG_DWORD /d "1" /f

rem News and Interests Open on hover / 0 - No / 1 - Yes
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Feeds" /v "ShellFeedsTaskbarOpenOnHover" /t REG_DWORD /d "0" /f

rem News and Interests Taskbar Menu / 0 - Hide / 1 - Show
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Feeds" /v "IsFeedsAvailable" /t REG_DWORD /d "0" /f

 

Thanks. I already had Cortana disabled in ShutUp10. I was planning to update my Windows 10 version anyway, so I have done it now and now ShutUp10 shows the option to disable News and Interests.