SATC vs Chrome v77 vs GPO/Flags

Question

SATC used to work with Chrome GPO "ForceNetworkInProcess" enabled.
Now this doesn't work anymore, every user would have to enable "chrome://flags/#network-service-in-process" for SATC to work.

This is no option, chrome:/flags is blacklisted, i don't want my users to be able to mess with the flags of chrome...

I think we need a update of SATC as soon as possible, please also see here: https://bugs.chromium.org/p/chromium/issues/detail?id=930750

This thread was automatically locked due to age.

RichBaldry · Accepted Answer

The ability to set this option via GPO was broken in Chrome v77 and v78. The bug was acknowledged here: https://bugs.chromium.org/p/chromium/issues/detail?id=1004179 
 Chrome v79 was released on 10 December 2019 and has fixed the issue. It is once again possible to enforce the "Force networking code to run in the browser process" option in Chrome via GPO. 
 Our understanding is that this option will continue to be available for at least the next 3-4 versions of Chrome. 
 We are working towards a long term solution that works with the new Chrome network service architecture.