Windows 10 Creators Update - what a disaster!

[Geoff.D]

For 1 PC I would rather use WUMT as pointed out before. Does what WSUS does but without the need for Server.

The same here. WUMT is just a supposed easier front end for the existing facilities available (Group Policy etc).
Again if you are really interested in doing this just use the facilities available direct.

 

[vic777]

For 1 PC I would rather use WUMT as pointed out before. Does what WSUS does but without the need for Server.

Thanks, I'll check it out

 

[Ho3n3r]

No issues on this side either

Same here, and I upgraded 3 different PC's the day after the update came out (around 10 April, I think).

 

[Ho3n3r]

Upgrade to Linux

 

[HunterGR]

Just finished a upgrade rollout to the creators update via WSUS of over 1000 machines, desktops and laptops, not one issue reported

 

[Geoff.D]

Just finished a upgrade rollout to the creators update via WSUS of over 1000 machines, desktops and laptops, not one issue reported

Interesting. So what did you tell the users of those 1000 PCs? Did you inform them that an upgrade will be happening at a certain time and that the PCs would be unavailable for normal use during that time?

 

[Praeses]

I have 7 computers running on Creator's update, ranging from Core2Duo laptop and PC (2GB RAM even) to i5 systems without a single issue.

 

[HunterGR]

Interesting. So what did you tell the users of those 1000 PCs? Did you inform them that an upgrade will be happening at a certain time and that the PCs would be unavailable for normal use during that time?

Was done in stages and outside office hours, in batches.

took about 3 weeks to do them all

 

[Budza]

My Dell laptop now wont come out of monitor power save mode for both the primary and secondary monitor
Screen saver comes on...no problem. Move the mouse of hit the keyboard and screes come back on.
But if power saving setting turns the screen off...then I cannot get the screens to come back on without unplugging the external monitor.
For now, I've set it to never turn the screens off...screen saver only.

Shift+Crtl+Win+B

Resets graphics driver.

Worked for me, but the latest updates from a day or two ago resolved my monitor/flickering mouse issue.

 

[Geoff.D]

Was done in stages and outside office hours, in batches.

took about 3 weeks to do them all

Yes! this is the crucial point of any update process regardless. The roll out requires planning and the PCs were all not in use at the time!

This thread is about someone who expected an update/upgrade to not impact on a working PC with all sorts of third party sw installed and probably running at the time without any control of the process.


It just cannot be expected to work smoothly! No amount of automation using technologies and sw used in large environments such as WSUS and WUMT makes up for having to understand what will happen when an update is automatically triggered.

WSUS requires a server, properly configured, AND requires that the PCs that will be updated are not busy with other things when the update kicks in.
WUMT allows whatever has been decided in a WSUS deployment to be easily used on a stand alone PC. It does NOT make up for the stand alone PC to be out of use at the time the update runs.

In other words the owner of the standalone PC MUST know what he needs to do beforehand anyway, which means he might as well learn how the basic update setup works and configure the PC accordingly. If he still insists that he wants to "carry on running whatever" while the update is happening in the background, he will still have to prevent any update process that impacts on that sw from happening especially any requests for a restart that the update process may require.

Unfortunately, most complaints of this sort are from persons who just do not want to make the effort to understand what they need to do beforehand. MS goes to quite extreme lengths to try and protect users and their devices but cannot possibly handle cases where users do not want to follow some very basic steps.

 

[sajunky]

Erm I dont think you actually looked at my post?

Its not a block update hack, but in fact points your system to use WSUS. And trust me if Microsoft ever ignore that one they would have way more than Mr Home user to deal with.

It is a hack, and yes I read your posts.

Yes, they can ignore this on the new Pro and Home releases, the same like they currently ignore automatic updates GP settings. They will not do that on Enterprise version to not upset guys like you.

I know I can't win with Microsoft. With such arrogant approach to the consumer, it is better to get replacement for all Microsoft offerings and forget about this bastard.

 

[Geoff.D]

It is a hack, and yes I read your posts.

Yes, they can ignore this on the new Pro and Home releases, the same like they currently ignore automatic updates GP settings. They will not do that on Enterprise version to not upset guys like you.

I know I can't win with Microsoft. With such arrogant approach to the consumer, it is better to get replacement for all Microsoft offerings and forget about this bastard.

You have referred to this quite often, that "they" (meaning MS) ignore automatic update GP settings? What do you mean by this? I have never had my GP settings ignored? Does this happen in Enterprise networks? Don't you think it is probably the WSUS sw configuration that is set to "ignore" user specific GP settings maybe and that this does not apply to single user PCs?

 

[sajunky]

Unfortunately, most complaints of this sort are from persons who just do not want to make the effort to understand what they need to do beforehand. MS goes to quite extreme lengths to try and protect users and their devices but cannot possibly handle cases where users do not want to follow some very basic steps.

The only Microsoft concern is to upload to the all computers around the world in the same time a new distributed processing bot-nets. Whatever they do on it, depends on current Microsoft needs - from breaking sha1 signatore to mining Bitcoins or similar currency.

 

[sajunky]

You have referred to this quite often, that "they" (meaning MS) ignore automatic update GP settings? What do you mean by this? I have never had my GP settings ignored? Does this happen in Enterprise networks? Don't you think it is probably the WSUS sw configuration that is set to "ignore" user specific GP settings maybe and that this does not apply to single user PCs?

Read other threads. GP automatic updates settings is ignored (at least since v1607 which I discovered first and posted on this forum). It is provisional now, depends on Microsoft servers approval.

 

[Geoff.D]

The only Microsoft concern is to upload to the all computers around the world in the same time a new distributed processing bot-nets. Whatever they do on it, depends on current Microsoft needs - from breaking sha1 signatore to mining Bitcoins or similar currency.

Unfortunately that is not an answer -- it is just conjecture. I take it that there is thus no substantiation to your claims about GP settings being ignored by MS on a stand alone PC. I cannot say what happens with PCs in a setup under the update control of WSUS on a server.

 

[sajunky]

Unfortunately that is not an answer -- it is just conjecture. I take it that there is thus no substantiation to your claims about GP settings being ignored by MS on a stand alone PC. I cannot say what happens with PCs in a setup under the update control of WSUS on a server.

Proof that GP settings is merely provisional (not binding) was already given by the user Ivan_Leon (post #19529714) here: https://mybroadband.co.za/vb/showth...ators-Update-and-this-auto-restart-bs-is-back

A hijacked screenshot:

 

[Geoff.D]

First of all, no one in his right mind should suggest that ALL updates are blocked.
Second, I have set GP to provide me with the ability to control the update process, to prevent update downloads on metered networks (which works), and then ensure that I undertake the updates within the time limits as specified by MS.

This does NOT equate to MS ignoring GP settings as you imply. So that is why I say you are misleading persons as to what can and can't be done. I am made aware of updates, I take note of those notifications and organise for the updates to be done when suitable.

So yes the screenshot is what I have and I have taken the trouble to set the available settings to suit me, which normally means that an update will proceed when I allow it.

 

[sajunky]

First of all, no one in his right mind should suggest that ALL updates are blocked.
Second, I have set GP to provide me with the ability to control the update process, to prevent update downloads on metered networks (which works), and then ensure that I undertake the updates within the time limits as specified by MS.

This does NOT equate to MS ignoring GP settings as you imply. So that is why I say you are misleading persons as to what can and can't be done. I am made aware of updates, I take note of those notifications and organise for the updates to be done when suitable.

So yes the screenshot is what I have and I have taken the trouble to set the available settings to suit me, which normally means that an update will proceed when I allow it.

Can you write something not implying what is correct/incorrect or what should be according to your views?

It could be a topic for a new thread. For now you must admit that I was right and gave you a proof you asked for. This will help to maintain your integrity.

 

[Geoff.D]

So this is where the misinformation starts about this topic.
On Windows 10 Pro, without any Group Policy settings, the message in red on the update screen does NOT appear at all. And neither does the note.

*some settings are hidden or managed by your organization

We'll ask you to download updates, except when updates are required to keep Windows running smoothly. In that case, we'll automatically download those updates.

Both the above only appear IF you have set local GP settings. If you choose NOT to use the GP options, you should follow through and set the active hours options, the restart Options and the check on the advanced options.

All of these are greyed out IF you use GP.

There is another setting that should be set even if using GP. It is on the Restart options screen.

We'll show a reminder when we're going to restart. If you want to see more notifications about restarting, turn this on.

Under the Advanced Options you are able to Choose when updates are installed. (The download of updates DOES NOT imply that they will be automatically installed).

This option allows you to defer the installation of updates for periods of up to 365 days for non critical updates and 30 days for quality and security updates.

You can temporarily Pause updates for 7 seven days should it be necessary.

Then you can choose HOW updates are downloaded/delivered.

This is the crucial step that all should check, because the defaults are not what most persons would want. The default is ON, and the default is updates downloaded on this PC will be shared with PCs on my local network, and PCs on the Internet

So, if you leave this option ON, then you should at least set it to only share updates with PCs on my local network.

With the above settings:

I am never caught by a update download, nor am I ever surprised by an update installation or a restart. All it now takes is to ensure that you set aside some time every 24 hours when updates can be installed without affecting your work.

 

[Geoff.D]

Can you write something not implying what is correct/incorrect or what should be according to your views?

It could be a topic for a new thread. For now you must admit that I was right and gave you a proof you asked for. This will help to maintain your integrity.

Next time you work with a PC, a new one, with a fresh install of WIN 10 spend a few minutes and check on what the default settings are. At least we will then all be on the same page about what happens after we start making configuration changes.

IF all the customizations are done, updates that may have been downloaded automatically will never catch you out and will only be installed in the time period that you allow. BUT you must take the trouble to set the times or at least be aware of what the defaults are.

What MS did after 1607 is to try and gently force users to deal with updates responsibly. That does not equate to ignoring your GP settings in my book.