build 14926 Sfc still stops at 19% and network shares are still absent

I see no difference between this and 915 same error s . oh well back to 905

Hi

Be very careful about reverting to earlier builds. This is explained in a paragraph of the release article for the current build.

An important note about build expirationJust as we’ve always done with pre-release versions of Windows, Insider Preview builds have expiration dates. Starting tomorrow September 15th, PCs running really old Insider Preview builds will start to see build expiration notifications once a day. Then on October 1st, these PCs will start rebooting every 3 hours and then on October 15th – these PCs will stop booting all together. If your PC is running one of these old Insider Preview builds, please make sure you update to Build 14926 via Settings > Update & security > Windows Update. Build 14926 has an updated expiration date of May 1st, 2017. If your PC is running the Windows 10 Anniversary Update (Build 14393) in the Slow and Release Preview rings today – this does not apply to you and you will not be notified of your build expiring.

September 14, 2016 10:02 am

Announcing Windows 10 Insider Preview Build 14926 for PC and Mobile:

Regards

well i disagree .. it will do it once then it will be gone. Now either fix it or quit threatening.

Hi

Nobody is threatening and how can you disagree?

When too many Insiders are using older builds, it really makes it very difficult because the Feedback is about builds that are no longer being developed?

And the SFC not working is a non-issue. SFC was first reported as being problematic with the first Preview Build (9841-10/1/2014). The reason is that the SFC component cannot work with all of the developer code in the files on these pre-release versions.

Regards

Speaking for myself, I want to have a fresh and clean start with a peace of mind with a brand new build such that further problems should not be in any way thought of arising from system files being corrupt in the first place.

Keeping in mind that these first few beta builds of rs2 as stated by Microsoft were going to be buggy, it is expected that there are going to be issues which in our testing any bugs or issues we find are to be reported in the Feedback Hub. These issues would not be found in the public release versions (currently 14393.xxx) where the SFC and DISM would be able to run to completion. Since I have been here from the beginning, I agree with Ronnie's assessment which I am repeating here:

"And the SFC not working is a non-issue. SFC was first reported as being problematic with the first Preview Build (9841-10/1/2014). The reason is that the SFC component cannot work with all of the developer code in the files on these pre-release versions."

Thanks for the fair-enough explanation. It is kind of you to take the time and burden to make it simple and straight.

Regards