Why is only one browser working on windows 10?
I currently have Firefox, Chrome and Opera installed (in that order).
At the moment I use Firefox/Opera for personal use and Chrome for work related stuff.
Firefox works like normal. Chrome and Opera however don't seem to load websites until after several times (sometimes never).
I don't know if it maybe a privacy setting or something, (like I couldn't figure out why my microphone wasn't working in Audacity and it was because I had stopped Windows 10 from allowing use of Microphone), however I cannot find any settings.
I have uninstalled and reinstalled all the browsers and ran in safemode, nothing seems to work.
What can I do to resolve this?
google-chrome firefox browser opera
|
show 1 more comment
I currently have Firefox, Chrome and Opera installed (in that order).
At the moment I use Firefox/Opera for personal use and Chrome for work related stuff.
Firefox works like normal. Chrome and Opera however don't seem to load websites until after several times (sometimes never).
I don't know if it maybe a privacy setting or something, (like I couldn't figure out why my microphone wasn't working in Audacity and it was because I had stopped Windows 10 from allowing use of Microphone), however I cannot find any settings.
I have uninstalled and reinstalled all the browsers and ran in safemode, nothing seems to work.
What can I do to resolve this?
google-chrome firefox browser opera
Try 52.222.146.72 - if this works, it's a DNS related issue.
– davidbaumann
Dec 5 at 9:55
@davidbaumann And if it doesn't work? (I get a 403 error).
– DavidPostill♦
Dec 5 at 15:39
I guess it's a DNS related issue, as it connects successfully using the IP. The server does not know which site to display because you connected using the ip.
– davidbaumann
Dec 5 at 15:57
@davidbaumann I don't follow. You say if you can connect to the IP address it's a DNS related issue. Now the case is that one can not connect to that address and you again say that it is a DNS issue. Based on your first statement only succesfully connecting to the IP would signal a DNS issue. Unsu
– Saaru Lindestøkke
Dec 5 at 16:08
Actually, your computer connects to the ip. Otherwise it could not show the 403 Error, but would show a timeout. So connecting to an IP directly works.
– davidbaumann
Dec 5 at 16:22
|
show 1 more comment
I currently have Firefox, Chrome and Opera installed (in that order).
At the moment I use Firefox/Opera for personal use and Chrome for work related stuff.
Firefox works like normal. Chrome and Opera however don't seem to load websites until after several times (sometimes never).
I don't know if it maybe a privacy setting or something, (like I couldn't figure out why my microphone wasn't working in Audacity and it was because I had stopped Windows 10 from allowing use of Microphone), however I cannot find any settings.
I have uninstalled and reinstalled all the browsers and ran in safemode, nothing seems to work.
What can I do to resolve this?
google-chrome firefox browser opera
I currently have Firefox, Chrome and Opera installed (in that order).
At the moment I use Firefox/Opera for personal use and Chrome for work related stuff.
Firefox works like normal. Chrome and Opera however don't seem to load websites until after several times (sometimes never).
I don't know if it maybe a privacy setting or something, (like I couldn't figure out why my microphone wasn't working in Audacity and it was because I had stopped Windows 10 from allowing use of Microphone), however I cannot find any settings.
I have uninstalled and reinstalled all the browsers and ran in safemode, nothing seems to work.
What can I do to resolve this?
google-chrome firefox browser opera
google-chrome firefox browser opera
edited Dec 5 at 15:47
asked Dec 5 at 9:30
Aasim Azam
2546821
2546821
Try 52.222.146.72 - if this works, it's a DNS related issue.
– davidbaumann
Dec 5 at 9:55
@davidbaumann And if it doesn't work? (I get a 403 error).
– DavidPostill♦
Dec 5 at 15:39
I guess it's a DNS related issue, as it connects successfully using the IP. The server does not know which site to display because you connected using the ip.
– davidbaumann
Dec 5 at 15:57
@davidbaumann I don't follow. You say if you can connect to the IP address it's a DNS related issue. Now the case is that one can not connect to that address and you again say that it is a DNS issue. Based on your first statement only succesfully connecting to the IP would signal a DNS issue. Unsu
– Saaru Lindestøkke
Dec 5 at 16:08
Actually, your computer connects to the ip. Otherwise it could not show the 403 Error, but would show a timeout. So connecting to an IP directly works.
– davidbaumann
Dec 5 at 16:22
|
show 1 more comment
Try 52.222.146.72 - if this works, it's a DNS related issue.
– davidbaumann
Dec 5 at 9:55
@davidbaumann And if it doesn't work? (I get a 403 error).
– DavidPostill♦
Dec 5 at 15:39
I guess it's a DNS related issue, as it connects successfully using the IP. The server does not know which site to display because you connected using the ip.
– davidbaumann
Dec 5 at 15:57
@davidbaumann I don't follow. You say if you can connect to the IP address it's a DNS related issue. Now the case is that one can not connect to that address and you again say that it is a DNS issue. Based on your first statement only succesfully connecting to the IP would signal a DNS issue. Unsu
– Saaru Lindestøkke
Dec 5 at 16:08
Actually, your computer connects to the ip. Otherwise it could not show the 403 Error, but would show a timeout. So connecting to an IP directly works.
– davidbaumann
Dec 5 at 16:22
Try 52.222.146.72 - if this works, it's a DNS related issue.
– davidbaumann
Dec 5 at 9:55
Try 52.222.146.72 - if this works, it's a DNS related issue.
– davidbaumann
Dec 5 at 9:55
@davidbaumann And if it doesn't work? (I get a 403 error).
– DavidPostill♦
Dec 5 at 15:39
@davidbaumann And if it doesn't work? (I get a 403 error).
– DavidPostill♦
Dec 5 at 15:39
I guess it's a DNS related issue, as it connects successfully using the IP. The server does not know which site to display because you connected using the ip.
– davidbaumann
Dec 5 at 15:57
I guess it's a DNS related issue, as it connects successfully using the IP. The server does not know which site to display because you connected using the ip.
– davidbaumann
Dec 5 at 15:57
@davidbaumann I don't follow. You say if you can connect to the IP address it's a DNS related issue. Now the case is that one can not connect to that address and you again say that it is a DNS issue. Based on your first statement only succesfully connecting to the IP would signal a DNS issue. Unsu
– Saaru Lindestøkke
Dec 5 at 16:08
@davidbaumann I don't follow. You say if you can connect to the IP address it's a DNS related issue. Now the case is that one can not connect to that address and you again say that it is a DNS issue. Based on your first statement only succesfully connecting to the IP would signal a DNS issue. Unsu
– Saaru Lindestøkke
Dec 5 at 16:08
Actually, your computer connects to the ip. Otherwise it could not show the 403 Error, but would show a timeout. So connecting to an IP directly works.
– davidbaumann
Dec 5 at 16:22
Actually, your computer connects to the ip. Otherwise it could not show the 403 Error, but would show a timeout. So connecting to an IP directly works.
– davidbaumann
Dec 5 at 16:22
|
show 1 more comment
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1380948%2fwhy-is-only-one-browser-working-on-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1380948%2fwhy-is-only-one-browser-working-on-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Try 52.222.146.72 - if this works, it's a DNS related issue.
– davidbaumann
Dec 5 at 9:55
@davidbaumann And if it doesn't work? (I get a 403 error).
– DavidPostill♦
Dec 5 at 15:39
I guess it's a DNS related issue, as it connects successfully using the IP. The server does not know which site to display because you connected using the ip.
– davidbaumann
Dec 5 at 15:57
@davidbaumann I don't follow. You say if you can connect to the IP address it's a DNS related issue. Now the case is that one can not connect to that address and you again say that it is a DNS issue. Based on your first statement only succesfully connecting to the IP would signal a DNS issue. Unsu
– Saaru Lindestøkke
Dec 5 at 16:08
Actually, your computer connects to the ip. Otherwise it could not show the 403 Error, but would show a timeout. So connecting to an IP directly works.
– davidbaumann
Dec 5 at 16:22