Is live.co.uk using POP on a mail host out of order or discontinued.

I didn't see any link which did the registry change automatically. I did it manually (and found it quite frightening to do so!).

I have no idea whether this is going to continue to work. It has only been a couple of hours so far. I'm waiting to see how it continues over the next day or so and/or whether anything else crops up, particularly as Clitheroe Kid says he/she has to change server address back and forth every day. I also wonder whether things will change when my home hub reallocates my 4-block (IMAP) IP address

I think you would be well advised to check the registry entries to see whether they ARE now the same as what Clitheroe Kid says in https://learn-attachment.microsoft.com/api/attachments/20b2fcb9-e29d-4e52-b9fb-1231c5f6968f?platform=QnA

Put your server settings and ports back to what they were in WLM. This MIGHT be the same as what Clitheroe Kid said -

imap-mail.outlook.com

smtp-mail.outlook.com

Outgoing smtp port 587

Incoming IMAP port 993

and check the SSL boxes for both

• but I obviously can't be sure these are correct as I'm not on MSN mail.

Assuming your registry IS now correct as per the filestore image referred to in paragraph 3 of this post and your WLM server settings are back to what they used to be when it last worked, then close WLM and reopen and see whether it now works.

Hopefully Clitheroe Kid will revert later with further advice.

Good luck

hi

just read your last post and am about to read back a couple more of your posts, glad to hear it's sorted for you.

on my thread i've done the registry change but i did mine automatically with the link supplied,i'm not as brave as you.

i've tried changing the server settings to the one on my msn server but it says it's not recognised so i'm back to square one at the moment. although i have done the automatic registry update i've gone into the registry manually and i've noticed there is only one entry in the section mentioned, and that is "SSL 2". obviously the automatic version doesn't do what it supposed to and i did follow the instructions. sooo i'm going to have to pluck up the courage and do it manually. sorry forgot to say yes i am in the u'k, retired and male.or is that male and retired,he he

I have done as you said and the registry now looks like you say in the filestore. It did previously only have SSL 2.0 as you said.

I have to say I find it quite frightening to be instructed to change registry keys for fear this leads to other problems which I don't understand and cannot fix.

I wasn't really sure how to get into the registry to edit it although I guessed correctly. For the benefit of another poster on here, what I did was tap Windows key, type regedit in search box and double click on the resultant regedit.exe file

I had a bit of trouble initially finding the correct area to edit and found this article helpful https://www.lifewire.com/hkey-local-machine-2625902 

I left the server settings in WLM 2012 as they were. When I finished the registry edit I closed WLM and reopened.

At the moment all seems to be working on WLM 2012 (This includes all my other email accounts, which had of course been performing normally anyway. I had had concerns that they might be affected by this registry edit, especially AOL which uses a different protocol). I sincerely hope this will continue. We'll see what tomorrow brings.

Hopefully we will hear from poster para999 whether this helps them too. That person only has one email account which is MSN and he/she uses IMAP.

Thank you for your ongoing help. It is much appreciated.

To do this registry edit manually, open the Windows Registry and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols

If the TLS 1.1 and TLS 1.2 subkeys are missing (i.e. if the "Protocols" key only has a single subkey named "SSL 2.0"), you need to create them manually. Here's how to do so:

1. Right-click on "Protocols". Select "New", then "Key". Name the new key "TLS 1.1" (without the inverted commas).
2. Right-click on that new key, then create another key underneath it named "Client" (without the inverted commas).
3. Right-click on the new "Client" key. Select "New", then "DWORD (32bit) Value". Name the new item "DisabledByDefault" (without the inverted commas). By default, its value is zero (which is what you need, so leave it as that).
4. Right-click on "Protocols". Select "New", then "Key". Name the new key "TLS 1.2" (without the inverted commas).
5. Right-click on that new key, then create another key underneath it named "Client" (without the inverted commas).
6. Right-click on the new "Client" key. Select "New", then "DWORD (32bit) Value". Name the new item "DisabledByDefault" (without the inverted commas). By default, its value is zero (which is what you need, so leave it as that).

Here is a link to an image which shows what the fixed registry should now look like:

https://learn-attachment.microsoft.com/api/attachments/20b2fcb9-e29d-4e52-b9fb-1231c5f6968f?platform=QnA

Sorry but I don't see any "Once you've made the manual registry change I advised, your Windows 7 machine will then cope with the new protocol that now substitutes for SSL." What registry change do you mean please ?

I'm back to finding I have to close WLM and restart about 8 times before it connects.

I'm beginning to have the impression this is only happening in UK and only to Microsoft accounts using WLM & only on Windows 7. I think it could be related to SSL - but as I have no technical knowledge at all I'm simply guessing. If I happen to be watching as WLM goes through checking my 6 email accounts I can see it run through the other 5 quickly then taking a time to try to connect to live.co.uk then I get the error.

It seems to be related to the dns - but again I have no idea what this is and how it is affecting matters. I had a few days of the system working normally after I cleared the dns cache (Elevated command prompt, ipconfig /flushdns) and registered the dns (Elevated command prompt, ipconfig/registerdns), then it started going wrong again

I'm using POP3.live.com on Port 995 and smtp.live.com on Port 25 They've been working fine for many years now until 9th October 2021.

I have tried changing the server settings to outlook but it made no difference at all

For the last few days I've been getting a WERtmp file created each night but I don't think this is related because it has started being created more recently than this connection issue.