Stories
Slash Boxes
Comments

SoylentNews is people

posted by mrpg on Saturday June 23 2018, @05:54PM   Printer-friendly
from the systemd dept.

If you've been trying to keep Microsoft's forced updates and upgrades off your machine, your job just got harder. With KB 4056254, we now have a new Win10 Update Facilitation Service joining its comrade-in-arms Update Assistant V2 to ensure no patch gets blocked.

You can look at the new KB 4056254 Win10 Update Facilitation Service and the re-emergence of Win10 Update Assistant V2 from two different perspectives. On the one hand, you have those poor hapless Win10 users who accidentally munged Windows Update. On the other hand, you have folks with bazookas and flamethrowers who want to keep some semblance of control over updating their machines.

Both groups now face two different Microsoft initiatives to reset Windows Update.

[...] Seems, from April to June 2018, some savvy Win 10 users have found new ways to disable or block Windows Update. So, M$ has to come out with KB4056254 to "neutralize" their efforts. It's like a cat-and-mouse game.

Which seems to me like the core of the matter. It's not nice to mess with Mother Microsoft's patching schemes, so you're going to get a few new services running in the background to whop your system upside the head if you dare to block patches.

Sources:
Win10 Update Facilitation Service joins Update Assistant V2 to make sure you get patched | Computerworld
Watch out: Win10 Update Facilitation as a Service and a new push for the Update Assistant | AskWoody


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1, Interesting) by Anonymous Coward on Sunday June 24 2018, @05:11PM

    by Anonymous Coward on Sunday June 24 2018, @05:11PM (#697630)

    Have run Windows since 1990. Learned to work my computer on MS-DOS 3.3, in the very beginning. I've been with Windows for a very long time.

    And then Windows 10 was released, and things have been on a steady downhill slide ever since then. The slide ended earlier this year with a crash into the ground when Win10 v1803 was pushed, unwanted, into one too many machines.

    That's when I finally had to admit that I have completely lost administrative control of my own, and my customer's machines. This is unendurable, and I am no longer putting up with it.

    Everything, my own, and my customers, is now being moved over to Linux Mint Mate. VirtualBox has been installed, and runs on all but the oldest machines in the group. (I have elderly customers on meager fixed incomes, unable to afford even the cheapest used computer, who are forced by brutal economic necessity to continue running ancient XP-era machines, and these machines run well without any need for a VM, performing just the bare basics that are what these people only ever wanted in the first place) I have butchered copies of Win7x32 and Win10 set up for VirtualBox if it becomes absolutely necessary to run something that has yet to be set up for Linux in any user-friendly way. The VM is shut down just as soon as such dirty work as requires MS, is finished. These VM's are destroyed and overwritten from an exported appliance .ova file on a regular basis, bringing them back to square one, each time.

    No more Windows, and it's for goddamned sure there's no more Microsoft Office, either.

    My people are all now happily running Linux, and so am I.

    Fuck you, Microsoft. Just fuck you to hell, ok?

    I will not miss you in the slightest, and my only regret is that I did not move my people off of your hateful Greedware any sooner than I did.

    Goodbye.

    Starting Score:    0  points
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  

    Total Score:   1