News for hackers. Stuff that matters.
Re:.NET on Linux – bye, Windows 10 by scandox on Monday October 17, 2016 @06:31AM (#12723870)
The real story here is the forced updates. How do people who are planning demos and presentations handle this? It's my worst nightmare.
Re:.NET on Linux – bye, Windows 10 by swsieber on Monday October 17, 2016 @10:32AM (#12725331)
Set back the system clock.

I watch movies on my laptop while I exercise. One day I was about to start exercising and Windows was like "Would you like to update now or in 10 minutes?" And I was like "I'm going to watch my movie," and set back my system clock, and surprisingly, it worked.

(I find this experience funny because moving back the clock was a knee-jerk reaction and it actually worked)

Re:.NET on Linux – bye, Windows 10 by qb45 on Monday October 17, 2016 @12:49PM (#12726727)
MSFT here. Thank you your report. I have escalated your issue to the Windows Update team. Microsoft is committed to your security and the loophole will promptly be closed by another forced update. Resistance is futile.
Re:.NET on Linux – bye, Windows 10 by eitland on Monday October 17, 2016 @02:11PM (#12727598)
Know you are joking but still want to mention:

A while ago I reported that the pw field in W10 gave away a lot of entropy easily (basically ctrl+arrow keys stopped between every character class so if your password was: newr..!VYIV you could in five seconds conclude that the password contains of 4 chars of something, then 3 chars of something else, then 4 characters of something other than the second group.)

Whoever handled it concluded that it was absolutely "interesting" but not a security issue so no bounty for me :-/

Re:.NET on Linux – bye, Windows 10 by tmzt on Monday October 17, 2016 @06:44PM (#12730500)
Hmm, combine that with a USB stick-like device and you could probably implement a brute-forcer that doesn't actually attempt most passwords, since key based editing of the original password would probably work.

This of course assumes the entered password is still on the screen.

Re:.NET on Linux – bye, Windows 10 by eitland on Monday October 17, 2016 @11:20PM (#12731770)
Didn't think so far as a USB stick.

That said, once you can leave a usb stick attached to targets computer I'd say all bets are off since at that point we can be reasonable secure that the target won't notice a USB or PS2 keyboard sniffer either, giving you plaintext passwords.

Re:.NET on Linux – bye, Windows 10 by tmzt on Tuesday October 18, 2016 @04:59AM (#12732988)
Was your original issue dealing with an already typed password? The stick would emulate a USB keyboard using something like a tiny and wouldn't be left attached. It would perform edits to the password and try to determine which charecters were special, the apply a simplified dictionary attack to the contiguous groupings of characters of the same class. The goal would be to reduce the space of the attempted guess. I don't see how it would be a practical attack though.
Re:.NET on Linux – bye, Windows 10 by qb45 on Tuesday October 18, 2016 @05:56AM (#12733167)
IIRC Windows has pretty strong rate limiting on login attempts. You don't really need a USB stick to execute them as fast as possible.
Re:.NET on Linux – bye, Windows 10 by CWuestefeld on Monday October 17, 2016 @08:17AM (#12724342)
Twice I've been bit by the unexpected updates during shutdown during a power failure. At home my UPS is only good for 5 minutes, so I want to shut down as soon as the power goes down. I do that, and Windows starts on "Installing 17 updates", with absolutely no way for me to intervene. And powering down in the middle of OS updates has to be about the worst possible time for it.
Re:.NET on Linux – bye, Windows 10 by ygra on Monday October 17, 2016 @08:21AM (#12724369)
It will simply roll back the half-finished updates and retry the next shutdown. Those things are done transactional. Powering down won't hurt it.
Re:.NET on Linux – bye, Windows 10 by Tharre on Monday October 17, 2016 @08:32AM (#12724437)
You mean pulling the plug instead of shutting down normally? I suppose that'd work but usually you only realize that Windows wants to update _after_ you hit the shutdown button. And powering the machine down in this state will likely result in an unbootable machine.

And good luck fixing that, especially if your hard-drive is encrypted.

Re:.NET on Linux – bye, Windows 10 by BorgHunter on Monday October 17, 2016 @09:54AM (#12724983)
What version of Windows do you use? My desktop uses the latest version of 10 (AFAIK) and the shut down button reads something like "Shut Down and Install Updates" when Windows wants to install an update. I also remember 7 having a little orange icon next to the shut down button when it was going to install an update.

Granted, I don't think there's a way to properly shut down without the update in an I-have-five-minutes scenario. But it does, at least, warn you.

Re:.NET on Linux – bye, Windows 10 by roblabla on Monday October 17, 2016 @10:25AM (#12725262)
IIRC there is. You can log out, and then have the option to not apply the updates (you'll have Shut down or update and shut down in the poweroff menu).
Re:.NET on Linux – bye, Windows 10 by petagonoral on Monday October 17, 2016 @02:16PM (#12727659)
You can shutdown without applying updates if you use 'Alt + F4' to initiate shutdown
Re:.NET on Linux – bye, Windows 10 by knd775 on Monday October 17, 2016 @11:28AM (#12725871)
Running shutdown -s -t 0 works.
Re:.NET on Linux – bye, Windows 10 by LoneWolf on Monday October 17, 2016 @12:51PM (#12726747)
Add a -f to that too, I have never seen a windows with pending updates install them with "shutdown -s -t 0 -f"
Re:.NET on Linux – bye, Windows 10 by coldpie on Monday October 17, 2016 @10:08AM (#12725114)
For what it's worth, I regularly "pull the virtual plug" on my Win10 VM during updates because fuck you it's time to go home, and I've never had it fail to boot the day after. It's obviously an unacceptable solution to the problem, but it's at least not disastrously fatal in most cases.
Re:.NET on Linux – bye, Windows 10 by ygra on Monday October 17, 2016 @09:21AM (#12724719)
Windows updates fall into various categories in how they are deployed (this also causes variations in whether you need a restart or not). The overwhelming vast majority of updates nowadays are deployed in a rather safe mode where nothing on the system is changed during install until at the very end effectively a switch is made to the newly-deployed components. Those updates tend to not care very much, or at all, about sudden power loss. The next start notices there's an unfinished update and either finishes it, or rolls back and you can try again.
Re:.NET on Linux – bye, Windows 10 by Tharre on Monday October 17, 2016 @09:43AM (#12724880)
True, but that doesn't really help you, does it. There is no indication on the screen which kind of update is currently being deployed. So shutting down your machine is still a gamble, something you definitely don't want on a production machine.

To use a car analogy: modern car's safety measures would probably protect me in case of an accident, but there is no way of being sure. So I'd rather avoid crashing into things at great cost.

Re:.NET on Linux – bye, Windows 10 by ocdtrekkie on Monday October 17, 2016 @10:15AM (#12725180)
As a Windows system admin, I can confirm this is incredibly rare. Windows is pretty darn good at recovering from broken update states.
Re:.NET on Linux – bye, Windows 10 by MertsA on Monday October 17, 2016 @02:07PM (#12727554)
Eh, honestly compared to other operating systems it's really not. Windows 10 is starting to get there.
Re:.NET on Linux – bye, Windows 10 by verbify on Monday October 17, 2016 @08:36AM (#12724459)
So the message 'do not turn off your computer' is just a suggestion?
Re:.NET on Linux – bye, Windows 10 by Aardwolf on Monday October 17, 2016 @08:41AM (#12724488)
"It's now safe to turn off your computer."
Re:.NET on Linux – bye, Windows 10 by pbhjpbhj on Monday October 17, 2016 @02:22PM (#12727720)
Why it couldn't be an "install updates now?" prompt with default set by the admin is beyond me.
Re:.NET on Linux – bye, Windows 10 by pbhjpbhj on Monday October 17, 2016 @02:17PM (#12727669)
Anecdotally I'm 1-for-1 on forced shutdown breaking Windows 10. It messed up the users user account; recovery was done by rolling back in System Restore.

So I'll go with powering down shouldn't hurt it.

It wasn't however update related. The user went to shutdown, the computer said "no" (apps are open, blah blah) and the user held the power button down.

Re:.NET on Linux – bye, Windows 10 by discreditable on Monday October 17, 2016 @10:54AM (#12725496)
> Powering down won't hurt it.

Usually. I see enough students who mess up their machines due to hard poweroffs during updates to say that sometimes it does not work out.

Re:.NET on Linux – bye, Windows 10 by pasta on Monday October 17, 2016 @08:30AM (#12724421)
In Task Scheduler, expand the Task Scheduler tree to go to Task Scheduler Library -> Microsoft -> Windows -> UpdateOrchestrator -> Disable Reboot task

In the folder %Windows%\System32\Tasks\Microsoft\Windows\UpdateOrchestrator remove write permissions for all users from the reboot file.

https://techjourney.net/permanently-disable-prevent-automati...

Re:.NET on Linux – bye, Windows 10 by jasonkostempski on Monday October 17, 2016 @09:43AM (#12724876)
Don't forget to do it again after any updates because MS will likely "fix" the obvious mistake you just made.
Re:.NET on Linux – bye, Windows 10 by pasta on Monday October 17, 2016 @09:49AM (#12724934)
Check point 6 of the linked article.
Re:.NET on Linux – bye, Windows 10 by croon on Monday October 17, 2016 @07:08AM (#12724012)
Group policy editor.

You can configure it to not update while anyone is logged in, only manual, at a set time, etc. It's just not in any of the "usual" settings menues. Likely rationalized by average users not disabling security updates by accident or something.

Re:.NET on Linux – bye, Windows 10 by geostyx on Monday October 17, 2016 @08:11AM (#12724305)
I love that group policy! It will still force a restart about every 9 days with that enabled, but it's much better than daily restarts.
Re:.NET on Linux – bye, Windows 10 by scandox on Monday October 17, 2016 @09:28AM (#12724766)
This seems a tad depressing...ever heard the Malcolm X quote: "If you stick a knife nine inches into my back and pull it out three inches, that is not progress"?

And yes I am completely aware that Windows 10 updates are in no way comparable to the civil rights movement and I am in no way making any such comparison.

I am just quoting a witty man.

Re:.NET on Linux – bye, Windows 10 by Grishnakh on Monday October 17, 2016 @11:48AM (#12726096)
I find it ridiculous that you feel the need to issue a disclaimer about a comparison between Malcolm X and Windows 10. It's a perfectly valid comparison, though obviously using hyperbole, and it's pathetic that you can't use a hyperbolic comparison like this without some stupid hipster bitching about it these days.
Re:.NET on Linux – bye, Windows 10 by keyle on Monday October 17, 2016 @08:36AM (#12724457)
I'm glad I'm not the only one that was mad about that. My PC just shut off and started doing updates, in the middle of the day.

My friend said "how much did you pay for Windows 10." I said "nothing, it's free update." then he said "There you go."

Re:.NET on Linux – bye, Windows 10 by vetinari on Monday October 17, 2016 @11:13AM (#12725680)
> My friend said "how much did you pay for Windows 10." I said "nothing, it's free update." then he said "There you go."

You paid for the original system that you updated from. If you are outside the 30-day window (which you are, because the free offer is over for more than 30 days), you cannot go back to the old system.

So you didn't get the system for free, you exchanged it for the old one. Just the act of the exchange was free, which does not make the system free.

Newly bought Windows 10 licenses are not free either.

Re:.NET on Linux – bye, Windows 10 by luckroy on Monday October 17, 2016 @09:24AM (#12724741)
Most no-cost Linux-class OS/WM's don't shut themselves down for updates.
Re:.NET on Linux – bye, Windows 10 by kefka on Monday October 17, 2016 @12:11PM (#12726368)
I'm sure I could write a cronjob that would be naggy and demand to do what Windows does.

And I could even use SELinux so even as root, couldn't kill it. That's what "System" is, right?

/grrrr

Re:.NET on Linux – bye, Windows 10 by DanBC on Monday October 17, 2016 @09:53AM (#12724977)
XBox One is expensive, and has a ridiculous amount of updating.
Re:.NET on Linux – bye, Windows 10 by wubbfindel on Monday October 17, 2016 @07:04AM (#12723997)
If your using Windows 10 Professional or above, you can change the Local Group Policy to prompt you for both downloading and installing updates.

For lower versions (like "Home"), there is a way to tell it that your connection is "Metered" and then updated won't be downloaded automatically; but that's not an official method to prevent updates.

Re:.NET on Linux – bye, Windows 10 by pritambaral on Monday October 17, 2016 @07:24AM (#12724079)
For public information: Wired connections cannot be set as "metered". Only wireless ones.
Re:.NET on Linux – bye, Windows 10 by verbify on Monday October 17, 2016 @08:38AM (#12724476)
Also for public information: There are hacks that allow wired connections to be set as metered:

http://www.windowscentral.com/how-set-ethernet-connection-me...

Re:.NET on Linux – bye, Windows 10 by wubbfindel on Monday October 17, 2016 @07:35AM (#12724132)
I didn't realise that, thanks.
Re:.NET on Linux – bye, Windows 10 by mattchew on Monday October 17, 2016 @09:56AM (#12725002)
This is indeed the worst. By itself it is enough to make me want to switch.

It's not the only thing, though. Win 10 is a decent OS in most ways, but there are too many places where it does things that I don't want and I can't (easily?) change.

I use Windows because I do C# development for a living. For now, it's not practical for me to switch, but maybe it will be in a few years. I'm hoping so.

Really stupid to drive developers off of your OS, Microsoft.

Re:.NET on Linux – bye, Windows 10 by Grishnakh on Monday October 17, 2016 @11:55AM (#12726187)
Since when do developers have much say in which OS they use? These things are decided by corporate policy and management in most places.

The best you can hope for here is that you can do the bulk of your C# development on a "rogue" Linux machine or VM, and then do some final testing and bug-fixing on Windows, since it's going to be deployed on Windows with customers (internal or external) who use Windows.

Re:.NET on Linux – bye, Windows 10 by eikenberry on Monday October 17, 2016 @02:36PM (#12727868)
Developers get a say in which OS the same way they get a say about lots of things, by finding a job that fits their desires. For example I decided a while back that my computer had become to integrated in my life for me to consider using a company provided computer, so I don't, and I haven't had any problem finding good jobs.
Re:.NET on Linux – bye, Windows 10 by abiox on Monday October 17, 2016 @05:31PM (#12729969)
> Since when do developers have much say in which OS they use

i predominantly work in java; and while windows is the "official" development environment (more by default than by decree) there weren't any objections or policies against using linux, as nothing in the workflow is tied to a single platform. (hooray!)

Re:.NET on Linux – bye, Windows 10 by Dinius on Monday October 17, 2016 @10:24AM (#12725255)
Simply stop and disable the windows update service, and turn it on when you have time to actually install updates. Been doing it this way for more than a year now without problems.

Of course you'll have to remember to turn it on to check for updates, but that's no different from using manual updates in past versions of Windows. The only downside is that certain things, i.e. Add/remove features might not work 100% while the service is disabled.

Re:.NET on Linux – bye, Windows 10 by Grazester on Monday October 17, 2016 @01:23PM (#12727085)
I was out in the field consoling into a cisco switch and I had my laptop restart(I had been cancelling it a while now and it got to the point where it just restarted)

It took the better part of 10 minutes to apply updates. Thankfully it was nothing pressing I was going on the switch. I have disabled auto updates with a registry hack. Microsoft isn't serious about Windows and is now treating it like an OS used for petty un-important work

Re:.NET on Linux – bye, Windows 10 by ivan_gammel on Monday October 17, 2016 @09:19AM (#12724708)
In Win 10 Anniversary Update you can specify active hours, when you use the device and it shall not be rebooted. Also, there's a setting for custom restart time.

http://betanews.com/2016/06/09/control-when-windows-10-insta...

Re:.NET on Linux – bye, Windows 10 by falcolas on Monday October 17, 2016 @09:29AM (#12724774)
I found out the hard way that you may only specify up to 12 hours as active, in one period. So, if like me, you use the computer in the morning and again in the evening, you are SOL.
Re:.NET on Linux – bye, Windows 10 by ivan_gammel on Monday October 17, 2016 @09:37AM (#12724819)
You can reschedule the reboot if it hits during your working hours beyond that period (second part of the article under the link shows the UI).
Re:.NET on Linux – bye, Windows 10 by gwbas1c on Monday October 17, 2016 @09:51AM (#12724954)
The updates drove me away from Windows 10 years ago.

I still have a windows machine for occasional games. What drives me nuts is "Install Updates and Shut Down" leads to a 15 minute boot time. WTF? I thought all that was supposed to finish before the computer turned off???

Re:.NET on Linux – bye, Windows 10 by coldpie on Monday October 17, 2016 @10:10AM (#12725135)
What games keep you on Windows? It is my job to solve that problem, we'd love to help you out.
Re:.NET on Linux – bye, Windows 10 by jaegerpicker on Monday October 17, 2016 @02:22PM (#12727711)
Star Wars: The Old Republic Witcher 3 Watch_dogs Overwatch Mirror's Edge (both games) Paragon

There is a general selection of games I play but can only play on windows. In general I settle for the Mac graphics stack proforming on par with Windows.

Re:.NET on Linux – bye, Windows 10 by unethical_ban on Monday October 17, 2016 @02:24PM (#12727737)
Overwatch - Windows/Mac only.
Re:.NET on Linux – bye, Windows 10 by coldpie on Monday October 17, 2016 @02:51PM (#12728035)
We're working on Overwatch, but DirectX 11 just isn't quite there yet :(
Re:.NET on Linux – bye, Windows 10 by kkarakk on Tuesday October 18, 2016 @07:32AM (#12733493)
reason why gaming on linux is never gonna take off - there is always some reason that the new hot game isn't gonna work. it's been a couple of months for overwatch, the initial hype is already gone - confirms my suspicion that if you have a linux gaming pc you essentially have a paperweight for playing older games that no one cares about
Re:.NET on Linux – bye, Windows 10 by coldpie on Tuesday October 18, 2016 @08:43AM (#12733819)
This is largely only true for huge AAA games. Lots and lots of indie games come out with support for Linux on day one, largely thanks to Unity. Indie games that don't have a native port frequently (though not always) work in Wine because they tend to be less demanding. Personally I don't like AAA games, so I'm actually pretty happy gaming on Linux these days.

So yes, it might be a paperweight if you're a big Call of Duty fan, but it's hardly a paperweight to everybody :)

Re:.NET on Linux – bye, Windows 10 by ocdtrekkie on Monday October 17, 2016 @10:16AM (#12725186)
"The updates drove me away from Windows 10 years ago."

This is amazing because Windows 10 is barely more than a year old!

Re:.NET on Linux – bye, Windows 10 by Tenhundfeld on Monday October 17, 2016 @11:08AM (#12725630)
Heh, I read it the same way you did, but I think the author's statement could be reworded like this: "10 years ago, the updates drove me away from Windows."
Re:.NET on Linux – bye, Windows 10 by ocdtrekkie on Monday October 17, 2016 @11:59AM (#12726234)
Heh, now that I look at it, you could definitely be right! Freaking English language. IMHO, the British can keep it.
Re:.NET on Linux – bye, Windows 10 by bkmartin on Monday October 17, 2016 @11:06AM (#12725622)
This can be turned off... You can use the group policy editor to set it up like windows 7. I just did this on my dev machine this weekend after being bit by it. Now I get notified of the updates available and can choose to install them at my whim. No more coming back to a rebooted machine and all my development windows, webservers, etc are no longer running. I have windows 10 pro, so I cannot speak to how this works in Home, but I would be surprised if a developer was using the Home version anyway.
Re:.NET on Linux – bye, Windows 10 by flipchart on Monday October 17, 2016 @11:18AM (#12725748)
Doesn't work in Home edition (edit: the group policy editor is not available). Cheaper laptops (which are still fine for lighter web dev) come with Home edition so there are a few people (me at least) who do have to live with the forced updates
Re:.NET on Linux – bye, Windows 10 by AlexeyBrin on Monday October 17, 2016 @01:48PM (#12727324)
> Cheaper laptops (which are still fine for lighter web dev) come with Home edition so there are a few people (me at least) who do have to live with the forced updates

Recently I bought a pretty expensive ASUS laptop, 2K and it comes with Home edition. At this point I can buy an upgrade license from MS for about $100 or buy a full retail Windows 10 license for > $200.

Re:.NET on Linux – bye, Windows 10 by tsomctl on Monday October 17, 2016 @11:18AM (#12725745)
I just disable the Windows Update service. Every couple of months, when I feel the need to clean up all my open pdfs and Chrome tabs, I'll enable it and restart.
Re:.NET on Linux – bye, Windows 10 by sk5t on Monday October 17, 2016 @01:06PM (#12726897)
Launch "Windows Update Settings" and review "Active Hours." The dialog claims, "When a restart is necessary to finish installing an update, we won't automatically restart your device during active hours."

Note that the use of "we" (instead of "Windows") is a tad unusual, and maybe a little ominous, for Microsoft.

Re:.NET on Linux – bye, Windows 10 by teh_klev on Monday October 17, 2016 @01:17PM (#12727012)
As mentioned in another comment, I have all these things configured and yet twice in that past seven days Windows 10 Pro has given me the 20 minute warning, right in the middle of my working hours. To add insult to injury for some reason the "Use a custom restart time" is now disabled.

I'd love to have the annoying old windows update nag box with the postpone button back.

Re:.NET on Linux – bye, Windows 10 by cptskippy on Monday October 17, 2016 @01:16PM (#12727001)
You're implying that the reboots occur at random without notification. They do not. Windows notifies you that updates were installed that require a reboot and that it will occur at off hours. If you ignore that notification then when the reboot is schedule to occur you receive another notification with the option to postpone the reboot for another amount of time.

I've had these forced reboots happen a couple times and it's disruptive but that's about it. The most disruptive was when I was working on a project and stopped for dinner then never came back and left my desktop on overnight. The next day I discovered that my computer had rebooted and was at the login prompt.

I can see how this would really suck for applications that do not respect the shutdown notification that Windows broadcasts but even the Arduino IDE dutifully saved my work.

I suspect that over time app developers will pay more attention to OS level event notifications and we'll get to a point similar to Mobile or even MacOS where apps can be halted and resumed at will. Personally that sounds like heaven.

Re:.NET on Linux – bye, Windows 10 by teh_klev on Monday October 17, 2016 @01:22PM (#12727070)
> You're implying that the reboots occur at random without notification. They do not.

Well actually......twice in the past seven days I had updates installed during my "work hours" and it still went ahead and did the 20 minute reboot warning thing during the same specified work hours in the same day.

Re:.NET on Linux – bye, Windows 10 by cptskippy on Monday October 17, 2016 @03:16PM (#12728352)
That's curious. I just checked and all of my machines have the reboot during off hours option turned on. I don't recall turning it on explicitly but it's entirely possible that I did, I'm usually not that thorough though.
Re:.NET on Linux – bye, Windows 10 by khedoros1 on Monday October 17, 2016 @03:13PM (#12728312)
> Personally that sounds like heaven.

It sounds like heaven to have the capability. It sounds like hell to be forced to use it just because the computer's doing something you didn't ask it to.

Re:.NET on Linux – bye, Windows 10 by cptskippy on Monday October 17, 2016 @03:19PM (#12728396)
The user isn't forced to use it so much as it just works. The feature itself is nice in for many reasons beyond the operating system rebooting after updates. Loss of power, system hangs, and program lockups come to mind as situations where it would be nice.

I think about my browser not restoring tabs after crashing and I shudder because that happens at least once a week. Notepad++ has had this saved state functionality for a while and I take advantage of it quite a bit. I think it would be great if every application did it. Most core Apple applications can resume after reboot.

Re:.NET on Linux – bye, Windows 10 by khedoros1 on Monday October 17, 2016 @04:13PM (#12729218)
> The user isn't forced to use it so much as it just works.

In the context of forced updates, one would be forced to use it (or deal with recovery of what they were doing on their own).

> Loss of power, system hangs, and program lockups come to mind as situations where it would be nice.

Absolutely. But in these cases, it's acting as a way from recovering from a system exception. The few times that I've recently had a system unexpectedly restart (pulled plug on a laptop with a dead battery, for instance), things like saved browser sessions were great. I just don't like it as the mitigation of negative effects of a system-enforced reboot.

Re:.NET on Linux – bye, Windows 10 by cptskippy on Monday October 17, 2016 @10:15PM (#12731522)
> In the context of forced updates

I was speaking more in general and less in that context.

> I just don't like it as the mitigation of negative effects of a system-enforced reboot.

I don't either but I don't consider it all bad. Honestly the session resuming capability of Android and iOS is a great selling point and one that's sorely missed on desktop operating systems. Apple has done a great job bringing it to their core apps but how widely available is it beyond that? In a way Microsoft's policy of forced updates might expedite the spread of this feature.

Putting my conspiracy hat on, Microsoft was and still sort of is pushing everyone towards UWP which promotes this sort of application design at the core. Maybe this is how they force everyone to it.

Re:.NET on Linux – bye, Windows 10 by skrebbel on Monday October 17, 2016 @08:22AM (#12724375)
Hibernate. I don't reboot more than once a month or so. It doesn't do on-bootup updates when you resume from hibernation.
Re:.NET on Linux – bye, Windows 10 by gaurav-gupta on Monday October 17, 2016 @03:14PM (#12728320)
Windows 10 is designed to keep your computer safe. It'll let you know when you can use it! No time limits. Safety first.
Re:.NET on Linux – bye, Windows 10 by GrumpyYoungMan on Monday October 17, 2016 @10:06AM (#12725098)
>The real story here is the forced updates. How do people who are planning demos and presentations handle this? It's my worst nightmare.

Manually run the update check every 2-3 days and run it again two hours before the presentation. Any updates that come out in that two hour window will allow you at least one delay.

Come on, folks, this isn't exactly rocket science here. Keep your OS up to date and, surprisingly enough, you won't have any problems caused by it being not up to date.

EDIT: May I also remind everyone that your corporate IT security policy almost certainly requires you to keep the OS on your work PCs up to date?

Re:.NET on Linux – bye, Windows 10 by roblabla on Monday October 17, 2016 @10:23AM (#12725246)
OS updates (or any update that potentially takes more than 2 minutes) shouldn't ever be forced. It's just terrible. Sure, there should be some prominant prompts saying "Plz update me" from time to time (so the average joe's computer isn't terribly out of date). But don't force me to update in the middle of prez. Because clearly, I'm best placed to know what's the best time for my computer to become an expensive paperweight.
Re:.NET on Linux – bye, Windows 10 by acdha on Monday October 17, 2016 @12:52PM (#12726757)
The problem is that if you don't make them automatic, people won't install them. Microsoft spent most of the Windows XP era with people being bitten by problems which had been patched in many cases years before.

The approach they've taken of making things mandatory is clearly not universally popular but most of the arguments about it tend to ignore the fact that it was designed to solve a very real problem which affected millions of people.

Re:.NET on Linux – bye, Windows 10 by roblabla on Monday October 17, 2016 @02:33PM (#12727840)
And yet macos doesn't have forced updates. They just prompt the user (with a very in-your-face message) and people DO update.

Same with linux.

Same with android.

Same with IOS.

If you prompt the user to update, they generally will.

Re:.NET on Linux – bye, Windows 10 by acdha on Monday October 17, 2016 @02:56PM (#12728094)
That's technically true but not true in real life for most people. Yes, you can ignore the notice for awhile but fairly soon you'll reach the point where something like iTunes requires a newer release or you need to upgrade iOS/Android because an app developer made the business decision that using a new API offers more benefits than supporting legacy devices.

There are two reasons why this works out better. One is that the non-Microsoft world isn't dominated by enterprise IT departments demanding binary compatibility with antique code; the second is that those platforms have spent many years building trust that major upgrades won't prevent you from working. In the case of Windows, that was complicated by charging for updates and the broken IT culture which resisted them amplified with the rough Windows Vista release cycle causing many people to avoid it for a decade.

Re:.NET on Linux – bye, Windows 10 by ramy_d on Monday October 17, 2016 @10:24AM (#12725261)
What if the update goes badly and locks the machine two hours before your presentation? Your post is probably the worst excuse for this behaviour I have yet to read and its frustrating, on so many levels, to see it being excused.
Re:.NET on Linux – bye, Windows 10 by GrumpyYoungMan on Monday October 17, 2016 @10:33AM (#12725344)
What if your laptop battery catches fire two hours before your presentation? It's just about as likely.

I am surprised to be asked by adults to think of a solution to a broken laptop given two whole hours in which to find a solution. (Hint: borrow somebody else's laptop.)

Re:.NET on Linux – bye, Windows 10 by ramy_d on Monday October 17, 2016 @02:50PM (#12728012)
Laptop batteries catching fire are such a rare and dramatic occurrence. A simple battery is much more likely in which case you should have come prepared with your charging cable, a very reasonable mitigation scenario. The difference here is agency - a user is empowered to bring the tools to ensure a best case scenario. When your OS decides restart time is NOW, you are not empowered. Quite the opposite.

Software is meant to serve us, not the other way around. Updates can wait for when we're ready, it's a purely coded decision to resolve otherwise. There is no value, worth, expertise, or pride to be extracted from being a slave to your machine which makes it all the more stunning that this is still happening to people today and that people like you can excuse it.

Re:.NET on Linux – bye, Windows 10 by jongalloway2 on Monday October 17, 2016 @01:00PM (#12726843)
I do a lot of presentations, and I'm on the Windows Insiders Fast Ring, meaning I get a new build about weekly, hence a lot more Windows Updates. I check for and install updates as part of my preparations before presenting. I've been doing this for years, on every operating system I present on (yay xcode updates over hotel wifi!). I've never had a problem with unexpected OS updates, because I run them explicitly. I do the same for frameworks and IDEs I'll be demonstrating. I'm surprised someone doing a presentation wouldn't make sure their software was up to date before doing a presentation, honestly. Not just because it makes sure you know the state of your software stack, but because you'll know if - for whatever reason - your demonstrations don't work or work differently on the latest software release.

End to end tech checks (including your software stack) is just part of respecting your audience.

I think some people run into surprise software updates because they do demonstrations on a virtual machine. I don't think that's a good idea, but if you're going to present on VM images, it's just good practice to test out your environment before you present on it.

Note: I'm not making any statement here about how I think software updates should be installed or how Windows works. I've blogged about controlling Windows Updates over the years, here's a post from a decade ago: https://weblogs.asp.net/jongalloway/438009. This comment is about how I make sure, as a developer and presenter, that software updates don't affect my presentations.

Disclaimer: Microsoft employee, Nazgûl

Re:.NET on Linux – bye, Windows 10 by TheSpiceIsLife on Monday October 17, 2016 @03:17PM (#12728366)
You work for an OS company. Your experience is by no means universal. Your way out on the far side of the bell-curve by about several light years.

What about non-tech savvy people who expect a computer to work like an appliance and "the bloody uupdate broke my presentation software".

The problem with the world today is there are too many bloody software dwvelopers, too many who seem so keen on sacrificing stability and compatibility with "The Next Thing".

As someone who works with computers and machines in a fabrication shop that, CNC machines that have never had a software update but they still work day in day out, and UI element that don't move or disappear on a weekly basis, I have to say my personal experience of smartphones and computers (Mac, Windows, Linux) is this: OH MY FUCKING GOD WHY DID THEY CHANGE THAT. WHY DOES IT DO THAT. STOP CHANGING EVERYTHING ALL THE TIME.

Yep, computers are huge piles of black-box shit to the average person, who expects their computer to be more like an appliance.

Re:.NET on Linux – bye, Windows 10 by kkarakk on Tuesday October 18, 2016 @07:40AM (#12733530)
1. you use the app everyday so you're excited/opinionated about UX and UI changes so you'll be vocal and help the developer improve your usage of the service 2. you use the app infrequently enough that you forget how to use it everytime so it doesn't matter if they change everything on you, it'll look new to you everytime
Re:.NET on Linux – bye, Windows 10 by cesarb on Monday October 17, 2016 @10:22AM (#12725235)
> and run it again two hours before the presentation.

Wouldn't two hours be too short to fix any problems caused by the update?

Re:.NET on Linux – bye, Windows 10 by khedoros1 on Monday October 17, 2016 @03:45PM (#12728856)
> Manually run the update check every 2-3 days and run it again two hours before the presentation. Any updates that come out in that two hour window will allow you at least one delay.

OK, it's possible to work around if you take special care. No one should have to pay that much attention to their update schedule.

> Keep your OS up to date and, surprisingly enough, you won't have any problems caused by it being not up to date.

The problem isn't caused by the machine being not up to date. It's caused by Microsoft requiring forced updates. The computer doing something disruptive that I didn't ask it to do is something that I associate with malicious software; it shouldn't be something that I expect from my OS.

> EDIT: May I also remind everyone that your corporate IT security policy almost certainly requires you to keep the OS on your work PCs up to date?

They do. I typically have 2 weeks of warning, and the chance to update anytime within that time period. I am warned repeatedly as the day approaches that the computer will restart on its own. Patch sets are released monthly, so it's not particularly onerous.

Re:.NET on Linux – bye, Windows 10 by hedora on Monday October 17, 2016 @10:24AM (#12725252)
It is seriously that bad now? You have to touch windows update three times a week?!?

That sounds like an even bigger time sink than the whole "find a new Debian derivative because Unity breaks the alt key, and systemd breaks everything else" thing.

Re:.NET on Linux – bye, Windows 10 by witty_username on Monday October 17, 2016 @10:57AM (#12725528)
You don't need to switch distros to install other desktop environments. What did systemd break?
Re:.NET on Linux – bye, Windows 10 by 9mit3t2m9h9a on Monday October 17, 2016 @12:06PM (#12726321)
In this specific context I'd guess startx/xinit