Dave-H

There's also KB4486738, which I wasn't offered on Windows 10 presumably because I don't need it.

I know some people do use Stunnel on domestic PCs for things like logging onto current e-mail servers with legacy e-mail clients like Eudora which now can't log on normally.

Thanks again. I've tried the new URL (the original one you gave didn't have the "nf:8530" bit) but still no joy. It seems a bit different now, sometimes it fails almost immediately, sometimes it scans for ages and then fails, but always ends up with "An error has occurred: 0x8024400A".

Strange, the updates are listed on that link now, but when I Googled for the KB numbers a few hours ago, there was nothing found at all! They must have almost literally just put that information up, long after the updates were being offered by Windows Update!

Completely unexpectedly, another five Office 2010 updates on my Windows 10 netbook today! KB4484455 Office KB4486740 Word KB4486737 Office KB4486743 Excel KB4484534 Office

Completely unexpectedly, I've been offered five updates for Office 2010 today, on my Windows 10 netbook! They are - KB4484455 Office KB4486740 Word KB4486737 Office KB4486743 Excel KB4484534 Office They all seem to have downloaded and are pending install (I'm also doing the 20H2 Windows 10 update, which is going to take ages on this machine!) Searching for those updates, there seems to be no information about them, but they are in the Update Catalogue!

No, still no joy at all here I'm afraid!

Thanks! I tried with your proxy, and WUMT is just failing with error 0x8024400A all the time.

Thanks, yes Stunnel has been around a long time, and I know that many people use it. Personally I use ProxHTTPSProxy, which has been ported to XP my @heinoganda. I don't know what the pros and cons are of one program over the other, but HTTPSProxy seems to do everything I need at the moment. Welcome to the forum BTW!

Not working now here I'm afraid, on Windows Update or Microsoft Update, on the IE8 website, or on WUMT. Error 0x80072EFD.

I doubt that page is wrong, as it's the official download page from the K-Lite developers of course, but I'm sure that when 13.8.2 came out, they said that was the last XP version, because I labelled the installation file as such. It is of course possible that they then changed their mind and produced a further XP version! All I know is that 13.8.2 has worked for me for several years now with no problems. It might still be worth trying it if you can find a copy, I doubt that 13.8.5 is very different.

Some people, including me, had it apparently working again using the hack from MDL. Unfortunately it looks as if that workaround has now been blocked.

Unfortunately very intermittent faults which cannot be triggered at will are always extremely difficult to pin down. I agree that ntdll.dll is extremely unlikely to be the culprit, it's recorded as having been involved in the crash, but it probably wouldn't have actually caused it. I think the only thing you can do is to uninstall the K-Lite Codec Pack and see if the problem goes away, as it seemed to appear after you installed it. I realise this isn't ideal, as it could be months before you can prove whether the problem has actually gone away or not! Incidentally, you said you installed K-Lite version 13.8.5. My understanding is that the last XP compatible version is 13.8.2, which is an update to the last compatible full version which is 13.8.0. It is just possible that 13.8.5 does in fact contain something which isn't actually XP compatible, and is causing the problem. I have had 13.8.2 installed for several years, and it has caused no problems, so perhaps trying that version might be an idea.

Thanks again, I have expanded the thread title to be a bit clearer as to what it's actually about!

My Firefox 52 wasn't configured for TLS 1.3, now it is, thank you @Vistapocalypse! That hasn't made any difference to the problem with OnlyFans though. It looks as if it's connecting with TLS 1.2 anyway, with FF52 and FF82 - Firefox 52 Windows XP Firefox 82 Windows 10 I guess it probably is some sort of javascript issue, but I'm still surprised that it's affected all of my XP browsers! Perhaps it is time to start looking at using one of RoyTam's browsers, but I'm loathe to drop Firefox 52 as it synchronises with the copies of Firefox on all my other devices. I must say this is the first site which has stopped working on it which I haven't been able to find a workaround for, at least not yet!

Thanks guys. So, it's only me then! If it is a TLS 1.3 issue it must have only just happened, as the site worked fine until a couple of days ago. I thought Firefox 52.9 ESR did support TLS 1.3?

InternetOpenUrl looks like a call which goes to an internet address. https://docs.microsoft.com/en-us/windows/win32/api/wininet/nf-wininet-internetopenurla That might be worth investigating.

Just a couple of days ago I found that I could no longer access https://onlyfans.com/ using Firefox 52.9 ESR. OK I thought. perhaps it now just needs a different user agent string. No joy though, and I then found to my surprise that I cannot now access it with any of the browsers I have installed on Windows XP! I've tried with Firefox 52.9, Google Chrome 49.0.2623.112, Otter 1.0.81 Weekly #333, Opera 12.18, and even Safari 5.1.7. Every one of them just produces the splash screen with the pulsating logo, but never goes any further to the login page. On Firefox 82 and Edge on Windows 10, needless to say it still works fine! Is anyone else seeing this? You don't need to be registered with OnlyFans to test it, it should still load the login page. Cheers, Dave.

I'm intrigued by this entry - Failed calling InternetOpenUrl, GLE=12029 FAULTING_IP: +73 077444f6 ?? ??? What exactly is that? The last part looks like a mobile phone number. The +73 code is for Kazakhstan. Could that be something from a piece of malware?

Well here's what I managed to pull out of it, FWIW - Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [E:\Dump Folder\explorer crash.dmp] User Mini Dump File with Full Memory: Only application data is available Comment: '2nd_chance_AccessViolation_exception_in_EXPLORER.EXE_running_on_YOUR-7D8859AF69' Symbol search path is: srv*d:\programf\microsof\windowss.1\debuggin\symbols*http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*d:\win-nt\localsymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows XP Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible Product: WinNt, suite: SingleUserTS Machine Name: Debug session time: Wed Jul 8 10:02:31.000 2020 (UTC + 0:00) System Uptime: 11 days 13:04:15.434 Process Uptime: 4 days 5:46:39.000 ................................................................ ................................................................ ................................. Loading unloaded module list .............. This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (f4c.454): Access violation - code c0000005 (first/second chance not available) eax=0174fc9c ebx=00000000 ecx=00000000 edx=00000000 esi=077444f6 edi=04d069f0 eip=077444f6 esp=0174fc84 ebp=0174fccc iopl=0 nv up ei pl zr na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246 077444f6 ?? ??? 0:003> !analyze -v ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* Failed calling InternetOpenUrl, GLE=12029 FAULTING_IP: +73 077444f6 ?? ??? EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 077444f6 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 077444f6 Attempt to read from address 077444f6 DEFAULT_BUCKET_ID: BAD_INSTRUCTION_PTR PROCESS_NAME: explorer.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 077444f6 READ_ADDRESS: 077444f6 FOLLOWUP_IP: ntdll!RtlpWaitOrTimerCallout+73 7c927d39 834dfcff or dword ptr [ebp-4],0FFFFFFFFh FAILED_INSTRUCTION_ADDRESS: +1e22faf00fddf58 077444f6 ?? ??? MOD_LIST: <ANALYSIS/> NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 IP_ON_HEAP: 077444f6 IP_IN_FREE_BLOCK: 77444f6 FAULTING_THREAD: 00000454 PRIMARY_PROBLEM_CLASS: BAD_INSTRUCTION_PTR BUGCHECK_STR: APPLICATION_FAULT_BAD_INSTRUCTION_PTR_INVALID_POINTER_READ LAST_CONTROL_TRANSFER: from 7c927d39 to 077444f6 STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. 0174fc80 7c927d39 04d069f0 00000000 0014e800 0x77444f6 0174fccc 7c92a600 077444f6 04d069f0 00000000 ntdll!RtlpWaitOrTimerCallout+0x73 0174fcf8 7c92a54e 0014e800 00000004 00000020 ntdll!RtlpProcessWaitCompletion+0x112 0174ffb4 7c80b729 00000000 00000020 00f4fce4 ntdll!RtlpWaitThread+0x277 0174ffec 00000000 7c92a3f3 00000000 00000000 kernel32!BaseThreadStart+0x37 STACK_COMMAND: ~3s; .ecxr ; kb SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: ntdll!RtlpWaitOrTimerCallout+73 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ntdll IMAGE_NAME: ntdll.dll DEBUG_FLR_IMAGE_TIMESTAMP: 4d00f27d FAILURE_BUCKET_ID: BAD_INSTRUCTION_PTR_c0000005_ntdll.dll!RtlpWaitOrTimerCallout BUCKET_ID: APPLICATION_FAULT_BAD_INSTRUCTION_PTR_INVALID_POINTER_READ_BAD_IP_ntdll!RtlpWaitOrTimerCallout+73 WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/explorer_exe/6_0_2900_5512/48025c30/unknown/0_0_0_0/bbbbbbb4/c0000005/077444f6.htm?Retriage=1 Followup: MachineOwner --------- Hope this helps. You could try searching on some of the entries. Nothing stood out to me as identifying the culprit here, but I'm not expert at interpreting debug logs either!

Ah, sorry I had forgotten! Editing the registry wouldn't do anything different to what the ShellExView program does, so I guess it isn't a shell extension causing the problem this time (normally that would be the number one suspect).

Even easier, download and use this - http://www.nirsoft.net/utils/shexview.html This utility will display all of the Shell Extensions on the system and allow you to easily disable some or all of them. HTH.

There seems to be a lot of duplication in your lists. How does my list compare with what you were expecting?

Yes, working again for me now, I guess I tried it at the wrong moment!

OK, I just installed Office 2010 new onto my Windows 10 Netbook, 32 bit version, from an ISO file. I was then offered 11 updates, in this order of installation - KB2553092 Office KB2553065 Office File Validation KB2553347 Office KB2553406 Outlook Social Connector KB2825640 Office KB982726 Definition Update KB3115475 Definition Update KB2553310 Office KB2566445 Sharepoint Workspace KB3001652 Visual Studio 2010 Tools for Office KB2687455 Service Pack 2 After restarting and scanning again, I was offered another 63 updates! - KB2589375 Office KB2589298 Office KB2850016 Office KB2817369 InfoPath KB2880971 Office KB2589386 Office KB2883019 Office KB2553140 Office KB2553154 Office KB2956076 Office KB3054873 Office KB2589318 Office KB2553313 Office KB3055047 Office KB2553388 Office KB3054886 Office KB2791057 Office KB2881029 Office KB2956063 Office KB2881030 Office KB2999465 Visio Viewer KB3191908 Office KB3213626 Office KB3213631 Office KB2553308 Outlook Social Conector KB3114414 InfoPath KB4011610 Office KB3115248 Office KB4022206 Office KB4022208 Office KB4092436 Office KB3213636 Office KB3114565 Office KB4461579 Office KB2553332 Office KB4462187 Office KB4461626 Office KB2589339 Office KB3115197 Office KB3114559 Outlook KB2920812 PowerPoint KB3114879 Filter Pack 2.0 KB4032216 Publisher KB2597087 Office KB3203462 Office KB4484377 Office KB3114885 OneNote KB4462172 Office KB4484385 Access KB4484379 Office KB4484530 Office KB2760601 SharePoint Workspace KB4486700 Office KB4092435 PowerPoint KB4486663 Outlook KB3203468 Office KB4484235 PowerPoint KB4486703 Word KB2956084 Excel KB4461625 Word KB4486707 Excel KB2881025 Visio KB4462225 Visio I assume the second lot were actually the updates to Service Pack 2 after it was installed. I hope this helps. This was on Windows 10, but I assume the same updates would be applied if the procedure was done on XP or any other version of Windows. Cheers, Dave.