I don't prefer to do anything but upgrade these days (as I have 200+ programs and games installed), but my c:\ drive (SSD) is dedicated to Windows, drivers, and utilities, exclusively, with everything else on several separate physical drives/partitions spanning a few TB's, so I always backup the latest installed build (c:\) in case of a problem. At any rate, wanted to say that the last three builds, including this one, have all installed perfectly through WU via the Flight upgrade--so haven't needed to go the esd-iso upgrade route in a while (don't need a tlu, etc.). It seems Microsoft has refined the upgrade process so that now it is reliable enough to begin taking for granted--fingers crossed, big grain of salt...
Next time you still claim this is one 'magic' account to ban xinso. Always forgive your enemies; nothing annoys them so much. What I read here today from xinso was not nice. And they do not seem to be any better either. Probably better I leave this place, as some others.
It could be that Pc Build passed testing, but a last minute Bug was found in Mobile that had to be fixed then recompiled.
This has been explained in the previously released Insider Preview Build 14942. I quote: "Service hosts are split into separate processes on PCs with 3.5 GB+ of RAM: If your PC has 3.5+ GB of memory, you may notice an increased number of processes in Task Manager. While this change may look concerning at first glance, many will be excited to find out the motivation behind this change. As the number of preinstalled services grew, they began to get grouped into processes known as service hosts (svchost.exe’s) with Windows 2000. Note that the recommended RAM for PC’s for this release was 256 MB, while the minimum RAM was 64MB. Because of the dramatic increase in available memory over the years, the memory-saving advantage of service hosts has diminished. Accordingly, ungrouping services on memory-rich (3.5+ GB of RAM) PCs running Windows now offers us the opportunity to do the following: 1. Increase reliability: When one service in a service host fails, all services in the service host fail. In other words, the service host process is terminated resulting in termination of all running services within that process. Individual service failure actions are then run. As you may have noticed in Task Manager before, service hosts can contain a lot of services: 2. Increase transparency: Task Manager will now give you a better view into what is going on behind the scenes. You can now see how much CPU, Memory, Disk & Network individual services are consuming.To see the name of the service, click on the left-most arrow such that the Display name drops down. Alternatively, right-click on the header and select 'Command Line' to add the Command Line column. Service names will be listed in the format 'svchost.exe -k <svchost name> -s <service name>.' 3. Reduce servicing costs: Following reports of instability, service engineers, IT admins, and Microsoft engineers can rapidly pinpoint issues to the exact service and fix it. 4. Increase security: Process isolation and individual permission sets for services will increase security. "
Well I've got one bug I'm going to report..I'm using all MS for protection but can't install a defender update:- KB2267602 (Definition 1.231.1329.0) - Error 0x80070643
If I'm not mistaken this is updated almost every hour i just installed 1.231.1343.0 perfectly fine, wouldn't worry about being unprotected.. Just keep updating it no matter even if it is an error chances are new one will be out shortly.
How quickly do Insider Preview builds move into the mainstream? I'm tempted to join, but I can't risk it, since I'm down to one PC at the moment. Just curious to know how long before the mainstream sees these updates.