[DISCUSSION] Windows 10 (1709 RS3) "Fall Creators Update" Final 16299.15 , 16299.64 & 16299.125 (PC)

Then why does it say dec? and not jan? Right.

 

what i posted are MSDN filenames and posted dec
yours are VLSC filenames and posted jan

 

any direct link to
*en_windows_10_multi-edition_vl_version_1709_updated_dec_2017_x64_dvd_100406172.iso

thanks.
Ahsan

 

@Ahsan

all nfo's are on 1st page

 

still waiting for redstone 4 , it is 16th March already

 

Can someone explain to me what's the difference between using the Media Creation Tool vs downloading the ISO:
en_windows_10_multi-edition_version_1709_updated_dec_2017_x64_dvd_100406711.iso ???

Is the Media Creation tool fetching a more updated build?
Is there a way to have the latest RS3 build + all updates in a AiO solution?

 

You need to login to view this posts content.

 

if you are willing to install win10 on only one powerful machine, no need to integrate the updates, there is no point in doing this when you use a powerful machine because the updates will be installed without you even knowing about it, to me the only advantage of integrating updates into iso is for old machines, in this case, you will save time otherwise if you choose to not integrate them, you will notice some slowness using the pc while updates are being downloaded and installed through WU.

 

So, other than time-saving whilst deploying on multiple machines, there's no actual benefit in integrating updates to an ISO prior installation. I was thinking that such a house-keeping process you mention (installing updates / deleting all superseded ones) would be somewhat messy and result in a slower system. As it usually happens over time, when new hotfixes / updates are released and installed. I have observed this marginal performance deterioration over time with Windows 7 installations (I am not talking about performance loss / slowness during update installation, but afterwards.

Other possible factors considered (e.g. installing other 3rd party apps, disk fragmentation etc), I am pretty convinced that OS system updates, do have an impact on performance in the long term. But it is a sucrifice we must take anyways, as security / correct functionality comes first.

For example, consider it like a road under construction. Having the road repaired all in one goal vs having it partially repaired here and there and then dig and patch and so on. The later will end up being a road full of bumps.

My approach on a new build has always been like: hardware/firmware update(where applicable) >>> OS installation >>> OS patch/hotfix installation >>> drivers >>> applications.
Of course, in the long term, you will have to install an OS update, which in turn might cripple a driver or functionality of an xyz application. But this is inevitable.

 

Well, yes, but I d take it 16299.15 is relatively 'fresh'. I m talking about running an installation for several years. The performance loss I mentioned is observed on installations running anything from 2 - 5 years. Then, it would be a different case.

Now, given the (much) shorter release lifecycle of Win10 (an average of 2 years per release), I guess I won't be noticing that performance deterioration, as I ll definitely have to clean-install every 2 years tops.

 

Do you change your vehicle's engine oil every 3,000 miles / 5,000 kilometres ?
Do you wait until the engine oil life indicator reaches 0%?
Do you carry a case of engine oil in the trunk / boot of your vehicle and change the engine oil when you buy a new case of oil ?
"Fresh" means different things to different people.

 

You need to login to view this posts content.

 

funy = Interestingly, it lists the “initial build” (meaning RTM) as 17115 !
Second = Microsoft is still working on finalizing Redstone 4 with Windows Insiders and it is best not to take the “initial build” part too seriously for now

 

yes wait till april.

 

April is for the public. So probably you can get esd file before April.

 

You need to login to view this posts content.