Leaderboard

Hey all, sorry for the delay. Thanks to everyone for all the contributions and keeping the topic active while I've been away! Now for the summary of changes since the last time I posted one of these... SUMMARY OF CHANGES TO THE LIST FOR JUNE 13, JULY 22, & AUGUST 19, 2019: Added Yandex Browser Portable 17.6.0.1633 to "Web Browsers" section. Added CryptoPrevent Antimalware, Cybergenic Shade Sandbox,Dr. Web Antivirus, Dr. Web KATANA, Hitman Pro, Jetico Personal Firewall, KeyScrambler, NoVirus Thanks Programs: Anti-Auto-Exec, SysHardener, & Registry Guard/guard service, RogueKiller Antimalware, SecureAPlus, Simplewall, SpyShelter AntiKeylogger, TinyWall, TrustPort, Unchecky, Xvirus, & Zemana to "Antivirus & Security software" section. Added TeamSpeak 3.2.5 to "Instant Messaging software" section. Updated Audacity to UNS status, as the software no longer officially supports Vista, but continues to work fine as of August, 2019. Added Daz Studio to "2D/3D Modeling software" section. Added TeamViewer 14.2.8352 as last version for Vista to "Remote Access" section. Re-added NVIDIA GPU & AMD GPU driver sections.

I used this to finally see the back of ctfmon.exe. It does work! Office Ctfmon Remover 2.3.zip

Hey guys! I saw a Video recently, where Windows 7 got transformed into Windows Vista. I tried it out on a Virtual Machine and I am very impressed by that. It Looks 100 % like Windows Vista, even the Branding is original Vista. As you also know Windows 7 supports Internet Explorer 10/11, Office 2013/2016, Microsoft Security Essentails, latest Chrome, latest Firefox, latest Skype, latest Spotify... It feels like Vista supports those Applications now too I will add a screenshot.

I've always use that to save memory/cpu and now i know i'm also preventing vulnerability

Earlier today, I was watching a Weather Network-produced segment on CBC News Network and noticed their fondness for Windows Server 2003 (R2?): It It is strange, considering that everything else on The Weather Network seems to run on 7 or 10. or at least the stuff like the touchscreen used by the on-camera personalities.

Thanks for letting me know. NVIDIA drivers (as well as AMD GPU drivers) used to be covered in LVSFWV/2008, but I decided to move them here since I felt they would be more appropriate here since, although they are software (obviously), they are drivers pertaining to hardware listed here. I have added them back to the software list since I see no harm in doing so: I must admit that my knowledge of hardware/driver compatibility is pretty shaky compared to my knowledge of program support for Windows Vista, so suggestions to improve this list are welcome.

I'm glad you're enjoying my transformation pack! I found it to be a practical solution for those that are using newer hardware incompatible with Windows Vista (such as Intel Haswell), or those that require newer software that don't work with Vista. The Windows 8.1 one isn't as accurate to the real Windows Vista due to changes in the shell/DWM compared to Windows 7 but it's still far better than anything achievable on Windows 10, where everything is such a broken mess and Microsoft insists on keeping any sort of customization impossible through forced updates that break your changes. As for me, personally though, I choose to stick with the original Windows Vista as I use Ivy Bridge hardware which works with Vista fine, and don't require anything that only runs on Windows 7 or later. I also find Windows Vista with Service Pack 2 to be faster and more stable than Windows 7 on the same hardware in most cases. Thank you for the kind words

That video was posted by MSFN member WinClient5270, OP of Last versions of software for Windows Vista and Windows Server 2008 and perhaps the greatest Vista guru of our time! This is no doubt a much more practical idea than your earlier wish to essentially transform Vista into Windows 7. Edit: Of course I wrote that before win32 developed Windows Vista Extended Kernel.

This thread is just for XP we have seen "out in the wild" or on the internet, not our own personal systems. We have a thread for that kind of thing here: Which I will be posting in soon once I get my notebooks sorted out.

I was tearing my hair out trying to get Windows 9x/ME clients (VMs and one real machine) to connect to my file shares served by Windows 7. I'd previously gotten it to work just fine served by Windows XP, so I set it up identically under Windows 7, to be greeted by it not working. Absolutely nothing I found Googling about this problem led me to a solution. I tried: Navigating directly to the shares by path Setting LmCompatibilityLevel and NoLmHash on the server side Setting LMCompatibility on the client side Installing dsclient9x.msi on the client Enabling NetBIOS on the server side Changing the network type from Public to Home on the server side Setting the Full Name of the account to be equal to its Name instead of being blank Actually logging in locally on the server side to an account meant only for file-sharing use Rebooting both the server and client after changing all of the above settings and more So if anyone coming across this thread still hasn't got this to work, here's the last thing I finally figured out: Account passwords are case-sensitive in Windows Vista and above, but are case-insensitive on Windows 9x/ME. Apparently the password is converted to lowercase by the 9x/ME client when sent over the network, because I had to change my mixed-case passwords to lowercase on the server side. With that done, it worked! As it turned out, I only needed to do two things differently under Windows 7 than I had under XP: Set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibilityLevel to a DWORD value of 1 on the server side (which is the same as going to Control Panel → Administrative Tools → Local Security Policy → Local Policies → Security Options, and setting "Network security: LAN Manager authentication level" to "Send LM & NTLM - use NTLMv2 session security if negotiated"). (Attempts to get the client to use NTLMv2 failed.) Note that a reboot is not needed after changing this setting. Use lowercase passwords on the server side. I reverted all the other changes I'd made, because none of them had any effect. Which is a shame, because it would've been nice to get the Windows 9x/ME clients to use NTLMv2, but maybe that only works for domains, and not workgroups? Oh, and I do have to navigate directly to the shares, but I don't mind that at all; I map them to drive letters anyway.

Well, first thing you should check the permissions of the file (and of the directory where it is): http://www.ntfs.com/ntfs-permissions.htm You may need to take ownership. You are however "mixing" two different "features". One is NTFS permissions (that have been on NTFS since the dawn of time) and the other is UAC, User Account Control, which is the "new" thing since Vista). BUT it seems strange that it can run once and then no more. Is it not some feature of that "Threatfire" thingy? jaclaz

This is one of the most useful Windows Vista posts anywhere! I realize that the topic is hardware rather than drivers, but NVIDIA drivers are not covered in Last versions of software for Windows Vista and Windows Server 2008 (another extremely useful post). This gives the impression that 365.19 was the one and only last driver version to officially support Vista, but that is generally only the correct driver for GeForce 400 Series and above. For GeForce 8 Series (I have an 8500 GT), and also 9, 100, 200 and 300 Series, the recommended driver version is 342.01 ( 32 bit 64 bit ). Despite its lower version number, 342.01 was released 7 months after 365.19.

... And I'm so tired reading that same ol' mantra there: As if they (third party software developers) would give one nickel whether someone's setup is secure or not; what is the underlying truth inside this PR talk is that Microsoft themselves make it gradually impossible for third party software developers to target older OSes with their (M$'s) updated Windows SDKs! ... and it always comes down to that! Win7 will soon reach End of Extended Support, hence it'll also be "outdated and unsupported by Microsoft", with no more "security patches"; what is their stance on Win7? Security reasons my... behind!

@Windows Vista Welcome to MSFN forums Yandex.Browser already covered in the first post of this thread: The link provided in that first post, as well as the link one gets when visiting https://browser.yandex.com/ with an XP/Vista User Agent string (*NT 5.x*/*NT 6.0*) is for a stub (on-line) installer! Official download link for off-line (Full/Standalone) installer, for version 17.4.1.1026: http://download.cdn.yandex.net/browser/update/17_4_1_1026_2644_w_s_m/yandex.exe 17.4.1.1026 is built on Chromium 57.0.2987.1026 source and is the last officially supported version on Vista; however, it is not the latest version that can be reliably run on Vista (but not XP); that one is version 17.6.0.1633, built on Chromium 58.0.3029.1633 source: Most sadly, it has proven impossible to locate a stub and/or full installer for that version, thankfully a third party portable (PAF) package has been archived in SourceForge (and is the one used here ): https://sourceforge.net/projects/thumbapps/files/Internet/Yandex%20Browser/YandexPortable_17.6.0.1633_on_Chrome_58.0.3029.1633.paf.exe/download Considering latest Yandex.Browser (19.6.1.153) is based on Chromium 74.0.3729.15 source, version 17.6.0.1633 should be considered deprecated/insecure by today's web standards; be that as it may, I find most websites render OK, with the exception, of course, of github.com (since they insist on always using the cutting edge version of Javascript code); if you spoof your UA to being FirefoxESR 60.x.x, even github works OK (but I suspect this hack will soon break, as FxESR60 will reach EoL towards the end of this month...). Cheers