I have a theory that profox barfs on certain "thread IDs" or something at times. So I'm resending this under a new subject line and not in reply to anything to see what happens.

I don't ever allow any computer under my supervision to automatically download or install ANY updates until I am satisfied that they won't break the computer. And I almost never install any of the non-security or other "important" updates in any case. MS can't be trusted as regards hardware drivers, and I'm usually not interested in anything else they have to offer.

So KB3035583 is not installed on any computer that I am responsible for.

Nor would I ever "upgrade" any MS OS. When I get new ones, they are installed from scratch. MS OSes that are "upgraded" tend to be unstable.

I haven't purchased any Win 10 boxes yet. When I do, I will only purchase the "enterprise" version, because that is supposed to provide the maximum amount of control over updates.

That is supposed to include deferring anything that is not a "security" update indefinitely. As best as I can tell, "home" doesn't allow delaying any type of updates. "Pro" allows delaying non-security updates for some relatively brief period of time, after which they are installed by force. That means that MS can at some point change the OS so much that my software will no longer work on it, and there would be nothing I could do about it. That is not acceptable.

So I'm waiting for "enterprise", which is supposed to allow me prevent non-security updates indefinitely. And it is also suppose to allow me to establish my own schedules and "rings" for exposing machines to other types of updates.

However, my reading on this indicates that this feature is not yet actually available, and won't be fully implemented until sometime next year. I don't use an update server now, and I don't see the value of using one unless and until it can give me complete control over updates.

MS is just as capable of screwing up a "security" update as it is of messing up other updates. They've done it many times. Until I am certain that I can prevent ANY update from being installed until I know it is safe, I won't be putting Win 10 into production.

I do believe that MS will eventually change its tune about this, because there are many, many people who are not happy campers.

I wanted to get a Win 10 box to experiment with in the meantime, but I think now I'll wait until at least after next "major" update, scheduled for October, and then see what the situation is after that.

Ken Dibble
www.stic-cil.org


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/1A.5D.28483.129E1E55@cdptpa-oedge01
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to