VistaLover

Source: Description of Software Update Services and Windows Server Update Services changes in content for 2017 Tuesday, July 18, 2017 Non-security Updates 1. July, 2017 Preview of Quality Rollup for .NET Framework 2.0 SP2, 4.5.2 and 4.6[.1] on Windows Server 2008 SP2 (KB4032116); MS Catalog link: KB4032116 This is a .NET Framework bundle update, that breaks down to the following individual ones: 1a: May 2017 (Yes, May) Preview of Quality Rollup for .NET Framework 2.0 SP2 on Windows Server 2008 SP2 (KB4014592); I haven't been able to find concrete info on why this was re-released; FWIW, if you have been following this thread, you should've already installed this as part of the May 2017 .NET FW updates, as outlined here ; no need to re-install if already inside your list of installed .NET FW updates. 1b: July, 2017 Preview of Quality Rollup for the .NET Framework 4.5.2 on Windows Server 2008 SP2 (KB4024845); if (by choice) you're still on .NET Framework 4.5.2, then this one's for you... 1c: July, 2017 Preview of Quality Rollup for the .NET Framework 4.6 (and 4.6.1) for Windows Server 2008 SP2 (KB4024848); if on .NET Framework 4.6[.1], that's the one for you (i.e omit the previous one). But be careful: It has another one as a prerequisite: D3D Compiler Update for Windows Server 2008 SP2 (KB4019478) You must first install (manually) KB4019478 (I wasn't asked for a reboot afterwards) and then proceed to install KB4024848; the latter took some time, but did install successfully (reboot required): PS: While file NDP46-KB4024848-x86.exe obviously pertains to .NET Framework 4.6, when actually running it one sees references to .NET Framework 4.7 (also, file version is stated as 4.7.2102.5); this has me believe it actually adds 4.7 features to the 4.6.1 installed version of .NET Framework (whereas, as you know, 4.7 itself won't install on Vista SP2). 2. Update for Windows Server 2008 SP2 (KB4019276); MS Catalog link: KB4019276 This is a most important update, as it implements TLS 1.1/1.2 support systemwide (to the whole OS); you can read more at MS's KB article. TLS 1.2 is the recommended standard for server-client authentication via the HTTPS protocol, recent Firefox and several other browsers already offer support for the next iteration, TLS 1.3. One can't help but wonder why this wasn't offered earlier for the Vista OS (NT6.0), while it was still under Extended Support ; as said, it's a significant security and performance enhancement to the NT6.0 platform, making it overall more secure and robust, in tune with current tightened internet security implementations. I will post a separate topic on how to enable TLS 1.1/1.2 support on Internet Explorer 9, Vista SP2 version - I don't have WS 2008 SP2 to check, but on my Vista SP2 Home Premium (x86) OS, just installing KB4019276 (and rebooting) wasn't enough . KB4019276 requires a reboot afterwards, other than that it installed fine:

You are welcome ... Just a small oversight on my part that I'd like to address: Inside the "Palemoon" directory resides another .dll related to MS VS2013, file vcomp120.dll, still on the old version 12.0.21005.1. I advised deleting only files msvcp120.dll and msvcr120.dll (the latter is the one that appeared in your appcrash log) and according to your post that alone worked; however, just to be on the safe side, I would also advise deleting (outdated) vcomp120.dll, too; can you check for me, please? As for the video playback issue of PM 27.3.0 x64, I followed your conversation with the developer here onwards, plus read the related GitHub issue; on my 32bit platform, I fail to duplicate your issues even when I deselect "Enable MSE for WebM video"; deselecting that GUI option sets in about:config media.mediasource.webm.enabled;false The following prefs are in their default state: media.mediasource.enabled;true media.mediasource.format-reader.mp4;true media.mediasource.mp4.enabled;true With the above prefs, in a fully updated Windows Vista SP2 32bit running PM 27.3.0 (32bit), Youtube are streaming via their HTML5 player DASH, avc1 (h264) encoded, MP4 streams: As posted previously, if I set media.mediasource.webm.enabled;true then YT prefer to serve their VP9 encoded WebM streams. The PM developer said that he has no access currently to a Vista OS; the fact that their "new" MSE mp4 format reader works in Vista 32bit but not on Vista 64bit is probably something that needs to be communicated to him, for eventual fixes - AFAICT, WMF/MSE on Vista shouldn't behave differently depending on OS architecture . Some words on the browser (PM) itself: I have always been a Mozilla Firefox person myself (since v2.0.0.x); a browser is a kind of app I always like to test, so I have tested PM several times in the past - as long as Fx was/is supported on Vista, I had no real reason to convert to PM. I will continue using Fx 52.x.x ESR as my main browser on Vista until, itself, is being EOL'd, but PM is an option I seriously consider after that time... The cruel fact is that PM has simply now diverged too far from being a Fx/Gecko fork; many of the Fx addons I currently rely upon will simply not work on it; some have PM equivalents, others not; the whole PM ecosystem is now (with the Goanna 3.2 platform) significantly different to Fx and AMO; AMO treats PM 27.3.0 as Fx 27.9, despite PM having in its UA Firefox/45.9. Most 27+ Firefox addons are old and unsupported, newer versions of them use newer SDKs incompatible with PM. So a definite loss of some functionality with the eventual move to PM... . And news for a long-term Vista support isn't good either; the next platform (UXP) that will follow Goanna won't be targeting Vista...

... Whatever your video playback issues are with PaleMoon 27.3.0 x64 on Vista SP2 x64, they must be specific to that architecture . In the release notes to 27.3.0, it is stated that On my environment, i.e. Vista Home Premium SP2 32bit with all post EOL MS updates, no Flash NPAPI installed, portable PaleMoon 27.3.0 (32bit), YouTube does play fine via their HTML5 player, serving DASH, VP9 encoded, streams: Plus, when visiting youtubehtml5 I pass all six of those tests (white ticks inside blue squares). If not already, go to Options -> Content -> Video and select all 3 "Enable" options: I also have no problems playing back local MP3/M4A/MP4 files...

Sadly, I'm on 32bit Vista HP SP2, so can't test this myself - but I did download "Palemoon-Portable-27.3.0.win64.exe" and extracted it with 7-zip. File msvcr120.dll that ships with it is on version 12.0.21005.1 (dig. sig. 20131005), which is already outdated, since MS has issued several updates to it; their "Microsoft Visual C++ 2013 Redistributable" package was on version 12.0.30501.0 (dig. sig. 20140501), while update KB3138367 installs version 12.0.40649.5 (dig. sig. 20160216). But I think your issue with Palemoon x64 on Vista/WS2008 falls into what is described in Update for Visual C++ 2013 and Visual C++ Redistributable Package : Vista/WS2008 do not support AVX state saving, hence (outdated) msvcr120.dll crashes... Install KB3179560 (dig. sig. 20160707) from that page (I would suggest both x86 & x64 .exe files, English - US locale), delete msvcp120.dll & msvcr120.dll from the "Palemoon" directory and then reboot - palemoon.exe 64bit should be able to load the updated versions of these dlls from System32 - if not, do as advised by burd Hope I've helped

Greetings from tropical Greece (36 Celsius as I write ). I really think that post should have been placed in the Updates Thread , the one you started! Well, no-one claimed exclusivity here, it's not like someone's discovered a new element, given past experience from POSReady updates ported to XP (and Server 2012 ported to Win8). Perhaps the "Sardoc" person did, in fact, got his/her idea from us (in which case a mention would've been proper), or perhaps not; either way, it's not like "water been spilt on sugar" (Greek proverb!). What I'm worried the most is the event Microsoft block the installation of WS2008 updates on Vista, as they did with their "Malicious Software Removal Tool" - which will run on WS2008 but not on Vista, despite both being Windows-6.0 .

... Haven't you read the part of my post about media playback (and some gfx) capabilities of Fx 53 being seriously impaired on Vista? Fx 53 on Vista will never work the same as the 52esr branch, because under the hood some functionalities that still work in 52esr don't on 53; just compare the youtubehtml5 score of 53.0.3 (on Vista) to 52.2.0esr (on Vista): E.g., this icecast mp3 stream will play natively in a tab on 52esr, 53 won't be able to play it (and may offer to download instead, or open via a dedicated player) ...

While the proper .exe setup won't install on Vista itself, you can download and install on Vista the portable (PAF) setup, available from portableapps repo: https://downloads.sourceforge.net/portableapps/FirefoxPortable_53.0.3_English.paf.exe So no need for a Win7+ box; I have used myself pe_patch.exe http://www.the-sz.com/products/pe_patch/ to change subsys version to 6.0; place pe_patch.exe inside /App/firefox/ and simply drag & drop firefox.exe onto it - its GUI opens; just manually change "Sub System Version", then click "Save" & "Exit" in the bottom. What pe_patch.exe patching does is actually reverting bugzilla bug 1322646 ; since the Firefox 53.0 code doesn't include functions not present in the Vista (in fact XP, too) kernell, the patched firefox executable will perfectly launch on Vista SP2 (should also do on XP SP3 !). While Fx 53.0.3 should be fine on Vista for casual browsing, your "it works flawlessly" statement is, sadly, not entirely true . The Firefox devs (namely a Japanese guy who harbours some unusual aversion to Vista) were very quick/keen to excise vital Vista support code; I tried to fight their decisions in the relevant bugzilla bugs back in the day, but, as you may assume, to no avail... In fact, at the initial bugs, Mozilla were to only drop support for XP, but, in another Google Chrome aping, Vista was put in the same boat... But I'm going OT here... Bug 1324183 has removed WMF support from Firefox on Vista, so Fx 53.0.x can't use system codecs (MP3, AAC, h264) to play back standalone .mp3/.mp4/.m4a media files or play back mp3/mp4 streams via HTML5. Adobe CDM has been removed, so has support for Quicktime/VLC NPAPI plugins, so media playback is a serious drawback here... Another bug (1329547) completes what 1324183 started... You can check yourself by visiting HTML5 test or youtube html5 . In another bug, WebGL(2) renderers, at least on my machine, can't use D3D11 and fall back to D3D9x; in Fx 52.2.0, about:support, graphics section: WebGL Renderer Google Inc. -- ANGLE (Software Adapter Direct3D11 vs_4_1 ps_4_1) WebGL2 Renderer Google Inc. -- ANGLE (Software Adapter Direct3D11 vs_4_1 ps_4_1) In Fx 53.0.3: WebGL Renderer Google Inc. -- ANGLE (Mobile Intel(R) 965 Express Chipset Family Direct3D9Ex vs_3_0 ps_3_0) WebGL2 Renderer WebGL creation failed: * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Exhausted GL driver caps. There is additional XP/Vista specific code that was removed in the transition from 52.0 -> 53.0, I can't go on in detail here, so after my curiosity tests running 53.0.x, I saw no real gain in running that on Vista and went back to the supported 52ESR branch (currently on 52.2.0). And to save someone the trouble of trying to launch Fx 54.0 on Vista just by lowering subsys version, it doesn't work : ... As was reported by me 14 months ago ; again, the portable installation was used. Opera 37.0.2178.54 is based on Chrome 50.0.2661.102 code, so that is why it runs fine on Vista: As Opera 36 for XP/Vista has turned out to be a sort of a "joke" (hasn't been updated since August 2016), why not use (on Vista) Opera 37 ? They should be probably equally vulnerable, security-wise ...

Hi @Vistaboy and welcome to the MSFN forums Obviously, this is not the right thread to discuss this, but... On Windows 7 and earlier, WD != MSE; I think when you install MSE, WD is disabled by default - WD is a sort of antimalware app, while MSE can be regarded as a full blown security suite . While many 3rd party Security Suites can happily coexist with standalone WD (I know Kaspersky can, but even then it is advised you disable the real-time component of WD), MSE must be the only Internet Security Suite running on your system, to avoid conflicts... And in the case of both WD & MSE, some higher CPU/RAM consumption is expected/justified during the time WU checks for (and installs, according to WU settings) definitions updates (usually once daily) and during the time a scheduled scan is performed. If you did experience quite random significant CPU usage due to MSE, then you should investigate possible conflicts particular to your setup... Just my 2cent here...

Thursday, May 25, 2017 High Priority/Non-Security Update May 25, 2017: Update for Windows Server 2008 SP2 (KB4023136) Finally released, this is 2017 - Morocco Ramadan DST changes (MUC link), it was announced for WS2008SP2 on May 18th (see here). IMHO, it's safe to disregard if not inside Morocco...

While I see you're referring to major security (and other) updates for the whole OS, I have Windows Defender enabled and I still see that "icon" pop up in the tray area to prompt me to install def updates for WD; and if you happen to have installed other MS products for which MS support is still ongoing, then, I assume, that WU icon in the tray area is still relevant...

Hello As posted, if you search on Microsoft Update Catalog for KB4019291 - May 2017, Preview of the Quality Rollups for the .NET Framework 2.0 Service Pack 2, 4.5.2, and 4.6[.1] for Windows Server 2008 Service Pack 2 - and click on download with Mozilla Firefox, in the pop-up that opens you get three individual links for KB4014592: May 16, 2017: Quality Rollup for the .NET Framework 2.0 SP2 for Windows Server 2008 SP2 KB4014613: May 16, 2017: Quality Rollup for the .NET Framework 4.5.2 for Windows Server 2008 SP2 KB4014606: May 16, 2017: Quality Rollup for the .NET Framework 4.6[.1] for Windows Server 2008 SP2 You'll have to download & install windows6.0-kb4014592-x86(or -x64).msu regardless, which is the 2.0SP2 update. Then, if you're on 4.5.2 you'll have to download & install NDP45-KB4014613-x86(or -x64).exe, else if you're on 4.6/4.6.1 download & install NDP46-KB4014606-x86(or -x64).exe I can't answer those questions . I went for the latest installable version, which on Vista SP2 is 4.6.1. If you're on 4.5.2, as I see it you'll be prompted to update via WU to 4.6, the last officially supported version. As that is an in-place replacement of 4.5.2, all the 4.5.2 related updates will be uninstalled when you upgrade to 4.6, and then WU should offer you all the relevant 4.6 security and quality updates released for Vista until EOL, April 11th 2017. From then on, you should manually install all 4.6 released updates for WS2008SP2. If you manually update from 4.5.2 to 4.6.1, WU will not offer you any further updates - see also my previous post here ; all further updates will have to be installed manually. The "source" link I referenced does have such info; e.g. on KB4019291 it states: "Supersedes: KB3216520 on Windows Server 2008". But yes, I agree it's a pain in the rear end to keep track of...

Source: Description of Software Update Services and Windows Server Update Services changes in content for 2017 Tuesday, May 16, 2017 Optional/Non-Security Updates May 2017, Preview of the Quality Rollups for the .NET Framework 2.0 Service Pack 2, 4.5.2, and 4.6[.1] for Windows Server 2008 Service Pack 2 (KB4019291) This is a bundle, which contains: 1. May 16, 2017: Quality Rollup for the .NET Framework 2.0 SP2 for Windows Server 2008 SP2 (KB4014592) 2. May 16, 2017: Quality Rollup for the .NET Framework 4.5.2 for Windows Server 2008 SP2 (KB4014613) 3. May 16, 2017: Quality Rollup for the .NET Framework 4.6[.1] for Windows Server 2008 SP2 (KB4014606) (2 or 3 should be chosen and installed according to the version of .NFW you're on...) Thursday, May 18, 2017 High Priority/Non-Security Update May 18, 2017: Update for Windows Server 2008 SP2 (KB4023136) This is actually 2017 - Morocco Ramadan DST changes and the individual update for WS 2008 SP2 will be published in the coming days:

It was never my intention to show any hint of disrespect, so my sincere apologies if it came through that way . I only suggested (without giving it much thought, apparently) what appeared to me as a convenience for fellow Vista users (i.e. ease of access, much like what is being currently done in that other Vista thread, "Last versions of software for Windows Vista and Windows Server 2008"). Again, sorry for any misunderstanding caused!

No, it did not error out when I tried to install it - if you inspect my "Installed Updates" (second) screenshot you'll see it there; I just thought, after reading what it patches, that it should be redundant for Vista ... You probably know a lot more on this than I, so it's up to you what you do ; thanks again!

You are welcome @greenhillmaniac and thanks for creating the MEGA repo; is the link to it going to be stickied in the Windows Vista forum? Or, possibly, could a mod let you create a "new" #1 post in this current thread, which could, hopefully, be updated every month from now on? And a clarification about "Update for .NFW 4.6[.1] on Windows Server 2008 (KB4020503)", published May 2nd: The relevant KB article details that it patches an error specific to "Windows PowerShell v3.0+"; since PS v3.0 isn't available on Vista SP2, I would argue that patch (that I did include in my list in my previous post and you, too, included in your repo) isn't strictly needed on Vista SP2 ...

Today (May 15th 2017) I hunted down and installed all non-security and security Windows Updates destined for Windows Server 2008 SP2 32bit (that were published after April 11th 2017) onto my Windows Vista SP2 32bit laptop; together with security updates for .NET Framework 2.0 SP2, this is how it looks in the "Installed Updates" section of my WU: Further updates for installed .NET Framework 4.6.1 (not officially supported on either Vista SP2 nor WS 2008 SP2, but still installable on both these OSes, see here) were also hunted down and installed: So far, everything seems to be working as expected... @2008WindowsVista wrote: > I didn't try any updates related to .NET Framework, as I couldn't figure out how to obtain them. Well, my starting point for locating all Windows Updates is the following MS page: Description of Software Update Services and Windows Server Update Services changes in content for 2017 This gets updated in chronological order, whenever new updates are published... You can isolate WS 2008 SP2 updates and via the KB links you can hopefully arrive to individual WUC links (and pray that the catalog site isn't crawling like a worm...). Hence, for updates issued after April 11th 2017 (Vista's EOL), I have written down the following list of updates: April 18th (nonsecurity) Update for Windows Server 2008 (KB4015193) May 2nd Update for .NFW 2.0 SP2 on Windows Server 2008 (KB4020511) Update for .NFW 4.6[.1] on Windows Server 2008 (KB4020503) May 9th Cumulative Security Update for IE9 (KB4018271) Security Update for Windows Server 2008 (KB4018466) Security Update for Windows Server 2008 (KB4018556) Security Update for Windows Server 2008 (KB4018821) Security Update for Windows Server 2008 (KB4018885) Security Update for Windows Server 2008 (KB4018927) Security Update for Windows Server 2008 (KB4019149) Security Update for Windows Server 2008 (KB4019204) Security Update for Windows Server 2008 (KB4019206) (nonsecurity) Update for Windows Server 2008 (KB4020535) "Security Update for Windows Server 2008 (KB4018196)" does not install on (client) Vista SP2, because it strictly affects a Server function (Windows DNS Server Denial of Service Vulnerability in Microsoft Windows Server 2008: May 9, 2017); as for "Malicious Software Removal Tool - May 2017 (KB890830)", it has already been discussed in this thread... .NET Framework: May, 2017 Security Only Update for .NFW 2.0 SP2, 4.6[.1] on WS 2008 SP2 (KB4019109) => [Security Only Update for the .NFW 2.0 SP2 for WS 2008 SP2 (KB4014575) & Security Only Update for the .NFW 4.6[.1] for WS 2008 SP2 (KB4014591)] May, 2017 Security and Quality Rollup for .NFW 2.0 SP2, 4.6[.1] on WS 2008 SP2 (KB4019115) => [Security and Quality Rollup for the .NFW 2.0 SP2 for WS 2008 SP2 (KB4014502) & Security and Quality Rollup for the .NFW 4.6[.1] for WS2008 SP2 (KB4014511)] NB: If you install the "Security and Quality Rollup" bundle, you need not also install the standalone "Security Only Update"; if you have not yet moved to 4.6[.1] and are still on 4.5.2, you should locate the corresponding updates for that version of .NFW ! For future reference, I will conclude by posting some helpful (to me at least) links (with the hope the mods do not mind...) :

Thanks to both @segaklon and @dencorso for their replies Yep, it's nice to know MSE can still be used on Vista!

@dencorso wrote: > Seems to me nobody did the test Apologies, I am indeed on Vista Home Premium SP2 x86, but am currently running Kaspersky Internet Security, which is incompatible with MSE . Windows Defender is only used for on-demand quick scans... It would've been a hassle for me to test MSE: 1. Uninstall KIS, then reboot. 2. Use Kaspersky Removal Tool (all settings are lost), then reboot. 3. Install MSE, then reboot. 4. Do various tests with MSE. 5. After I was finished testing, I would uninstall MSE (possibly aided by MSE Removal Tool ) then reboot. 6. Then go through the trouble of re-installing and reconfiguring KIS (another reboot required), followed by a lengthy definitions update with possibly another reboot required after that... So, a definite NO-GO it was for me... Just some additional info: On both following official MS links for MSE: https://support.microsoft.com/en-us/help/14210/security-essentials-download https://www.microsoft.com/en-us/download/details.aspx?id=5201 Vista SP1+ (both 32 & 64bit) "appears" to be supported . Both those links fetch the current client version of MSE, which is 4.10.209.0 - is this the one reported broken by @Werewolf at this previous post? I presume they disabled it via a definition update, am I correct? Version 4.4.304.0 reported as working by @segaklon has a digital signature from October 2013; is this version good/efficient enough? And how was 1) its definitions update performed, 2) itself prevented from upgrading to 4.10.209.0 ? Apologies for being a pest, I just want to establish what my options are when my KIS licence expires... Regards

Many thanks for the info . In my eyes, this looks like a promising replacement to MSRT that I could download and manually run every month... To be on the safe side, I did create a Restore Point before letting it perform a quick scan; that took ca. 12min (I recollect MSRT taking somewhat less, perhaps 7-8 min), 0 infected files were found, so all OK !

I was dismayed to discover they were that quick to remove Vista Support from MSRT - I distinctly remember that on my (now decommissioned) XP SP3 desktop, WU continued to find updated versions of MSRT many months after XP SP3 was EOL'd... But given how swift they were to disable MSE on Vista after April 11th, I can't say I was surprised ... So, Windows-KB890830-V5.48.exe wouldn't run on Vista; previous version Windows-KB890830-V5.47.exe (for April 2017) is the last that would... They have issued a statement, to be found on https://support.microsoft.com/en-us/help/890830/remove-specific-prevalent-malware-with-windows-malicious-software-removal-tool I suspect there now is a built-in OS version check that hinders v5.48 from running the scan on Vista ; I'll leave the task to the real experts (to query if it's even possible to lift that restriction), but as Vista and Server 2008 are both NT 6.0, I'm curious as to how they implemented it... I've never been much dependent on MSRT, so I'll not lament its deprecation on Vista... Does anyone have any prior experience with Microsoft Safety Scanner ? Latest version 1.0.3001.0 doesn't complain when started on Vista SP2, but I haven't let it perform the scan yet

... Judging from this recent post, it would appear it's GAME OVER for MSE 4.10.209.0 on Vista SP2 currently; I couldn't tell myself, since I am running Kaspersky IS on this Vista SP2 x86 laptop. FWIW, Windows Defender still functions properly at the time of writing: Updated definitions can be downloaded manually from Malware Protection Center, in the "Windows Defender in Windows 7 and Windows Vista" links; let's wait and see if/when that "Windows Vista" reference gets removed and whether the remaining "Windows Defender in Windows 7" links would yield files installable on Vista ...

You are correct - the last version of .NET Framework 4.x.x that would install on Vista (Home Premium SP2 x86 here) is 4.6.1; but the last version officially supported by MS on Vista is 4.6, so WU won't offer you to install 4.6.1 if you have 4.6 already installed; as I see it, if you have 4.5.2 installed, WU will find updates for 4.5.2 and offer an in-place upgrade to 4.6; if the upgrade is chosen and applied, only updates for 4.6 are found. The full standalone installer for 4.6.1 is file "NDP461-KB3102436-x86-x64-AllOS-ENU.exe" and can be fetched via MS Download Center; this will install fine on your fully patched Vista OS, replacing your previous .NET FW 4.x.x version and all of its updates. Sadly, as pointed out by @Mine Turtle, being an unsupported version means that WU won't be able to find any updates for it . One can always track down in MS Security Bulletins (now discontinued) or Microsoft Catalog individual updates for 4.6/4.6.1 destined for Windows 7 SP1, fetch them to disk and apply them manually... I am lucky with regards to the tracking part, because sister's laptop runs W7 SP1 x64 with .NET FW 4.6.1 (purposely not upgraded yet to 4.6.2) and I am monitoring what .NET FW updates this gets, write down their KB numbers and then download their x86 flavours and apply them manually in my Vista laptop. For anyone curious/needing those, here's a capture (via snipping tool) of the .NET Framework 4.6.1 section of my "Installed Updates" list (4.6.1 was manually installed last May): As for 4.6.2, its .EXE installer may have been "artificially" made incompatible with Vista or it may indeed be the case that 4.6.2 as a whole requires API functions not present in the Vista OS; really inapt to tell... And since v4.6/4.6.1 is still supported on W7, it may well be that future security/performance updates for 4.6/4.6.1 on W7 could be manually applied on Vista, too (unless MS plays it nasty and blocks them via an OS check switch or whatever ).

> Thank you for the information, VistaLover! ... You are most welcome > I finally got around to updating the Last versions of software for Windows Vista list to reflect this information ... from your PDF viewers section: >> Adobe Reader DC version 2015.10.2006.0 (FREE, CS, UNS) ... a small typo there, actually it's 2015.010.20060 > and I added an installation package for Reader DC for Vista containing all of the needed files. Very much appreciated, no doubt, by Vista users Please accept some well-intended remarks: >> To install, download this file Your link actually points to a MEGA shared folder; one has to click the "Download as ZIP" button Incidentally, MEGA was being mean at me the day you first uploaded this and wouldn't let me fetch anything from inside that folder; it was fixed the next day, though (by that time I was anxiously trying to figure out what's wrong at my end ) ! >> and follow the instructions ... from your "Instructions.rdf" file (step 1): >>> run setup.msi There doesn't exist such a file; as per my original post, one would have to manually execute first the patched AcroRead.msi file, followed by executing manually file AcroRdrDCUpd1501020060.msp (step 2 of your guide), or, possibly, only execute file setup.exe which, if setup.ini is to be trusted, does the same things... >>> 4. Browse to the "Wrappers" folder, and copy both files to Windows\System32 (AND SysWOW64 if on 64-bit OS) I am on Vista x86, but according to @smeezekitty's original instructions for his wrappers, Vista users shouldn't mess with system dirs/files; both user33.dll & kernel33.dll can be placed (along with app's modified dlls) inside the app's installation directory, as per your step 3 - this is what I've done myself (all 5 dlls inside Acrobat Reader DC installation folder) and everything's OK! >> There are some bugs ... Nothing encountered on Vista Home Premium SP2 32bit >> Unfortunately, later versions currently don't work under Vista. BTW, many thanks for: >>> CREDITS: -VistaLover of MSFN.org, for finding out the absolute final version of Adobe Reader DC that works in Vista. ... and I hate to bring this up, but, considering Adobe Acrobat Reader DC is a closed source software (owned by Adobe), distributing modified parts of it (EXE installer, AcroRead.msi and three DLLs) might not go down well with their legal department... Best regards from Greece

Hello Running Windows Vista SP2 Home Premium x86 as my only OS here (Toshiba Laptop), so not inside a Virtual Machine. KB3217877 appeared on Windows Update as an optional update on Mar 22nd 2017; it was at that time completely undocumented, so did not install it initially... The following days various related articles appeared on line: https://answers.microsoft.com/en-us/windows/forum/windows_other-update/vista-patch-kb3217877/4b622ea2-2050-436f-8e35-096d1dd0ce87 https://www.askwoody.com/forums/topic/kb3217877-for-vista-and-windows-server-2008/ http://borncity.com/win/2017/03/23/update-kb3217877-for-windows-vistaserver-2008/ and finally M$ uploaded the relevant KB article at: https://support.microsoft.com/en-us/help/3217877/update-for-windows-server-2008-and-windows-vista-kb3217877 It was then that I decided to go ahead with the install, did it, restarted laptop as indicated and do not have any issues whatsoever since... It appears KB3217877 is an update to Win10 UCRT (KB2999226, file Windows6.0-KB2999226-x86.msu) so make sure this is installed first in your virtual OS. I am very sorry I can't help you any further, but MSFN does have very knowlegdeable members that should be able to... Regards

Hi all I got as far as File Version 15.010.20060.43353 of the "Continuous Track", which was released one year ago (March 8th 2016) and has the tabbed interface: I think people will find valuable Adobe's own ftp links: ftp://ftp.adobe.com/pub/adobe/reader/win/AcrobatDC/ Open the "1501020060" directory and download "AcroRdrDC1501020060_en_US.exe". As per the instructions previously in this thread, unpack (I used 7-zip) into a folder and patch "AcroRead.msi". A free alternative to Orca is Superorca, but be cautious because Superorca instantly modifies .msi installers; there's no "Save" option, only a "Save as" one, which allows for saving the modified file under a new name... To install base version 15.007.20033 on Vista, I changed "Not((VersionNT<601))" under "LaunchCondition" to "Not((VersionNT<600))". "AcroRdrDCUpd1501020060.msp" (windows installer patch) is the file that will update your initial installation from 15.007.20033 to 15.010.20060. My aged memory fails me at this point, what I think I did was to "cheat", so to speak: I installed "AcroRdrDC1501020060_en_US.exe" directly onto a Win7SP1 laptop (without a prior Adobe Reader installation), and (before it got updated further) I copied over the whole installation dir to a USB stick; this was then used to overwrite the initial 15.007.20033 Vista installation... I don't remember whether file "AcroRdrDCUpd1501020060.msp" runs on Vista or not, (Super)Orca can't inspect it... Last stage is to hex-edit DLLs "AcroRd32.dll", "AGM.dll", "AdobeLinguistic.dll" (read previously in this thread) and add "kernel33.dll" and "user33.dll" kindly and selflessly compiled and provided by @smeezekitty (...huge belated thanks ) The next update Adobe issued to 15.010.20060 was 15.016.20039, released on May 4th 2016. Most sadly, @smeezekitty's fixes cease to work at this point, because the devs introduced another Vista kernel incompatibility: I don't possess the knowledge to tell whether this error could be still fixed by another "redirection" DLL by @smeezekitty or someone else... Version 15.010.20060 is already one year old, superseded by many others in between (from 15.016.20039 to latest 15.023.20070). I would be very keen on having one of those later versions made to run on Vista, since they implement the new "DarkTheme.acrotheme", a dark UI which is much softer on the eyes, especially during the night... If I understood right, @Dibya works on XP and has modified the XP kernel accordingly... Can a solution be worked out on Vista OS, too? Please do share here if anyone's managed to have a recent version of Reader DC run on Vista... EDIT1: To prevent your Vista installed version (15.010.20060) from auto-updating to a non-compatible newer version, rename or delete the "Updater.api" file inside "plug_ins" folder. EDIT2: Acrobat Reader DC needs files msvcp100.dll, msvcp110.dll, msvcp120.dll, msvcr120.dll to be present inside app's root installation folder; the "110" flavours belong to MSVC++2010 (should be already present in Vista SP2) and the "120" ones belong to MSVC++2013. If not already present in your system (e.g. via another app or via Windows Update), look for them in Microsoft Download Center: https://www.microsoft.com/en-us/download/developer-tools.aspx Best regards