An update to update the updates.

I'm quite curious to see how it affects the performance of the machine

Businesses should really be using Windows 10 Pro not Home, that way they can disable either the automatic downloading of updates or the automatic rebooting (or both).

UbersonicBusinesses should really be using Windows 10 Pro not Home, that way they can disable either the automatic downloading of updates or the automatic rebooting (or both).

Businesses are using Enterprise. It allows for more than that. :)

but also requires the latest security upgrades

So what exactly would they gain by disabling Updates?
I wouldn't trust a company, that disables Windows Updates.

I have honestly never understood the complaints. Is rebooting like once a month really such a hassle? The problem was that it sometimes rebooted automatically when you used it, but that is far less a problem now.

_JP_Businesses are using Enterprise.

Most use Pro as usual, it's only the larger ones that use enterprise.

FrickI have honestly never understood the complaints.

Losing work because the machine decides it's going to reboot itself, machine decided to download/install updates when you're trying to use it, etc, etc.

OFC both of these can be fixed by disabling automatic updates and auto restarts, though the former is still useful for regular office computers (non workstations)

Vayra86An update to update the updates.

I'm quite curious to see how it affects the performance of the machine

It seems to be in the latest insider's builds and I've not seen any slowdown of the machine. The download/install online phase is pretty slow, but as it happens while you are using the machine and causes no apparent issues it's all good.

The off-line phases are getting less and less which is great.

Vayra86An update to update the updates.

It reminds me of Windows 7 with its:

To check for updates, you must first install an update for Windows Update.

:laugh::roll::laugh:

FrickI have honestly never understood the complaints. Is rebooting like once a month really such a hassle? The problem was that it sometimes rebooted automatically when you used it, but that is far less a problem now.

+1

UbersonicLosing work because the machine decides it's going to reboot itself, machine decided to download/install updates when you're trying to use it, etc, etc.

Just a few days ago I did this at work. No hassle, no problems, no interference with work schedule. Those guys run a mix of Ubuntu, Win10 Home and Pro on consumer hardware (laptops and pre-built desktops), and with update sharing on the local network it took a lot less time and effort than you'd expect. And I had to do that only because their employees are too lazy to do it themselves. They are all IT specialists, for christs sake (except for a pretty HR girl).
It's kind of ridiculous complaining about "tedious" and "time consuming" update process on windows, when your Android and iOS devices nag about updates every day, sometimes several times a day.
My HTC One is fairly clean (less than 10 third-party apps) and runs an older Android 5.0.2, but I still do get updates almost every day, and for some reason (maybe common sense), I do not complain about it.

silentbogoJust a few days ago I did this at work. No hassle, no problems, no interference with work schedule. Those guys run a mix of Ubuntu, Win10 Home and Pro on consumer hardware (laptops and pre-built desktops), and with update sharing on the local network it took a lot less time and effort than you'd expect. And I had to do that only because their employees are too lazy to do it themselves. They are all IT specialists, for christs sake (except for a pretty HR girl).
It's kind of ridiculous complaining about "tedious" and "time consuming" update process on windows, when your Android and iOS devices nag about updates every day, sometimes several times a day.
My HTC One is fairly clean (less than 10 third-party apps) and runs an older Android 5.0.2, but I still do get updates almost every day, and for some reason (maybe common sense), I do not complain about it.

basic user machines are not the issue any IT worth their snuff can setup system center to manage the updates so they happen on weekends, etc.

Sales people who travel still might find it annoying.

but you have this middle ground of test machines, workstations, etc where you really need them always performing their duties. So for compression engineers/graphic designers tend to setup their machines to run all weekend so the job is done when they come back on monday.

windows updates destroy that possibility.

testing software is similarly run after hours or on weekends, then come windows updates fubaring that up. (we also have offshore testing engineers who work opposite hours on purpose)

Network analysts setup crawlers to check things on a weekend, oops windows updates.

It sounds like your business certainly maintains no applications because seriously this is an obvious production issue.

The problem is Microsoft still isn't listening. The updates need to work like linux in which no reboot is required. That way the only way the above scenarios run into an issue is when the service they are running at night/on the weekend is the thing getting updated. Even then you can set the job to restart after the service does.


*insert required "its 2017, you shouldn't have to reboot" here*

@yogurt_21, here is the thing: these kind of updates don't happen every day, and normal companies, be it a small business of 2 people, or a large corporation of 1000 users, they should have provisions for this stuff.
Plus you do have an option to postpone the update to whatever time it is comfortable for you to update, and if my memory is not failing me completely - there is a textbox in an update window which clearly states that you can alt-tab and do your stuff while it's doing the update magic. So, I don't see any feasible scenario, in which the Creators Update may cause an unplanned disruption of work process.

yogurt_21*insert required "its 2017, you shouldn't have to reboot" here*

Any OS, be it OSX, iOS, Android, FreeBSD, Ubuntu or Windows, requires you to reboot after a major update. At this point of time a claim of "There can be no reboots in 2017" is a total fiction... overactive imagination... something desirable but definitely not real...

UbersonicLosing work because the machine decides it's going to reboot itself, machine decided to download/install updates when you're trying to use it, etc, etc.

Then your admin needs to learn how to push GPOs configuring reboot windows. if its a 24/7 business then have him do it in flights and properly segregate groups of machines. Not doing updates is not an option and he is less an admin and more of an idiot if they/he/she believes otherwise.

Is there anyway to reach that "blog post" for us lowly, non-10 Luddites?

UbersonicBusinesses should really be using Windows 10 Pro not Home, that way they can disable either the automatic downloading of updates or the automatic rebooting (or both).

No, it doesn't. Microsoft admitted that they disregard the GP settings, so your only options for disabling updates are via disabling its services or blocking the connection externally (both are applicable to the home version). The above is true for Enterprise as well.

With this day's fast SSDs a reboot isn't that bad.

Solaris17Then your admin needs to learn how to push GPOs configuring reboot windows. if its a 24/7 business then have him do it in flights and properly segregate groups of machines. Not doing updates is not an option and he is less an admin and more of an idiot if they/he/she believes otherwise.

Plus they need to learn to set the Active Hours. Windows 10 gives you a 12 hour window that you can set where it will not install updates or force reboot the computer. Yeah, if you use the computer for more than 12 hours you still get stuck with a reboot in the middle of your work, but most business won't be affected by that since most computers are only in use for an 8 hour shift, maybe 10 hours.

9700 ProWith this day's fast SSDs a reboot isn't that bad.

It isn't really the reboot, but the 30+ minutes of waiting for the updates to install during the reboot. And even with SSDs, that time can be that long.

newtekie1Plus they need to learn to set the Active Hours. Windows 10 gives you a 12 hour window that you can set where it will not install updates or force reboot the computer. Yeah, if you use the computer for more than 12 hours you still get stuck with a reboot in the middle of your work, but most business won't be affected by that since most computers are only in use for an 8 hour shift, maybe 10 hours.

less we forget that windows will "toast" you to let you know a reboot is impending in which the user can delay it upto 30min upto 3 times. Nor should we forget that as admins we can invoke a message to be displayed if needed to inform them the unit will be rebooting at X:XX. but thats none of my business

At my company, we are starting to move towards "live" kernel patching and OS security patching. As well as a "ZDT" (Zero Down Time) model for our Financial applications.

:) I would like to see the day where we can call windows a "non-disruptive" industry OS. As of today, we only ever use Windows for end user PC's , or for app's that are a joke.

I don't think Windows will ever be able to do live/hot patching due to the limitations in the file systems of Windows. On Windows you can't change a file that's currently in use be it an EXE or DLL file. This limitation of course has caused application developers to have to create special routines to replace their binaries as part of application update procedures. I myself have done this for my own programs which usually includes downloading a new binary file to a new file like "application.exe.new.exe" and executing it with a "-update" switch. This isn't a problem on Linux due to its use of iNodes at the file system level. The file system on Linux is fundamentally different than NTFS which allows Linux to patch in-use binaries.

silentbogo@yogurt_21, here is the thing: these kind of updates don't happen every day, and normal companies, be it a small business of 2 people, or a large corporation of 1000 users, they should have provisions for this stuff.
Plus you do have an option to postpone the update to whatever time it is comfortable for you to update, and if my memory is not failing me completely - there is a textbox in an update window which clearly states that you can alt-tab and do your stuff while it's doing the update magic. So, I don't see any feasible scenario, in which the Creators Update may cause an unplanned disruption of work process.


Any OS, be it OSX, iOS, Android, FreeBSD, Ubuntu or Windows, requires you to reboot after a major update. At this point of time a claim of "There can be no reboots in 2017" is a total fiction... overactive imagination... something desirable but definitely not real...

You either didn't read it or failed literature and reading comprehension in school. We are talking about set it and forget it compression, QA testing, file transfers, network crawlers, etc. You run your day, set your machine up for an uninterrupted long job and go home expecting it to have worked all night. There is no user present to stop the update.

These are required for any production focused company. All of you sound like you work in offices in the 80's where computers are used but not the main focus.

"So sure bob had to wait on his email while the machine rebooted, big deal." wherefore do any of you work that this is your current reality?

Certainly not software companies, media companies, online application companies, gaming industry, filming industry, streaming, security companies, etc.

your use case is limited to retail and legal offices. Great. What about the rest?

also what linux are you running that REQUIRES as reboot? Ubuntu/Redhat = all package updates happen in place and service restarted, if you're talking major kernel jumps the update happens but the old kernel is still running in memory until YOU initial a reboot, not the update service. Mobile devices do reboot after major changes, but not after app updates and it doesn't reboot on its own. OSX the same. Sure SOME things in this realm need a reboot, its not often though.

Not sure how new you are to all of this but seriously that's not how microsoft does it. Nearly every update big or small requires a reboot and does so without user initiation.

What downtime. I never want to upgrade the existing win or whatever and that is what it does...
Every big update so far has been a reinstall by renaming of the old windows folder,
Every time a mess, it looses fonts, programs stop working. I can't imagine who came up with this idea.

Kinda prefer my deffered updates and reboot only when I want so. Not hard to set up and works.

yogurt_21You either didn't read it or failed literature and reading comprehension in school. We are talking about set it and forget it compression, QA testing, file transfers, network crawlers, etc. You run your day, set your machine up for an uninterrupted long job and go home expecting it to have worked all night. There is no user present to stop the update.

These are required for any production focused company. All of you sound like you work in offices in the 80's where computers are used but not the main focus.

"So sure bob had to wait on his email while the machine rebooted, big deal." wherefore do any of you work that this is your current reality?

Certainly not software companies, media companies, online application companies, gaming industry, filming industry, streaming, security companies, etc.

your use case is limited to retail and legal offices. Great. What about the rest?

also what linux are you running that REQUIRES as reboot? Ubuntu/Redhat = all package updates happen in place and service restarted, if you're talking major kernel jumps the update happens but the old kernel is still running in memory until YOU initial a reboot, not the update service. Mobile devices do reboot after major changes, but not after app updates and it doesn't reboot on its own. OSX the same. Sure SOME things in this realm need a reboot, its not often though.

Not sure how new you are to all of this but seriously that's not how microsoft does it. Nearly every update big or small requires a reboot and does so without user initiation.

Seems like you've totally missed the point again. Creators Update is not a Gremlin, which you can't feed after midnight or let near the water: it won't install on its own, it won't forcibly reboot your PC when you least expect it, it won't mess up your environment, and it won't destroy your data. If you ignore the "privacy settings" popup bubble, the update process won't even start. Even my tech-uneducated uncle was able to figure it out, so he can call me a week later and confirm that it's safe to install.
And if you are an admin in a large organization, you should already have WSUS up and running, and have group policies for WU in place.

You can postpone the update for as long as you need, even if you have a render farm or big data cruncher with 24/7 uptime, which for some reason is running a Windows 10 Home/Pro.
As I understand it, you can ignore that stupid privacy settings bubble 'till the next full moon, or christmas, or next easter, if you absolutely need to.

Either way - your complaints still don't apply to the real world, unless you are running a disorganized mess-of-a-company with very lazy admin and no provisions or contingency plans for scheduled or unscheduled maintenance.

Regarding Linux: Live kernel patching was only introduced in 4.0, so all of those organizations still running 3.xx are out of luck on this one (which is still a lot). Also, even though it was introduced back in 2015, it was not until mid-2016 when all the quirks of live patching were almost ironed out. I think so far the only distros that fully support it are Ubuntu 16.04+ and RedHat 7.2+. Few others have some progress, but nothing 100% working. FreeBSD 11.0/10.0 definitely does not support live patching (and no plans, I guess), otherwise I wouldn't have to deal with occasional pornhub outages at 2AM, every time my neighbor's network admin is high on coffee somewhere 500km away.

silentbogoEither way - your complaints still don't apply to the real world, unless you are running a disorganized mess-of-a-company with very lazy admin and no provisions or contingency plans for scheduled or unscheduled maintenance.

This kinda destroyed all your arguments...

You need provisions and contingency plans for this. This means resources and time lost. For a huge company it means a big amount of time and work hours.

If the Linux OS can do it, why is it M$ still lagging behind?? ITs the biggest OS Software company!

SkullFoxThis kinda destroyed all your arguments...

You need provisions and contingency plans for this. This means resources and time lost. For a huge company it means a big amount of time and work hours.

If the Linux OS can do it, why is it M$ still lagging behind?? ITs the biggest OS Software company!

In which universe does this make sense? What were you smoking last night?
Contingency for non-existent Windows Live Patching service? Provisions for lazy users and admins?
You, kids, made me very confused, and it's already 9:30AM here and I had 3 big cups of coffee...

I feel like my head is gonna turn into a pumpkin by noon....

*Sigh*
Windows 10 1607/1703, Office 2016, browser of choice with "remember tabs" feature.
If rebooted due to updates, Windows WILL "try" to bring it all back up just like you left it. Yes, it's a feature that exists.

newtekie1Plus they need to learn to set the Active Hours. Windows 10 gives you a 12 hour window that you can set where it will not install updates or force reboot the computer. Yeah, if you use the computer for more than 12 hours you still get stuck with a reboot in the middle of your work, but most business won't be affected by that since most computers are only in use for an 8 hour shift, maybe 10 hours.

It's 18 hours now.