Leaderboard

alright it works. new Saturday binaries will work with 1.3 compat mode.

I prefer my browsing habits sent to China than to Google anyway. And I never keep logged in to it... just for Gmail, if at all, when needed.

Hi, First time poster here. I have the same problem that Jaguarek62 reported but do not use VMware. Vista Home premium with Avast Free 18.8.2356 Build 18.8.4084.0 Def. ver.190521-4. All been running Ok with monthly Server 2008 updates up till April 2019 update Kb4493471(also tried Kb4493458) now get BSOD stop error 0x0000008E WIN32K.sys (Kernelmode exception not handled) Tried disabling Avast in MSconfig and services.MSC but still same. Eventually managed to boot into safemode and uninstalled update and all working OK again. Decided to leave this update out and wait till May Kb4499149 but sadly still the same BSOD stop error. Next, removed Avast with Avastclear and installed Kb4499149 successfully. IE9 updates have not been a problem. Tried a fresh install of Avast and back to same problem. Seems I will not get anywhere with Avast solving problem as they want you to update to W7 B4 they will entertain a support request. I will just have to use Windows Defender instead for a while and maybe fingers crossed an emergency fix might come out from Avast? Just sent them a quick note about problem as a bug/report a problem as well. What other free AV products are out there for Vista/Server 2008 that won't suffer this problem?

Welcome to MSFN Stevo. I certainly appreciate your post, but I'm not really surprised. Avast seems to think their issues with Windows updates in April were limited to business solutions, and that the issues have now been resolved by "micro-updates." You might want to post about this problem in their End of support for Windows XP/Vista thread, but in all likelihood you will have to choose between continuing to use the legacy version of Avast or installing the last 10 months of Windows 6.0 updates. As for "other free AV products...that won't suffer this problem": If WinClient5270 is still using Security Essentials 4.4.304.0, then I would presume that it is unaffected. We have a thread about using that MSE version on Vista here. Sandboxie is not a traditional AV product, but Ruan has reported version 5.28 as working with April 2019 updates (see my May 8 post). If you intend to continue running Vista beyond Server 2008's EoL in January, then definition updates for Avast might be available much longer than definition updates for Security Essentials. New Edit: That was a pretty good speech; but as Stevo already knows, he does not have to choose between using Avast and updating to build 6003 because Avast has fixed the issue with a micro-update! It occurs to me that "Windows 6.0.6002 March 2019" is a very strategic point to create an image or clone using Macrium or Acronis. This method of backing up your system becomes all the more valuable in light of Jody Thornton's April 27 post above, i.e. updating Vista after reinstallation may go from "a major pain" to "virtually impossible" before long.

I don't think it adds any features; just bug / security fixes

We know! Read from here.

seems possible, will have a look later.

The default setting is ambiguous "default". I think that there should be no problems if there is no Google account entry in the browser itself. Or it is hidden. But I still turned off this option.

Yes, it turns out i don't need to install windows 1.01 to play reversi after all! When we thought MS was giving up on XP they surprised us again!

It's WORKING!!!....been playing windows XP Hearts all morning.....

I long for a time people stop saving as docx and save as .doc. there are zero gains from the docx format over doc (regarding MS word) I do use the compatibility pack on XP to open docx. All this itteration bullcrap will one day be looked back upon by future generations and viewed as pretty dumb and unecessary. The only reason for software updates is mortages and hungry mouths. period. FYI I just use FileFormatConverters.exe from MS website. never had a problem using MSo 2003 thus far

@Blados, no, both architectures are supported. But the developers, when they throw support for Vista, complained that the code was very different and difficult to maintain. Due to hardware acceleration. I tried to run the MSI file - it sends to setup.exe . Setup.exe requires Windows 7. I modified the MSI file and installed it. With .NET 4.7.2 is installed. ... is not Win32 application. Alas.

@Blados, I also tried to look for what is possible to install - it turned out 22 updates. Here is a list. But probably, it's also did not complete. It now remains to find applications that require these fresh versions of the .NET Framework

Not sure if I can post this here, but... Here's the list of updates I've installed for .NET Framework 4.7.2: Not sure if that's all of them. It's based on my list of previously installed .NET 4.6.1, also have tried installing the older ones I had before, but all of them gave me the "not applicable to your system" error so I don't think there are any more updates to install, aside from the possible May 2019 ones, which I have yet to install. Also, it seems you can't install Language Packs since doing it the normal way yields yet another "not applicable to your os" error, and unpacking the installer with 7-zip and running the other installer (forgot its name) tells you to use setup.exe instead... Note: These are security and quality rollups, I don't know the update numbers for security only updates.

Well it turns out that Microsoft .NET Framework 4.7.2 can also be installed on Windows Vista using the same installation method for 4.6.2 Final, and it can also be patched using the .NET 4.6 security updates for Server 2008! In addition, ShareX still works with this version installed, and no dependency errors are present: Now, I could not find an application that specifically required this version of .NET Framework, but it appears that ShareX is able to use it without any issues, in contrast to .NET Framework 4.8 Preview... As such, I have also added this version of .NET Framework to the list Also, this is irrelevant to .NET Framework, but Twitch Desktop App recently dropped support for Windows XP and Vista, so it has been removed from the list

... As it finally turned out, it is yet again another case of intentional/artificial block of Vista by M$ ; the blocking code lies somewhere inside the compiled .EXE setup, but it's obviously absent in the unpacked .MSI installer.I do wonder if it's still possible to install 4.6.2 Final by running the Setup.exe file (86.1KB) that exists inside the (unpacked) directory; an inspection with Resource Hacker reveals it does indeed support Vista in its manifest: <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1"> <application> <!-- Windows 10 --> <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}" /> <!-- Windows 8.1 --> <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}" /> <!-- Windows 8 --> <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}" /> <!-- Windows 7 --> <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}" /> <!-- Windows Vista --> <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}" /> </application> </compatibility> I guess if that doesn't work, on a 32-bit platform one should run netfx_Full_x86.msi (in the unpacked directory); as mentioned by Osman, in the root of the unpacked setup one can see prerequisite windows updates for Win8 (KB3151804), Win8.1 (KB3151864) and Win10 (KB3151900), but, surprisingly, not for Win7 (and, of course, none for WinVista, which the package doesn't officially support) - in any case, it should be stressed that the (somewhat unorthodox) 4.6.2 install shouldn't be attempted on a Vista system which isn't fully updated (SP1+SP2+all subsequent updates at least until EoS on April 2017), just for good measure... All in all, a very positive outcome from a joint effort, started by @Osman Kovan and joyfully concluded by @WinClient5270! Cheers PS: I couldn't help noticing how a 59.1 MiB file (NDP462-KB3151800-x86-x64-AllOS-ENU.exe) blows up to more than 1.62 GiB (!) when expanded!

GOOD NEWS EVERYONE! Thanks to @Osman Kovan for figuring out how to install Microsoft .NET Framework 4.8 on Windows Vista, I was able to use that same method to install Microsoft .NET Framework 4.6.2 Final on Windows Vista. I just extracted the setup .exe file with 7zip and ran the .MSI installation file contained within it, netfx_Full_x64.msi: After installing, I then tested ShareX Portable to see if it gave the same missing dependency errors that it does when running it with .NET Framework 4.8 Preview installed, and to my delight, it works just fine in Vista with 4.6.2 Final! Remembering what @VistaLover asked me to try with 4.6.2 Preview installed, I then decided to try the latest .NET Framework 4.6.x security rollup for Windows Server 2008 to see if it would patch .NET Framework 4.6.2 Final on Vista, and, lo and behold: It works! This means that .NET Framework 4.6.2 Final CAN be installed and patched on Windows Vista using @Osman Kovan's installation method, and then by downloading the .NET 4.6 patches for Server 2008 manually from the Microsoft Update Catalog. As such, Microsoft .NET Framework 4.6.2 Preview has been replaced with the final version on the list: Special thanks to @VistaLover, @Osman Kovan, and @artomberus for helping make this possible!