WinClient5270

Thanks for these additions. I shall add them now. Although these are noteworthy additions, the Web browsers section is getting quite long. As such, I don't want to overfill it with obscure Web browsers that are discontinued altogether (not just for Vista). I'm not trying to put down your suggestions as they do meet the criteria of "Web browsers", but like I said, the Web browsers list is getting pretty long and I don't want to overload it. Sorry about that. As for Conkeror, I could never figure out how to get it working... I obtained the browser using 'git' and installed xulrunner 1.9.2 (Conkeror 1.0 requires at least 1.9.1), and I couldn't ever get a browser window to even open. The installation process seems overly complicated and not very user friendly (mainly due to the lack of a simple installer). Not to mention, it hasn't been updated since April 2016 according to Wikipedia, so I'm afraid I'll have to decline this addition too... Thanks for all the other additions you've contributed so far though, burd. Please keep them coming.

It's already added in an ONG subsection called "VPN Clients."

SUMMARY OF CHANGES TO THE LIST FOR JUNE 27, 2017: Added a new ONG subsection (VPN clients) Added Tunngle to (ONG) VPN Clients subsection Added Google Chrome 50, Opera 37, and Firefox 53 as (UNS) browsers for Windows Vista. Referred users to @burd and @VistaLover's solution for getting the browsers to install and run in Vista. Added a new ONG subsection (Audio editing software) Added Audacity and Acoustica Mixcraft to (ONG) Audio editing software subsection Updated information about Pale Moon under Vista (64-bit version of the browser requires an option to be enabled for proper video playback; both versions of the browser now require users to install SP2, Platform Update, and Platform Update Supplement for Windows Vista). Removed HxD Hex Editor from the ONG section, as it has not been updated since 2009 and as such, is likely abandoned. Moved to Misc. System utilities section. Added VideoPad Video Editor to (ONG) Video/photo editing software subsection Separated screen capture software from screen recording software in (ONG) "Screen Recording & Capture software" subsection.

Waterfox 53.0.3 runs fine in Windows Vista, however later versions do not (I am the OP of this issue): https://github.com/MrAlex94/Waterfox/issues/166 Again, Waterfox 53.0.3 is the last version for Windows Vista. However, if you check out the link above, you'll find where the head developer told me that he has plans for a separate release for older platforms, presumably Vista/XP x64.

Once again, your solution worked. "Enable MSE for WebM video" was all I needed to check, and now it works great. Thanks a ton, VistaLover.

Sure: https://forum.palemoon.org/viewtopic.php?f=3&t=16016#p116388

I will have to report this issue on the PM forum. The issue seems to be exclusive to Vista, as I can play YouTube videos just fine with Pale Moon under Windows 8. In other news, Moonchild said he would use updated DLLs in the next release of Pale Moon, so the issue should be fixed for Vista in the next update.

I tried your solution, and it worked perfectly. Thanks so much for the help. I shall now report this to the Pale Moon dev. I personally don't use the browser. However, I do respect the fact that it still continues to receive major version updates on Windows Vista, as browsers of that nature are getting more and more difficult to come by.

Speaking of web browsers, Pale Moon 64-bit crashes for me on Windows Vista and Windows Server 2008, and I want to know if anyone else can reproduce this problem or if it's just me. Upon starting the browser, I'm greeted with a "Stopped working" error, with the crash being caused by MSVCR120.dll. It affects all versions of Pale Moon from 27.0.0 64-bit onward, with 26.5.0 64-bit working just fine, as well as all 32 bit versions of Pale Moon (latest version included). Can one of the Vista (64-bit) users here install the latest version of the 64-bit variant of Pale Moon and see if you can reproduce the problem I'm having? I posted about it on the Pale Moon forum, and received a reply from the main developer that I needed to send a crash dump to see what the problem is. However, I'd like to make sure the issue just isn't on my end before doing that. Said post (and more info about the error) can be viewed here: https://forum.palemoon.org/viewtopic.php?f=3&t=16016

On another note, in an effort to give the list more exposure and keep it from getting buried into obscurity, I will now post comments containing a log of any major updates/changes to the list each time they are made. I hope this is okay with the admins. Prior to now, I was simply summarizing the changes in the "Reason for edit" section. However, the section has a character limit that doesn't always allow for me to mention all of the changes made, unless I leave out some information, which is not desirable for me.

Thanks for the addition, Werewolf. NOTE: Waterfox 53.0.3 is the final release for Windows Vista. Later versions require the TryAquireSRWLockExclusive function located in KERNEL32.DLL, which is a Windows 7+ function. However, after a discussion about it with the head developer himself, he said he would consider doing a separate release for older systems, which I presume to be Vista/XP x64. You can view our discussion here: https://github.com/MrAlex94/Waterfox/issues/166

Also, for some reason, the patches aren't showing up in Windows Update on Vista for me... So, to get June 2017's patches for Windows Vista, I'd suggest checking out Microsoft Knowledge Base article 4025687 for a chart containing links to the patches: https://support.microsoft.com/en-us/help/4025687/microsoft-security-advisory-4025685-guidance-for-older-platforms

According to various sources, it looks like Microsoft has decided to include Windows XP and Vista in June's patch Tuesday updates, in an attempt to "address the elevated risk of cyberattacks by government organizations.": https://betanews.com/2017/06/13/windows-xp-patch-tuesday/

Thanks for the additions, all. Sorry it took so long to add them, I've been quite busy with other things lately so I just got around to adding them.

You're welcome, and thank you for taking the time to create and maintain both update repositories, @greenhillmaniac. It's very appreciated

Added SuperAntiSpyware... The other two are already on the list, and since Pale Moon continues to support Vista, I won't specify a version number, since it's constantly changing. Once the final version of Pale Moon is released for Vista (whenever that may be), I will add it to the list.

Yes. I have successfully installed the following (post-Vista EOL) Server 2008 updates in Windows Vista (SP2, x64): KB4020535 KB4019206 KB4019204 KB4019149 KB4018927 KB4018556 KB4018885 KB4018821 KB4018466 KB4018271 Screenshot: http://prntscr.com/f602cl From my testing, the following updates did NOT work on Windows Vista: KB4018196 (Displays "Not applicable to your system" message) Windows Malicious Software Removal Tool for May 2017 (Not compatible with your OS error message) So it looks like Vista will be good to go until 2020, with the exception of a few updates here and there. I also must note that I didn't try any updates related to .NET Framework, as I couldn't figure out how to obtain them. Alright @greenhillmaniac, it's time to make that Server 2008-Vista repository

Thanks for the information and addition. Perhaps MSRT will support Vista for a while longer, as Windows 8.0 is still supported. Just have to wait and see.

Thank you both for the additions! I will wait for you to test 3dsmax 2013 and Unity 5 before adding them to the list, just to be certain whether or not they do work on Vista. As for Windows Defender, I must mention that the Vista/7 version of the software hasn't been very reputable for providing quality protection, so I'd recommend using a free, third party alternative, such as Avast! Free Edition or pretty much any of the (free) listings in the ONG section. However, Windows Defender is still a valid option, so it has been added to the list. Hopefully, I can find out more information about MSE, and whether or not the solution pointed out (in the post you linked) that XP users are currently using, will also work in Vista. As I figure things out, I'll update the list accordingly. Thanks again!

I didn't say to try all updates, but to try at least more than one or even two, to give us a better idea of whether at least most Server 2008 security updates will work in Vista. Sorry for the confusion. Trying only one (security) update, in my opinion, isn't enough to go all out and say that all Server 2008 security updates will work on Vista... Maybe you weren't meaning to imply that, and maybe I just misunderstood. But the way you put it in a couple of your prior posts: ...made it look to me like you were implying that since you tried only one security update, that all of them would work in Vista. Even if the filenames are similar or the same, there's a chance that the updates still won't work in Vista, because Microsoft does indeed have the ability to make updates Server-only or Client-only if they see fit, as I'm sure you know. Take the platform update for example, the filenames and even the file sizes are the same, but there are separate versions for Vista and 2008, and neither of them will work on the opposing OS. Microsoft has different version numbers inside the CAB files contained in the .MSU files to identify each update as either Client or Server compatible. If the version number inside the update mismatches the "host" OS, the update will NOT install. This is the main reason why Powershell 3.0 doesn't work. I'm guessing for the Server 2008 security updates that do work under Vista, there is no specific number specified, for whatever reason, other than just NT 6.0.6002, which is why the updates work in Vista. I actually agree with you about Powershell, as I never use the program myself. I was just tinkering around with the update to see if the version number contained within it could be changed to make it install under Vista. But as greenhillmaniac points out, it can't be done, so I have stopped bothering with it. I'm not trying to be rude or argue about it, but like I said before, I just want to make sure we have strong evidence to make an educated guess, and judging by the information that has been presented to me, I can confidently "guess" that most Server 2008 security updates will work in Vista But we have to wait until May 9th to know for sure, so I'm not going to worry about it until then. Thank you for the information. That's very interesting to know about .NET Framework 4.6.1. I wonder if future (major) versions of .NET Framework, whether it be 4.7 or 5.0, will work. That's stretching it a bit, though.

Are you referring to what @sanszajnrege said? I'm not trying to be rude, but I wouldn't take someone saying that one update works (and without even elaborating on what specific update they tried) as confirmation that Server 2008 security-only updates work in Vista. Otherwise, the only update I tried (at first) was Powershell 3.0 for Server 2008, but from my understanding (according to a knowledgeable source that greenhill consulted), Powershell 3.0 is completely incompatible with Windows Vista, for some reason. However, I did some more searching on the Microsoft Update Catalog site, and tried several different Server 2008 security updates on Vista, and they all installed just fine, oddly enough. Here's a link to the updates I tried (excluding the Server 2008 R2 updates, the Sharepoint services update, and some outdated security updates for IE8. Also, I only tried those on page 1 of the search results): https://www.catalog.update.microsoft.com/Search.aspx?q=security update server 2008 x64 This is a good sign that May 2017 (and beyond) Server 2008 security-only updates will work in Vista. However, it should be noted that most if not all of the updates I tried have Vista-only versions too, so Microsoft could decide to change something regarding the compilation of future Server 2008 security-only updates (when Vista is no longer supported) that prevents them from installing under Vista. Retracting my last statement about April 11th, it will be the next patch Tuesday that excludes Windows Vista that will give us answers, so make that... May 9th, IIRC? After this finding, my outlook on the situation has changed. I believe that Vista users will be set until 2020, as far as security-only updates go, as long as Microsoft doesn't get any ideas (and at this point, that seems unlikely, given that Server 2008 is no longer in mainstream support). I also doubt that we'll have to worry about incompatible updates, since Microsoft didn't include Server 2008 support in newer .NET framework updates (4.6.1 requires 2008 R2 or later). The only updates I'd imagine wouldn't work would be anything to do with Powershell 3.0. But does that component even get updated at all? I hope I didn't sound rude (that was certainly not my intention), I just don't want people to get their hopes up and then just get hit with disappointment come Vista's EOL. However, like I said, I believe we'll be fine, but I like to take everything into consideration before I jump to conclusions, because Microsoft can be pretty unpredictable sometimes. Best regards.

AFAIK, nobody has done so (yet). I have a feeling it isn't going to work either, at least not without modification to the updates themselves (view this to find out more): However, Tuesday (April 11) will tell...

At the time I made the package and listing, I was very tired so I made some mistakes... Sorry about that. You can safely copy the wrappers to the System32 location, and nothing should be affected, as I've done so several times myself. However, as you pointed out, it would be simpler to copy all the files at once to a single location, so thanks for the information. Unfortunately, according to Adobe's terms of use here, you're not allowed to redistribute or host the software, so I've removed the package from the list. Instead, I'll create a video tutorial on my YouTube channel on how to manually download and install Reader DC under Windows Vista, and will link that video on the list when it's complete. This will cause the process to become much more lengthy compared to using my installation package, but I certainly would rather avoid any legal issues and play it safe. Instead of hosting their software on my MEGA account, I'll just link their FTP server in the video's description, and I'll demonstrate how to manually edit the MSI files, as well as manually hex editing the DLLs to use the wrappers instead of Vista's system DLLs. The only thing I'll host is Smeezekitty's wrappers, which should be fine since they're not part of Reader DC in any way, and I'll be certain to give him credit.

Sure, all additions are welcome as long as the software works with Windows Vista/2008 (and isn't malware obviously, lol).

Thank you for the information, VistaLover! I finally got around to updating the Last versions of software for Windows Vista list to reflect this information, and I added an installation package for Reader DC for Vista containing all of the needed files.