Leaderboard

The update "WINDOWS2000-OTSKB000001-V7-X86-INTL.exe" has been released to the general public. The help file "OTSKB.chm" and the code comparison file "code.htm" have been updated accordingly. --- There will probably be a slight update for Windows XP users, soon (WINDOWSXP-OTSKB000001-V2-X86-INTL.exe). --- things to do: Windows XP + Windows Embedded for Point of Service update: add the version "5.1.2601.0001-V2" of the file "win32k.sys" to "code.htm" (edit: done) add the update "Windows XP/OTSKB000001-V2" to the help file write the update test it release it Windows Server 2003 update: add the version "5.2.3790.6946" of the file "win32k.sys" to "code.htm" add the version "5.2.3791.0001-V1" of the file "win32k.sys" to "code.htm" add the update "Windows Server 2003/OTSKB000001-V1" to the help file write the update test it release it Windows Embedded POSReady 2009 update: add the version "5.1.2600.7684" of the file "win32k.sys" to "code.htm" add the version "5.1.2602.0001-V1" of the file "win32k.sys" to "code.htm" add the update "Windows Embedded POSReady 2009/OTSKB000001-V1" to the help file write the update test it release it

The update "WINDOWSXP-OTSKB000001-V1-X86-INTL.exe" has been released to the general public. The help file "OTSKB.chm" and the code comparison file "code.htm" have been updated accordingly. --- There will probably be a medium update for Windows 2000 users, soon (WINDOWS2000-OTSKB000001-V7-X86-INTL.exe) and a slight update for Windows XP users (WINDOWSXP-OTSKB000001-V2-X86-INTL.exe). --- things to do: Windows 2000 update: Write the version "5.00.2196.0001-V7" of the file "win32k.sys". Then update "code.htm". add the update "Windows 2000/OTSKB000001-V7" to the help file write the update test it release it Windows XP update: Write the version "5.1.2601.0001-V2" of the file "win32k.sys". Then update "code.htm". add the update "Windows XP/OTSKB000001-V2" to the help file write the update test it release it Windows Server 2003 update: Analysis of the version "5.2.3790.6946" of the file "win32k.sys". Then update "code.htm". Write the version "5.2.3791.0001-V1" of the file "win32k.sys". Then update "code.htm". add the update "Windows Server 2003/OTSKB000001-V1" to the help file write the update test it release it Windows Embedded POSReady 2009 update: Analysis of the version "5.1.2600.7684" of the file "win32k.sys". Then update "code.htm". Write the version "5.1.2602.0001-V1" of the file "win32k.sys". Then update "code.htm". add the update "Windows Embedded POSReady 2009/OTSKB000001-V1" to the help file write the update test it release it

Hi @NotHereToPlayGames, VirusTotal has changed its interface. A lot of old browsers didn't work anymore with VT's new interface. I could fix it in @roytam1's browsers and in @feodor2 Mypal 68 by setting variable dom.moduleScripts.enabled to false in about:config. Have a look in this post: The browsers Mypal 68, New Moon 28 and Serpent 52 are working properly with VT's new interface in Windows XP. Unfortunately the Chrome browsers 360Chrome v11 and 360Chrome v13 are not working with the new interface of virustotal.com. Loading of the new interface works, a file can be uploaded, the hash is generated, but the results (Checking hash) are not shown. I tried to change some script related flags, but without any success. I already know that there is a link for old browsers: https://www.virustotal.com/old-browsers/, but for external tools or browser add-ons only the new interface is important and will work. Any ideas how this could be fixed in your 360Chrome browsers? Cheers, AstroSkipper

And following tools are working again with the new interface of virustotal.com in Windows XP: VirusTotal Uploader 2.2 and Winja VirusTotal Uploader 7.1. Here are the download links: https://www.virustotal.com/static/bin/vtuploader2.2.exe , https://www.majorgeeks.com/files/details/winja.html Kind regards, AstroSkipper

I can confirm that following browsers are working with the new interface of virustotal.com if variable dom.moduleScripts.enabled is set to false in about:config: Mypal 68, New Moon 28 and Serpent 52. Firefox 52.9.0esr is natively working with the new interface of virustotal.com, presumably because of lacking this variable dom.moduleScripts.enabled. Unfortunately the Chrome browsers 360Chrome v11 and 360Chrome v13 are not working with the new interface of virustotal.com. I tried to change some script related flags, but without any success. Cheers, AstroSkipper

And here is a link from December of 2015 where you can compare the Free and the Plus version: https://web.archive.org/web/20151229143305/https://www.sphinx-soft.com/Vista/order.html Have a nice day, AstroSkipper

The portable version is not compatible with Windows XP. Only the versions ending in their name on XP are written for Windows XP. This is the free version for Windows XP: https://www.sphinx-soft.com/download/W10FC7.5/Windows10FirewallControlFree-XP-Setup.exe And this is the Plus (paid) version for Windows XP: https://www.sphinx-soft.com/download/W10FC7.5/Windows10FirewallControlPlus-XP-Setup.exe The Plus version is the one I use for years. It's definitely worth the money. I wouldn't use a portable version in case of a firewall. There are components which have to be installed in Windows sytem folder, otherwise the services couldn't start at Windows startup. The goal of a firewall must be in managing and controlling all connections, especially at system startup. A firewall should be deeply integrated into the system. Therefore a portable version isn't a good idea. Cheers, AstroSkipper

Windows 10 Firewall Control XP 7.5 is a free version. I said I use the paid Plus version. It has a lot of features other firewall are lacking of.

Or the access to this site from your location is restricted. Then you should use a VPN connection.

Hi @mina7601, I've checked the link and it's working for me. Check your internet connection or try another browser! Or go to homepage, download section and then Windows 10 Firewall Control XP 7.5 at the bottom of this site! Cheers, AstroSkipper

Hi @e-t-c, I tried al lot of firewalls in the past. The best I found is Windows 10 Firewall Control XP 7.5 from sphinx-soft.com. I use this special version for Windows XP for years and it's simply great. There is a Free and a paid Plus version. My preferred version is the Plus one. Try it! I love it! Here is a link of archived versions: https://www.sphinx-soft.com/download/W10FC7.5/ Cheers, AstroSkipper

Not really! There are a lot of programs using IE8 engine to connect to internet. For example some email clients, the update function of some programs and so on. Access to WU or MU is only one area of application. If the system itself has to access an url which needs TLS 1.2 protocol, you have to use one of these proxies system-widely. I thought you read my article "ProxHTTPSProxy and HTTPSProxy in Windows XP for future use". I already described it there in detail. Therefore your statement is not correct. Cheers, AstroSkipper PS: BTW I wouldn't have started a thread about these proxies and logically I wouldn't have maintained them if there hadn't been any need to preserve and prepare them for future use. And to access MU or WU two other methods exist too where there is no "need" of these proxies. These methods are described in this post:

@ExtremeGrief I could do that but I didn't. If you want to merge it's up to you. I did it my way as Frankie Boy would say (or better sing). Don't say other people what they should, could or have to do. If you want to do it "better" do it by your own!

@maile3241 Oh man, dllcache is a subfolder of system32 folder.

@maile3241 Of course you can. Copy new code, mark this region with your mouse and paste new code, But do not change other bits. Check after patching if only these ten digits have changed. It's the most simple thing.

@maile3241https://imgur.com/AqLdRes Of course you have. In hexeditor all lines are arranged hexadecimal on left side. Find line 0000EC80 and then position (column) 4. Open your eyes! In your screenshot I can see the matching code.

@maile3241 At offset EC84, replace 83F89D7508 by 3BC0EB3290. But first check if code 83F89D7508 matches exactly in your file.

@maile3241 Version 5.1.2600.5512 is what I have and is an original service pack 3 file. And patching is no problem using hexeditor.

@maile3241 Have you already checked if at offset EC84 of your file this code 83F89D7508 matches? You always say the same but you give less information about what you have tried. Use an hexeditor like WinHex and look inside! If code matches then you can patch outside of system32 without any problems.

@Dave-H Such an Intermediate Certificate Authorities called "Microsoft Update Secure Server CA 1" doesn't exist in my system. I agree to @Mathwiz your problem is most likely related to ProxHTTPSProxy. I had applied its cert. installer program "ProxHTTPS Cert Install.exe" too. If the mentioned version doesn't work for you try HTTPSProxy from @Thomas S.. That's what I use most of the time and it works flawlessly. No certificate problems and very comfortable with a launcher in your Taskbar Notification Area (SysTray) and a lot of options.

@maile3241 rshx32.dll is only related to security tab. To disable WFC/SFC you have to patch sfc_os.dll too. I patched this file only to disable SFC permanently. I think this is your source: https://www.neowin.net/forum/topic/600928-xp-home-file-system-hacks/

@maile3241 Then this instruction should work. It is just for your version. My version is higher.