I had issues with this build after upgrading. Random BSODs, computer refusing to wake up from sleep and a couple other things.
After a clean install, though, this build is as smooth as I Can't Believe It's Not Butter.
Lets face it if Microsoft wants everyone to download huge updates they are going to have to perfect it, it's a huge task because of all the thousands of different configurations, but it will have to be done.
If you like conspiracy theories - it's because Ms is in league with ISP's so the ISP's can charge those who don't have unlimited downloads more money --and even those that do have unlimited downloads the ISP's will say because of increased usage we need to "invest more" (i.e give more to stock holders and management) - or in other words increase our fees to use the Internet !!!!.
We've been through this before with the "Microsoft doesn't want you to go into the BIOS" (and similar) statements on another thread. The fact is that Microsoft needs us to test everything. Including clean installs.
Although it's better now, historically, upgrades have picked up nasties from a prior install. Only a clean install could fix the situation. In fact, during this Technical Preview, I've had issues with upgrades over prior installs that I couldn't get around. One such stuck around for three or four upgrades; I did a clean install and the issue went away.
When a system is flummoxed with things that Gramma's lye soap won't take off, a clean install is in order. This is where Feedback comes in . . . Need I say that you tell Microsoft about all the problems you were having with Build 10xxx and that a clean install cured all or most of them? The more detail we give Microsoft, the better the end result will be.
Yes, Microsoft wants us to test updates first; that's why those of us on the Fast Ring only get the updates as an online upgrade. However, if Microsoft didn't want us to do a clean install, I'm sure Windows would find a way to prevent our use of the .esd file to create an ISO. We're not forbidden to clean install, nor to go the extra mile with our testing.
In the end, it looks like Microsoft has sent us the image in the form of the .esd file. We just have to work to get the ISO out of it.
It's not so much MS being in-league with ISPs, it's more that MS wants and needs the infrastructure that is not limited by bandwidth and unreasonable usage charges. If MS thought that ISPs were going to make a lot of money through their upgrade policy, Microsoft would have added those ISPs to their portfolio in the years leading up to the release of 10.
Governments too want full broadband coverage for all users - if it gets too cheap, they will use it as a source of revenue, adding their own taxes - but as a means to enable e-commerce, working and shopping from home, and generally as a means to progress away from historical problems, which cost governments money - in fact e-currency is a good example there - no more banknotes, or coins, or bank robberies or banks even... ...and so many other situations which are changing because of an interconnected society.
Customers will vote with their choice of ISPs that give the fullest and cheapest service.
As far as images are concerned, I would have thought that upgrades could be delivered incrementally instead of a full system upgrade each time, as well as being available for download as full installable upgrade packages, or a patch to slipstream into the previous full upgrade.
They used to be called Service Releases, and would surely suit the current (fast/slow) insider/mainstream user populations for Windows now, however fast their broadband, as well as those of those overworked MS servers or P2P update networks. Just because many of us can handle the bloat, it doesn't mean we have to.
Solved memory compression churning issue, there is now a reg hack for it.
Followed your step by editing the registry key and reboot. Still got around 1 GB at the system process. :\.
2.6 GB now reserved by the System.
Hey Support Engineer, any update on this? I have to restart my computer many times per day???
I solved it by changing the registry (different from @Alex DC). Open notepad, save the below text (after the start line and before the end line) as .reg extension and run the file:
--------------- START ----------------
Windows Registry Editor Version 5.00
---------- END ---------------------
Yes, you are right but it seems that from now on every "patch" to Windows 10 will be an entirely new version of Windows 10, thus creating one new installation over another for many, many people. Yes they are huge downloads, but for the general populace this might cause headaches after the second or third version of Windows 10 being installed over the old OS that is already sluggish. So is this really Microsoft's vision of an OS as a service?
I'd say that we don't know how MS is going to distribute 'Threshold 2', or whatever the big update in early November is going to be called. It could be in the form of a 'Service Pack'-like deal. Or it could be a full OS download. I sure hope not.
For now, the Insider updates come as entirely new builds, but that doesn't mean that's the way it will be for the final update bits. I'm not going to worry about it until we see how it goes...