Archive for June, 2019
January 1st, 2019 is the day when Steam officially dropped Windows XP and Vista support, but it was still working and including updates, but suddenly on January 31th Steam automatically updated and resulted in an error “Failed to load steamui.dll”
But it doesn’t stop us from using Steam as Valve said! The last working build of Steam on Windows XP/Vista is the January 4th build, But someone archived an earlier build of it from November 26th, that still works too. First of all download the .zip file including config.vdf. It has a steam.cfg file with settings to prevent further auto updates. When you downloaded it place everything in the C:\Program Files\Steam, when you finish copying all files place the config.vdf file into C:\Program Files\Steam\config. You will have to re-login to your Steam account.
For Steam users with the last working January 4th build!
To prevent automatic updates that update to broken builds download steam.cfg and place in C:\Program Files\Steam.
Now as you can see Steam works fine on XP without issues.
By default NLA isn’t enabled on XP, so if you try connecting to a remote server that has it enable you will get an error saying that you don’t have NLA support. The issue here is with Credential Security Service Provider (CredSSP) in Windows XP, it’s easy to fix, first make sure if you have Remote Desktop Connection 7 by verifying in the about box:
If you don’t you can Download and install the following update KB969084. Alright, first go to the Registry editor by typing regedit in the run box(How to open the run box the easiest way in by pressing the Windows Key + R)
We will change two registry keys, first navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa and modify the key named Security Packages.
Add ‘tspkg’ to the listing of security packages. Do not remove any packages.
Click OK and now navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders. Modify the key named SecurityProviders
Add ‘credssp.dll’ to the listing of Security Providers.
Click OK and close the editor. Now you will be able to connect to remote servers/computer that have NLA support enabled.
Windows XP lacked any modern cipher support in his heyday. With the POSReady 2009 trick you can get AES 256-Bit, TLS 1.2 support. I will show how to get them. First make sure you have the POSReady trick so you would be able to install them, next download the following updates in order:
AES 256-Bit support(KB3081320)
Update for WES09 and POSReady 2009(KB4019276)
Cumulative Update for Internet Explorer 8(KB4316682)
Update for WinHTTP to add TLS 1.2 support(KB4467770)
Install them all in order, then apply the registry file to enable TLS 1.2 and reboot. Now you can check at the Internet Options and you will see TLS 1.2 and TLS 1.1 in the list.
And Internet Explorer 8 will show that the cipher strength is now 256-Bit.
And howsmyssl.com reports that we do indeed have TLS 1.2 support and no insecure ciphers and we’re no longer vulnerable to the BEAST Vulnerability that affected TLS 1.0.
This doesn’t fully fix the issue with Chromium browsers that use XP’s schannel.dll because SNI or ECC support is not available on XP and you can get ERR_SSL_VERSION_OR_CIPHER_MISMATCH sometimes.