none
KB2263829 Gives "Not Applicable" Error

    Question

  • I have two new servers with 2008 R2 SP1, with Hyper-V Role and Failover Clustering.  When I try to install KB2263829 I get a message indicating that it is not applicable.  Is there a log I can look at to see why it thinks it is not applicable?  This is a fresh install, so no VMs, yet.

    Tuesday, July 24, 2012 5:59 PM

Answers

  • We do have AMD and I did have to install the AVX fix so that Hyper-V would run VMs.

    That is the reason. The AVX patch.

    Hvax64.exe 6.1.7601.17640 610,816 23-Jun-2011 02:39 x64
    Hvboot.sys 6.1.7601.17640 118,144 23-Jun-2011 05:42 x64
    Hvix64.exe 6.1.7601.17640 652,288 23-Jun-2011 02:39 x64

    See:

    http://support.microsoft.com/kb/2568088

    Tuesday, July 31, 2012 3:45 PM

All replies

  • My guess is that you are using the Option 6 on the Sconfig.cmd menu to install patches, right?

    Tuesday, July 24, 2012 9:46 PM
  • Hi,

    In the KB2263829, you will be able to find the following description.

    Prerequisites
    To apply this update, you must be running Windows Server 2008 R2 Service Pack 1. Additionally, you must have Hyper-V role installed on your computer.

    So I would like to ask whether you have Hyper-V role enabled already? If it’s a fresh installed computer without Hyper-V enabled, you will get the not applicable message.

     

    Wednesday, July 25, 2012 3:04 AM
    Moderator
  • In this case, this is a Full Install - not Core, so I am not using Sconfig.  I am using Windows Update and then running the hotfix.
    Wednesday, July 25, 2012 5:06 PM
  • Yes, the Hyper-V Role is installed, and SP1 is installed.
    Wednesday, July 25, 2012 5:07 PM
  • Can you take a look and verify the file version of the following files?..

    Post the # of version you have in your host.

    For all supported x64-based versions of Windows Server 2008 R2
    Collapse this tableExpand this table
    File name File version File size Date Time Platform
    Hvax64.exe 6.1.7601.17579 614,400 15-Mar-2011 02:35 x64
    Hvboot.sys 6.1.7601.17579 118,144 15-Mar-2011 05:34 x64
    Hvix64.exe 6.1.7601.17579 652,288 15-Mar-2011 02:35 x64
    Hvax64.exe 6.1.7601.21683 614,400 15-Mar-2011 02:28 x64
    Hvboot.sys 6.1.7601.21683 118,144 15-Mar-2011 05:19 x64
    Hvix64.exe 6.1.7601.21683 652,288 15-Mar-2011 02:28 x64
    Thursday, July 26, 2012 3:50 PM
  • We are on version 6.1.7601.17640 for all.
    Friday, July 27, 2012 3:47 PM
  • Hi,

    I just tried to install the KB on a fresh installed Windows Server 2008 R2 SP1 compute with Hyper-V enabled and it installed without any issue.

    By the way, you can check the following logs.

    c:\Windows\logs\CSB\CBS.log and c:\Windows\WindowsUpdate.log

     

    Monday, July 30, 2012 9:11 AM
    Moderator
  • We are on version 6.1.7601.17640 for all.

    That is the reason why is not applicable.

    That KB will update your file version to 6.1.7601.17579 and you already have a version newer.

    • Proposed as answer by AlexitoRG Monday, July 30, 2012 11:07 PM
    Monday, July 30, 2012 11:07 PM
  • That would be my impression, too.  The reason I am trying to install the "update" is because NetApp's SnapManager for Hyper-V 1.1 will not install, indicating that it needs this KB to be installed.  When I contacted NetApp, suggesting that their software was asking for an update that is not needed any longer, they indicated that this is an MS issue and that the update should install even on R2 with SP1.  So, I guess the mystery is what updated it to a newer version that keeps the update from installing.  Any reference available to show what hotfix or other update would have upgraded it to the version we have - the 17640?
    Tuesday, July 31, 2012 12:42 AM
  • Hi,

    Please proceed to Control Panel\All Control Panel Items\Windows Update\View update history to see the updates installed on your computer. You can also run PowerShell command “get-hotfix > c:\updates.txt” to export the list to a txt file.

     

    Tuesday, July 31, 2012 7:44 AM
    Moderator
  • That would be my impression, too.  The reason I am trying to install the "update" is because NetApp's SnapManager for Hyper-V 1.1 will not install, indicating that it needs this KB to be installed.  When I contacted NetApp, suggesting that their software was asking for an update that is not needed any longer, they indicated that this is an MS issue and that the update should install even on R2 with SP1.  So, I guess the mystery is what updated it to a newer version that keeps the update from installing.  Any reference available to show what hotfix or other update would have upgraded it to the version we have - the 17640?

    Do you have in your hosts  AMD CPUs?.. Did you install the AVX patch?
    Tuesday, July 31, 2012 3:03 PM
  • I should have stated my question more clearly ... I know how to list the applied updates, but what I am after is this:

    If the version is .17640 and that did not come from SP1 and it did not come rom KB2263829, where did it come from?  I was hoping there would be some way to cross reference the version to the hotfix or other update that installed it.

    Tuesday, July 31, 2012 3:09 PM
  • We do have AMD and I did have to install the AVX fix so that Hyper-V would run VMs.
    Tuesday, July 31, 2012 3:10 PM
  • We do have AMD and I did have to install the AVX fix so that Hyper-V would run VMs.

    That is the reason. The AVX patch.

    Hvax64.exe 6.1.7601.17640 610,816 23-Jun-2011 02:39 x64
    Hvboot.sys 6.1.7601.17640 118,144 23-Jun-2011 05:42 x64
    Hvix64.exe 6.1.7601.17640 652,288 23-Jun-2011 02:39 x64

    See:

    http://support.microsoft.com/kb/2568088

    Tuesday, July 31, 2012 3:45 PM
  • Thanks for your answer.  So, I will head back to NetApp, because this would seem to confirm that their installation of SnapManager for Hyper-V 1.1 is looking for the exact hotfix rather than that or newer. One thing I can try is to remove the AVX patch, install KB 2263829, and then re-install the AVX patch.
    Tuesday, July 31, 2012 3:49 PM
  • I did remove KB2568088, then apply KB2263829, then re-apply KB2568088 and when all was complete I was able to install NetApp SnapManager for Hyper-V v1.1, which was looking for the KB2263829 as a prerequisite.

    Thanks, again, to all.

    Tuesday, July 31, 2012 7:19 PM
  • I did remove KB2568088, then apply KB2263829, then re-apply KB2568088 and when all was complete I was able to install NetApp SnapManager for Hyper-V v1.1, which was looking for the KB2263829 as a prerequisite.

    Thanks, again, to all.

    Glad to hear that.

    Just remember to tell NetApp SnapManager to update their prerequisite patchs.

    Tuesday, July 31, 2012 9:51 PM
  • Hi Guys,

    I'm having similar issue that I cannot install the needed KB for Snapmanager for Hyper-V Setup, as it says its not applicable.

    Because the Files which the KB wants update are more newer then these in the KB. I cannot remove the Hotfixes mentioned in the reply above (i have Intel CPU).

    Anyidea, i guess Snapmanger Hyper-V Setup checks hardly on KB2263829 - but I cannot install, since my files are newer due some other update.

    some ohter ideas?

    Wednesday, September 19, 2012 2:43 PM