After new updates Win10 Opera and chrome doesnt work anymore
-
A Former User last edited by
@cobusopera i dunno if this will help.. Make sure that this flag is not Enabled on Both browsers.. Set the Flag to Default
opera://flags/#network-service
chrome://flags/#network-service
-
A Former User last edited by
@leocg The browsers cannot load the pages an sometimes really slow... Now the other browsers have it also?
-
blackbird71 last edited by
Several questions:
- What version/build-number of Windows 10 Pro are you "clean installing" each time?
- Approximately how many updates is it installing each time when the computer reboots and "finds some updates"?
- How old is your computer?
- What antivirus is installed on the system?
-
A Former User last edited by
@cobusopera try this - go to control panel - click Internet Options - click Connections tab - click LAN Settings button - Uncheck (Automatically detect settings) or it may be called (Detect automatically the configurations)
if its already un-checked no harm..
Note - uncheck use proxy server if it is checked..
actually there should be no boxes checked
-
A Former User last edited by
@blackbird71
17134.112 is the build.
question number 2 i don't know because i cannot turn off the updates(really annoying!) so it is doing it always when im not in front of my pc.
My computer is new AMD ryzen 7 etc. and the first installation i was running AVG and the second time i was running AVAST. -
A Former User last edited by A Former User
Yesterday, Microsoft released a special update (KB4284848), dealing mainly with network issues, applying to Windows 10.
-
blackbird71 last edited by
@cobusopera said in After new updates Win10 Opera and chrome doesnt work anymore:
17134.112 is the build. ...
That indicates you are using the so-called "April Update" Windows 10 (1803 version), and the related patch download that bumped the 1803 version to that build number (17134.112) was KB4284835 which first emerged on 12 June. Depending on the version you've been reinstalling, it's possible that one of the subsequent Windows auto-updates/upgrades following reinstall is triggering the problem. The suggestion from @yanta has merit, since one of the fixes in that just-released update is for an issue Win10 can have with causing the latest Chrome versions to stop working, along with fixing a host of other performance/incompatibility issues.