Will Win10 1803 be called (yuck!) Spring Creators Update (/yuck!)?

Topic

New Reply

WalkingCat (@h0x0d) asked someone with a copy of the next-next version of Win10 (the Skip Ahead version 17618, presumably version 1809) to run a Power
[See the full post at: Will Win10 1803 be called (yuck!) Spring Creators Update (/yuck!)?]

1 user thanked author for this post.

Fred

Reply | Quote

Replies

Looking at the depth of improvements, just a slight change in the name was the best idea ;).

Antec P7 Silent * Corsair RM550x * ASUS TUF GAMING B560M-PLUS * Intel Core i5-11400F * 4 x 8 GB G.Skill Aegis DDR4 3200 MHz CL16 * Sapphire Radeon 6700 10GB * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit

Reply | Quote

Redmond must’ve fired all the creative people.

Reply | Quote

Southern hemisphere residents will now have two Springs 🙂

1 user thanked author for this post.

Karlston

Reply | Quote

Yep, still clueless about the way seasons work on our planet.

Dear Microsoft (again),

Your “Spring Creators Update” will be released here when it’s Autumn (Fall).

For us it’s actually the “Autumn Creators Update”. Not to be confused with the “Fall Creators Update” (which should be called “Autumn Creators Update” outside North America) which is released in our Spring.

Accuracy matters.

Yours sincerely

Users living in the Southern Hemisphere (the bottom half of Planet Earth)

P.S. And you’re also still clueless about apostrophe usage.

Hanlon's Razor: Never attribute to malice that which can be adequately explained by stupidity.

Reply | Quote

IIRC, one of the first new versions after the original Windows 10 came out was slated to be named the “Fall Update,” but then MS changed their mind after people pointed out that it was the fall only in the Northern Hemisphere, and they ended up calling it the October (or was it November) Update.

Now, it seems, they no longer care about such niceties. It’s almost like they’re trying to see how many users they can treat with contempt and get away with it.

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Karlston

Reply | Quote

I think I will skip until this Upgrade (1803) is blessed by woody  (currently in 1703) after all we have until October to Upgrade.

is that Ok?

1 user thanked author for this post.

Fred

Reply | Quote

Sure, it’s OK, as long as you remember that Microsoft is making it clearer that they “own” your computer. Look at the thread with the forced 1709 update. I don’t see this changing with future releases. Microsoft will update your PC whenever they want to update it.

Lovely, isn’t it?

Reply | Quote

There is always a way to block updates, we just need to find the right recipe to do it.

1 user thanked author for this post.

DriveBee

Reply | Quote

At least, Microsoft admits that Windows Update is broken and 1803 will show a warning sign on the Windows Update settings page when updates are available so users are aware of the mess waiting for download…

Reply | Quote

Will Win10 1803 be called (yuck!) Spring Creators Update (/yuck!)?

How about Win10 1803 Spring Creators Yuck! Update?

Glad to help!

Reply | Quote

We all know tone-deaf people in the figurative sense. I’ve had the label applied to me, and admit it fits on some of those occasions. But Microsoft takes the concept to Quasimodo like levels and beyond.

I have a cartoon like picture in my head of fine British man named Smythe. A mechanical worker in London who can stand in the workroom atop Elizabeth’s Clock Tower remaining blissfully unaware that Big Ben is striking 13times every hour. Yet he responds happily when asked about it, “Why yes! Wonderful thing, isn’t it!”

1 user thanked author for this post.

DriveBee

Reply | Quote

anonymous wrote:

There is always a way to block updates, we just need to find the right recipe to do it.

And they will find a way around those blocks. See the latest Upgrade to 1709 that didn’t come from Windows Update.

No matter where you go, there you are.

Reply | Quote

As long as you detect it on time, you are fine. What happened this morning didn’t happened suddenly, this happened ’cause people didn’t block certain updates in time.

Reply | Quote

Yeah, but the update that delivers the pushed upgrade came from Windows Update 🙂

WU in Windows 10 is a lost cause without intervention

some steps are obligatory to keep the current version:
– set connection to metered
– set AU policy to disabled or notification
– disable UpdateOrchestrator and WindowsUpdate schedule tasks
– use wushowhide.diagcab or WUMT to check for updates and hide the upgrader-updates

2 users thanked author for this post.

MrBrian, woody

Reply | Quote

That’s scary.

I’m going to elevate this, and get a discussion going. Thanks!

Reply | Quote