News for hackers. Stuff that matters.
Re:Filezilla installer is suspicious again by nmg on Saturday June 23, 2018 @10:51PM (#17384682)
One of the most frustrating parts of Win10 is the update scheduling. You can request that an update be delayed, but the OS does not always honor the request as specified (settings - update & security - windows update - active hours).

In Win10 Pro, you can postpone an update for max 35 days (windows update - advanced options - pause updates), but never indefinitely. If a pending update will break your machine (and you know because you already had to uninstall it), there's nothing you can do; it will install in five weeks no matter what. It's a timebomb.

Adding insult to injury is that these are primarily "feature" updates, and the features are for Microsoft's benefit. The April 2018 update enabled "Timeline" in the Task View (Win + Tab). All session activity is now shared with Microsoft by default. It must be disabled in Settings - Security & Privacy - Activity Sharing... so I disable all the new less-privacy things I don't want, and there are a lot of them... a week later, they are all switched on again, without notification or consent, after a subsequent Tuesday update.

And this is the reboot I can't postpone, on the OS I purchased. It's part Heller, part Kafka.

Re:Filezilla installer is suspicious again by pssflops on Monday June 25, 2018 @01:09PM (#17393950)
Best advice for your situation: Assign the Windows Update service to an account (which doesn't have to exist in your Windows install [like ".\FFFFFFFFF"] ) and it will never succeed with updates again. You can remove the account and let it run as System if you want to restore Windows Updates functionality.
Re:Filezilla installer is suspicious again by sgroppino on Sunday June 24, 2018 @02:17AM (#17385237)
Are there no registry entries or system scheduler tasks that one can disable to stop the updates altogether?
Re:Filezilla installer is suspicious again by oxide on Sunday June 24, 2018 @11:48AM (#17386962)
I'm positive if it was a regedit away there would be wide spread dissemination of all relevant information and likely a very simple process for nuking it.