|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
November 17th 17, 09:29 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
Firefox starts with windows 10 and has wrong start page
Sometimes Firefox starts automatically when I start Windows 10 and it
has MSN as the start page. If I click on the homepage button the right homepage comes up. If I close Firefox and restart it it starts normally. I can't find any startup entry. 
|
| Ads |
|
#2
November 17th 17, 10:04 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Firefox starts with windows 10 and has wrong start page
On 11/17/2017 3:49 PM, Wolf K wrote:
On 2017-11-17 16:29, Lucifer Morningstar wrote: Sometimes Firefox starts automatically when I start Windows 10 and it has MSN as the start page. If I click on the homepage button the right homepage comes up. If I close Firefox and restart it it starts normally. I can't find any startup entry. Options - General - "Startup" - "When Firefox starts" select from dro pdown menu. Unless FF 57 has dropped that option, in which case it's just another deal-breaker for me. WTF are those devs thinking? All we want is faster and more secure. All the rest should stay as it is. There's absolutely no need to tinker with the GUI and customisation. Hi, Lucifer, I just opened mine and it did the same thing! Opened to MSN. home button set me back home. It only did it once and now seems OK. Now got to get used to the GUI changes. Rene
|
|
#3
November 17th 17, 10:15 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Firefox starts with windows 10 and has wrong start page
Wolf K wrote:
Options - General - "Startup" - "When Firefox starts" select from dro pdown menu. Unless FF 57 has dropped that option, in which case it's just another deal-breaker for me. WTF are those devs thinking? All we want is faster and more secure. All the rest should stay as it is. There's absolutely no need to tinker with the GUI and customisation. No it still there. When Firefox starts []Show your home page []Show a blank page []Show your windows and tabs from last time -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com
|
|
#4
November 17th 17, 10:24 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Firefox starts with windows 10 and has wrong start page
Lucifer Morningstar wrote:
Sometimes Firefox starts automatically when I start Windows 10 and it has MSN as the start page. If I click on the homepage button the right homepage comes up. If I close Firefox and restart it it starts normally. I can't find any startup entry. My guess is that just the URL (e.g., www.msn.com) is getting loaded by a startup program, even if the startup entry is only the URL which then has it use the default URL handler (which is probably Firefox if you made it the default web browser). Use SysInternals AutoRuns to search for any startup item that has "msn.com" (sans quotes) in its command string. Same happen when you disable all startup program and restart Windows? If it still happens with all startup programs disabled, start Windows in its safe mode with networking and see if Firefox still loads on Windows startup.
|
|
#5
November 18th 17, 12:22 AM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Firefox starts with windows 10 and has wrong start page
On 11/17/2017 4:29 PM, Lucifer Morningstar wrote:
Sometimes Firefox starts automatically when I start Windows 10 and it has MSN as the start page. If I click on the homepage button the right homepage comes up. If I close Firefox and restart it it starts normally. I can't find any startup entry. As Vanguard suggests, a start-up program is launching your default browser (FF?) with the MSN URL. The question is which one? I would think that a hint could be found on the MSN page that comes up. -- best regards, Neil
|
|
#6
November 18th 17, 02:10 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Firefox starts with windows 10 and has wrong start page
"Lucifer Morningstar" wrote in message ... Sometimes Firefox starts automatically when I start Windows 10 and it has MSN as the start page. If I click on the homepage button the right homepage comes up. If I close Firefox and restart it it starts normally. I can't find any startup entry. I believe that's part of Microsoft's "phone home" philosophy. I have my PCs and my cable modem on the the same UPS, which I use to turn everything off at night. When I turn the UPS on in the morning, the PC usually boots up faster than the cable modem, and FF will be up with a "cannot connect to MSMSN blah blah blah" message on the screen. Most of the time, FF doesn't pop up, but occasionally, the timing must be just right between the two devices' boot times, and FF will be on the MSN site. Close it out and the next time I start FF, it's on my home page. -- SC Tom
|
|
#7
November 19th 17, 12:20 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Firefox starts with windows 10 and has wrong start page
"SC Tom" wrote in message news  "Lucifer Morningstar" wrote in message ... Sometimes Firefox starts automatically when I start Windows 10 and it has MSN as the start page. If I click on the homepage button the right homepage comes up. If I close Firefox and restart it it starts normally. I can't find any startup entry. I believe that's part of Microsoft's "phone home" philosophy. I have my PCs and my cable modem on the the same UPS, which I use to turn everything off at night. When I turn the UPS on in the morning, the PC usually boots up faster than the cable modem, and FF will be up with a "cannot connect to MSMSN blah blah blah" message on the screen. Most of the time, FF doesn't pop up, but occasionally, the timing must be just right between the two devices' boot times, and FF will be on the MSN site. Close it out and the next time I start FF, it's on my home page. To add further to this, I turned my laptop on before I turned on the modem. It came up with the "We're sorry" page, and the address it was looking for is "http://www.msftconnecttest.com/redirect". If I refresh the page (after the modem is up), it goes directly to MSN. -- SC Tom
|
|
#8
November 19th 17, 04:08 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Firefox starts with windows 10 and has wrong start page
On Sun, 19 Nov 2017 07:20:59 -0500, "SC Tom" wrote:
"SC Tom" wrote in message news "Lucifer Morningstar" wrote in message ... Sometimes Firefox starts automatically when I start Windows 10 and it has MSN as the start page. If I click on the homepage button the right homepage comes up. If I close Firefox and restart it it starts normally. I can't find any startup entry. I believe that's part of Microsoft's "phone home" philosophy. I have my PCs and my cable modem on the the same UPS, which I use to turn everything off at night. When I turn the UPS on in the morning, the PC usually boots up faster than the cable modem, and FF will be up with a "cannot connect to MSMSN blah blah blah" message on the screen. Most of the time, FF doesn't pop up, but occasionally, the timing must be just right between the two devices' boot times, and FF will be on the MSN site. Close it out and the next time I start FF, it's on my home page. To add further to this, I turned my laptop on before I turned on the modem. It came up with the "We're sorry" page, and the address it was looking for is "http://www.msftconnecttest.com/redirect". If I refresh the page (after the modem is up), it goes directly to MSN. The link above is how Windows tells the user that they do or do not have "Internet access". That's the status you see when you click the Network connectoid/icon in your System Tray (status area). The behavior is supposed to be that Windows silently tries to retrieve that link, which consists of a HTTP Redirect, then if successful, simply do not follow the redirect and instead close the connection. Interestingly, that redirect leads to another redirect, and the second redirect leads to msn.com. You can see all of that with curl, as follows. Note the presence of the HTTP 302 response code, along with the Location header telling the browser where to go next: # curl -v http://www.msftconnecttest.com/redirect * About to connect() to www.msftconnecttest.com port 80 (#0) * Trying 13.107.4.52... connected * Connected to www.msftconnecttest.com (13.107.4.52) port 80 (#0) GET /redirect HTTP/1.1 User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8y zlib/1.2.3 libidn/0.6.5 Host: www.msftconnecttest.com Accept: */* HTTP/1.1 302 Found Location: http://go.microsoft.com/fwlink/?Link...72&clcid=0x409 Server: Microsoft-IIS/10.0 X-MSEdge-Ref: Ref A: 337421B960CF49CB94FA0691BE9CED59 Ref B: DALEDGE0707 Ref C: 2017-11-19T15:54:17Z Date: Sun, 19 Nov 2017 15:54:16 GMT Content-Length: 0 * Connection #0 to host www.msftconnecttest.com left intact * Closing connection #0 # curl -v http://go.microsoft.com/fwlink/?Link...72&clcid=0x407 * About to connect() to go.microsoft.com port 80 (#0) * Trying 23.40.18.233... connected * Connected to go.microsoft.com (23.40.18.233) port 80 (#0) GET /fwlink/?LinkID=219472 HTTP/1.1 User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8y zlib/1.2.3 libidn/0.6.5 Host: go.microsoft.com Accept: */* HTTP/1.1 302 Moved Temporarily Cache-Control: no-cache Pragma: no-cache Expires: -1 Location: http://www.msn.com/?ocid=wispr&pc=u377 Server: Microsoft-IIS/8.5 X-AspNetMvc-Version: 5.2 X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET Content-Length: 0 Date: Sun, 19 Nov 2017 15:55:09 GMT Connection: keep-alive * Connection #0 to host go.microsoft.com left intact * Closing connection #0
|
|
#9
November 20th 17, 04:03 AM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Firefox starts with windows 10 and has wrong start page
On Sun, 19 Nov 2017 10:08:57 -0600, Char Jackson
wrote: On Sun, 19 Nov 2017 07:20:59 -0500, "SC Tom" wrote: "SC Tom" wrote in message news "Lucifer Morningstar" wrote in message ... Sometimes Firefox starts automatically when I start Windows 10 and it has MSN as the start page. If I click on the homepage button the right homepage comes up. If I close Firefox and restart it it starts normally. I can't find any startup entry. I believe that's part of Microsoft's "phone home" philosophy. I have my PCs and my cable modem on the the same UPS, which I use to turn everything off at night. When I turn the UPS on in the morning, the PC usually boots up faster than the cable modem, and FF will be up with a "cannot connect to MSMSN blah blah blah" message on the screen. Most of the time, FF doesn't pop up, but occasionally, the timing must be just right between the two devices' boot times, and FF will be on the MSN site. Close it out and the next time I start FF, it's on my home page. To add further to this, I turned my laptop on before I turned on the modem. It came up with the "We're sorry" page, and the address it was looking for is "http://www.msftconnecttest.com/redirect". If I refresh the page (after the modem is up), it goes directly to MSN. The link above is how Windows tells the user that they do or do not have "Internet access". That's the status you see when you click the Network connectoid/icon in your System Tray (status area). The behavior is supposed to be that Windows silently tries to retrieve that link, which consists of a HTTP Redirect, then if successful, simply do not follow the redirect and instead close the connection. Interestingly, that redirect leads to another redirect, and the second redirect leads to msn.com. You can see all of that with curl, as follows. Note the presence of the HTTP 302 response code, along with the Location header telling the browser where to go next: # curl -v http://www.msftconnecttest.com/redirect * About to connect() to www.msftconnecttest.com port 80 (#0) * Trying 13.107.4.52... connected * Connected to www.msftconnecttest.com (13.107.4.52) port 80 (#0) GET /redirect HTTP/1.1 User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8y zlib/1.2.3 libidn/0.6.5 Host: www.msftconnecttest.com Accept: */* HTTP/1.1 302 Found Location: http://go.microsoft.com/fwlink/?Link...72&clcid=0x409 Server: Microsoft-IIS/10.0 X-MSEdge-Ref: Ref A: 337421B960CF49CB94FA0691BE9CED59 Ref B: DALEDGE0707 Ref C: 2017-11-19T15:54:17Z Date: Sun, 19 Nov 2017 15:54:16 GMT Content-Length: 0 * Connection #0 to host www.msftconnecttest.com left intact * Closing connection #0 # curl -v http://go.microsoft.com/fwlink/?Link...72&clcid=0x407 * About to connect() to go.microsoft.com port 80 (#0) * Trying 23.40.18.233... connected * Connected to go.microsoft.com (23.40.18.233) port 80 (#0) GET /fwlink/?LinkID=219472 HTTP/1.1 User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8y zlib/1.2.3 libidn/0.6.5 Host: go.microsoft.com Accept: */* HTTP/1.1 302 Moved Temporarily Cache-Control: no-cache Pragma: no-cache Expires: -1 Location: http://www.msn.com/?ocid=wispr&pc=u377 Server: Microsoft-IIS/8.5 X-AspNetMvc-Version: 5.2 X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET Content-Length: 0 Date: Sun, 19 Nov 2017 15:55:09 GMT Connection: keep-alive * Connection #0 to host go.microsoft.com left intact * Closing connection #0 C:\Users\Lucyping msftconnecttest.com Pinging msftconnecttest.com [40.84.199.233] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Ping statistics for 40.84.199.233: Packets: Sent = 3, Received = 0, Lost = 3 (100% loss), Control-C ^C C:\Users\Lucytracert msftconnecttest.com Tracing route to msftconnecttest.com [40.84.199.233] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms dsldevice.gateway [10.0.0.2] 2 26 ms 26 ms 25 ms 172.18.209.11 3 26 ms 26 ms 26 ms 172.18.65.205 4 28 ms 26 ms 27 ms bundle-ether4.chw-edge902.sydney.telstra.net [203.50.12.110] 5 26 ms 27 ms 27 ms bundle-ether2.ken-edge902.sydney.telstra.net [203.50.11.104] 6 28 ms 26 ms 28 ms bundle-ether14.ken-core10.sydney.telstra.net [203.50.11.96] 7 26 ms 26 ms 26 ms bundle-ether1.ken-edge901.sydney.telstra.net [203.50.11.95] 8 28 ms 26 ms 25 ms mic1909400.lnk.telstra.net [139.130.58.222] 9 27 ms 27 ms 28 ms ae11-0.syd03-96cbe-1b.ntwk.msn.net [104.44.226.159] 10 119 ms 119 ms 119 ms ae6-0.hnl01-96cbe-1a.ntwk.msn.net [104.44.226.252] 11 167 ms 166 ms 166 ms ae29-0.lax-96cbe-1a.ntwk.msn.net [104.44.227.145] 12 193 ms 193 ms 192 ms be-73-0.ibr02.lax03.ntwk.msn.net [198.206.164.233] 13 193 ms 192 ms 192 ms be-3-0.ibr01.sn4.ntwk.msn.net [104.44.4.5] 14 190 ms 191 ms 190 ms ae66-0.sn2-96cb-1b.ntwk.msn.net [104.44.9.59] 15 * * * Request timed out. 16 * * * Request timed out. 17 ^C
|
|
#10
November 20th 17, 04:29 AM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Firefox starts with windows 10 and has wrong start page
Lucifer Morningstar wrote:
On Sun, 19 Nov 2017 10:08:57 -0600, Char Jackson wrote: On Sun, 19 Nov 2017 07:20:59 -0500, "SC Tom" wrote: "SC Tom" wrote in message news
"Lucifer Morningstar" wrote in message ... Sometimes Firefox starts automatically when I start Windows 10 and it has MSN as the start page. If I click on the homepage button the right homepage comes up. If I close Firefox and restart it it starts normally. I can't find any startup entry. I believe that's part of Microsoft's "phone home" philosophy. I have my PCs and my cable modem on the the same UPS, which I use to turn everything off at night. When I turn the UPS on in the morning, the PC usually boots up faster than the cable modem, and FF will be up with a "cannot connect to MSMSN blah blah blah" message on the screen. Most of the time, FF doesn't pop up, but occasionally, the timing must be just right between the two devices' boot times, and FF will be on the MSN site. Close it out and the next time I start FF, it's on my home page. To add further to this, I turned my laptop on before I turned on the modem. It came up with the "We're sorry" page, and the address it was looking for is "http://www.msftconnecttest.com/redirect". If I refresh the page (after the modem is up), it goes directly to MSN. The link above is how Windows tells the user that they do or do not have "Internet access". That's the status you see when you click the Network connectoid/icon in your System Tray (status area). The behavior is supposed to be that Windows silently tries to retrieve that link, which consists of a HTTP Redirect, then if successful, simply do not follow the redirect and instead close the connection. Interestingly, that redirect leads to another redirect, and the second redirect leads to msn.com. You can see all of that with curl, as follows. Note the presence of the HTTP 302 response code, along with the Location header telling the browser where to go next: # curl -v http://www.msftconnecttest.com/redirect * About to connect() to www.msftconnecttest.com port 80 (#0) * Trying 13.107.4.52... connected * Connected to www.msftconnecttest.com (13.107.4.52) port 80 (#0) GET /redirect HTTP/1.1 User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8y zlib/1.2.3 libidn/0.6.5 Host: www.msftconnecttest.com Accept: */* HTTP/1.1 302 Found Location: http://go.microsoft.com/fwlink/?Link...72&clcid=0x409 Server: Microsoft-IIS/10.0 X-MSEdge-Ref: Ref A: 337421B960CF49CB94FA0691BE9CED59 Ref B: DALEDGE0707 Ref C: 2017-11-19T15:54:17Z Date: Sun, 19 Nov 2017 15:54:16 GMT Content-Length: 0 * Connection #0 to host www.msftconnecttest.com left intact * Closing connection #0 # curl -v http://go.microsoft.com/fwlink/?Link...72&clcid=0x407 * About to connect() to go.microsoft.com port 80 (#0) * Trying 23.40.18.233... connected * Connected to go.microsoft.com (23.40.18.233) port 80 (#0) GET /fwlink/?LinkID=219472 HTTP/1.1 User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8y zlib/1.2.3 libidn/0.6.5 Host: go.microsoft.com Accept: */* HTTP/1.1 302 Moved Temporarily Cache-Control: no-cache Pragma: no-cache Expires: -1 Location: http://www.msn.com/?ocid=wispr&pc=u377 Server: Microsoft-IIS/8.5 X-AspNetMvc-Version: 5.2 X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET Content-Length: 0 Date: Sun, 19 Nov 2017 15:55:09 GMT Connection: keep-alive * Connection #0 to host go.microsoft.com left intact * Closing connection #0 C:\Users\Lucyping msftconnecttest.com Pinging msftconnecttest.com [40.84.199.233] with 32 bytes of data: Request timed out. Request timed out. Request timed out. That means ICMP is turned off on the server. You can kill ping, without killing other functions. ******* And that's not the same address that older OSes use for the desktop networking icon state. The older test did not attempt to foist anything on users. It delivered a tiny file purely for connectivity checking. And that's why practically nobody knows the address, because it never broke anything. https://blogs.technet.microsoft.com/...n-status-icon/ "Every time a network configuration event occurs (meaning that something has changed in the network configuration), the NCSI process performs several tests to identify the network’s connectivity status. 1) DNS query for www.msftncsi.com. 2) HTTP get request for http://www.msftncsi.com/ncsi.txt. This file is a plain-text file and contains only the text "Microsoft NCSI." 3) DNS query for dns.msftncsi.com. " If you try that test, you'll notice it loads pretty fast. No Javascript to slow it down. No Google AdSense :-) Paul
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Linear Mode
