Yes, the Win10 Creators Update files are available

Topic

New Reply

But, no, you don’t want to install them.
[See the full post at: Yes, the Win10 Creators Update files are available]

Reply | Quote

Replies

Installed, tried, closed.. and back to Winsows 8.1

my personal journey with Windows 10 so far 🙂

Reply | Quote

I’ll wait until the next update with NEON interface… Skipping this one completely unless Game Mode turns out to do magic :).

And when the next one hits CBB, it’ll be Christmas or so.

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

I have been running the builds on a virtual machine through the insiders program and installed build 15063 on my system yesterday and except for the start menu greyed out there have been no problems.  The start menu isn’t an issue since I use a third party start menu.

But it is a stable, solid build (for me) and the start menu has been the worst of my problems with this or past updates.

Reply | Quote

Not sure what you mean by “Start menu grayed out.”

Are you saying that when you click the Windows logo in the lower left corner, you see a Start menu, but all of the entries are grayed out, and none of them work?

What third party Start menu do you use? Start10? Classic Shell?

Thanks!

Reply | Quote

He propably mean that left-click doesn’t work and Start Menu doesn’t open

i get this a lot, specially in ver 1607

this UWP stuff is very fragile and can be easily broken
specially for tweakers 🙂

Reply | Quote

Clicking on the icon brings up the start menu but none of the tiles or menus are usable (grayed out),  the right click works.  Changing my theme setting seems to have fixed. it though.  I use Start Menu 8 from IOBit.

Reply | Quote

All I can get is a “403 forbidden” message at the moment when I try to download the ISO file from the link provided. This may be a case where they didn’t want the data to get out quite yet… Can’t say that I blame them.

-Noel

Reply | Quote

Or it’s possible that 15063 isn’t the “final” RTM.

The plot thickens.

Reply | Quote

The data gone out already since 20 houtrs or so

but apparently they decided to take it down temporary, until the official availability

1 user thanked author for this post.

woody

Reply | Quote

I thought the release date for 1703 might have been April first. 🙂

Reply | Quote

“I recommend that you do not install these ISOs. In fact, over the course of the week I will describe how to avoid the Creators Update, at least until it’s ready for prime time. No matter how you slice it, Creators Update isn’t ready for any PC that you rely on.” – Woody

Noted, but dismissed out of hand for lack of clarifying justification for such a pointed, yet broad statements. I’m both a commercial customer and private consumer that sees your article as doing nothing more than showing a vain attempt to keep people reading what you write.

The Windows Insider program sure beats the old beta program, but has a drawback in that I see more complaining over substance in a lot of the feedback. At least the Feedback Hub has gotten better at allowing me to filter what is important versus the mundane. Unfortunately the tech media over the years has gotten worse instead of better at providing information and guidance that’s worth anything.

Reply | Quote

“a massive numbers of bugs … by design” is a stretch too. Last time it was referred to by Woody as a “short list”. (But of course, Woody always refers to cumulative updates as “massive”.)

“Microsoft has conveniently pulled the list of released build numbers for version 1511.” seems to be fake news: https://support.microsoft.com/en-us/help/4000824/windows-10-update-history-version-1511

Windows 11 Pro version 22H2 build 22621.2361 + Microsoft 365 + Edge

Reply | Quote

b wrote:

“a massive numbers of bugs … by design” is a stretch too. Last time it was referred to by Woody as a “short list”. (But of course, Woody always refers to cumulative updates as “massive”.)

The Anniversary Update had a massive number of bugs, no matter how you count. Nine cumulative updates in three weeks does not speak well for stability. I’ve never referred to the list of bugs in any of the version changes as “short.” And the patches in February weren’t massive at all. Not sure where you read that.

b wrote:

“Microsoft has conveniently pulled the list of released build numbers for version 1511.” seems to be fake news: https://support.microsoft.com/en-us/help/4000824/windows-10-update-history-version-1511

Take a look at your referenced list. It starts with KB 3135173, build 10586.104. That was cumulative update 9. Microsoft seems to have deleted reference to all of the eight previous cumulative updates.

http://www.infoworld.com/article/3031366/microsoft-windows/microsoft-releases-windows-10-build-10586104-cumulative-update-9-kb-3135173-with-changelog.html

I count 23 cumulative updates for Win10 1511, which has been out for 16 months.

3 users thanked author for this post.

Elly, satrow, radosuaf

Reply | Quote

woody wrote:

I’ve never referred to the list of bugs in any of the version changes as “short.”

“Two weeks ago I posted a short list of the major bugs that continue to bedevil the Windows 10 versions.”
http://www.infoworld.com/article/3120737/microsoft-windows/whats-been-fixed-and-whats-still-broken-in-windows-10.html
(I don’t remember you ever discussing “minor” bugs.)

woody wrote:

And the patches in February weren’t massive at all. Not sure where you read that.

There were patches in February?

Windows 11 Pro version 22H2 build 22621.2361 + Microsoft 365 + Edge

Reply | Quote

That was a short list of the major bugs that remained after six weeks of once-or-twice-a-week patches.

Yes, there were patches in February. Microsoft knew it would have to patch IE, and they dropped the ball.

Reply | Quote

anonymous wrote:

dismissed out of hand for lack of clarifying justification for such a pointed, yet broad statements.

If the move from Anniversary Update to Creators Update goes as smoothly as many would like, you’re absolutely right.

If, on the other hand, it limps along like the Fall Update to Anniversary Update shift, you can come back here and tell me how well it went. 🙂

Reply | Quote

First, I’ve registered since my only anonymous post. Secondly, wanted to let you know that all Insider Preview test platforms, whether a Slow, Preview or Fast ring, have gone through the latest updates loading the Creators Update without any significant (show stopper) issues or problems. Still digging down but haven’t found anything that would preclude me from allowing production, Anniversary Edition, platforms to automatically update when Creator is finally released.

Reply | Quote

The Neowin article saying that Win10 creators update files were available from Microsoft has been revised to say the following:

Update: 18 hours after the ISOs appeared on Microsoft’s servers, it seems they’ve now been pulled, returning 404 errors when trying to download. It’s likely that they’ll return eventually as the ‘final’ RTM release – including the additional 15063.xxxx cumulative updates that will eventually roll out as the Creators Update. For now, it appears that build 15063 won’t be available for a little white so hang in there for now!

Reply | Quote

The links are back online, and now officially available from insider download page
https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewadvanced

nothing changed, still the same 15063.0. version with no updates integrated

1 user thanked author for this post.

woody

Reply | Quote