Dear Microsoft - honey never change...
-
No not honey the code witch - honey as in referring to MS.... So, it's Sunday 0 dark early - I don't sleep much these days, but I have started the habit on Sunday morning to check all my VMs and other systems for updates. I'm doing this deliberately to avoid getting randomly nuked... Every VM and system times out trying to get updates. :doh: Trying to live in the MS ecosystem is like living on the Serengeti - you never know when you are going to get eaten. ------------------------------------------------------------- Meanwhile, on the update page, I read this: "Windows Update is committed to help reduce carbon emissions." Clicking on the Learn More button, I get this drivel: "Windows Update is now carbon aware" - that's the title of the article. If you read down, MS has decided it's a good idea to turn off all of these devices, etc, yada yada. Great, now I need to go in and change all of my settings so that Windows 11 does NOT turn off all of my usb devices talking to hardware. I really think there is a "Drop Managers on Their Head" department somewhere in Microsoft. I have got to get back to Unix development.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
No not honey the code witch - honey as in referring to MS.... So, it's Sunday 0 dark early - I don't sleep much these days, but I have started the habit on Sunday morning to check all my VMs and other systems for updates. I'm doing this deliberately to avoid getting randomly nuked... Every VM and system times out trying to get updates. :doh: Trying to live in the MS ecosystem is like living on the Serengeti - you never know when you are going to get eaten. ------------------------------------------------------------- Meanwhile, on the update page, I read this: "Windows Update is committed to help reduce carbon emissions." Clicking on the Learn More button, I get this drivel: "Windows Update is now carbon aware" - that's the title of the article. If you read down, MS has decided it's a good idea to turn off all of these devices, etc, yada yada. Great, now I need to go in and change all of my settings so that Windows 11 does NOT turn off all of my usb devices talking to hardware. I really think there is a "Drop Managers on Their Head" department somewhere in Microsoft. I have got to get back to Unix development.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
I'm confused, are these two stories related? I'm guessing not and was just reading too much into it. Regardless: If you have multiple VMs, have a look at WSUS. It's trivial to set up, it'll keep itself up to date, you'll save a ton of bandwidth, and it's up to you to decide whether something should be deployed or not. By the time you're ready to deploy, you should have the update already downloaded locally (even if there's some outage that lasts some time).
-
I'm confused, are these two stories related? I'm guessing not and was just reading too much into it. Regardless: If you have multiple VMs, have a look at WSUS. It's trivial to set up, it'll keep itself up to date, you'll save a ton of bandwidth, and it's up to you to decide whether something should be deployed or not. By the time you're ready to deploy, you should have the update already downloaded locally (even if there's some outage that lasts some time).
I'll look into it, and yes, the two stories are related. If MS prompts me to update my system that requires a reboot, don't you think connecting to the update service should work? I find that ironic. And, after it eventually updated, it informs me the the update fluster cluck now reduces carbon emissions - which I consider to be so irrelevant as to be absurd. Story 1 - stupid, story 2 - more stupid. I'm concluding that the mandatory training session for MS management being dropped on their heads for a week continues its success.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
No not honey the code witch - honey as in referring to MS.... So, it's Sunday 0 dark early - I don't sleep much these days, but I have started the habit on Sunday morning to check all my VMs and other systems for updates. I'm doing this deliberately to avoid getting randomly nuked... Every VM and system times out trying to get updates. :doh: Trying to live in the MS ecosystem is like living on the Serengeti - you never know when you are going to get eaten. ------------------------------------------------------------- Meanwhile, on the update page, I read this: "Windows Update is committed to help reduce carbon emissions." Clicking on the Learn More button, I get this drivel: "Windows Update is now carbon aware" - that's the title of the article. If you read down, MS has decided it's a good idea to turn off all of these devices, etc, yada yada. Great, now I need to go in and change all of my settings so that Windows 11 does NOT turn off all of my usb devices talking to hardware. I really think there is a "Drop Managers on Their Head" department somewhere in Microsoft. I have got to get back to Unix development.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
I would recommend you do your best to disable updates or keep them minimum ... could turn off the service.. if these are not connected to net .. just manually update based on whats needed.unless you have like more vms
Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
-
I would recommend you do your best to disable updates or keep them minimum ... could turn off the service.. if these are not connected to net .. just manually update based on whats needed.unless you have like more vms
Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
I agree. That's why they are disabled and on Sunday morning I take care of it manually. Just surprised that the update service fails after notifying me to update. I just need a little cheese with my whining.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
I agree. That's why they are disabled and on Sunday morning I take care of it manually. Just surprised that the update service fails after notifying me to update. I just need a little cheese with my whining.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
charlieg wrote:
Just surprised that the update service fails after notifying me to update
I totally get what you're saying. They tell you, "Hey, there's an update available", so you actually believe it is _available_. Meanwhile it isn't available (at some specific time for some unknown reason). Also, here's the one that has been getting me. Nothing is happening on herself's computer but she needs to reboot due to some software. I say, "Sure, let's check to see if there is an update pending though. Okay, all safe, there isn't. Just do a restart." She does and then Windows 10 starts spinning. It spins a long time. Well, don't you know it, there is an update that they haven't warned about anywhere but MS has suddenly decided that yes, we will update now because you decided to restart your machine. So it spins a long while and doesn't mention it's updating. So long that you wonder, is it stuck, should we power down? Let's wait. Finally it restarts and says, "oh you got the latest update." :wtf: :wtf: :mad:
-
I'll look into it, and yes, the two stories are related. If MS prompts me to update my system that requires a reboot, don't you think connecting to the update service should work? I find that ironic. And, after it eventually updated, it informs me the the update fluster cluck now reduces carbon emissions - which I consider to be so irrelevant as to be absurd. Story 1 - stupid, story 2 - more stupid. I'm concluding that the mandatory training session for MS management being dropped on their heads for a week continues its success.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
charlieg wrote:
If MS prompts me to update my system that requires a reboot, don't you think connecting to the update service should work? I find that ironic.
Usually by the time you're asked to reboot, the update's already been downloaded and installed, and has no business attempt to connect to WU. The exception might be that, before it installs anything, it detects your system is already in a "reboot pending" state and the installer gets stopped in its tracks.
charlieg wrote:
I'm concluding that the mandatory training session for MS management being dropped on their heads for a week continues its success.
I'm pretty sure that's already taken place. In fact sometimes I wonder if it's actually a requirement for anyone who applies to any MS product management job.
-
I agree. That's why they are disabled and on Sunday morning I take care of it manually. Just surprised that the update service fails after notifying me to update. I just need a little cheese with my whining.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
Gotcha. It sounds like the system *was* able to get in touch with WU and is aware an update is available. But when it tells you so (which can be hours/days after the fact), and you tell it to go ahead and fetch it, there happens to be a connectivity problem *at that time*. Frankly I'd rather have that than Windows detecting an update, and download it without first getting my approval. And least with WSUS, you get the update list, and the server sits on it and will wait indefinitely for you to approve/reject whatever you want. Only when you've approved of an update will the system download it. Then all your clients connecting to your WSUS server will see the updates when the server has them locally. Then maintaining the connection between your server and its clients is something that remains in your control. And that's the key to everything - remaining in control. Back when MS was pushing Windows 7 users *hard* to upgrade to 8 (which I didn't want), or 8 -> 10, the KB article that triggered the full-screen upgrade nag was well-known, so I blocked it from my WSUS server. I've *never* seen those nag screens on any of my machines.
