-[ snip ]-

These don't include all the Windows 10 nagware and telemetry updates. It'll cut your "waiting for the updates to show up and download" time down to the wait time for the package to download, which is dependent on your download speed.

We are making this change – shifting to rollup updates, to improve the reliability and quality of our updates.

-[ snip ]-

Greetings Jord,

With all the underhanded crap Micro$oft has been doing to get Window$ 10 shoved down our throats, how can we trust this to be legit? I do not trust Micro$oft.

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

-[ snip ]-

These don't include all the Windows 10 nagware and telemetry updates. It'll cut your "waiting for the updates to show up and download" time down to the wait time for the package to download, which is dependent on your download speed.

We are making this change – shifting to rollup updates, to improve the reliability and quality of our updates.

-[ snip ]-

Greetings Jord,

With all the underhanded crap Micro$oft has been doing to get Window$ 10 shoved down our throats, how can we trust this to be legit? I do not trust Micro$oft.

Keep on BOINCing...! :)

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

...how can we trust this to be legit?

{Shrug}

Then don't and don't update ever again if you feel you cannot trust MS, continue on with a crap broken Windows, and find that sites will start to actively block your computer because it cannot be trusted. Or just walk away and go the Linux tour.

These roll-up updates aren't necessarily for the users who update each Tuesday, but are more for those that clean install/reinstall/repair install their Windows 7 and and 8.1 and then have to sit through the multi-hour/multi-day ordeal of updating.

Look at the list of updates available in the present roll-up, you'll find it may only hold one update that adds telemetry for 7 and 8.1, but at the same time this is also an update for this part of the User Account Control (UAC) that may hang the whole computer.

It also contains the update for BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2, which has a known issue:

Known issues in this update:
After you install update 3133977 on a Windows 7 x64-based system that includes an ASUS-based main board, the system does not start, and it generates a Secure Boot error on the ASUS BIOS screen. This problem occurs because ASUS allowed the main board to enable the Secure Boot process even though Windows 7 does not support this feature.

Having sat through a 4 day ordeal of updating Windows after repair installing it, I think it's a neat service. One I'll use on my new repair install to be done soon (got self-inflicted registry corruption that heavily impairs my right-click context menu and can only be fixed by reinstalling Windows).

---

Amen. Sadly. Less than 4 years, and 7 will be 'dead'. Choosing to not think about it at the moment, but will eventually have to plan for this occasion. I'm sure by that point, W10 will be in the rear view mirror and what, W11 will be out? I dunno, maybe Linux, though my experiences with it have been less that optimal up to now. Too much else to think about right now, will try to worry about it when the time draws nearer.

---

Amen. Sadly. Less than 4 years, and 7 will be 'dead'. Choosing to not think about it at the moment, but will eventually have to plan for this occasion. I'm sure by that point, W10 will be in the rear view mirror and what, W11 will be out? I dunno, maybe Linux, though my experiences with it have been less that optimal up to now. Too much else to think about right now, will try to worry about it when the time draws nearer.

No at some point in time Windows 10 will change to something like "Windows OS". Their plan is to go with a constantly updating environment where users don't have to worry about versions. Much like how facebook or ebay operate. When those sites update the users don't normally notice unless there is a change in the layout.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I can't imagine how businesses are going to accept that with business critical apps running, and then MS lobs an "update" over the wall, blowing up said program without getting permission. I think that will be a huge hulking fly in that ointment for them. I used to work in IT years ago, and if they had tried to pull something like that, with no regression/compatibility testing, it would have been war. lol

So, as the the ancient Chinese saying/curse goes: May you live in interesting times. And apparently, we do...

---

I can't imagine how businesses are going to accept that with business critical apps running, and then MS lobs an "update" over the wall, blowing up said program without getting permission. I think that will be a huge hulking fly in that ointment for them. I used to work in IT years ago, and if they had tried to pull something like that, with no regression/compatibility testing, it would have been war. lol

So, as the the ancient Chinese saying/curse goes: May you live in interesting times. And apparently, we do...

Updates work differently for consumer vs business.
Consumers, by default, run Current Branch, but can opt-in to Preview Branch if they want to be be guinea pigs.
Businesses with Windows 10 Pro or Enterprise can run Current Branch for Business.
Businesses with Windows 10 Enterprise can also run Long Term Servicing Branch.
Each branch has different options for deferring or blocking updates.

Any moderately sized business I would expect to be using Windows Server Update Services instead of allowing each client to update individually. Which gives admins control over which updates the clients will get. That way if a business finds there is an issue with update KB8675309 they can block from their clients before it is ever deployed.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Any moderately sized business I would expect to be using Windows Server Update Services instead of allowing each client to update individually. Which gives admins control over which updates the clients will get. That way if a business finds there is an issue with update KB8675309 they can block from their clients before it is ever deployed.

I have actually seen bad updates mentioned here in the past, and relayed them to out IT Admin before they caused problems. One update I am thinking of could actually brick a machine. Our Admin stopped the update until it was patched.

Steve

Edit: And they say I shouldn't be looking at Seti while I work...... :D

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

Any moderately sized business I would expect to be using Windows Server Update Services instead of allowing each client to update individually. Which gives admins control over which updates the clients will get. That way if a business finds there is an issue with update KB8675309 they can block from their clients before it is ever deployed.

I have actually seen bad updates mentioned here in the past, and relayed them to out IT Admin before they caused problems. One update I am thinking of could actually brick a machine. Our Admin stopped the update until it was patched.

Steve

Edit: And they say I shouldn't be looking at Seti while I work...... :D

I believe it was mentioned in a MS WSUS Best Practices document to have a sandbox to test updates before they are deployed. I think the default, or recommended, configuration makes all updates available to the clients as soon as they are downloaded by the server.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Excellent, thanks for that Jord. Will make things much easier & save a lot of time & grief. :-)

I believe it was mentioned in a MS WSUS Best Practices document to have a sandbox to test updates before they are deployed. I think the default, or recommended, configuration makes all updates available to the clients as soon as they are downloaded by the server.

I use WSUS here at home, and if I recall correctly.. the default is needing manual approval for new updates. You can set up multiple groups, and you can approve updates for a 'guinea pig' group, and a 'production' group, or all.

In environments that have more than like.. 5 machines, you have one set aside to be a guinea pig. Approve all the updates for the guinea pig group, see how that machine reacts and if anything breaks. If it's fine, then you can go back and approve all those updates for 'production'.

I have heard of some people doing 'automatically approve updates for distribution' in WSUS, and that sounds like a disaster waiting to happen, to me.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

That is how it is working now, but how do you think what you have said applies to it when it becomes a Windows as a Service, with no version releases, just basically continuous updates/patches? That is going to be a whole new paradigm, but I suppose that if they are allowed to, as now, opt out of having them back-doored into their systems, then they'll be safe, but I'll feel pity for the unfortunate souls on the consumer side of things.

---

I see KB3123862, "Updated capabilities to upgrade Windows 8.1 and Windows 7" was re-re-released again yesterday. In the "Update replacement information" section it claims: "This update doesn't replace a previously released update." I guess replacing itself doesn't count. ;^)

Hello everyone just a quick question for now a lady I work with just had her computer upgraded to 10 without her permission and I want to tell her how to rollback to her 8 but I forget how to do it. I had given her a copy of Cosmic's list but she had not removed anything yet. Thanks for your help.

---

ME AND MY BOY LOOKING FOR ET

...how can we trust this to be legit?

{Shrug}

Then don't and don't update ever again if you feel you cannot trust MS, continue on with a crap broken Windows, and find that sites will start to actively block your computer because it cannot be trusted. Or just walk away and go the Linux tour.

-[ snip ]-

It also contains the update for BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2, which has a known issue:

Known issues in this update:
After you install update 3133977 on a Windows 7 x64-based system that includes an ASUS-based main board, the system does not start, and it generates a Secure Boot error on the ASUS BIOS screen. This problem occurs because ASUS allowed the main board to enable the Secure Boot process even though Windows 7 does not support this feature.

-[ snip ]-

Greetings Jord,

I highly doubt that this thread would exist if everyone trusted Micro$oft. ;)

As for KB3133977, I find it very hard to believe that ASUS is the only motherboard manufacture to send out their boards with Secure Boot enabled. I believe that KB3133977 was just one more trick from Micro$oft's bag to get Win7 users to upgrade to Window$ 10.

I don't know much about Secure Boot except that I had to disable it to install Linux next to Win7.

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I highly doubt that this thread would exist if everyone trusted Micro$oft. ;)

[Shrug] :-(

I moved over to other system after what I considered to be unholy compromises made for WinXP and the ensuing ongoing malware crapshoot.

For what I see for the move to Win10: Add proprietary tyranny to that!


Are Windows users really so hopelessly trapped and befuddled by the Microsoft Marketing?

Or are computer users just hopelessly trapped and shackled? :-(


IT is what we allow it to be,
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

I don't recall if we decided in this thread to avoid the May 2016 roll-up for 7 or not... I can't find anything inherently wrong with it... but I don't know if I can trust it just yet without doing more research.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I don't recall if we decided in this thread to avoid the May 2016 roll-up for 7 or not... I can't find anything inherently wrong with it... but I don't know if I can trust it just yet without doing more research.

I downloaded & used it today on an install for Win7 (w/SP1) and did not find any Win10 "malware" or "telemetry beacons" in it. I think it's OK to use.

---

I also installed the May 2016 roll-up, seems to be doing, what it claims, no Win 10 fuzz in it - so far. ;)

...but some old fellow in new disguise had to be dismissed again!

---

Aloha, Uli

I have had my daily driver on 7 locked down with update disabled for months now.
What, exactly, do I have to do if I wish to bring it up to date with this package without risking any 10 shenanigans?

---

"Time is simply the mechanism that keeps everything from happening all at once."