Stories
Slash Boxes
Comments

SoylentNews is people

posted by cmn32480 on Sunday April 16 2017, @08:53PM   Printer-friendly
from the get-on-the-upgrade-treadmill dept.

Betanews reports on an announcement from Microsoft regarding its Windows 10 operating system:

[...] come May 9 it will stop updating the original release, known as 1507. The software giant had intended to stop supporting that release on March 26, but pushed back the deadline.

additional coverage:
Computerworld

related story:
Microsoft Kills Windows Vista On April 11: No Security Patches, No Hot Fixes, No Support, Nada


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: 5, Informative) by Zyx Abacab on Sunday April 16 2017, @11:46PM (5 children)

    by Zyx Abacab (3701) on Sunday April 16 2017, @11:46PM (#495014)

    The way Windows 10 schedules and enforces updates is with a bunch of tasks in the "UpdateOrchestrator" group. You could use TASKSCHD.MSC to remove the "Reboot" task, but all your changes get nuked after a while.

    Did you know that the Task Scheduler does not store its library in a sane way, like some sort of markup file? Rather, every scheduled task is stored as a binary file in a folder hierarchy right in the filesystem. It's like a shockingly-badly-designed version of Cron.

    Anyway, if you disable the task, then navigate to "%WINDIR%\System32\Tasks\Microsoft\Windows\UpdateOrchestrator"...and delete the "Reboot" file...and create a directory named "Reboot"...it'll both prevent the reboots from happening, and the restoration mechanism from undoing your change.

    It's completely insane that this works, if it still works. It's been a while since I switched to Linux. The last version I tried it with was build 14393.

    -----

    (Even so, please switch to Linux, if you can. With Windows 10, there are many more problems than just this.)

    Starting Score:    1  point
    Moderation   +3  
       Informative=3, Total=3
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   5  
  • (Score: 2) by Lagg on Monday April 17 2017, @12:05AM

    by Lagg (105) on Monday April 17 2017, @12:05AM (#495023) Homepage Journal

    Thanks for the tip. Hopefully it still preserves the actual prompt to reboot since that's the only way it's obvious that you have queued updates (sigh). And sadly I would use Linux (and do for things that require sanity such as code) but among other things work and video games locks me into it still and will likely do so for at least another year.

    --
    http://lagg.me [lagg.me] 🗿
  • (Score: 3, Informative) by Scruffy Beard 2 on Monday April 17 2017, @01:37AM (2 children)

    by Scruffy Beard 2 (6030) on Monday April 17 2017, @01:37AM (#495054)

    Sounds a lot like sytemd [freedesktop.org], actually.

    • (Score: 3, Insightful) by frojack on Monday April 17 2017, @03:45AM

      by frojack (1554) on Monday April 17 2017, @03:45AM (#495087) Journal

      Snort...

      systemd is clear-air transparent compared to windows 10.

      --
      No, you are mistaken. I've always had this sig.
    • (Score: 2) by Zyx Abacab on Monday April 17 2017, @04:26AM

      by Zyx Abacab (3701) on Monday April 17 2017, @04:26AM (#495101)

      Unlike Windows, Linux gives you choice: you can replace systemd with OpenRC or Minit, or just stick with SysVinit.

      Heck, I'd like to see any swapping-out of low-level system components with Windows. That'd really be something.

  • (Score: 2) by Arik on Monday April 17 2017, @04:36AM

    by Arik (4543) on Monday April 17 2017, @04:36AM (#495106) Journal
    "Anyway, if you disable the task, then navigate to "%WINDIR%\System32\Tasks\Microsoft\Windows\UpdateOrchestrator"...and delete the "Reboot" file...and create a directory named "Reboot"...it'll both prevent the reboots from happening, and the restoration mechanism from undoing your change."

    Hah. Yes, interesting to see if that still works. An old DOS trick was to make a directory with a particular name to prevent a file with the same name from being created. So for instance if you wanted Netscape Navigator to do session cookies but Netscape hadn't yet heard of session cookies, you could just go find cookies.txt, delete it, then make a directory named cookies.txt there. (On *nix you linked cookies.txt -> /dev/null instead but with DOS you had to be more creative sometimes.)

    --
    If laughter is the best medicine, who are the best doctors?