Windows 10: All Chromium based browsers crashing on Build 14342.rs1

I'm not sure if there is a fix for this or not. It may take a Microsoft fix to get it sorted.

I received the new build 14342.rs1_release.160506.1708 and immediately my Google Chrome crashed within about 20/30 seconds of loading. Although it was a little later I also noticed that Skype fails to load. It also crashes within 20 or seconds of loading. There may be others but I haven't noticed them yet.

I uninstalled Chrome and reinstalled it again but all was exactly the same. I downloaded Comodo Dragon and three other Chromium based browsers and all crash in exactly the same way; they appear to load perfectly and then stop working and need to be closed.

I have tried running them in 'compatibility' mode and with administrator privileges but nothing changes.

I ran SFC /ScanNow and it show up errors that it is unable to fix. I ran DISM /Online /Cleanup-Image /RestoreHealth and although it appeared to work perefctly running SFC again shows that errors are still present and of course the main problem still remains.

I am just hoping against hope that someone has come up against this problem and solved it.

Any help would be very much appreciated.
Dave

:)

 

Edge automatically signs out from Microsoft Community

When closing Edge, it automatically signs out from Microsoft Community account. So it's necessary to sign in every time when opening Edge. And it's uncomfortable.

All other sites work well including different sites using Microsoft account - outlook.com, onedrive. com, etc. Only Microsoft Community doesn't work properly.

Problem appears in both TH2 and RS1 builds. The first RS1 build with this bug - 14342, in 14332 everything worked well.

To solve the problem I uninstalled all apps which are able to affect internet connectivity and all extensions. No result.

Other browsers including IE work properly.

Here's a link to Feedback Hub.

Minimum 3 moderators including me have this problem. What can we do with it?

 

Windows 10 we couldn't find wireless device on this PC

After installing #14342.rs1 had this problem, reapplying the drivers fixed problem.

 

Most software makers do not support Beta OS's. I seriously doubt Microsoft would waste time fixing Chrome.

 

Aside from that; I could see two ways for me personally to et sorted. One was selecting the option 'Go back to an earlier build' and the other was to pursue the faults shown up by SFC /ScanNow. I don't know (1) if 'going back to an earlier build' removes all installed software or leaves your system intact just as it was proir to the last update or (2) if there are any further options to DISM /Online /Cleanup-Image /RestoreHealth that are likely to be more successful.

 

The question is, why are you using unsupported beta version of Windows on your main system. If I were you I would go back to the last stable version.

If you want to try out the beta version, try it in a virtual environment.

 

Obviously a fair comment. I am on the Slow Ring on the PC and I do have two separate backups to go back to if it all went belly-up. However if I could avoid the hassle and just get it fixed it would be the preferable option. I have had the Fast Ring running on a Tablet since February 2015 and not had any major issues at all. Indeed Chrome is running perfectly on that machine.

 

A tablet is much less complex than a PC so less chance of things going wrong.

 

Does anybody know what the effect is of 'Going back to an earlier build' is? Is it the same as a fresh install while keeping your personal files, or is it as it infers; reinstating the earlier build leaving everything just as it was before the update?

 

You will need to format clean install to roll back. I would not use the roll back feature as it could bring in additional elements into your problems.

 

Ah OK. Thanks for the info. I think I'll just stick it out for the moment.