Windows 10: Win 10 Ann Ed - "Shutdown without updating"

Could it be that I don't see them because I am not on Insider builds?

 

I don't think so. As I mentioned, Insider build upgrades are not only update types that offer those options. I do not believe Windows Update would work differently on public release builds and Insider builds.

One thing is clear: if a user always when WU shows Restart now button clicks it, this user would naturally never see the option to restart or shut down without updating.

 

@Kari
Working on someone's laptop just now, running MBAM scan, found 2 PUPs which I need to reboot in order to clear out. While scanning, KB3914496 downloaded again (had failed earlier), and is requiring a reboot to install. Now, I need to finish what I'm doing with MBAM first, and I wanted you to see this:












I changed the active hours, as it was ready to shutdown on me as the MBAM scan finished.

















I delayed the restart until October 12th - no difference.

















So I am not crazy, and it is a problem. :-(

 

And your point is what?

Extract from an earlier post of mine:

The fact that WU lets you select a later time for automatic restart can seem a bit misleading, but it's there for a logical purpose: it's there for you to select a convenient point of time when the pending updates will be installed in case this PC is one that's always on. I use this feature on an HTPC and a server which are always on (occasionally sleeping / suspended but not shut down / restarted) to make sure they will not restart at for me inconvenient time.

Cumulative updates always require an immediate restart, immediate in this case not meaning you have to restart the moment update has been downloaded and prepared but instead that pending updates will be installed next time the PC is either shut down or restarted. Update can be postponed only to next shut down / restart, and will be performed latest at the time you select in Restart options if PC has not been shut down / restarted before that.

If Restart options is not used to select time for an automatic restart and no manual shut down / restart is done, automatic restart will happen soon after next by user selected Active hours time period ends.

 

Okay I understand. Thanks. Still is a PITA the way it's set up.

 

Yet it's completely logical:

• Critical updates (cumulative, minor build etc.)
  • Must be installed as soon as possible, can be postponed only until next shut down or restart
  • If no manual shut down or restart will be done, an automatic restart to install pending updates will be done at the end of set Active hours or Restart options, whichever comes last
• Non-critical updates (major build, other updates not requiring immediate install)
  • Can be postponed max to end of sixth day after downloaded and prepared (depends on update) by selecting restart or shut down without updating
  • When above mentioned time period ends, any restart will do the update and install pending updates or build upgrade, option to shutdown or restart without updating is no longer available
  • If no manual shut down or restart will be done, an automatic restart to install pending updates will be done at the end of set Active hours or Restart options, whichever comes last

I am using terms major and minor build above as in XXXXX.YYYY where XXXXX is major build and YYYY is minor build. For example I am currently running 14936.1000, 14936 being major and 1000 minor build.

 

@simrick, conveniently we got a new Insider build upgrade a few hours ago, I captured the change of shut down options in a short video (less than two minutes).

[youtube]LBoVdW_Fwws[/youtube]

I repeat that I have been using a build upgrade as an example but also other non-critical updates offer the same shutdown options as soon as updates have been prepared are pending installation.

 

Thanks Kari. I understand now, that not every update requiring a reboot provides this shutdown option.
Still, it's a problem, when I'm cleaning an infection, and need to reboot many times before completing the cleaning process. I don't want to install updates on a system that's not clean. That is my current problem. Guess I'll have to start changing systems to metered connections before starting a cleaning process, in order to get my work done first.

 

In cases like that I hide the updates until I am done and am ready to install them. See this tutorial: Windows Updates - Hide or Show in Windows 10 - Windows 10 Forums

 

Cheers Kari. That or metered connection. *Smile

 

I was interested to see if I remember it correctly, if this option to shut down or restart without updating was already available in original RTM build 10240. Had to install it on a vm and check.

Screenshot is from RTM 10240 from July 2015 (#1). WU has finished downloading version 1607 upgrade (#2), all shut down options already available (#3):





This is Windows 10 PRO, only a local account, never had any Microsoft accounts nor has it been opted for Insider builds.

 

Hi ALL,

I started this thread and I appreciate all the input - it's been a lively discussion! But while I am still glad I upgraded to Win 10 I frankly am fed up with how the updates work. Especially since I believe MS was saying that in Win 10 the updates would be faster than in previous versions. Here's the latest experiences I had with some updates.

Yesterday I was working on my PC when a notification came up that some updates were ready and that a restart was required. So I went into the Updates to take a look and it showed the updates and an option to Restart Now. I was curious to see what was in the Start Menu's power down options and it was "Update and Restart" and "Update and Shutdown." I also went to the Alt-F4 and it also only showed those two options and lastly Ctl-Alt-Del also had only those two options. So Kari was right that they all show the same options and only sometimes allow Shutdown and Restart without Updates. OK, so I selected the Restart Now and it did its thing. While my PC is getting on in years, it does have a very fast SSD where Win 10 sits and usually the updates don't take too long. I did see the shut down blue screen with the percentages and then it restarted with its own percentages and went into Win 10 and the whole thing took about 5 minutes. Fine.

Today I nearly threw a brick at my PC!!! Again working on it but this time I did not get any notification of any updates. I went to shutdown and the standard options of Shutdown and Restart were shown. So I selected Shutdown. But instead of shutting down it went to the blue screen working on updates with the rotating balls and stayed there FOR HALF AN HOUR and NO PERCENTAGE indicator. I was looking at the disk activity and at times it was barely blinking so it didn't seem all that busy. But I had to go out and was going to just leave the PC on assuming it would power down when done. But as I said it finally shut down but after a full half an hour.

When I turned it back on later it went right into Win 10 and there was no indication that any updates were done as you usually get a notification but I got none. I then went into the Update History and it showed the updates that went in yesterday but it showed absolutely nothing for today. SO WHAT DID IT DO TODAY THAT TOOK A HALF AN HOUR??!

And while I'm venting why do the updates in general take so long to get done? Isn't it just copying files? Yes, there are many different PC configurations but I still can't see why it should take so long.

Back to the surprise update today when selecting the regular shutdown resulted in a long update with no percentage indicator. This happened to me a couple of other times and I have no idea why. Has anyone else gotten these type of surprise long updates and does anyone know what they are for?

Thanks,
Gerry

 

Gerry,

The same thing happened to me yesterday. I installed the updates from the 2nd Tuesday Windows Updates on an old laptop (which I don't normally use so it was not turned on for about a week) and did the normal restart. It seems that the last several updates have a two restart process in them. After everything was installed and my system came up again, I then did some things on it for a little over an hour and then hit shutdown. It immediately went into the "Getting Windows ready.... Do not turn off your computer". About 40 minutes later, it finally shut down. I brought it back up and checked to see if anything else had been installed and, as you mentioned, nothing showed up. I initially posted a message here because I was concerned that I would have to force shutdown my PC. But when it finally came back, I cancelled the post. I did post a message in the Microsoft Community Forum to see if MS has any answers. One of their moderators requested some log info which I sent, but I have received no further response from them. As I have commented to a number of friends, "Windows 10 is an accident waiting to happen".

BTW, I have Windows Update configured to notify me when updates are available, not to automatically download and install updates.

JohnD

 

Hi John,

Its nice to know that other are getting the same results as I am! I do think Win 10 has some nice improvements but on the other hand the update procedures are a disaster. I don't mind that you no longer can select which updates to install or not install as that was always rather complicated. But what I do mind is that you can no longer just shutdown or restart without doing the updates, except under some circumstances. If MS deems an update to be critical then Win 10 should hit you with many "nag" screens but it should not force the update until you say OK. This is even more important if its one of those updates that can take a long time.

But what drives me crazy is this unexpected update without any notification and especially without any percentage progress indicator which just sits and churns for 30 minutes or more until it eventually shuts down or completes the restart. If you're heading out the door this can be a real inconvenience.

I'm going to start a new thread with a better title to see how many others have seen this.

Gerry

 

Thanks John to pointing towards this thread on my other one. I also got the same yesterday across three machines. No updates yet got stuck on that getting windows ready. And you know what I've seen it before on different builds / versions. Unfortunately I force shutdown windows in the end on each machine. Luckily no lasting damage down. Another big error from MS!