New
#80
Little late but downloading !
After using it for a day this build is running fine apart from the 400+ error messages showing in event viewer, A fatal error occurred while creating a TLS client credential. The internal error state is 10013.
I've had this for the last 4 builds in the Fast Ring, however they don't seem to cause any problems.
My laptop is running 19603. WU tried to download 19608 on it's own last night. Download failed, it threw error 0x80070002.
Ever since the laptop is so slow as to be pretty much unusable, sign in takes forever then system is brutally slow. Scanned for malware/viruses, ran DCIM and SFC (No problems reported). Ran Windows Update troubleshooter. Nothing was helping.
I discovered that if I could get Task Manager to open and end the Windows Error Reporting Service task (was using 30-40% of CPU), the system would start operating normally.
I disabled the Windows Error Reporting Service and boot/login/operation are back to normal.
Attempted to update to 19608 afterwards still throws 0x80070002 but the system no longer slows down.
I left the Windows Error Reporting Service disabled so I can use the laptop.
Not sure what the next step should be to get 19608 to install and Windows Error Reporting Service back to running. Any ideas?
Maybe restart your computer several times, and see if it helps. Sometimes it takes several restarts in a row to get all things to load properly. If that doesn't work, then delete you video driver, load an older graphics driver, and then restart again. Hope this helps.
- - - Updated - - -
Good information. You can also use NeoSmart Technologies iReboot. It works perfectly, even after an update through WU.
HDR is broken again with this build multiple nvidia driver versions, rolling back.
I have one SSD with two partitions.
Every time I get a new Build of the Fast Ring, it reverts back to Windows 10 (instead of Windows 10 Fast Ring I've named it). Also, I have the default set for Windows 10 Production, but the Fast Ring kicks it out of its way and puts itself first!
I gave up on reporting that issue; now I just change things back to how I had them.
Now, this issue, and when I use the Macrium Rescue Media, both partitions are left at Windows 10.
I'm waiting for the next Fast Ring Build to see if msconfig timing has been changed with the new Build.