Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Security updates for Vista after end of support - Windows Server 2008 patches


  • Please log in to reply
80 replies to this topic

#31 Sardoc

Sardoc
  • Topic Starter

  • Members
  • 31 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:52 PM

Posted 20 August 2017 - 10:56 AM

Welcome to August ladies and gentlemen.

 

First off, I apologise for not posting the list for July, as well as posting the August list so late. I wasn't available due to moving houses. I'm finally done with the move and I have proper "Interwebs" now, as well as some free time, so without further ado, let's get back to business at full speed and all guns blazing. I'll post both July and August 2017 lists below.

 

 

 

 

 

 

 

Here is the list for July 2017:

 

Windows Server 2008 security fixes: KB4020535 (originally listed for June, but I had missed this one, so I've added it to this list. Thanks to KYKaren for reporting!), KB4022746, KB4022748, KB4022914, KB4025240, KB4025397, KB4025398, KB4025409, KB4025497, KB4025674, KB4025877, KB4026059, KB4026061, KB4032955. All of those are available for both 32 and 64 bit versions, and all installed correctly. Make sure you choose the correct 32 or 64 bit version for Windows Server 2008 (without R2), as WS2008 R2 is a different operating system based on Windows 7's codebase.

 

KB4025872 was listed as well, however it said it was not applicable. It could be because it addresses an issue with Windows PowerShell, and I know the latest version for WS2008 is 3.0, but for Vista only 2.0 (and installing WS2008 version does not work).

 

Internet Explorer 9: KB4025252. Make sure you choose the correct 32 or 64 bit version for Windows Server 2008 (without R2), as WS2008 R2 is a different operating system based on Windows 7's codebase.

 

D3D Compiler Update (required to install one of the .Net updates for this month): KB4019478 - this update is listed both for July and August 2017, and while both versions have the same file size, it is not the same file. I was able to install one after another, and that's what I would advise myself. I'll post links to both variants. Once again thanks to KYKaren for reporting! (version for July 2017; 32 bit version link and 64 bit version link), (version for August 2017; 32 bit version link and 64 bit version link) .

 

.Net 2.0 (co-exists with version 4 without replacing it, recommended to install alongside anything newer): KB4014592 (32 bit version link and 64 bit version link).

 

.Net 4.6 (install alongside version 2.0): KB4024848 (32 bit version link and 64 bit version link), KB4014606 (32 bit version link and 64 bit version link. Both have a date of May 2017 for some reason).

 

.Net 4.5 (ignore if you're using version 4.6, which supersedes 4.5): KB4024845 (32 bit version link and 64 bit version link), KB4014613 (32 bit version link and 64 bit version link).

 

 

 

 

 

 

Here is the list for August 2017:

 

Windows Server 2008 security fixes: KB4022750, KB4034034, KB4034741 (you can ignore the mpsyschk file, as it's just a compatibility checker), KB4034744, KB4034745, KB4034775, KB4035055, KB4035056, KB4035679. All of those are available for both 32 and 64 bit versions, and all installed correctly. Make sure you choose the correct 32 or 64 bit version for Windows Server 2008 (without R2), as WS2008 R2 is a different operating system based on Windows 7's codebase.

 

Internet Explorer 9: KB4034733. Make sure you choose the correct 32 or 64 bit version for Windows Server 2008 (without R2), as WS2008 R2 is a different operating system based on Windows 7's codebase.

 

Updates to add TLS 1.1 and TLS 1.2 support: KB4019276. There are 2 sets of updates: one from July, one from August. I have hex-compared them, and they're identical bit by bit. I have no idea why they're listed twice, but it doesn't matter which one you choose.

 

.Net 2.0 (co-exists with version 4 without replacing it, recommended to install alongside anything newer): KB4033994 (32 bit version link and 64 bit version link).

 

.Net 4.6 (install alongside version 2.0): KB4033990 (32 bit version link and 64 bit version link).

 

.Net 4.5 (ignore if you're using version 4.6, which supersedes 4.5): KB4033993 (32 bit version link and 64 bit version link).

 

 

 

 

This is it. I'm really glad Microsoft finally stopped being ridiculous and just added TLS 1.1 and 1.2 support to WS2008 (and thanks to this thread to Vista as well, at least unofficially anyway). It shouldn't have taken this many years of constant requests for it though, considering it is a security issue, but at least we have the support now.

 

However, I'm disappointed at how much digging I had to do to get any sort of information on .Net updates for both July and August. None of them were listed on the Security Update Deployment Information sheets, as if there weren't any .Net updates at all for both months. I had to double check using external sites which publish the same lists as I do. I'm very surprised Microsoft's pages are so lacking, and that I have to rely on external crutches instead.

 

If I've missed anything, please let me know.


Edited by Sardoc, 21 August 2017 - 05:09 AM.


BC AdBot (Login to Remove)

 


m

#32 VolumeZ

VolumeZ

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:04:52 PM

Posted 20 August 2017 - 02:13 PM

Hi Sardoc,

 

you're late for KB4025877. Like every regular Patch Day, the Security update for the Win32k information disclosure vulnerability has been straight superseded the next month.

 

You're free to skip KB4025877 for KB4035055.

 

Regards, VZ  :)



#33 KYKaren

KYKaren

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Local time:10:52 AM

Posted 20 August 2017 - 06:51 PM

Welcome to August ladies and gentlemen.

 

.....

 

This is it. I'm really glad Microsoft finally stopped being ridiculous and just added TLS 1.1 and 1.2 support to WS2008 (and thanks to this thread to Vista as well, at least unofficially anyway). It shouldn't have taken this many years of constant requests for it though, considering it is a security issue, but at least we have the support now.

 

However, I'm disappointed at how much digging I had to do to get any sort of information on .Net updates for both July and August. None of them were listed on the Security Update Deployment Information sheets, as if there weren't any .Net updates at all for both months. I had to double check using external sites which publish the same lists as I do. I'm very surprised Microsoft's pages are so lacking, and that I have to rely on external crutches instead.

 

Hi Sardoc,

Thanks for all of the information and links to July and August WS2008 patches for Vista.

 

Do you think that there is no information in Microsoft Security Update Deployment information about these July and August NFW updates because they are 'Quality' updates and not 'Security' / 'Quality and Security' updates??

 

All of the Windows Server 2008 Security Updates for July and August are listed in the Microsoft Security Update Summary, except for KB4034741 (August 4), which replaced KB4022013 (June 13). This is a Security Update, so, this, too, shows that it’s difficult to depend on Microsoft for complete information.  Thanks for finding this.

 

I have a couple of questions:

1. Do you advise installing KB4019478 (D3D Compiler Update) and then restarting before installing any of the .NFW files?

2. Must Vista already have something in place in order for the updates adding TLS 1.1 and TLS1.2  Support to work??  If so, what must be in place?

 

Thanks again.



#34 KYKaren

KYKaren

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Local time:10:52 AM

Posted 20 August 2017 - 09:38 PM

Here is the list for July 2017:


 

---

D3D Compiler Update (required to install one of the .Net updates for this month): KB4019478 (32 bit version link and 64 bit version link).

 

==========================


 

Sardoc,

 

I’ve noticed that KB4019478 (D3D Compiler Update) is available in the Microsoft Update Catalog under 2 parent numbers: KB4032116 (July 2017 Preview of Quality Rollup for NFW 2.0. 3.0, 4.5.2, 4.6) and KB4035039 (August 2017 Preview of Quality Rollup for NFW 2.0, 3.0, 4.5.2, 4.6).   The files are not coded with the same name, but they are the same size 1,402 KB.  Are they the same file??



#35 Sardoc

Sardoc
  • Topic Starter

  • Members
  • 31 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:52 PM

Posted 21 August 2017 - 05:01 AM

 

Welcome to August ladies and gentlemen.

 

.....

 

This is it. I'm really glad Microsoft finally stopped being ridiculous and just added TLS 1.1 and 1.2 support to WS2008 (and thanks to this thread to Vista as well, at least unofficially anyway). It shouldn't have taken this many years of constant requests for it though, considering it is a security issue, but at least we have the support now.

 

However, I'm disappointed at how much digging I had to do to get any sort of information on .Net updates for both July and August. None of them were listed on the Security Update Deployment Information sheets, as if there weren't any .Net updates at all for both months. I had to double check using external sites which publish the same lists as I do. I'm very surprised Microsoft's pages are so lacking, and that I have to rely on external crutches instead.

 

Hi Sardoc,

Thanks for all of the information and links to July and August WS2008 patches for Vista.

 

Do you think that there is no information in Microsoft Security Update Deployment information about these July and August NFW updates because they are 'Quality' updates and not 'Security' / 'Quality and Security' updates??

 

All of the Windows Server 2008 Security Updates for July and August are listed in the Microsoft Security Update Summary, except for KB4034741 (August 4), which replaced KB4022013 (June 13). This is a Security Update, so, this, too, shows that it’s difficult to depend on Microsoft for complete information.  Thanks for finding this.

 

I have a couple of questions:

1. Do you advise installing KB4019478 (D3D Compiler Update) and then restarting before installing any of the .NFW files?

2. Must Vista already have something in place in order for the updates adding TLS 1.1 and TLS1.2  Support to work??  If so, what must be in place?

 

Thanks again.

 

Hi,

 

I installed all of July and August updates without any restarts in-between. I then restarted the machine after everything was installed, and it works fine for me. Though if you want to reboot, feel free to. Definitely won't make things worse.

 

For the patch introducing TLS 1.1 and 1.2, it says "To install this update, you must have Windows Server 2008 SP2 installed." So you should be fine with just Vista SP2. However, as was the case with WS2008 R2, here both of them are also disabled by default. I haven't found a way to turn them on yet, but hopefully I will soon. Everyone is welcome to try that, too.

 

As for the D3D Compiler, thanks for reporting! These are indeed 2 different files, and having installed the July version yesterday, I still was able to install the August version today. I'll edit my post and include both links, as well as a mini-explanation. Thanks again!



#36 Sardoc

Sardoc
  • Topic Starter

  • Members
  • 31 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:52 PM

Posted 21 August 2017 - 05:14 AM

Hi Sardoc,

 

you're late for KB4025877. Like every regular Patch Day, the Security update for the Win32k information disclosure vulnerability has been straight superseded the next month.

 

You're free to skip KB4025877 for KB4035055.

 

Regards, VZ  :)

Hi,

 

I haven't noticed anything about one replacing the other in the KB knowledge articles. For now, I'll keep the list like it is until someone tries to install KB4035055 first, then KB4025877 and the system says it's not applicable. Thanks for reporting though!

 

Anyone cares to try that? Please let us know if you do.



#37 Sardoc

Sardoc
  • Topic Starter

  • Members
  • 31 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:52 PM

Posted 21 August 2017 - 05:16 AM

As promised, I've edited the list for July and August, adding extra links and explanation about the D3D Compiler update.

 

I've also edited the wrong link for the TLS update (it was leading to the IE9 update instead, woops!) It's fine now. Sorry about that.



#38 KYKaren

KYKaren

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Local time:10:52 AM

Posted 21 August 2017 - 08:20 AM

 


 

For the patch introducing TLS 1.1 and 1.2, it says "To install this update, you must have Windows Server 2008 SP2 installed." So you should be fine with just Vista SP2. However, as was the case with WS2008 R2, here both of them are also disabled by default. I haven't found a way to turn them on yet, but hopefully I will soon. Everyone is welcome to try that, too.

 

 

 

I'm confused.  Is this thread is about keeping Vista up-to-date, despite Microsoft's EOL declaration?  Or is about keeping WS2008 up-to-date on a virtual machine?   The header for this thread indicates the former, but now it seems to be about both.  

 

I'm a Vista user (and not a user of WS2008 on a virtual machine). I know nothing about VMs, but I think that I am going to have to learn how to sort out the suggested patches that apply to both a Vista machine and a WS2008 VM from those that apply only to a WS2008 VM.



#39 KYKaren

KYKaren

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Local time:10:52 AM

Posted 21 August 2017 - 08:41 AM

 

Hi Sardoc,

 

you're late for KB4025877. Like every regular Patch Day, the Security update for the Win32k information disclosure vulnerability has been straight superseded the next month.

 

You're free to skip KB4025877 for KB4035055.

 

Regards, VZ  :)

Hi,

 

I haven't noticed anything about one replacing the other in the KB knowledge articles. For now, I'll keep the list like it is until someone tries to install KB4035055 first, then KB4025877 and the system says it's not applicable. Thanks for reporting though!

 

Anyone cares to try that? Please let us know if you do.

 

There might be a typo here??   KB4035055 replaces KB4022887. 



#40 lmacri

lmacri

  • Members
  • 365 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Canada
  • Local time:09:52 AM

Posted 21 August 2017 - 09:23 AM

2. Must Vista already have something in place in order for the updates adding TLS 1.1 and TLS1.2  Support to work??  If so, what must be in place?

For the patch introducing TLS 1.1 and 1.2, it says "To install this update, you must have Windows Server 2008 SP2 installed." So you should be fine with just Vista SP2. However, as was the case with WS2008 R2, here both of them are also disabled by default. I haven't found a way to turn them on yet, but hopefully I will soon. Everyone is welcome to try that, too.

 

Hi Sardoc:

As far as Vista SP2 home users are concerned, support for making secure connections with TLS 1.1, 1.2 and 1.3 (currently in beta) are built in to the browser, not the OS, and when they browse to a secure https: site the backend server will try to negotiate a connection with the highest (and safest) TLS version supported by both the browser and the server.  I haven't been following your advice to install Windows 2008 patches on my Vista SP2 machine and if I browse to the Qualys browser test site at https://www.ssllabs.com/ssltest/viewMyClient.html with my Firefox ESR v52.3.0 browser it shows that I can still make TLS 1.1 and TLS 1.2 connections with any server that also supports these protocols as long as I use this Firefox browser.

 

Attached File  Firefox ESR v52_3_0 Qualys TLS 1_2 Supported 21 Aug 2017.png   14.67KB   0 downloads

I`m not certain, but I suspect the TLS 1.1 and 1.2 support in KB4019276 is intended for backend servers that are actually hosting content.  When TLS 1.3 is out of beta most supported web browsers like Firefox will be disabling older, less secure protocols like TLS 1.0 and users will not be able to create secure connections to web servers running Windows Server 2008 unless the server has been upgraded for TLS 1.1 and 1.2 support.

Microsoft has some information in their blog at TLS 1.2 Support added to Windows Server 2008 and the registry changes required to enable TLS 1.2 support on Windows Server 2008 web servers is posted in the KB article for KB4019276, but I don`t think this is going to have a direct affect on Vista SP2 home users.  In practice, Vista SP2 users would want to know if one of the recent Windows Server 2008 updates for IE9 also added TLS 1.1 and 1.2 support to that old browser.

My IE9 browser, last patched in June 2017 (Update Versions 9.0.61 / KB4018271), shows that TLS 1.0 is the newest protocol I can currently use to make a secure connection with IE9.  Check at Tools | Internet Options | Advanced and scroll down to the Security section to see it the latest Windows Server 2008 August cumulative update KB4034733 for IE9 added TLS 1.1 or 1.2 support for this browser.

 

Attached File  IE9 v9.0.61 TLS 1_0 Highest Protocol 21 Aug 2017.png   15.14KB   0 downloads

-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.3.0 * NS Premium v22.10.0.85 * MB Premium v3.1.2


Edited by lmacri, 21 August 2017 - 09:43 AM.


#41 KYKaren

KYKaren

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Local time:10:52 AM

Posted 21 August 2017 - 02:43 PM

 

2. Must Vista already have something in place in order for the updates adding TLS 1.1 and TLS1.2  Support to work??  If so, what must be in place?

For the patch introducing TLS 1.1 and 1.2, it says "To install this update, you must have Windows Server 2008 SP2 installed." So you should be fine with just Vista SP2. However, as was the case with WS2008 R2, here both of them are also disabled by default. I haven't found a way to turn them on yet, but hopefully I will soon. Everyone is welcome to try that, too.

In practice, Vista SP2 users would want to know if one of the recent Windows Server 2008 updates for IE9 also added TLS 1.1 and 1.2 support to that old browser.

....

 Check at Tools | Internet Options | Advanced and scroll down to the Security section to see it [sic] the latest Windows Server 2008 August cumulative update KB4034733 for IE9 added TLS 1.1 or 1.2 support for this browser.

 

attachicon.gifIE9 v9.0.61 TLS 1_0 Highest Protocol 21 Aug 2017.png

-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.3.0 * NS Premium v22.10.0.85 * MB Premium v3.1.2

 

Thanks for the explanatory information on the 3-pronged relationship of browser, TLS protocol, and server.

 

My Vista x86 has the August WS2008 IE9 patch KB4034733 installed.  In the IE9 brower, the dialogue box for Tools | Internet Options | Advanced > Security also has only 'Use TLS 1.0' listed and the box is checked (i.e., no listing for TLS 1.1 or TLS 1.2).  (It also has the box for  'Use SSL 3.0' checked. I am thinking that I should uncheck this box, because otherwise, TSL 1.0 can downgrade to SSL 3.0 and thus, weaken security, were I to use the IE9 browser.  Any ideas about this?

 

I always use Firefox ESR (now v52.3.0) and from your info, I've learned that were I to use the IE9 browser, even the latest one via WS2008 updates, there are greater risks (than using Firefox ESR) because the installation of WS2008's latest IE9 patch on a Vista machine does not provide the latest TLS protocol available.

 

BTW, I read on Wikipedia (about Transport Layer Security) that Firefox enabled TLS 1.3 by default in Feb, 2017.  But, given your brower test, this must not include Firefox ESR??

 

Thanks for all of this information -- it helps keep Vista safe, despite its EOL.



#42 lmacri

lmacri

  • Members
  • 365 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Canada
  • Local time:09:52 AM

Posted 21 August 2017 - 05:44 PM

My Vista x86 has the August WS2008 IE9 patch KB4034733 installed.  In the IE9 brower, the dialogue box for Tools | Internet Options | Advanced > Security also has only 'Use TLS 1.0' listed and the box is checked (i.e., no listing for TLS 1.1 or TLS 1.2).  (It also has the box for  'Use SSL 3.0' checked. I am thinking that I should uncheck this box, because otherwise, TSL 1.0 can downgrade to SSL 3.0 and thus, weaken security, were I to use the IE9 browser.  Any ideas about this?

 

Hi KYKaren:

 

Yes, I would recommend disabling SSL 3.0 support in your IE9 browser.  I did this back in 2014 when the POODLE exploit was first reported - see Martin Brinkmann's October 2014 ghacks.net article SSL 3.0 Vulnerability Discovered. Find Out How to Protect Yourself.  Both Mozilla and Google automatically disabled SSL 3.0 support in their browsers in January 2015 (FF v35, Chrome v40), and when it was later discovered that TLS 1.0 was also vulnerable to the POODLE exploit I went ahead and turned off TLS 1.0 in my Firefox settings as instructed in the SSL.com article Turn Off SSL 3.0 and TLS 1.0 in Your Browser.  Unfortunately, you can't disable TLS 1.0 in IE9 since you need at least one supported protocol to make a secure connection.

 

I switched from IE9 to Firefox back in 2011 because of this lack of TLS 1.1 and 1.2 support in IE9.  Firefox ESR is now the only secure browser for use on Vista SP2 computers since Google stopped supporting the Win XP and Vista platforms in April 2016 per their announcement <here>.

 

BTW, I read on Wikipedia (about Transport Layer Security) that Firefox enabled TLS 1.3 by default in Feb, 2017.  But, given your brower test, this must not include Firefox ESR??

 

According to Martin Brinkmann's June 2017 ghacks.net article How to Enable TLS 1.3 Support in Firefox and Chrome "Both Firefox and Chrome support TLS 1.3, but the version of Transport Layer Security is not enabled by default. The main reason for that, likely, is that it is still only available as a draft."  TLS 1.2 is still the recommended protocol until TLS 1.3 comes out of beta.  I posted further information about IE9 and TLS 1.3 in the Norton Tech Outpost board <here>.

-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.3.0 * NS Premium v22.10.0.85 * MB Premium v3.1.2


Edited by lmacri, 21 August 2017 - 05:46 PM.


#43 Sardoc

Sardoc
  • Topic Starter

  • Members
  • 31 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:52 PM

Posted 21 August 2017 - 06:30 PM

 

 


 

For the patch introducing TLS 1.1 and 1.2, it says "To install this update, you must have Windows Server 2008 SP2 installed." So you should be fine with just Vista SP2. However, as was the case with WS2008 R2, here both of them are also disabled by default. I haven't found a way to turn them on yet, but hopefully I will soon. Everyone is welcome to try that, too.

 

 

 

I'm confused.  Is this thread is about keeping Vista up-to-date, despite Microsoft's EOL declaration?  Or is about keeping WS2008 up-to-date on a virtual machine?   The header for this thread indicates the former, but now it seems to be about both.  

 

I'm a Vista user (and not a user of WS2008 on a virtual machine). I know nothing about VMs, but I think that I am going to have to learn how to sort out the suggested patches that apply to both a Vista machine and a WS2008 VM from those that apply only to a WS2008 VM.

 

It's a thread for keeping Vista up to date despite Microsoft's EOL declaration, by taking advantage of the code similarity and applying Windows Server 2008 updates to it. These two were the first ever Microsoft client and server systems to share the same codebase, to the point where they used one and the same binary for SP2 for both. Since Vista is officially unsupported now, but WS2008 will still receive security patches till Jan 2020 (just like Win 7 and its server counterpart, WS2008 R2), I thought might as well, and went for this approach. This is why for every list I give a short summary of how it went: whether the fixes installed fine, were deemed not applicable, etc. etc.

 

For this reason, software requirements and pre-requisites in the patch notes will obviously be listed for WS2008, but as they share the same SP2 binary, it also means Vista unless specifically said otherwise (e.g. Windows PowerShell 3.0).



#44 VolumeZ

VolumeZ

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:04:52 PM

Posted 21 August 2017 - 07:52 PM

There might be a typo here??   KB4035055 replaces KB4022887. 

 

Not a typo. An inconsistency in the Catalog. KB4025877 replaces KB4022887. KB4035055 replaces KB4025877 and KB4022887. In a hypothetical continuation of Dalai's list for August 2017, KB4015195 can be replaced by KB4019204, KB4022887, KB4025877 and KB4035055.

 

KB4025877 is a Security Update for the Win32k information disclosure vulnerability, formerly known as Update for Kernel-Mode Drivers.

 

 

For now, I'll keep the list like it is until someone tries to install KB4035055 first, then KB4025877 and the system says it's not applicable.

 

Hi Sardoc,

 

I am that person. Feel free to disregard my comment anyway. It's too little of an issue and too hard to figure out in the long term. Users desiring to avoid redundancy simply should not hesitate to apply the updates from new to old.

 

Regards, VZ


Edited by VolumeZ, 21 August 2017 - 07:56 PM.


#45 KYKaren

KYKaren

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Local time:10:52 AM

Posted 21 August 2017 - 09:33 PM

 

 

 


 

For the patch introducing TLS 1.1 and 1.2, it says "To install this update, you must have Windows Server 2008 SP2 installed." So you should be fine with just Vista SP2. However, as was the case with WS2008 R2, here both of them are also disabled by default. I haven't found a way to turn them on yet, but hopefully I will soon. Everyone is welcome to try that, too.

 

 

 

I'm confused.  Is this thread is about keeping Vista up-to-date, despite Microsoft's EOL declaration?  Or is about keeping WS2008 up-to-date on a virtual machine?   The header for this thread indicates the former, but now it seems to be about both.  

 

I'm a Vista user (and not a user of WS2008 on a virtual machine). I know nothing about VMs, but I think that I am going to have to learn how to sort out the suggested patches that apply to both a Vista machine and a WS2008 VM from those that apply only to a WS2008 VM.

 

It's a thread for keeping Vista up to date despite Microsoft's EOL declaration, by .....

 

For this reason, software requirements and pre-requisites in the patch notes will obviously be listed for WS2008, but as they share the same SP2 binary, it also means Vista unless specifically said otherwise (e.g. Windows PowerShell 3.0).

 

Yes, I know that WS2008 patches, for the most part, work on a Vista O/S.  But, I also have come to understand from the discussion here that the patch for TLS 1.1 and 1.2 support should be on the "specifically said otherwise" list,  joining membership with Windows PowerShell 3.0, right?   






3 user(s) are reading this topic

0 members, 3 guests, 0 anonymous users