none
KB2949927 fails to install if BitLocker (fvevol) service is disabled RRS feed

  • Question

  • Hi,

    Be warned, everybody: KB2949927 will fail to install and revert the changes at the next boot if you have BitLocker disabled.

    The "fvevol" service must be started, and it must be registered in the "LowerFilters" value under this registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71a27cdd-812a-11d0-bec7-08002be2092f}

    If you don't have it, KB2949927 will fail!

    Kind regards.

    EDIT: IMPORTANT: I pasted the wrong GUID in my original post, I've edited it with the correct GUID. Please accept my apologies!

    Also, the "LowerFilters" value MUST be "REG_MULTI_SZ" type

    • Edited by Leolo Wednesday, October 15, 2014 10:44 AM fix wrong GUID
    Wednesday, October 15, 2014 1:00 AM

Answers

  • My solution was to enable automount in Diskpart "automount enable" , this keeps the "System Reserved" partition online after a reboot.

    The error in the eventlog that brings me to this:
    Encrypted volume check: Volume information on \\?\Volume{33140243-4d22-11e2-aed7-806e6f6e6963} cannot be read.

    Wednesday, October 15, 2014 11:02 AM
  • I tried diskpart automount and fvevol, patch still rollback.

    I have installed grub on MBR and boot flag was set on Linux partition. 

    I fix my problem by setting boot flag to windows partition with windows boot files. Hope this can help Linux users.

    • Proposed as answer by FeRDNYC Thursday, October 16, 2014 5:57 AM
    • Marked as answer by Yolanda ZhuModerator Wednesday, November 5, 2014 10:03 AM
    Thursday, October 16, 2014 4:59 AM
  • I had the same situation as 柳局南段 (dual-booting Windows/Linux installation managed by Grub 2), and the same solution worked:

    1. Went into Disk Management
    2. Right-clicked the Windows 7 partition and chose "Mark Partition as Active"
    3. Allowed Windows to reboot and complete the installation (successfully)

    Then I just switched Active back to my Linux /boot partiton when Windows came back up.

    • Proposed as answer by c_w_t_ Thursday, October 16, 2014 7:00 AM
    • Marked as answer by Yolanda ZhuModerator Wednesday, November 5, 2014 10:03 AM
    Thursday, October 16, 2014 5:59 AM

All replies

  • Leolo, I'm having the problem you described in my Windows 7 Professional environment.

    However, I don't want to encrypt my drive, which I assume would happen if I enable BitLocker.  Right?

    Is it a big problem if KB2949927 isn't installed?

    Thanks, Tim

    Wednesday, October 15, 2014 1:49 AM
  • Hi,

    Be warned, everybody: KB2949927 will fail to install and revert the changes at the next boot if you have BitLocker disabled.

    The "fvevol" service must be started, and it must be registered in the "LowerFilters" value under this registry key:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}]

    If you don't have it, KB2949927 will fail!

    Kind regards.


    You may be right. My Win7 got stuck with this particular update an endless loop of install, fail & revert. I have disabled it (Hide) for now.
    Wednesday, October 15, 2014 1:51 AM
  • More detail please. Is LowerFilters an sz or a multi-sz? Is the entire field value "fvevol"?

    Since LowerFilters does not appear on the machine this update is failing on, I am having to create it manually.

    Please also confirm if the class belongs to DVD/CD-Rom drives.



    • Edited by Tarek Okail Wednesday, October 15, 2014 4:28 AM
    Wednesday, October 15, 2014 4:25 AM
  • Hello,

    KB2949927caused a 0xc000000e after Installation and the subsequent reboot.

    It does this reproducible on my Windows 7 Ultimate without Bitlocker activated.

    Had to restore my PC from backup two times to work this out.

    First time: Install all MS-Patches from October Patchday, receiving the 0xc000000e.

    Second time: Installing the 21 patches for my system one at a time with a reboot after each intsallation to check for the 0xc000000e until it appeared.

    After the second restore I installed the other 20 patches without problem.

    This Patch does something the my boot-device Windows doesn't like

    The Basic description of the article doesn't Sound like a big Change in the first place, but for my System it's not really good.

    Regards

    Uwe

    Wednesday, October 15, 2014 5:50 AM
  • Same problem here. KB2949927 fails on Windows Server 2008 R2 with Error Code 0X80004005.
    Wednesday, October 15, 2014 7:34 AM
  • Same problem. Windows 7 Home 64-bit failed twice. Each time, system tries to recover and eventually I had to use a previous restore point.

    Wednesday, October 15, 2014 9:37 AM
  • I'm sorry, I copy-pasted the wrong GUID.

    I've edited my original post with the correct GUID. It's the one that belongs to "Storage Volumes". The "LowerFilters" value is  "REG_MULTI_SZ" type.

    • Proposed as answer by arjan67 Wednesday, October 15, 2014 10:57 AM
    • Unproposed as answer by arjan67 Wednesday, October 15, 2014 10:57 AM
    Wednesday, October 15, 2014 10:46 AM
  • My solution was to enable automount in Diskpart "automount enable" , this keeps the "System Reserved" partition online after a reboot.

    The error in the eventlog that brings me to this:
    Encrypted volume check: Volume information on \\?\Volume{33140243-4d22-11e2-aed7-806e6f6e6963} cannot be read.

    Wednesday, October 15, 2014 11:02 AM
  • The automount enable solved my situation. It was already enabled on all other computers i looked at and of course i did not check the status before i enabled it. However that was all i did so i suppose it was not enabled from the beginning.
    Wednesday, October 15, 2014 1:26 PM
  • arjan67, thank you for your solution, which worked for me: CMD, diskpart, automount enable.

    This update was driving me to distraction ... and I hate being beaten!

    Wednesday, October 15, 2014 2:20 PM
  • Leolo, Please allow me to re-ask TimAtlanta's question:

    If I enable BitLocker does this encrypt my drive(s)? (which is not desired)

    If Bitlocker is not enabled, is KB2949927 necessary?

    Wednesday, October 15, 2014 3:04 PM
  • BitLocker doesn't automatically encrypt your drives until you tell it to do so.

    You can safely enable it and leave it unconfigured so it won't encrypt anything.

    Wednesday, October 15, 2014 3:21 PM
  • Same problem here. KB2949927 fails on Windows Server 2008 R2 with Error Code 0X80004005.

    I had SAME problem on my Windows 7 Pro SP1 x64 desktop PC, got Error Code 0x800004005 after suffering through multiple auto-reboots during multiple Install Update -> Fail -> Revert cycles.

    Thanks to Leolo for pointing out the KB2949927 problem and providing a regedit solution; however as a rookie I think I'll try Arjan's solution via CardPlayer's method to enable automount.


    Asus P5N32-E SLI mobo, C2D E8400 @3GHz, 4x 1GB PC2-8500 OCZ DDR2, Asus GTX580/1536MB, Win7 Pro SP1 x64

    Wednesday, October 15, 2014 3:35 PM
  • Hi,

    thx to  Leolo for bringing this up. It sounded actually a little bit strange to me that this should be related to BitLocker. We have a lot of Win 7 Pro installations - BitLocker is not part of Win 7 Pro; it is an exclusive feature of W7 Enterprise or Ultimate - and many of them have had this failure resulting in a "up to 4 times" over and over rebooting process for Windows Update to revert the patch installation.

    But not all of our installations failed. There is a BitLocker Service and it can be started but it will shutdown immediately as there is no BitLocker components in W7 Pro. So I was wondering...

    Then I read arjan67's suggestion to solve this. Sounded more reasonable and I tested it. It works perfectly. Thx! :-)

    Thx also to CardPlayer who pointed out how to enable automount (CMD -> diskpart -> automount enable).


    Wednesday, October 15, 2014 3:57 PM
  • for me the automount enable doesn't work, still getting 80004005 (and reverting on boot)
    Wednesday, October 15, 2014 4:01 PM
  • for me the automount enable doesn't work, still getting 80004005 (and reverting on boot)

    Same here, tried the automount "trick" with no success.

    Also, I do have the referenced reg entry and checking with "sc query fvevol" it's running.

    The error code on Event Viewer is different: 0x800f0816

    C:\Users\user>sc query fvevol

    NOME_SERVIÇO     : fvevol
            TIPO               : 1  KERNEL_DRIVER
            ESTADO             : 4  RUNNING
                                    (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
            WIN32_EXIT_CODE    : 0  (0x0)
            SERVICE_EXIT_CODE  : 0  (0x0)
            CHECKPOINT         : 0x0
            WAIT_HINT          : 0x0

    C:\Users\user>

    It might have something to do with, in my case, running the system with AMD RAID Driver? Will try and use AHCI.

    :edit

    Same when on AHCI mode.

    :edit2

    Reverted to RAID mode, performed a clean boot and disabled all not needed drivers with Autoruns, ESET drivers included, and tried the update.

    After reboot it failed and auto-repair/recovery was launched.

    On auto-repair it states that the ahcix64s driver (c:\windows\system32\drivers\ahcix64s.sys) is corrupted and a system restore is performed.

    • Edited by s0x Wednesday, October 15, 2014 5:36 PM
    Wednesday, October 15, 2014 4:18 PM
  • Start -> find Diskpart -> run Diskpart.exe -> type 'automount enable' on the command line that comes up.

    This worked for me. The symptom that I was seeing was that the install was failing at different percentages of the process. Most often at 77%, but sometimes at 81% or 85%.

    The error message I was getting when KB2949927 failed to update was the 0x80004005 unspecified error.

    Something was turning off or not remaining accessible. Bitlocker service turns itself off if it's not being used actively to encrypt/decrypt. 

    Or, as was the case with me, one of the disk volumes was being unmounted immediately after it wasn't needed anymore.

    Thank you for pointing me to that solution, Arjan67



    • Edited by Tarek Okail Wednesday, October 15, 2014 6:22 PM
    Wednesday, October 15, 2014 6:19 PM
  • I had the same issue on Windows 7 Home Premium 64 Bit.

    Then I downloaded it seperately and got the meassage- your system does not need this.

    So I just hid the update

    Wednesday, October 15, 2014 6:37 PM
  • So if I have Windows 7 Home Premium 64-bit installed then I shouldn't have BitLocker anyway. Isn't it only available in the Professional version and above?

    If that's the case then why is Win7 HP even trying to install this update?!
    • Edited by Ronald Waid Wednesday, October 15, 2014 8:49 PM
    Wednesday, October 15, 2014 8:47 PM
  • The update is not Bitlocker specific. Bitlocker does use encryption, and the update is to migrate from an older form of encryption to a newer one (SHA-1 to SHA-2). But it affects more than just Bitlocker.
    • Edited by Tarek Okail Wednesday, October 15, 2014 10:35 PM
    Wednesday, October 15, 2014 10:34 PM
  • I tried diskpart automount and fvevol, patch still rollback.

    I have installed grub on MBR and boot flag was set on Linux partition. 

    I fix my problem by setting boot flag to windows partition with windows boot files. Hope this can help Linux users.

    • Proposed as answer by FeRDNYC Thursday, October 16, 2014 5:57 AM
    • Marked as answer by Yolanda ZhuModerator Wednesday, November 5, 2014 10:03 AM
    Thursday, October 16, 2014 4:59 AM
  • I had the same situation as 柳局南段 (dual-booting Windows/Linux installation managed by Grub 2), and the same solution worked:

    1. Went into Disk Management
    2. Right-clicked the Windows 7 partition and chose "Mark Partition as Active"
    3. Allowed Windows to reboot and complete the installation (successfully)

    Then I just switched Active back to my Linux /boot partiton when Windows came back up.

    • Proposed as answer by c_w_t_ Thursday, October 16, 2014 7:00 AM
    • Marked as answer by Yolanda ZhuModerator Wednesday, November 5, 2014 10:03 AM
    Thursday, October 16, 2014 5:59 AM
  • Same issue here and the cmd -> diskspart.exe -> automount enable took care of it for me too. 
    Thursday, October 16, 2014 12:19 PM
  • Hi, I have this same problem with ahcix64s.sys reported as corrupt. How can I fix it? The computer won't boot.
    Thursday, October 16, 2014 12:28 PM
  • A bit of extra info.

    If rdyboost is disabled due to using a SSD this update can still fail.

    Thursday, October 16, 2014 1:04 PM
  • Tried all the suggestions mentioned above but still not able to install the patch :(

    I'm seeing an error in the event log

    The Cryptographic Services service failed to initialize the Catalog Database. The ESENT error was: -1305.

    I looked it up on the net and found a few suggestions and tried them still not able to install the patch.

    Can someone give some direction on how to resolve this?

    Thank you very much in advance.

    Thursday, October 16, 2014 3:19 PM
  • In Brazil at our company 3 notebooks had to be recovered using cdrom boot after applying this patch. They stopped to boot.
    Thursday, October 16, 2014 4:11 PM
  • If you're stuck at the recovery screen with repairs failing, here's what worked for me. From the Recovery Console command prompt: dism.exe /image:C:\ /cleanup-image /revertpendingactions
    Thursday, October 16, 2014 6:08 PM
  • Thanks for the hint!

    I am dual booting Linux and Windows as well, but from separate disks.

    Circumvented the grub boot manager by selecting a disk from the native boot menu of my ThinkPad (hitting F12) and all went well.

    Thursday, October 16, 2014 8:32 PM
  • Microsoft is intentionally botching updates so people will be driven to Win8/10.

    Friday, October 17, 2014 3:24 AM
  • I had the same issue on Windows 7 Home Premium 64 Bit.

    Then I downloaded it seperately and got the meassage- your system does not need this.

    So I just hid the update

    Multiple attempts earlier this week to install Oct2014 KB2949927 update failed and reverted KB2949927 on my Win7 Pro x64 desktop (see my earlier post in this thread).  On Wed 10/15 a Microsoft Level 1 tech also attempted to install it manually from a stand-alone download, which reported it is not applicable to my system.  Yesterday 10/16 Windows Update was still prompting me to install KB2949927 (I didn't attempt to install it yesterday, since I'm awaiting a callback from a Level 2 Tech).

    However, today (10/17/2014) Windows Update does NOT prompt to install when I run Windows Update > Check for Updates.  So apparently Microsoft has changed something in the Update check so it no longer prompts for this update (that is consistent with the "Not needed" result on Wed.).


    Asus P5N32-E SLI mobo, C2D E8400 @3GHz, 4x 1GB PC2-8500 OCZ DDR2, Asus GTX580/1536MB, Win7 Pro SP1 x64

    Friday, October 17, 2014 3:10 PM
  • I tried that but I get an error 3 where it cant access the c:

    it seems i'm stuck in x: and the c: does not exist or is locked somehow

    I have no idea what to do.

    Friday, October 17, 2014 7:15 PM
  • KB2949927 has been pulled on Friday, the 17th, without any comment from MS. :-)

    http://windowsitpro.com/security/kb2949927-may-have-been-pulled

    Many news regarding this patch now expalin the failing Update is due to not running BitLocker service. It must be pointed that this is not correct. The fact that the patch is being installed without any problems if BitLocker service is running, does not mean that the patch fails if BitLocker service is not running; misleading to the claim or thesis that BitLocker sevice is needed for installing this patch. This is a wrong "converse argument". :-)

    Example from our site:
    Before we were able to unapprove KB2949927, it has been rolled out to about 70 of our Windows 7 Pro machines. Win 7 Pro does not have BitLocker as it is a feature of Win 7 Enterprise or Utimate. Though 10% of these machines running Win 7 Pro did not have any problem when installing KB2949927 - of course no BitLocker service running. All of the other 90% have been able to install the Patch after enabling automount in diskpart. Just a remark: automount will be automatically disabled again after reboot.

    So the cause for KB2949927 not being installed has some other roots - missing system partition at install time - which obviously is not being a problem when BitLocker service is running (on Win7 Enterprise or Ultimate).

    Some users reports also point to a "re-boot loop" condition or no-boot condition after failed KB2949927 installation. I am not sure if this really applies. What I know from our experinece is that in all 90% cases (~60 machines) reverting the installation of KB2949927, it took about 3 to 4 reboots in a row which took up to 10 minutes, before reverting and uninstalling of KB2949927 had been completed. So impatience might also be one of the causes for a "re-boot loop" or no-boot condition... ;-)




    • Edited by Mamu20 Monday, October 20, 2014 10:10 AM
    Monday, October 20, 2014 9:43 AM
  • Also happens, if the parttion "bootmgr" is stored on, has no drive letter.

    It is possible to fix this by using diskpart and the "automount enable" and "assign" commands for the partition.

    Monday, October 20, 2014 6:32 PM
  • Hi, I have this same problem with ahcix64s.sys reported as corrupt. How can I fix it? The computer won't boot.

    Hopefully you've found a solution by now, but just in case...

    1. Boot to Windows installation media.

    2. Choose your preferred language and click Next.

    3. Choose the Repair your computer option.

    4. In System Recovery Options, click Command Prompt.

    5. At the command prompt, enter: dism /image:C:\ /cleanup-image /revertpendingactions (where C: is the drive letter for your Windows installation; in the recovery environment, the drive letter may well be something other than C:)

    6. Reboot. Pending updates should be backed out and Windows should boot normally.

    I'm assuming the error message said something about Windows not being able to verify the digital signature for ahcix64s.sys? The file likely is not corrupt and the problem is likely due to changes (by KB 2949927) in the way Windows attempts to verify signed drivers.


    -- Ron




    Monday, October 20, 2014 10:45 PM