Windows 10 Creators Update, non-Insiders opportunity.

I am wondering what happens after the Creators Update. If MS is expecting 'a high chance of various issues' on older hardware (I am assuming they are referring to a processor that meets requirements for W10 but is older gen) with the CU build that is considered somewhat minor in terms of changes, what is the prospect for a build that incorporates major changes? September might be an unpleasant surprise if the build is major.

 

Yes, dism..... /restorehealth gets to 98.4% and then says the source files could not be found. I'm not tampering with the registry as was proposed in the thread. Undoubtedly, this will get fixed sometime down the road.

 

I've noticed this from the very beginning. I've tried several things to no avail. However it is definitely Microsoft issue needing to be addressed. Has to-do with CBS Manifest Corruption of Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0. Sit back and relax and hope Microsoft will get around to addressing this. In the mean-time everything should be working alright.

 

Quick question - If you reset Windows 10 and select to save files I know it removes installed programs but does it wipe installers in your download folder too?

 

No it doesn't.

 

Great! Thanks Roger.

 

Is it true that Creators Update has 465 services? Wow.

Found the info here: https://www.wilderssecurity.com/thr...r-free-pro-updates.385125/page-2#post-2670292

 

I did a clean install of 2016 Windows 10 Enterprise LTSB.

Default start menu drove me crazy... I installed Classic Shell and enabled the Classic Start Menu. Now it works!

LTSB doesn't have Edge, Cortana or universal apps. Perfect for long term stability.

 

the number doesn't matter much, since many of them are set on manual or disabled.

 

This 465 services was specific to machines which were 64-bit and had (I believe 4GB or higher RAM) more memory and what MS had done was split off all of the services which were crammed into svchost.exe for many years. So therefore on 64-bit machines with more RAM, this has much greater performance benefits as well as reliability and stability and of course in the end, more granularity to control which of those services can be enabled/disabled individually. 32-bit machines or machines with less RAM wont have the svchost.exe split off. Remember back in the day when one svchost.exe crash would take down nearly all services?

 

Thank you, good to know.

 

I had not noticed this yet. Nice! This must be at least part of why this version runs so well.

 

That's good news . Now we'll be able to see which service is causing troubles high CPU, disk activity... Also firewall rules could now be created easier. Granular control OTOH over disabling/enabling was possible even before (using services.msc).

 

That news is why I opted to install the stable version of Windows 10.

Consumer versions suck because they're a perpetual beta.

 

The Fast Ring is a perpetual beta. The Creators Update is the most stable version of Windows 10 I have encountered yet. All versions will have hardware and configuration specific issues. Stick with what works for you obviously, but I see no reason for the general public to avoid this one unless you are affected by one of the specifically mentioned issues.

 

Microsoft wants to sell people on the idea they need to be constantly on the bleeding edge with a constant flow of updates and new features.

Irrelevant from the viewpoint of most computer users, who simply want an operating system that works.

 

No worries here. I'm on the LTS branch so odds are good I'll never see it.

 

Windows 10 Creators Update is the best one yet, and this isn't just a personal opinion.

 

Confirms Windows is a rolling release like Ubuntu.

Except Microsoft isn't making LTS available for consumer use. It should.

 

Agreed. This runs way better than any previous version of Windows 10. Or Windows anything for that matter. I have updated every machine I have access to (at least 15) and have had 0 issues. I haven't seen a crash on a single machine since updating them. Which is amazing considering some of my users.