I just updated to win 10. I tried using the new browser edge and it will not login here. No errors, it accepts my credentials and then reverts to the summary page showing I am not logged in. I checked the cookie settings and it is set to "don't block cookies"
I've had that problem on Windows 10 builds 10130 through to the 10240 TH1 release with MS Edge. There have been several EDGE update patches since. The problem seemed to disappear with one of those patches.
During the same period, Google also denied access to https://hangouts.google.com/ from all users connecting with MS Edge, be it through Windows 10 or any current Windows Phone 10 builds. https://www.reddit.com/r/google/comments/3iexwy/google_locked_out_microsoft_edge_browser_users/ Probably totally unrelated. But when I tested Hangouts on GooglePlus, using MS Edge, it rendered very poorly, and everything that was not supposed to scroll, scrolled. Fixed-location elements did not stay set in their fixed locations. Chrome and Firefox do not have this problem.
I couldnt tell you exactly what was done to fix Edge since 10240 RTM. But it may be related to a Windows 10 update patch since then.
I dont have the problem right now. And I am able to login just fine to UBBCentral using MS Edge on Windows 10. But I am currently on Windows 10 build 10565 for my primary desktop. And Windows 10 with all the current update patches for my secondary desktops -- 32bit and 64bit on each of those.
Though, the login problem still persists using MS Edge on clean install of Windows Phone 10 build 10536.
---
My results: Windows 10 build 10240 TH1 RTM -- has login issues for me. Windows 10 build 10240 TH1 RTM with all update patches installed -- works for me. Windows 10 build 10565 -- works for me. Windows Phone 10 build 10536 -- has login issues for me.
I now have three PC's using win 10/64 one of which is win10 pro. Same issues. The only common denominator I see is Trendmicro. I have not turned it off on all three machines. But I did for two of them. I usually keep current with updates, But I will check again.
Blue Man Group There is no such thing as stupid questions. Just stupid answers
If you are having problems with Edge, follow Microsoft's own advice and use Internet Explorer instead. There are some sites where Edge tells me the page works best if I open them in Internet Explorer.
If you're wondering why IE still ships with Windows10, instead of only including Edge, this is probably one reason why.
Microsoft knows that there are still bugs within Edge, and they are attempting to fix them as time goes along.
This link in Microsoft Edge, ms-appx-web://microsoft.microsoftedge/assets/errorpages/needie.html?reason=3
My test system: A freshly unboxed Surface Pro 4. Windows 10 build 10240. Edge browser. Nothing has been installed or setup on it. The first thing I did after creating my account and seeing the Windows 10 "This wont take long" dialog screen, was to visit both UBBCentral (759) and UBBDev (760):
• When "Keep me logged in." is checked/yes, it instantly logs me out. • If it is NOT CHECKED, I can do what is needed, and then log out on my own. The next browser session, I will have to login again -- as expected.
Try it on your install of Windows 10, using Edge browser. 1) Check the "Keep me logged in." box. 2) login. 3) browse around and see if it keeps you logged in. it probably will bump you out.
Now 1) UNCHECK the "Keep me logged in." box as you login. 2) login. 3) browse around. No problem And if you close your Edge browser window, you will need to login again -- as expected.
Central won't even read me as logged in, at no point does it say "Welcome, Gizmo"... Dev logs me in just fine, I see "Welcome, Gizmo" and can navigate around; do not get logged out. Attempted several times.
See I told you so. On my end like I said I disabled my security settings including trend micro,windows firewall, defender,etc. Cleared cookies here and on edge.No go. If ubbdev works then maybe something has been fixed that is not present here. I did not try UBBDEV.
Giz did you reboot to make it work? Or just close edge and open it again.
Blue Man Group There is no such thing as stupid questions. Just stupid answers
See I told you so. On my end like I said I disabled my security settings including trend micro,windows firewall, defender,etc. Cleared cookies here and on edge.No go. If ubbdev works then maybe something has been fixed that is not present here. I did not try UBBDEV.
This is an issue that I've only been able to duplicate in Microsoft Edge browsers -- on Windows 10 and Windows Phone 10.
I've outlined above, how to reproduce it in Microsoft Edge.
Put a CHECK MARK in the "Keep me logged in." box while logging in. This will instantly bump you off after the next page.
You can clear your cookies all day, and keep your security settings as open as the sun and the moon, this can be repeatably reproduced while using Microsoft's Edge browser on both version of Windows 10.
This Microsoft Edge issue can be duplicated in UBB.threads 7.5.8 and 7.5.9 and 7.6.0. It can probably be duplicated on every version of UBB.threads 7.x.
Now that I know exactly how to reproduce this "keep me logged in" issue... The login issue only happens with Microsoft Edge on Windows 10 and Windows Phone 10. I cannot reproduce it on IE11, Chrome, or Firefox using Windows 10. I cannot reproduce it on Android 5.x/6.x. I cannot reproduce it on Safari on iOS.
I'm kind of leaning towards Microsoft's recommendation when something doesn't work with Edge; use Internet Explorer. It definitely explains why they ship with both, I think Edge was just rushed out and that's why this is their "fix" for issues...
BTW, Ruben, great thinking of checking your security/virus utilities, in the past they have caused some grief for users; though in this particular instance it seems we can all produce some kind of bug with Edge, over various Win10 devices (including Windows Phone).
I was going to attempt this on my Xbox One, but it'd seem that even with the new Windows10 dashboard on it that IE is the only option.
I still have not tried the exclude remember me on login yet. As you suggested.
But as I said prior. If giz appears to not have issues with ubbdev now. Possibly some non stock code with v7.5.9 inadvertently fixed the issue at ubbdev?
Blue Man Group There is no such thing as stupid questions. Just stupid answers
Well I finally tried login without remember me selected. At this site ubbcentral. Seems to be working with limited testing. Oh and all default security settings are enabled and running.
Blue Man Group There is no such thing as stupid questions. Just stupid answers
Update. I tried with remember me checked again and it worked this time. There was a MS update like three days ago so possibly Microsoft corrected Something?
I don't recall if the updates included Edge.
Blue Man Group There is no such thing as stupid questions. Just stupid answers
With UBB Threads 7.6.0 I see the same thing on Microsoft Edge 40.15063.0.0, Microsoft EdgeHTML 15.15063 with Windows 10 and current on updates.
I notice that this is a 2015 topic. Has there been a solution for this yet? I'm still going through other similar topics in this message board and perhaps I will find the answer elsewhere.
Running Windows 10 [CURRENT VERSION] Microsoft Edge 41.16273.1000.0 Microsoft EdgeHTML 16.16273
No problems logging in with the current version of Edge. There was never an issue with Firefox, Chrome, Safari, Opera.
The issue seems to be reliant on which version of Microsoft Edge you are running (is your version outdated?). There is definitely an issue that seems to be related to something Microsoft is changing with their HTML tinkering within Internet Explorer and Edge browsers.
At the time of this post, 4% of users are IE/Edge users. There is a small percentage of that minority who are not running a current version of Windows. And then there is an even smaller percentage of that small group who are visiting UBB.threads forums. http://gs.statcounter.com/browser-market-share
It's a known issue, but not something I've been able to reliably duplicate recently on Microsoft's legacy Internet Explorer 11 browser, or the current version of Edge. So whatever the issue is, either Microsoft has fixed it, or they dont know that they have, because there was never an issue with Firefox, Chrome, Safari, Opera.