Live Not So Live
-
This one has (so far) stumped folks over at the Microsoft "Community". One of my Windows 10 boxes (x64, always updated, so whatever the latest build is) will not let me log in to any programs that reach out to login.live.com for authentication. But only the desktop programs or programs that don't have the authentication built in. The "Store" programs log in with no problem, as does the OS itself. And online things work fine, like signing in to MSDN or whatever. Running a desktop program, all I get is some variation of Can't reach that page or Something went wrong or Connection closed, depending on how the program is set up. So...I can't log in to Visual Studio or TFS, I can't log in to desktop Skype, I can't log in to OneDrive, etc etc etc. Except, and this is the killer, if I have Fiddler running and logging the traffic, all of the programs work just fine. A) What kind of sense does it make to only allow login if there's a spy on the line? B) Fiddler doesn't log anything "wrong" or even iffy. Just normal web requests and responses. (And a LOT of HTTP and HTML formatting errors like expecting X number bytes but receive 0, or unclosed quotations) None of the usual diagnostics like sfc or dism pick up anything, of course.
We won't sit down. We won't shut up. We won't go quietly away. YouTube and My Mu[sic], Films and Windows Programs, etc.
-
Probably. I'm pretty sure I checked that somewhere along the line. I know for sure I never unchecked them for any reason. :p
We won't sit down. We won't shut up. We won't go quietly away. YouTube and My Mu[sic], Films and Windows Programs, etc.
Any PAC files[^] on your network? Or any chance you could be affected by the WPAD name collision vulnerability[^]? If Fiddler's causing a "Schrödinger's Bug", you might need to get down and dirty with Wireshark[^] to track the problem down.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Any PAC files[^] on your network? Or any chance you could be affected by the WPAD name collision vulnerability[^]? If Fiddler's causing a "Schrödinger's Bug", you might need to get down and dirty with Wireshark[^] to track the problem down.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Pretty sure nothing of a proxy nature appears anywhere in my systems. I'll double check, and check the modem/router, too, to make sure they haven't "improved" it without telling me. Still, since it's just this one computer with the problem, it shouldn't be the network. (An identical Win10 box doesn't have any issues.)
We won't sit down. We won't shut up. We won't go quietly away. YouTube and My Mu[sic], Films and Windows Programs, etc.
-
This one has (so far) stumped folks over at the Microsoft "Community". One of my Windows 10 boxes (x64, always updated, so whatever the latest build is) will not let me log in to any programs that reach out to login.live.com for authentication. But only the desktop programs or programs that don't have the authentication built in. The "Store" programs log in with no problem, as does the OS itself. And online things work fine, like signing in to MSDN or whatever. Running a desktop program, all I get is some variation of Can't reach that page or Something went wrong or Connection closed, depending on how the program is set up. So...I can't log in to Visual Studio or TFS, I can't log in to desktop Skype, I can't log in to OneDrive, etc etc etc. Except, and this is the killer, if I have Fiddler running and logging the traffic, all of the programs work just fine. A) What kind of sense does it make to only allow login if there's a spy on the line? B) Fiddler doesn't log anything "wrong" or even iffy. Just normal web requests and responses. (And a LOT of HTTP and HTML formatting errors like expecting X number bytes but receive 0, or unclosed quotations) None of the usual diagnostics like sfc or dism pick up anything, of course.
We won't sit down. We won't shut up. We won't go quietly away. YouTube and My Mu[sic], Films and Windows Programs, etc.
Have you tried disabling the firewall and rebooting with it disabled? One of the people at work ran into an issue on Win7 where that was the only way to fix it. Something was preventing a program from binding to a socket that it needed, even though nobody was using it or had it reserved via the registry keys. It was some sort of new issue -- everything has been working fine for them, then poof, suddenly it stopped working fine.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
-
Have you tried disabling the firewall and rebooting with it disabled? One of the people at work ran into an issue on Win7 where that was the only way to fix it. Something was preventing a program from binding to a socket that it needed, even though nobody was using it or had it reserved via the registry keys. It was some sort of new issue -- everything has been working fine for them, then poof, suddenly it stopped working fine.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
Now that is something I haven't looked at. Ditto on the everything working fine, then not. Thanks. We'll see what happens when I get home. :) edit: Nope. Didn't fix it. :(
We won't sit down. We won't shut up. We won't go quietly away. YouTube and My Mu[sic], Films and Windows Programs, etc.
-
This one has (so far) stumped folks over at the Microsoft "Community". One of my Windows 10 boxes (x64, always updated, so whatever the latest build is) will not let me log in to any programs that reach out to login.live.com for authentication. But only the desktop programs or programs that don't have the authentication built in. The "Store" programs log in with no problem, as does the OS itself. And online things work fine, like signing in to MSDN or whatever. Running a desktop program, all I get is some variation of Can't reach that page or Something went wrong or Connection closed, depending on how the program is set up. So...I can't log in to Visual Studio or TFS, I can't log in to desktop Skype, I can't log in to OneDrive, etc etc etc. Except, and this is the killer, if I have Fiddler running and logging the traffic, all of the programs work just fine. A) What kind of sense does it make to only allow login if there's a spy on the line? B) Fiddler doesn't log anything "wrong" or even iffy. Just normal web requests and responses. (And a LOT of HTTP and HTML formatting errors like expecting X number bytes but receive 0, or unclosed quotations) None of the usual diagnostics like sfc or dism pick up anything, of course.
We won't sit down. We won't shut up. We won't go quietly away. YouTube and My Mu[sic], Films and Windows Programs, etc.
-
One of the things I would check is potential DNS problem. Check the contents of your hosts file for example.
I'm retired. There's a nap for that... - Harvey
Even with an empty HOSTS file, it does it. And it uses the same DNS servers as the other machine that works. I've done the whole \flushdns thing, too.
We won't sit down. We won't shut up. We won't go quietly away. YouTube and My Mu[sic], Films and Windows Programs, etc.
-
This one has (so far) stumped folks over at the Microsoft "Community". One of my Windows 10 boxes (x64, always updated, so whatever the latest build is) will not let me log in to any programs that reach out to login.live.com for authentication. But only the desktop programs or programs that don't have the authentication built in. The "Store" programs log in with no problem, as does the OS itself. And online things work fine, like signing in to MSDN or whatever. Running a desktop program, all I get is some variation of Can't reach that page or Something went wrong or Connection closed, depending on how the program is set up. So...I can't log in to Visual Studio or TFS, I can't log in to desktop Skype, I can't log in to OneDrive, etc etc etc. Except, and this is the killer, if I have Fiddler running and logging the traffic, all of the programs work just fine. A) What kind of sense does it make to only allow login if there's a spy on the line? B) Fiddler doesn't log anything "wrong" or even iffy. Just normal web requests and responses. (And a LOT of HTTP and HTML formatting errors like expecting X number bytes but receive 0, or unclosed quotations) None of the usual diagnostics like sfc or dism pick up anything, of course.
We won't sit down. We won't shut up. We won't go quietly away. YouTube and My Mu[sic], Films and Windows Programs, etc.
Sounds like Malware.
-
This one has (so far) stumped folks over at the Microsoft "Community". One of my Windows 10 boxes (x64, always updated, so whatever the latest build is) will not let me log in to any programs that reach out to login.live.com for authentication. But only the desktop programs or programs that don't have the authentication built in. The "Store" programs log in with no problem, as does the OS itself. And online things work fine, like signing in to MSDN or whatever. Running a desktop program, all I get is some variation of Can't reach that page or Something went wrong or Connection closed, depending on how the program is set up. So...I can't log in to Visual Studio or TFS, I can't log in to desktop Skype, I can't log in to OneDrive, etc etc etc. Except, and this is the killer, if I have Fiddler running and logging the traffic, all of the programs work just fine. A) What kind of sense does it make to only allow login if there's a spy on the line? B) Fiddler doesn't log anything "wrong" or even iffy. Just normal web requests and responses. (And a LOT of HTTP and HTML formatting errors like expecting X number bytes but receive 0, or unclosed quotations) None of the usual diagnostics like sfc or dism pick up anything, of course.
We won't sit down. We won't shut up. We won't go quietly away. YouTube and My Mu[sic], Films and Windows Programs, etc.
Uninstall Fiddler and - this is important - WinPCap. I bet you've found an incompatibility.
-
This one has (so far) stumped folks over at the Microsoft "Community". One of my Windows 10 boxes (x64, always updated, so whatever the latest build is) will not let me log in to any programs that reach out to login.live.com for authentication. But only the desktop programs or programs that don't have the authentication built in. The "Store" programs log in with no problem, as does the OS itself. And online things work fine, like signing in to MSDN or whatever. Running a desktop program, all I get is some variation of Can't reach that page or Something went wrong or Connection closed, depending on how the program is set up. So...I can't log in to Visual Studio or TFS, I can't log in to desktop Skype, I can't log in to OneDrive, etc etc etc. Except, and this is the killer, if I have Fiddler running and logging the traffic, all of the programs work just fine. A) What kind of sense does it make to only allow login if there's a spy on the line? B) Fiddler doesn't log anything "wrong" or even iffy. Just normal web requests and responses. (And a LOT of HTTP and HTML formatting errors like expecting X number bytes but receive 0, or unclosed quotations) None of the usual diagnostics like sfc or dism pick up anything, of course.
We won't sit down. We won't shut up. We won't go quietly away. YouTube and My Mu[sic], Films and Windows Programs, etc.
-
You mention Skype...Don't they somehow hijack browser content? (to inject call tags) Could it be a problem with the Skype account? I've seen stranger things... Good luck! :)
"Go forth into the source" - Neal Morse
Don't know about that, but...there are here versions of Skype (that I have, anyway). Two "native" Win10 versions, Skype for Business, and Skype Video -- both of which I have no problem logging in to, and the "desktop" version of Skype, which uses the reach out and touch live.com login.
We won't sit down. We won't shut up. We won't go quietly away. YouTube and My Mu[sic], Films and Windows Programs, etc.
