POSReady 2009 updates ported to Windows XP SP3 ENU

[heinoganda]

58 minutes ago, someguy25 said:

The thing is that is still here even though im with the latest updates

If the files "qedit.dll" and "quartz.dll" in the folder "%windir%\system32" do not have the file version 6.5.2600.7218, KB4014652 should be installed!

[NojusK]

1 hour ago, heinoganda said:

If the files "qedit.dll" and "quartz.dll" in the folder "%windir%\system32" do not have the file version 6.5.2600.7218, KB4014652 should be installed!

 

Those files dont say version 6.5.2600.7218

[dencorso]

So get and install KB4014652, already!

[NojusK]

35 minutes ago, dencorso said:

So get and install KB4014652, already!

Not risking.I dont want to screw my install :P

[Dclem]

1 hour ago, someguy25 said:

Not risking.I dont want to screw my install

You definitely need to invest in an image backup solution so you can revert your system when making a change that doesn't pan out.   I would certainly recommend investing in a copy of Acronis Backup & Recovery software which will also provide a "try and decide" option to test unknown software or changes to your system.  

[NojusK]

ok so i tested kb4014652 on my windows mce 2005 unpatched vm and the network tray icon is still working! :) That means im good to go 

[Mathwiz]

On 11/28/2018 at 6:09 PM, heinoganda said:

Update to enable TLS 1.1 and TLS 1.2 as secure protocols in WinHTTP.
Info KB4467770
Download KB4467770

OK; so, I installed the update and added the registry key & DWORD value specified on the info page. But IE8 already used TLS 1.1 & 1.2 before the update. So what software uses WinHttp.dll? OE6? Windows Live Mail perhaps?

[heinoganda]

49 minutes ago, Mathwiz said:

So what software uses WinHttp.dll? OE6? Windows Live Mail perhaps?

I found the following information about WinHTTP:

https://docs.microsoft.com/en-us/windows/desktop/winhttp/about-winhttp

https://securelink.be/blog/windows-proxy-settings-explained/

https://www.telerik.com/blogs/using-fiddler-with-winhttp

 

[Mathwiz]

From the second link:

Quote

Typical examples for applications and services using WinHTTP are:

1. Adding/Removing features and roles in Windows 8.
2. Windows Update
3. Certificate validation of code
4. Signed binaries / .NET applications that validate the certificate during application launch.

Obviously 1 doesn't apply, but the others could be used by Windows XP.

[Thomas S.]

As I understand, WinHTTP is used by Applications directly (without the functionality of IE and his API).

8 hours ago, Mathwiz said:

Obviously 1 doesn't apply, but the others could be used by Windows XP.

Often the kb articles are not fully transfered from the basicly descibed OS versions to PosReady, so it can be that 1 also works in XP.

[dencorso]

On 11/28/2018 at 6:09 PM, heinoganda said:

Update to enable TLS 1.1 and TLS 1.2 as secure protocols in WinHTTP.
Info KB4467770
Download KB4467770

Please do notice the direct link given points to the Finnish, not the English, version of the said update... 

[heinoganda]

48 minutes ago, dencorso said:

Please do notice the direct link given points to the Finnish, not the English, version of the said update..

Direct Download Link changed for Update in English (ENU)! Unfortunately I had overlooked.

[Thomas S.]

12 hours ago, Mathwiz said:

I installed the update and added the registry key & DWORD value specified on the info page.

To add the needed registry modification, I give here the code for a reg file for activating WinHTTP TLS1.1 AND 1.2 (as described in kb4467770 article):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00000A00

A download to use file is attached.

Short technical info:

Override defaults for WINHTTP_OPTION_SECURE_PROTOCOLS to specify TLS 1.1 and TLS 1.2

Add DWORD value for TLS 1.1 (0x00000200) and / or DWORD value for TLS 1.2 (0x00000800)

The resulting registry DWORD value for both would be 0x00000A00.

WinHttp DefaultSecureProtocols.reg

Edited November 30, 2018 by Thomas S.

[NojusK]

53 minutes ago, Thomas S. said:

To add the needed registry modification, I give here the code for a reg file for activating WinHTTP TLS1.1 AND 1.2 (as described in kb4467770 article):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00000A00

A download to use file is attached.

Short technical info:

Override defaults for WINHTTP_OPTION_SECURE_PROTOCOLS to specify TLS 1.1 and TLS 1.2

Add DWORD value for TLS 1.1 (0x00000200) and / or DWORD value for TLS 1.2 (0x00000800)

The resulting registry DWORD value for both would be 0x00000A00.

WinHttp DefaultSecureProtocols.reg

I have to say Microsoft is really focusing on TLS 1.1 and TLS 1.2 stuff on PosReady

[Mcinwwl]

I updated today certs and windows and Office. All went smoothly via Windows update. I have only TLS1.2 enabled in internet options.

Fun fact - recently I changed my monitor for XP machine, from damaged 17" ACER to used 19" Dell bought for a bargain price. Dell also can serve as a US hub. What surprised me is that Windows update actually found drivers for that and provided as optional hardware update. Drivers are dated back to 2006, which means they ain't throwing old stuff away from their servers yet :)