link to 2004 media creation or iso
- Thread starter pcpete
- Start date
pcpete
Well-Known Member
- Reaction score
- 564
interesting. Considering they are installing it on some, I figured it was available
Porthos
Well-Known Member
- Reaction score
- 14,075
- Location
- San Antonio Tx
Only the insiders have it now or a download from UUP dump like I got mine.
Who are 'they'?
I believe it is RTM and available to MSDN subscribers, as well as insiders. I won't use it on customer computers until it's available via the Media Creation Tool.
Mike McCall
Well-Known Member
- Reaction score
- 1,073
- Location
- Silverton, Oregon
I have several clients who show it available. A mix of Home and Pro OS versions.
Porthos
Well-Known Member
- Reaction score
- 14,075
- Location
- San Antonio Tx
Markverhyden
Well-Known Member
- Reaction score
- 11,097
- Location
- Raleigh, NC
When I first saw this thread title I'm thinking...
Office 2004?
Server 2004?
and so on.....
Office 2004?
Server 2004?
and so on.....
britechguy
Well-Known Member
- Reaction score
- 4,850
- Location
- Staunton, VA
Yes. The very moment that Microsoft announces the release of the latest Feature Update the MCT is revised to fetch it, and if you fetch the MCT it has indicated the Version number it's meant to create for a number of releases now.
P.S. Just did a download of the MCT so I have it for later. What downloads is MediaCreationTool2004.exe
Last edited:
britechguy
Well-Known Member
- Reaction score
- 4,850
- Location
- Staunton, VA
Only select users in the earliest Windows Update cohorts will have the Download and Install link for this feature update at the moment. It, like all feature update roll-outs, will be a months long process.
Just for giggles I did a manual check for updates in Settings, Windows Update both yesterday and today, and Microsoft has apparently not placed my machine in an Windows Update cohort yet.
Also, and everyone here should already know this, it is best not to force update a Feature Update, whether by MCT or manual checking, during the early weeks of any Feature Update.
Windows 10, Version 2004 - Why you should hold off from updating early.
Markverhyden
Well-Known Member
- Reaction score
- 11,097
- Location
- Raleigh, NC
I've got it. Wondering if it's because this laptop's installation is from MAP
britechguy
Well-Known Member
- Reaction score
- 4,850
- Location
- Staunton, VA
Microsoft, and only Microsoft, knows the algorithm used to form "Ready for the Feature Update" cohorts for a given Feature Update.
Some of my machines have been on the very bleeding edge - first day (and when the Feature Update process was far less under the end user's control than it is now) - for some Feature Updates and don't have the option appear for months for others.
I imagine the algorithm is a moving target, too, as things can change pretty significantly if telemetry is indicating there are issues that had not been encountered during in-house testing or in the Windows Insiders machines. The quoted blurb in the topic I gave the link to clearly indicates that they've stopped sending the Feature Update out to machines determined to have specific hardware until the issue(s) with same are fixed.
I really cannot imagine trying to manage Windows 10 Feature Updates. There are untold millions of computers that were never designed for Windows 10, and that were never certified for it, that are running it and heaven knows what additional hardware bits are in those that haven't been produced for years. It is absolutely impossible for Microsoft, or any other software maker with such a huge embedded user base, to test for all the system configurations that their software is going to encounter "in the wild" once it's released to the public.
Markverhyden
Well-Known Member
- Reaction score
- 11,097
- Location
- Raleigh, NC
Therein lies the problem. We have no idea what telemetry is involved. I, for one, don't trust any of these companies when it comes to data.
britechguy
Well-Known Member
- Reaction score
- 4,850
- Location
- Staunton, VA
Mark, that's actually not true. Microsoft has published extensive documentation about system health telemetry, and what is potentially included (as not everything is for every report) at each and every level setting for said telemetry.
I used to have the link to that exact reference on their site, but no longer do. I'll bet my bottom dollar that one of the articles returned by this search, https://duckduckgo.com/?q=Microsoft+Windows+10+Telemetry+Levels, will point directly to that reference material. I just don't feel like poring through it right now, as I've read it before.
I keep my telemetry level at "Basic" on all machines I have authority over after having reviewed what may be included at each level.
I used to have the link to that exact reference on their site, but no longer do. I'll bet my bottom dollar that one of the articles returned by this search, https://duckduckgo.com/?q=Microsoft+Windows+10+Telemetry+Levels, will point directly to that reference material. I just don't feel like poring through it right now, as I've read it before.
I keep my telemetry level at "Basic" on all machines I have authority over after having reviewed what may be included at each level.
nlinecomputers
Well-Known Member
- Reaction score
- 8,595
- Location
- Midland TX
I for one would NOT install a minutes old version of Windows on any of my clients. They have too sorry a reputation of falling over out of the gate to risk my reputation doing that. I always wait 30 days before I first deploy one to clients. Sometimes more. OTOH please do so. **** like that is how I gain new clients.
britechguy
Well-Known Member
- Reaction score
- 4,850
- Location
- Staunton, VA
Which is an excellent, and entirely reasonable, approach.
I moderate on several different groups that have a focus on screen reading and/or magnification technology for blind or low vision users and a Windows 10 for Screen Reader Users group. Those of us who are admins/moderators have been begging, pleading, and, sometimes, screaming at people NOT to run out and force update Windows 10 on the first day of a Feature Update for as long as there have been Feature Updates. There are always issues, sometimes trivial ones, occasionally not, but why put yourself into the position of having to deal with them unless your machine was placed into one of the early update cohorts? Even then, the way Windows Update has been working for a while now, and even under Windows 10 Home, the end user is presented with the Download and install link for the Feature Update in the Windows Update Pane of Update & Security Settings. It won't install, literally for months on end, unless they activate it.
My previous message (#12) includes a direct link to a message where a member on one of those groups directly quotes Microsoft's "problem notes" from the first day of release.
If you have the option, let someone else be the "bug shaker out-er" and only activate that Download and install link after a few weeks have passed, at a minimum, unless there is something in a Feature Update that you absolutely, positively must have to accomplish something that you can't accomplish easily now (and that's very, very rare indeed).
HFultzjr
Well-Known Member
- Reaction score
- 907
- Location
- Central PA, USA
But it's 16 years old........2004!
I can just see the questions coming already.....LOL!
Sky-Knight
Well-Known Member
- Reaction score
- 5,634
- Location
- Arizona
I only support PRO as an OS, I DESPISE Home... specifically because Home cannot defer feature updates.
Configure Pro to defer feature updates for at least 90 days, I actually do 180 in full production. And watch ALL of your feature update woes simply melt away.
I won't put 2004 into my own network for another month at best, clients won't see it for at least 90 days.
Configure Pro to defer feature updates for at least 90 days, I actually do 180 in full production. And watch ALL of your feature update woes simply melt away.
I won't put 2004 into my own network for another month at best, clients won't see it for at least 90 days.
britechguy
Well-Known Member
- Reaction score
- 4,850
- Location
- Staunton, VA
Seriously, did you pay any attention to what I just said.
You may not be able to set up "formal deferral" on Home as you can on Pro, but the way it works now you effectively can defer for months by not activating the Download and install link.
I'm typing from a Pro machine, but support mostly Home machines. None have auto-updated for quite a while now, because auto-updating will only occur at the very end of the roll-out period if the user has not activated that link, and the end of any Feature Update roll-out is literally and always months after the initial release date.
Potato, Po-tah-to.
Sky-Knight
Well-Known Member
- Reaction score
- 5,634
- Location
- Arizona
@britechguy, I know the behavior changed, and the new behavior is vastly improved. However, that doesn't change the fact that Microsoft uses the entire Home installation base at random as their first installers.
You will still have random units upgrade without input, and they'll do so sometime within the year after release. Yes, they'll get it now if they push the link to do so. But you still lack the control Pro provides.
This also doesn't exclude the silly people that manage to put themselves in the insider program...
You will still have random units upgrade without input, and they'll do so sometime within the year after release. Yes, they'll get it now if they push the link to do so. But you still lack the control Pro provides.
This also doesn't exclude the silly people that manage to put themselves in the insider program...
Similar threads
