A new week, a new pile-up in a cumulative patch package to W10.AU which moves it up to built 14393.186 (follow link at bottom of article): http://borncity.com/win/2016/09/14/fix-window...y-update-kb3189866-hangs/ , mere 431MB for the 64bit platform.

A new phenomenon I encounter is File Explorer goes unresponsive at some trivial actions such as copy / paste at the copy point, or simply selecting an item, the mouse wheel icon then spinning for a minute, after which explorer crashes and with it the Taskbar and several apps such as BOINCTasks, which then have to be started again. BOINC itself survives this (running as service), don't know if running as user app.

The number of File Explorer Crashing reports on the feedback hub are truly numerous, and since longer, way before the 1511 release. One source is having your user documents on a different drive than where the OS is, but that does not apply here... 1 single spinner, only the VM in it's own partition, as is BOINC... to reduce fragmentation and to not have Windows delete the ProgramData content, as it has done on my test machine.

Fortunately, this does not happen if an app accesses the the File Open/Save window, else you'd have in-app exiting with unsaved work as well. File Explorer crashing is a core system issue, which is likely sourced in the half baked transition the OS currently and still is. MS has yet to move all critical parts to the new interface layout.

Why these [expletive] from the computer industry dipped into the Italian dictionary again, is a riddle to me, but Cortana would be a female Consigliere... better known as a Maffia boss councelor (and we have many 'consigliere' here to the 'communities'.

For those done with the ever crashing Groove, get back into Windows Media Player... play music while getting your photographic collection randomly rolled over your display: http://betanews.com/2016/09/08/how-to-install...ws-10-anniversary-update/

To quote myself "A new week, a new pile-up in a cumulative patch package to W10.AU which moves it up to built 14393.186", which is the latest Anniversary Update i.e. the presumed stable release. On 350+ million who got this OS shuffled, there will doubtless be many who have a 'rock-solid' experience, but as noted, the feedback hub is inundated, to include build specific 14393 when you do build specific searches, the 1607 release you're now supposed to have.

Read today that 25% of the new PCs sold to businesses have W10 on it, usually the pro version... good for them. Whilst, MS is rapidly (suspected intentionally) breaking W7 and W8. I'm about to uninstall and pull my W7/8-Pro DVDs and re-image. There's just nothing 'must have' in W10, that I can see.

The supposed stable W10-1607 received another cumulative patch update, build 14393.222 (PC) and 14393.221 (Mobile)

Open the feedback hub (got it now pinned to the taskbar for quick access), where under the announcement section one note says:

"We fixed an issue resulting in Explorer.exe frequently crashing for some Insiders, particularly for those with multiple network switches."

Got only one WIFI to Ethernet bridge to the test system.

Hopefully it does, for it's tiresome to see your system half crash and take some user apps with it (was there not not the claim of sandboxing in this system?)