none
Update KB3033929 fails with error code 80004005

    Question

  • Security Update for Windows 7 for x64-based Systems (KB3033929)

    Installation date: ‎3/‎11/‎2015 8:57 AM

    Installation status: Failed

    Error details: Code 80004005

    Update type: Important

    A security update. . .

    I can't find any info on this error.  Tried the update twice and both times it failed.

    Wednesday, March 11, 2015 1:42 PM

Answers

  • You may want to try the following:

    1) Running the following FIX-it (for resolving WUS issues)
      LINK:  ~http://support.microsoft.com/en-us/kb/971058 

    2) Then change windows update to "manual" update mode (as aposed to install updates automatically)

    3) Scan for updates

    4) Uncheck and then "hide" KB KB3033929

    The update should no longer download or install going forward.  You can then revert the WUS to “automatic” if you desire (recommended).  Perhaps MS will FIX and re-release this in the future.  At that point you could choose to “unhide” the patch and then  try to reinstall it at that time.

    • Proposed as answer by LarisaKud Tuesday, March 17, 2015 8:27 PM
    • Marked as answer by Cloud_TSModerator Tuesday, March 31, 2015 7:14 AM
    Tuesday, March 17, 2015 7:31 PM

All replies

  • Failed for me too on a Dell Optiplex 790 with Windows 7 Pro SP1 64-bit.
    Wednesday, March 11, 2015 3:32 PM
  • Failed on my wife's Dell Inspiron as well. Tried about 6 different times yesterday.

    Wednesday, March 11, 2015 5:33 PM
  • Failing on all computers in my house. Had Microsoft support try and fix it via  remote desktop with no luck.

    Security Update for Windows 7 for x64-based Systems (KB3033929)

    Installation date: ‎12/‎03/‎2015 4:29 AM

    Installation status: Failed

    Error details: Code 800B0100

    Then I have two more that fail.

    Security Update for Windows 7 for x64-based Systems (KB3035131)

    Security Update for Windows 7 for x64-based Systems (KB3046049)


    • Proposed as answer by clintcom Wednesday, March 11, 2015 5:43 PM
    • Unproposed as answer by clintcom Wednesday, March 11, 2015 5:43 PM
    Wednesday, March 11, 2015 5:42 PM
  • Same problem with my pc with Win7 32bit with kb3033929

    I also have a problem in my second PC with Win7 64bit with 3 update:

    KB3046049

    KB3036493

    KB3033889

    Wednesday, March 11, 2015 6:05 PM
  • Download and install the standalone file: Security Update for Windows 7 for x64-based Systems (KB3033929)

    Carey Frisch

    Wednesday, March 11, 2015 6:08 PM
    Moderator
  • Same problem with my pc with Win7 32bit with kb3033929

    I also have a problem in my second PC with Win7 64bit with 3 update:

    KB3046049

    KB3036493

    KB3033889

    Download and install:


    Carey Frisch

    Wednesday, March 11, 2015 6:13 PM
    Moderator
  • I tried downloading & installing kb3033929 manually on my wife's Dell Inspiron Window 7 Home Premium PC.

    Still no-go. I threatened to install Linux Mint 17 right over the Windows OS. Still a no go on that one too!

    Wednesday, March 11, 2015 6:23 PM
  • Two out of 5 Windows 7 computers in my house have the problem where KB3033929 fails to install... The other, supposedly linked update, 3035131 was successful on all computers.

    All of the computers are running 64-bit version of Windows, all have at least 4 GB of memory, all have plenty of disk space.

    One of the computers that failed to install the update is running Windows 7 Professional, the other is running Windows 7 Home (I think, it's a laptop I don't have with me right now).

    The process is the same every time:

    - downloads and installs the update
    - requests a restart
    - before shutting down and restarting, it 'Configures Windows' for a while
    - after restart, it is 'Preparing to configure Windows', gets to about 72%, reports 'Failure configuring Windows update. Reverting changes'
    - restarts automatically
    - 'prepares to configure Windows' once again, shows the 'Failure configuring Windows update. Reverting changes' once again
    - shows the login screen

    After that, I can try again and all of that will happen again - even if I try it with the 'standalone' file...

    Out of the other 3 computers that did install the update, two are running Windows 7 Professional, the last one is running Windows 7 Ultimate...

    Wednesday, March 11, 2015 6:32 PM
  • I also have same issue on few PCs in work.

    HP Compaq Elite 8200, 16GB RAM, Win 7 Professional 64b SP1. Same process as Danilo Godec described.

    Wednesday, March 11, 2015 6:58 PM
  • Same process as Danilo Godec.

    I tried to manually intall with the link of Carey Frisch, it didn't work.

    I'm always stuck on 72%.


    • Edited by melinobio Wednesday, March 11, 2015 7:03 PM
    Wednesday, March 11, 2015 7:00 PM
  • 1. Open a Command Prompt (Run as Administrator).

    2. Type: cd %windir% and press enter.

    3. Type: net stop wuauserv and press enter.

    4. Type: ren softewaredistribution softwaredistribution.old and press enter.

    5. Type: net start wuauserv and press enter.

    6. Type: Exit and press enter.

    7. Try installing the updates once again.


    Carey Frisch

    • Proposed as answer by Little.Lynx Monday, June 27, 2016 12:06 PM
    Wednesday, March 11, 2015 8:05 PM
    Moderator
  • Has this worked for anyone?
    Wednesday, March 11, 2015 8:52 PM
  • In short - it hasn't worked for me.

    After renaming that directory, Windows Update took a long time to search for updates and it came up with three:

    • KB3033929
    • KB3021952
    • KB3032359

    Again, in first stage the two 'new' updates were installed successfully, while KB3033929 was in 'pending' state and required a reboot.

    After that, it was the same story as before - reboot, 'preparing to configure Windows', fail at 72%, revert changes, reboot, ...

    Also worth mentioning is that renaming the %windir%\SofwareDistribution directory also removes all previous 'update history'.

    Wednesday, March 11, 2015 9:13 PM
  • 1. Open a Command Prompt (Run as Administrator).

    2. Type: cd %windir% and press enter.

    3. Type: net stop wuauserv and press enter.

    4. Type: ren softewaredistribution softwaredistribution.old and press enter.

    5. Type: net start wuauserv and press enter.

    6. Type: Exit and press enter.

    7. Try installing the updates once again.


    Carey Frisch

    I just tried this technic (modifying step 4 softwaredistribution instead of softEwaredistribution) but it didn't work.

    Still stuck.

    Wednesday, March 11, 2015 9:27 PM
  • I had the same problem I even loged in as admin, and did the update through windows update and then the standalone package.
    Wednesday, March 11, 2015 9:38 PM
  • Did not work for me either.

    Guess we will have to wait till Microsoft pushes out a fix for the defective update.

    Wednesday, March 11, 2015 9:40 PM
  • Tried as admin also it has no effect.  This is effecting a laptop and two desktops on Windows 7.

    Security Update for Windows 7 for x64-based Systems (KB3033929)Is causing an infinite loop on one of the machines and the desktop in unreachable completely.

    The other two are able to back out of it and revert to a previous state.  None can install the update.

    KB3033929 should never have gone live in its current state and the vulnerabilities it addresses are critical.

    Lets try to get this story to some of the blogs like Krebs, etc. -- It is absolutely unacceptable for MS to ignore this and the only way anything ever really gets done in a timely manner seems to be if a media outlet picks it up.  This is a MS problem not an administrator or user problem.

    Wednesday, March 11, 2015 9:47 PM
  • I believe this is a bad update from Microsoft. I have a VERY bare bones Windows 7 Home Premium 64 bit install that attempted to install this update automatically and it failed. Now it repeatedly tries to install it and it fails every time. It reverts back, every time.

    I went through every troubleshooting suggestion from Microsoft to no avail.

    I have seen multiple errors in the event viewer regarding this, however this particular one appears most commonly. Also received a 80070002 on it.

    For the moment I have hidden the update to stop the endless failures.


    Wednesday, March 11, 2015 10:52 PM
  • I spent 12 hours trying to firgure this sh*t out.here is the solution fopr you guys, basically for some reason ONE single file gives access denied because system and trustedinstaller got no permission to access it.

    1. Try to install it via windows update.

    2. Open CBS.log (C:\Windows\Logs\CBS)

    3. CTRL + F, search for: "Error", for me it was:

    [code]2015-03-12 01:36:50, Error                 CSI    0000001c (F) STATUS_ACCESS_DENIED #792431# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowFileNotFound), handle = {provider=NULL, handle=0}, da = (FILE_GENERIC_READ), oa = @0x140dc48->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[133]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.18741_none_b9293c0383618646\winresume.exe"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x140dee0, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT), eab = NULL, eal = 0, disp = Invalid)
    [gle=0xd0000022]
    2015-03-12 01:36:50, Error                 CSI    0000001d@2015/3/12:00:36:50.643 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_ACCESS_DENIED originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
    [gle=0x80004005]
    2015-03-12 01:36:51, Error                 CSI    0000001e (F) STATUS_ACCESS_DENIED #792430# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::TransferFile(flags = (ReplaceIfExists|MissingFileIsOk), op = [4]"Copy", odir = NULL, oname = [l:266{133}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.18741_none_b9293c0383618646\winresume.exe", ndir = NULL, nname = [l:298{149}]"\SystemRoot\WinSxS\Backup\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.18741_none_b9293c0383618646_winresume.exe_85cd1215", disp = (null))
    [gle=0xd0000022]
    2015-03-12 01:36:51, Error                 CSI    0000001f (F) STATUS_ACCESS_DENIED #787751# from PrimitiveInstaller::CCoordinator::FinalizeChanges(...)[gle=0xd0000022][/code]

    4. Open directory where is the file mentioned in the error, in my case: "C:\Windows\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.18741_none_b9293c0383618646\winresume.exe"

    5. Right Click on the file > Properties > Security > Advanced > Owner > (Set it to your Account) > OK

    6. In previous Window: Edit > Add

    7. You need to add two accounts

    - "SYSTEM"

    - "NT SERVICE\TrustedInstaller"

    8. Give them both Read, Write, Execute permissions. > OK

    9. Now KB3033929 which is one big nightmare should install without any problems and ask you to restart your computer afterwards.

    Failure was possibly caused by Customized Boot Loader.



    Thursday, March 12, 2015 1:23 AM
  •  Microsoft support did all those thing's Carey posted and nothing worked, they have Tier 2 Tec's calling me in 2 day's , must be bad. I've got to hide it aswell , keeps downloading over and over.


    • Edited by clintcom Thursday, March 12, 2015 1:52 AM
    Thursday, March 12, 2015 1:52 AM
  • Strange, but the word 'error' doesn't appear in my log.

    I do have this though:

    2015-03-11 21:34:37, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
    2015-03-11 21:34:37, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
    2015-03-11 21:34:37, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
    2015-03-11 21:34:37, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]

    Thursday, March 12, 2015 3:34 AM
  • This can be misleading, I got many operations with failed status as well. Try to look for word "Rollback" in your CBS.log, and look above this word. Or upload your log, maybe I or someone else here will be able to help you. And yes, I am sorry, my error was: 80070005 which basically means acess denied. Yours is a little bit different.

    It looks like SQL permissions problem? It would actually be nice if somebody from microsoft post something useful.

    /edit I just checked, I got the same failure in my log ...even when my update was installed successfully.

    Seriously post your log.




    • Edited by rvnlord Thursday, March 12, 2015 3:59 AM
    Thursday, March 12, 2015 3:48 AM
  • Thanks for direction, rvnlord.

    I have same trouble with this KB, but neither refreshing premissions on \WinSxS\... nor sfc /scannow have no effect.

    Nevertheless, I found root of my problem, here is cbs.log, lasting after installing right after reboot, probably helps to others.

    2015-03-12 12:29:41, Info                  CSI    00000039 Begin executing advanced installer phase 38 (0x00000026) index 21 (0x0000000000000015) (sequence 60)
        Old component: [ml:356{178},l:354{177}]"Microsoft-Windows-BootEnvironment-Core-MemoryDiagnostic, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS"
        New component: [ml:356{178},l:354{177}]"Microsoft-Windows-BootEnvironment-Core-MemoryDiagnostic, Culture=neutral, Version=6.1.7601.18741, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS"
        Install mode: install
        Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}
        Installer name: [15]"Generic Command"
    2015-03-12 12:29:41, Info                  CSI    0000003a Performing 1 operations; 1 are not lock/unlock and follow:
      LockComponentPath (10): flags: 0 comp: {l:16 b:e3c3e1af9e5cd001190000004805d405} pathid: {l:16 b:e3c3e1af9e5cd0011a0000004805d405} path: [l:234{117}]"\SystemRoot\WinSxS\x86_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_6.1.7601.17514_none_da3cb85562df73c9" pid: 548 starttime: 130706225598920499 (0x01d05c9ea2c17733)
    2015-03-12 12:29:41, Info                  CSI    0000003b Performing 1 operations; 1 are not lock/unlock and follow:
      LockComponentPath (10): flags: 0 comp: {l:16 b:0412e2af9e5cd0011b0000004805d405} pathid: {l:16 b:0412e2af9e5cd0011c0000004805d405} path: [l:234{117}]"\SystemRoot\WinSxS\x86_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_6.1.7601.18741_none_da1934b762fa8f86" pid: 548 starttime: 130706225598920499 (0x01d05c9ea2c17733)
    2015-03-12 12:29:41, Info                  CSI    0000003c Calling generic command executable (sequence 1): [20]"C:\Windows\bfsvc.exe"
        CmdLine: [47]""C:\Windows\bfsvc.exe" C:\Windows\boot /nofonts"
    2015-03-12 12:29:42, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Percent progress: 74.
    2015-03-12 12:29:42, Info                  CSI    0000003d Performing 1 operations; 1 are not lock/unlock and follow:
      LockComponentPath (10): flags: 0 comp: {l:16 b:0afd78b09e5cd0011d0000004805d405} pathid: {l:16 b:0afd78b09e5cd0011e0000004805d405} path: [l:234{117}]"\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_6.1.7600.16385_none_3868158f24725705" pid: 548 starttime: 130706225598920499 (0x01d05c9ea2c17733)
    2015-03-12 12:29:42, Info                  CSI    0000003e Creating NT transaction (seq 1), objectname [6]"(null)"
    2015-03-12 12:29:42, Info                  CSI    0000003f Created NT transaction (seq 1) result 0x00000000, handle @0x23c
    2015-03-12 12:29:43, Info                  CSI    00000040@2015/3/12:08:29:43.143 CSI perf trace:
    CSIPERF:TXCOMMIT;60202
    2015-03-12 12:29:43, Error      [0x018009] CSI    00000041 (F) Done with generic command 1; CreateProcess returned 0, CPAW returned S_OK
        Process exit code 15299 (0x00003bc3) resulted in success? FALSE
        Process output: [l:60 [60]"BFSVC: Failed to get system partition! Last Error = 0x3bc3
    "][gle=0x80004005]
    

    My hard disk configuration have no active partitions. Boot- and Windows-partitons is inactive, because I use external bootloader (for security reasons). As soon as I set (fake, old) boot partition as active, KB3033929 was applied succesfully.

    Thursday, March 12, 2015 9:28 AM
  • Had the same problem. Windows 7 64-bit.
    I tried a couple of times both via windows update and the standalone installer. But always ended up with'Failure configuring Windows update. Reverting changes' and a reboot after that.

    But I found a fix for my problem.

    To start with, I have more than one OS on my computer so I can dualboot. And therefore a custom bootloader. So what I did was to unplug the other harddrive(s), and only boot the one with windows 7. And after booting up I ran the standalone installer 
    (KB3033929) which I previously had downloaded. Update went fine, windows rebooted without a problem. Finished 100%. Last thing I did was connect my other harddrives again.

    So the problem for me was the custom bootloader.
    Hope this helps.



    • Edited by Rawness Thursday, March 12, 2015 11:53 AM
    • Proposed as answer by MPCaseJr Thursday, March 12, 2015 3:35 PM
    Thursday, March 12, 2015 11:14 AM
  • Win7 x64. Failed for me too. And the PC could not boot anymore. I was using grub as a bootmanager and after this or one of the updates at the same time I had to reinstall the boot manager from scratch. 

    Thursday, March 12, 2015 11:17 AM
  • My log is about 9M, so here's a dropbox link to it.

    https://dl.dropboxusercontent.com/u/180172/CBS.log

    And the PC with the problem isn't using any sort of special boot loader.

    Thursday, March 12, 2015 1:23 PM
  • I'll check your log when I come back from the university (or sb more clever can do it before me).

    By the way, for everyone who will come here with similar problem, beware: If it is caused by custom bootloader and you use sfc /scannow, your computer might not boot at all! In such case simply take 'winload.exe' from 'system32\Boot' and put it in 'system32' replacing the files (it requires taking ownership of the files). This will require you to indeed as @ZitroneHolunder mentioned reinstallation of your custom bootloader.

    /edit

    Kiran Otter

    Are you sure, this is log from installation?

    Because I got exact same log almost every time I start my machine (which REPLACED logs from installation). Please open Windows Update and try update again, and then post generated log.

    • Edited by rvnlord Thursday, March 12, 2015 2:26 PM
    Thursday, March 12, 2015 2:15 PM
  • In case this wasn't mentioned the patched listed in MS15-025 are a perquisite for this update.

    On a Win 7x64 system try installing this update first : https://www.microsoft.com/en-us/download/details.aspx?id=46009

    Thursday, March 12, 2015 3:12 PM
  • Ah yes, the "Windows don't like Linux" issue again. Seen this before and will probably see it again. All my dual boot Windows/Linux systems failed this update. Setting the Windows system partition to boot (by first booting Knoppix), then rebooting directly to Windows, apply updates, reboot to Windows to finish the update and all is well. Just need to go back and set the grub partition to boot once again by booting Knoppix DVD and running gparted.
    Thursday, March 12, 2015 3:17 PM
  • Right, both computers that failed installing the update ARE dual-boot with GRUB, the other three are Windows 7 only...

    Thursday, March 12, 2015 3:25 PM
  • I had one dual boot update without a problem.  The other needed the Linux drive unplugged so it would boot directly to Windows and then I was able to apply KB3033929.  Thanks to Rawness above.

    Linux drive is back in and I'm back to booting Windows via Grub2.

    Thursday, March 12, 2015 3:33 PM
  • Both of my Dual-Boot machines w/Grub & Linux Mint updated just fine. It is my wife's laptop with just Windows 7 Home Premium that won't take the update.

    Thursday, March 12, 2015 4:35 PM
  • I had the same error, also in a dual boot scenario (Grub on first disk, Windows on second disk)

    This caused the PC three times to

    i) boot into windows, install updates

    ii) reboot automatically, detecting error, undoing patch installation

    iii) reboot automatically, informing me that patch installation failed

    After iii) I could use the PC, but the next time I started it the same sequence came up again.

    My mainboard allows selecting the disk to boot from during boot. I used that to boot directly from the Windows disk and manually installed KB3033929 which now worked without any issues. Rebooted once directly from that disk to be on the safe side and now switched back to booting from the first disc using Grub. Works fine now.

    Thursday, March 12, 2015 5:25 PM
  • I disabled GRUB2, so that Windows loaded automatically and now the update succeeded...

    I'm not 100% sure all of these steps are necessary, but here's what I've done:

    • boot Linux and set the 'active' flag for Windows partition (at that point I left the 'active' flag on my Linux partition as well)
    • GRUB2 menu still loaded first
    • boot Windows in 'Repair your computer mode' and run 'bootrec /fixmbr'
    • GRUB2 menu still loaded first, but I tried to boot Windows to install the update, but it failed in exactly the same way as before
    • boot Linux again and turn the 'active' flag on the Linux partition off
    • now Windows boot's directly without GRUB menu
    • KB3033929 update installs successfully

    After that I booted Linux from a CD drive, changed the active flag back to Linux boot partition and I got my dual-boot back.

    Thursday, March 12, 2015 6:10 PM
  • Try but don't work
    Thursday, March 12, 2015 6:16 PM
  • Also failing for me...dual boot Win7 x64 and OpenSuse 13.1.  Boots loops and evetually backs out, but no way to apply the patch.  "Breaking" grub2 temporarily sounds like a big hassle.  I guess I'll wait to see if MS fixes this for multi-boot systems.

    Thursday, March 12, 2015 9:27 PM
  • I have a dual-boot setup with Windows 7 and Xubuntu 14.04, but I've actually managed to figure out how to install  KB3033929.

    I have a bit of a strange setup, as I have Windows installed on one physical drive, and Xubuntu on the other. I use the Xubuntu drive, and its GRUB2 bootloader, as my main boot drive and bootloader, but I also have the normal Windows 7 BCD bootloader installed on my Windows 7 drive. This means that I can bypass GRUB2 and boot directly into my Windows 7 install just by unplugging the Xubuntu drive, or selecting it in my BIOS's boot menu.

    To install the update, what I did was go into my BIOS and temporarily disable my Xubuntu drive, just to make sure, then I booted into my Windows drive and installed the update. It worked!

    Now, for others who have a Windows/Linux dual-boot setup, but don't have both bootloaders installed, what you could do is overwrite GRUB2 using EasyBCD or a stock Windows 7 install disc, then use EasyBCD to add an entry for your Linux install. Do NOT uninstall GRUB2 from within Linux however; you still need to have part of it, just not the part that sits where BCD would normally sit. I haven't tried installing the update on this type of setup, but this is the method I use for dual-booting on my laptop, which only has one hard drive.

    If you're not running a dual-boot setup and you're encountering problems installing KB3033929, then it may be due to a manufacturer-installed recovery partition, though this is only a theory of mine. I'd suggest waiting for a newer version of the update, as it may do more harm than good if you try anything else.

    Friday, March 13, 2015 12:11 AM
  • Stopping wuauserv, renaming softwaredistribution, and restarting wuauserv did not work for me. Nor can I find the relevant entries in windows\logs\CBS\CBS.log.

    I do have dual boot installed, using grub with Linux 12. But I have no idea how to turn off grub and boot directly into Windows.

    Friday, March 13, 2015 12:49 AM
  • has anyone tried to physically disconnect the Linux hard drive? I am thinking about doing that
    Friday, March 13, 2015 3:53 AM
  • I disabled GRUB2, so that Windows loaded automatically and now the update succeeded...

    I'm not 100% sure all of these steps are necessary, but here's what I've done:

    • boot Linux and set the 'active' flag for Windows partition (at that point I left the 'active' flag on my Linux partition as well)
    • GRUB2 menu still loaded first
    • boot Windows in 'Repair your computer mode' and run 'bootrec /fixmbr'
    • GRUB2 menu still loaded first, but I tried to boot Windows to install the update, but it failed in exactly the same way as before
    • boot Linux again and turn the 'active' flag on the Linux partition off
    • now Windows boot's directly without GRUB menu
    • KB3033929 update installs successfully

    After that I booted Linux from a CD drive, changed the active flag back to Linux boot partition and I got my dual-boot back.

    This same procedure also worked on my other problematic PC - all I had to do is toggle the 'bootable' flag on the Windows partition (C: drive) and Windows booted directly...

    After the update installed successfully, I just turned the bootable flag back off and it was back to GRUB boot.

    Of course this may not work exactly like that for everyone, as they might have a different partition layout, different GRUB setup, etc. ...

    Friday, March 13, 2015 12:53 PM
  • OK, I ran it again.. and I think this is the relevant part of the +200M log.  It does seem to have something to do with the boot manager or knowing which drive is the 'globalroot', perhaps.

    2015-03-13 08:33:13, Info                  CSI    0000003d Begin executing advanced installer phase 38 (0x00000026) index 16 (0x0000000000000010) (sequence 55)
        Old component: [ml:360{180},l:358{179}]"Microsoft-Windows-BootEnvironment-Core-MemoryDiagnostic, Culture=neutral, Version=6.1.7601.18741, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
        New component: [ml:360{180},l:358{179}]"Microsoft-Windows-BootEnvironment-Core-MemoryDiagnostic, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
        Install mode: install
        Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}
        Installer name: [15]"Generic Command"
    2015-03-13 08:33:13, Info                  CSI    0000003e Performing 1 operations; 1 are not lock/unlock and follow:
      LockComponentPath (10): flags: 0 comp: {l:16 b:9c8942df895dd0011800000074043c05} pathid: {l:16 b:9c8942df895dd0011900000074043c05} path: [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_6.1.7601.18741_none_3637d03b1b5800bc" pid: 474 starttime: 130707235496916126 (0x01d05d89c55df49e)
    2015-03-13 08:33:13, Info                  CSI    0000003f Performing 1 operations; 1 are not lock/unlock and follow:
      LockComponentPath (10): flags: 0 comp: {l:16 b:9c8942df895dd0011a00000074043c05} pathid: {l:16 b:9c8942df895dd0011b00000074043c05} path: [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_6.1.7601.17514_none_365b53d91b3ce4ff" pid: 474 starttime: 130707235496916126 (0x01d05d89c55df49e)
    2015-03-13 08:33:13, Info                  CSI    00000040 Calling generic command executable (sequence 3): [20]"C:\Windows\bfsvc.exe"
        CmdLine: [47]""C:\Windows\bfsvc.exe" C:\Windows\boot /nofonts"
    2015-03-13 08:33:45, Error      [0x018009] CSI    00000041 (F) Done with generic command 3; CreateProcess returned 0, CPAW returned S_OK
        Process exit code 112 (0x00000070) resulted in success? FALSE
        Process output: [l:8995 [4096]"BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 1 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 2 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 3 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 4 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 5 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 6 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 7 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 8 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 9 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 10 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 11 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 12 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\Harddis[gle=0x80004005]
    2015-03-13 08:33:45, Error      [0x018009] CSI    kVolume1\Boot\bootmgr) failed! (Attempt 13 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 14 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 15 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 16 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 17 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 18 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 19 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 20 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 21 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 22 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 23 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 24 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 25 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 26 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\[gle=0x80004005]
    2015-03-13 08:33:45, Error      [0x018009] CSI    bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 27 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed!"[4096]" (Attempt 28 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 29 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 30 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 31 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 32 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 33 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 34 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 35 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 36 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 37 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 38 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 39 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 40 of 60) Last Error = 0x[gle=0x80004005]
    2015-03-13 08:33:45, Error      [0x018009] CSI    70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 41 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 42 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 43 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 44 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 45 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 46 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 47 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 48 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 49 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 50 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 51 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 52 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 53 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) fail[gle=0x80004005]
    2015-03-13 08:33:45, Error      [0x018009] CSI    ed! (Attempt 54 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 55 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALR"[803]"OOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 56 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 57 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 58 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 59 of 60) Last Error = 0x70
    
    BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 60 of 60) Last Error = 0x70
    
    BFSVC: Error copying boot files from C:\Windows\boot\PCAT to \\?\GLOBALROOT\Device\HarddiskVolume1\Boot! Last Error = 0x70
    
    "][gle=0x80004005]
    2015-03-13 08:33:45, Info                  CSI    00000042 Calling generic command executable (sequence 4): [24]"C:\Windows\fveupdate.exe"
        CmdLine: [35]""C:\Windows\fveupdate.exe" /memtest"
    2015-03-13 08:33:45, Info                  CSI    00000043 Done with generic command 4; CreateProcess returned 0, CPAW returned S_OK
        Process exit code 0 resulted in success? TRUE
        Process output: [l:248 [248]"BitLockerUpdate: Running.
    
    BitLockerUpdate: Service request is for memtest.exe.
    
    BitLockerUpdate: BitLocker Drive Encryption is not turned ON on the OS volume.
    
    BitLockerUpdate: No servicing was performed on the OS volume.
    
    BitLockerUpdate: Done.
    Edit: One thing I've noticed on that PC, the 'system reserved' partition is only 25M, versus the usual 100M.  I might try to boot using the recovery console and see what happens.


    Friday, March 13, 2015 1:15 PM
  • After this weeks updates one of my laptops (Win7 Home) showed so many errors that it has become unusable. Error messages for missing files, no internet connection unless it is in Safe Mode. System recovery files erased or unreachable. Acronis rendered unusable due to antoher mysterious Error. Panda Av doesn't seem to work either. A complete mess...  
    Friday, March 13, 2015 2:22 PM
  • What I've also noticed, for whatever it's worth; On my PCs that didn't have a problem, they all have 3 optional updates, KB2574819, KB2592687 and KB2830477.  On the PC that does have the problem, these updates are not listed as optional, nor are they installed.
    Friday, March 13, 2015 3:09 PM
  • Update was successful on my end, Win 7 x64 SP1 Using Acer Aspire 57442Z. Windows update history showing successful.
    Friday, March 13, 2015 3:18 PM
  • It worked!

    If you have this problem, don't complicate yourself messing with GRUB, BIOS, installing other things, permissions, logs or editing files.

    Here's whath I did, just 3 steps:

    - Unplug the SATA cable of the Linux hard disk

    - Start Windows, install the update KB3033929, restart Windows. It installs succesfully.

    - Replug the SATA cable of the Linux hard disk

    That was it.

    Friday, March 13, 2015 3:47 PM
  • Try performing a clean boot: http://support.microsoft.com/en-us/kb/929135 . 
    Friday, March 13, 2015 5:05 PM
  • That's fine if your Linux install is on a separate drive, but on separate partitions on the same drive will not work.  In my case, one of my machines has Linux on a different drive, but the others are on the same drive.  Anyway, as long as it worked (which it didn't, in my case), simply changing the boot drive in BIOS would be much easier than opening the case, pulling the cable, and putting it all back together again.  In my case, since the grub file lives on the Linux drive, if I try to boot from the Win7 drive I just get a grub error and no boot.  I guess I'll try pulling the cable, but still inclined to see if MS comes up with a fix for this patch.

    • Edited by mxcrowe Friday, March 13, 2015 5:16 PM
    Friday, March 13, 2015 5:15 PM
  • Same thing for me. Happens on 2 Dell and a HP all with Win 7 Home Premium. Have tried a restore and install of just the one update and it fails. 

    After restart, it is 'Preparing to configure Windows', gets to about 72%, reports 'Failure configuring Windows update. Reverting changes'

    Friday, March 13, 2015 7:49 PM
  • In my case (dual boot PC with grub (linux and windows on same disk) to solve the problem with installation of this infamous KB i did the following.

    Under linux I installed the boot loader also on root partition.

    Then I removed the boot loader from the MBR of sda (my primary disk) using

    dd if=/dev/null of=/dev/sda bs=446 count=1

    using fdisk I switched the active partition from partition2 to partition3 (linux to windows)

    then I booted into windows, installed this infamous patch, rebooted the pc to complete installation. this time everything went ok and the installation finished troubleless.

    Rebooted the pc using hirens boot cd using the included partition tool I switched back the active partition from 3 to 2.

    Now the pc is patched and starts again in dual boot.

    I hope it helps someone else.


    Indeed it seem something related to dual boot. Thanks to the forum to have indicated me the root cause of the problem.
    Friday, March 13, 2015 8:06 PM
  • Does Windows intend to fix this, or what?

    Friday, March 13, 2015 10:38 PM
  • I have a dual boot with Linux. I installed the update and on reboot I opened the motherboard bios settings, switched the primary boot hard disk to my windows disk, rebooted and let it boot into windows. It finished installing without issues.
    Saturday, March 14, 2015 1:10 AM
  • Dual boot Windows 7/Linux with both OSes on same disk. GRUB 2 bootloader.

    Same problem, solved by deactiating Linux partition and activating Windows partition in fdisk from Knoppix. After reboot, update installed successfully. Removing GRUB from MBR was not needed. Deactivating Windows and activating Linux partition back again with fdisk restored dual-boot functionality.

    Saturday, March 14, 2015 9:42 AM
  • Great, so this is a dual boot issue. I'm dual booting too, Fedora and Windows 7. Two drives.

    I can't wait until I get rid of Windows once and for all. I only have one application left that I need to run. Just one. Release me from my suffering. Sigh.

    Sunday, March 15, 2015 3:53 AM
  • I have a similar setup with Windows 7 Pro on SATA0 and Fedora on SATA1. SATA0 is a vanilla Windows install, SATA1 is grub and dual boot. BIOS is normally pointed at SATA1, I experienced the KB3033929 failure as described by so many here.

    The good news is that the update installed without incident after changing the boot settings to use SATA0. Three other Win 7 Pro machines that are not dual boot (2 lappies, 1 desktop) had no trouble with this update.


    • Edited by MKEtoDFW Sunday, March 15, 2015 8:41 PM
    Sunday, March 15, 2015 8:38 PM
  • We have two laptops and one desktop that dual-boot openSUSE 13.1 and Windows 7, in all cases on a single drive. All boot with GRUB2 in the extended partition.

    One laptop is 64-bit and has both a 100 MB Windows system (sda1) partition, and a 50 GB Windows C drive (sda2). It runs Windows 7 Ultimate. On this machine, when I moved the boot flag from sda4 (the extended partition) to either sda1 or sda2, GRUB2 still ran. I put the boot flag on sda2 (C drive), selected Windows in GRUB2, and started it. KB3033929 then installed correctly; it had previously failed. For some reason on this machine, GRUB2 seems to not care where the boot flag is. It runs in all cases, and will start either operating system. Windows did care; it installed KB3033929 correctly only when the boot flag was on the C drive.

    The desktop and other laptop are both 32-bit machines, and do not have the small Windows system partition, only the C drive. On both of these I moved the boot flag from the extended partition to the C drive. Booting went straight to Windows, without GRUB2 running. On both machines, KB3033929 then installed correctly. It had previously failed on the desktop; I had not tried on the laptop. I switched the boot flags back to the extended partitions, and now GRUB2 runs again with correct dual-booting.

    I did all the flag changing by booting gparted-live-0.21.0-1-i586.iso written to a USB memory stick.

    Sunday, March 15, 2015 10:19 PM
  • After this weeks updates one of my laptops (Win7 Home) showed so many errors that it has become unusable. Error messages for missing files, no internet connection unless it is in Safe Mode. System recovery files erased or unreachable. Acronis rendered unusable due to antoher mysterious Error. Panda Av doesn't seem to work either. A complete mess...  

    @erveka,

    You are probably a victim of a bad update for Panda AV issued on Wednesday 03/11.  See information at Panda's website:

    http://www.pandasecurity.com/mediacenter/panda-security/information-regarding-issue-with-the-signature-file-pcop-retail-2015/

    Sunday, March 15, 2015 11:49 PM
  • Problem solved with Microsoft Tec 2 support. Windows 7 64 only

    He followed all the step's everywhere I have read and He could not fix the problem.

    He ended up deleting my SoftwareDistribution / .old Directories  and a couple of other windows folders (not Shaw which one's) and reinstalling Service pack 1 and then reinstalled windows updates all over again.

    Good if they can post this up, I would if I knew exactly how it was done 100% ;)

    Monday, March 16, 2015 6:01 AM
  • I was not able to find word "error" in my log.

    2015-03-16 01:38:30, Info                  CBS    Appl: SelfUpdate detect, component: x86_microsoft-windows-p..ng-spooler-splwow64_31bf3856ad364e35_6.1.7601.21921_none_ca2d8d9909622d19, elevation: 2, applicable: 0
    2015-03-16 01:38:30, Info                  CBS    Appl: Evaluating applicability block(non detectUpdate part), disposition is: Staged, applicability: NotApplicable, result applicability state: Staged
    2015-03-16 01:38:30, Info                  CBS    Appl: Package: Package_1_for_KB2647753~31bf3856ad364e35~amd64~~6.1.4.0, Update: Trigger_1, Applicable: NotApplicable, Dis
    2015-03-16 01:38:30, Info                  CBS    Failed to get session package state for package: Package_1_for_KB2647753~31bf3856ad364e35~amd64~~6.1.4.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

    Monday, March 16, 2015 9:03 AM
  • I also had this problem on a dual-boot system. I have two disk partitions, one for Linux and one for Windows 7. GRUB 2 is the boot loader.

    All I had to do was set the 'bootable' flag on the Windows 7 partition, and the update installed correctly on the next boot into Windows.

    The full procedure I followed was:

    1. Booted into Linux, and used a disk utility (palimpsest, which is just called "Disk Utility" in the Ubuntu system utilities menu) to set the 'bootable' flag on the Windows 7 partition.

    2. Rebooted. GRUB still worked correctly, so I selected "Windows 7" from my boot menu. This time, Windows finished installing the update successfully.

    3. Rebooted into Linux again and removed the 'bootable' flag on the Windows 7 partition. This step might not be necessary, but I wanted to put things back the way they were, just in case anything else was expecting only the Linux partition to be bootable.

    I can't guarantee this'll work with other people's systems and configurations, but I hope it helps someone. I'd recommend making a bootable Linux CD or USB stick, so that if your system refuses to boot you can reconfigure your disks back to the way they were.

    Monday, March 16, 2015 3:45 PM
  • I also had this problem on a dual-boot system. I have two disk partitions, one for Linux and one for Windows 7. GRUB 2 is the boot loader.

    All I had to do was set the 'bootable' flag on the Windows 7 partition, and the update installed correctly on the next boot into Windows.

    The full procedure I followed was:

    1. Booted into Linux, and used a disk utility (palimpsest, which is just called "Disk Utility" in the Ubuntu system utilities menu) to set the 'bootable' flag on the Windows 7 partition.

    2. Rebooted. GRUB still worked correctly, so I selected "Windows 7" from my boot menu. This time, Windows finished installing the update successfully.

    3. Rebooted into Linux again and removed the 'bootable' flag on the Windows 7 partition. This step might not be necessary, but I wanted to put things back the way they were, just in case anything else was expecting only the Linux partition to be bootable.

    I can't guarantee this'll work with other people's systems and configurations, but I hope it helps someone. I'd recommend making a bootable Linux CD or USB stick, so that if your system refuses to boot you can reconfigure your disks back to the way they were.

    It works for me 

    Tested on Ubuntu 15.04 with dualboot 

    Monday, March 16, 2015 5:32 PM
  • Some are reporting that the problem is related to systems with customized boot loaders and/or dual boot systems.  However, I ran into the problem on one of my PC's which is not a dual-boot system.  In my case, the problem was traced to a permissions issue involving a patch-related system folder. 

    I speculate that the patch installation failures are limited to systems where the previously released version of the patch had been applied.  Note that the October release was SO problematic that MS had to rescind the patch.  I suspect that the original patch created the folder with flawed permissions and was left behind in an altered state.  In such a case, the new version of the patch finds the existing (flawed) folder and therefore does not created it.  It also fails to insure that the folder permissions are in fact correctly set

    Normally, the permissions would be inherited when new folder is created and therefore should be correct by default. 

    RESOLUTION

    à         Boot PC in Safe mode

    à         Log in as Administrator (or an account with administrative privileges)

    à         Open file explorer and then open the following subfolder: “C:\Windows\WinSxS\”

    à         LOOK FOT THE FOLLOWING FILE: “C:\Windows\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.18741_none_b9293c0383618646\winresume.exe”

    à         Right Click on the file > Properties > Security > Advanced > Owner > (Set it to your Account or administrators) > OK

    à         In previous Properties-security Window: Edit > Add

    à         You need to add two accounts (if not already present)

    -          "SYSTEM"

    -          "NT SERVICE\TrustedInstaller"

    à         Give them both Read, Write, Execute permissions. >

    à         Click OK

    à         Run Windows update

    This should solve the issue but I have not tested it.  I resolved the issue in my case by taking a more brutish approach.

    Specifically, I booted in safe mode, manually cleared the updated cache, forcefully deleted the existing folder (and files) DEL: “C:\Windows\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.18741_none_b9293c0383618646”; ran MS Update;

    In my case, following these steps allowed the patch to install as expected.

    PS: you can verify if the failure is being caused by a permissions issue by examining the CBS.log (C:\Windows\Logs\CBS)

    • Proposed as answer by Art Barnwell Monday, March 16, 2015 8:42 PM
    • Unproposed as answer by Art Barnwell Tuesday, March 17, 2015 12:57 PM
    • Proposed as answer by _eithe Thursday, March 26, 2015 11:40 AM
    Monday, March 16, 2015 8:42 PM
  • Same problem with my pc with Win7 32bit with kb3033929

    I also have a problem in my second PC with Win7 64bit with 3 update:

    KB3046049

    KB3036493

    KB3033889

    Examine your CBS.log (C:\Windows\Logs\CBS).  Look for related errors and post these. I would speculate that the errant installation of KB3033929 is preventing the other patches from completing. 

    You could try manually clearing the updates cache; then check for updates and install all patches except for KB3033929.  Then try installing KB3033929 by following my previously posted resolution steps.

    In my situation, the system was a x64 bit OS (standard single boot OS config) and several patches also failed to install including KB3033929.  The “brutish” method allowed all patches to install as expected.


    Monday, March 16, 2015 9:00 PM
  • Some are reporting that the problem is related to systems with customized boot loaders and/or dual boot systems.  However, I ran into the problem on one of my PC's which is not a dual-boot system.  In my case, the problem was traced to a permissions issue involving a patch-related system folder. 

    I speculate that the patch installation failures are limited to systems where the previously released version of the patch had been applied.  Note that the October release was SO problematic that MS had to rescind the patch.  I suspect that the original patch created the folder with flawed permissions and was left behind in an altered state.  In such a case, the new version of the patch finds the existing (flawed) folder and therefore does not created it.  It also fails to insure that the folder permissions are in fact correctly set

    Normally, the permissions would be inherited when new folder is created and therefore should be correct by default. 

    RESOLUTION

    à         Boot PC in Safe mode

    à         Log in as Administrator (or an account with administrative privileges)

    à         Open file explorer and then open the following subfolder: “C:\Windows\WinSxS\”

    à         LOOK FOT THE FOLLOWING FILE: “C:\Windows\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.18741_none_b9293c0383618646\winresume.exe”

    à         Right Click on the file > Properties > Security > Advanced > Owner > (Set it to your Account or administrators) > OK

    à         In previous Properties-security Window: Edit > Add

    à         You need to add two accounts (if not already present)

    -          "SYSTEM"

    -          "NT SERVICE\TrustedInstaller"

    à         Give them both Read, Write, Execute permissions. >

    à         Click OK

    à         Run Windows update

    This should solve the issue but I have not tested it.  I resolved the issue in my case by taking a more brutish approach.

    Specifically, I booted in safe mode, manually cleared the updated cache, forcefully deleted the existing folder (and files) DEL: “C:\Windows\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.18741_none_b9293c0383618646”; ran MS Update;

    In my case, following these steps allowed the patch to install as expected.

    PS: you can verify if the failure is being caused by a permissions issue by examining the CBS.log (C:\Windows\Logs\CBS)


    I have fallowed your instructions, but installation still failed. This time with error code 80070002.
    Monday, March 16, 2015 10:36 PM
  • Download and install the standalone file: Security Update for Windows 7 for x64-based Systems (KB3033929)

    Carey Frisch

    Still failed with standalone install
    Tuesday, March 17, 2015 11:21 AM
  • Please Verify the following:

    1) Is this a "dual-boot" system?

    2)Are any other patches failing to install (besides KB3033929)?

    2.A) If yes, which ones?

    3) Does the following folder exist: "C:\Windows\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.18741_none_b9293c0383618646"

    4) Have you checked your CBS.log file for errors?

    Tuesday, March 17, 2015 12:55 PM
  • Sry, I did not see this (cbs log) until after I had already replied further below.  

    Failed to get session package state for package: Package_1_for_KB2647753~31bf3856ad364e35~amd64~~6.1.4.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

    1. Make sure that the trusted installer service is set to run automatically (both in services and Group Policy).  See:
      ~http://support.microsoft.com/en-us/kb/968440
      AND
      ~http://blogs.technet.com/b/roplatforms/archive/2011/04/28/installation-failures-cbs-store-corruptions-uncommon-issues-and-troubleshooting.aspx

      “If the service Start value is set to Manual, the updates are never applied.  The registry key that is used for this setting is as follows: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TrustedInstaller\Start
      The display name of this service in services.msc is "Windows Modules Installer."
    2. PER MS: “If you receive Windows Update error 80070490, it means that a file (CBS Manifest) that's needed to install updates is corrupt.”

      See: http://windows.microsoft.com/en-us/windows/windows-update-error-80070490#1TC=windows-7
    3. You may want to run the following FIX-it (for resolving WUS issues)
      ~http://support.microsoft.com/en-us/kb/971058
    Tuesday, March 17, 2015 2:46 PM
  • I have been getting this error constantly since 13/03/15. Windows keeps telling I have an update to install after which it shuts down. When it restarts it advises me it that it is installing updates. After a while it advises that the update failed and that it is reverting. It is continuously doing this which has become extremely irritating. Is there a way to delete this failed update?


    • Edited by PhilipGr Tuesday, March 17, 2015 5:32 PM
    Tuesday, March 17, 2015 5:32 PM
  • You may want to try the following:

    1) Running the following FIX-it (for resolving WUS issues)
      LINK:  ~http://support.microsoft.com/en-us/kb/971058 

    2) Then change windows update to "manual" update mode (as aposed to install updates automatically)

    3) Scan for updates

    4) Uncheck and then "hide" KB KB3033929

    The update should no longer download or install going forward.  You can then revert the WUS to “automatic” if you desire (recommended).  Perhaps MS will FIX and re-release this in the future.  At that point you could choose to “unhide” the patch and then  try to reinstall it at that time.

    • Proposed as answer by LarisaKud Tuesday, March 17, 2015 8:27 PM
    • Marked as answer by Cloud_TSModerator Tuesday, March 31, 2015 7:14 AM
    Tuesday, March 17, 2015 7:31 PM
  • We had the same Problem on a Dell Precision where the recovery partition was the active boot partition and there was no space left on that partition.

    We used Partition Manager to grow the recovery Partition and KB3033929 installed successfully.

    We noticed the cause by those kind of entries in cbs.log:

    "...BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume..."

    Thanks to all for posting their experiences here!!


    • Edited by nord-soft Thursday, March 19, 2015 9:07 AM
    Thursday, March 19, 2015 8:40 AM
  • I tired that and got the same result. Failed to configure, Code 80004005
    Saturday, March 21, 2015 5:51 PM
  • My computer has those three updates installed, but it still won't successfully configure KB 3033929
    Saturday, March 21, 2015 6:09 PM
  • Win7Pro on an SSD, HDD for files and libraries.  NO dual boot.

    Here is my CBS.log, no errors...

    2015-03-21 13:02:51, Info                  CBS    Starting TrustedInstaller initialization.
    2015-03-21 13:02:51, Info                  CBS    Loaded Servicing Stack v6.1.7601.17592 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\cbscore.dll
    2015-03-21 13:02:53, Info                  CSI    00000001@2015/3/21:18:02:53.287 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee720f0ad @0x7fefb099849 @0x7fefb0634e3 @0xff6de97c @0xff6dd799 @0xff6ddb2f)
    2015-03-21 13:02:53, Info                  CSI    00000002@2015/3/21:18:02:53.505 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee720f0ad @0x7fefb0e6816 @0x7fefb0b2aac @0x7fefb0635b9 @0xff6de97c @0xff6dd799)
    2015-03-21 13:02:53, Info                  CSI    00000003@2015/3/21:18:02:53.536 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee720f0ad @0x7fefb288738 @0x7fefb288866 @0xff6de474 @0xff6dd7de @0xff6ddb2f)
    2015-03-21 13:02:53, Info                  CBS    Ending TrustedInstaller initialization.
    2015-03-21 13:02:53, Info                  CBS    Starting the TrustedInstaller main loop.
    2015-03-21 13:02:53, Info                  CBS    TrustedInstaller service starts successfully.
    2015-03-21 13:02:53, Info                  CBS    SQM: Initializing online with Windows opt-in: False
    2015-03-21 13:02:53, Info                  CBS    SQM: Cleaning up report files older than 10 days.
    2015-03-21 13:02:53, Info                  CBS    SQM: Requesting upload of all unsent reports.
    2015-03-21 13:02:53, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
    2015-03-21 13:02:53, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
    2015-03-21 13:02:53, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
    2015-03-21 13:02:53, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
    2015-03-21 13:02:53, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending.
    2015-03-21 13:02:53, Info                  CBS    NonStart: Checking to ensure startup processing was not required.
    2015-03-21 13:02:53, Info                  CSI    00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x9bfc30
    2015-03-21 13:02:53, Info                  CSI    00000005 Creating NT transaction (seq 1), objectname [6]"(null)"
    2015-03-21 13:02:53, Info                  CSI    00000006 Created NT transaction (seq 1) result 0x00000000, handle @0x204
    2015-03-21 13:02:53, Info                  CSI    00000007@2015/3/21:18:02:53.614 CSI perf trace:
    CSIPERF:TXCOMMIT;1694
    2015-03-21 13:02:53, Info                  CBS    NonStart: Success, startup processing not required as expected.
    2015-03-21 13:02:53, Info                  CBS    Startup processing thread terminated normally
    2015-03-21 13:02:53, Info                  CSI    00000008 CSI Store 1763584 (0x00000000001ae900) initialized
    2015-03-21 13:02:53, Info                  CBS    Session: 30434305_1084815336 initialized by client WindowsUpdateAgent.
    2015-03-21 13:02:53, Info                  CBS    Session: 30434305_1085439337 initialized by client WindowsUpdateAgent.
    2015-03-21 13:02:54, Info                  CBS    Read out cached package applicability for package: Package_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1, ApplicableState: 112, CurrentState:112
    2015-03-21 13:04:36, Info                  CBS    Archived backup log: C:\Windows\Logs\CBS\CbsPersist_20150321180251.cab.
    2015-03-21 13:06:18, Info                  CBS    Session: 30434305_3137082202 initialized by client WindowsUpdateAgent.
    2015-03-21 13:06:18, Info                  CBS    Read out cached package applicability for package: Package_for_KB2574819~31bf3856ad364e35~amd64~~6.1.2.0, ApplicableState: 112, CurrentState:112
    2015-03-21 13:07:03, Info                  CBS    Session: 30434305_3586028526 initialized by client WindowsUpdateAgent.
    2015-03-21 13:07:03, Info                  CBS    Read out cached package applicability for package: Microsoft-Windows-RDP-WinIP-Package-TopLevel~31bf3856ad364e35~amd64~~7.1.7601.16398, ApplicableState: 112, CurrentState:112
    2015-03-21 13:08:14, Info                  CBS    Session: 30434305_4291146169 initialized by client WindowsUpdateAgent.
    2015-03-21 13:08:14, Info                  CBS    Read out cached package applicability for package: Microsoft-Windows-RDP-BlueIP-Package-TopLevel~31bf3856ad364e35~amd64~~7.2.7601.16415, ApplicableState: 112, CurrentState:112
    2015-03-21 13:18:14, Info                  CBS    Reboot mark refs incremented to: 1
    2015-03-21 13:18:14, Info                  CBS    Scavenge: Starts
    2015-03-21 13:18:14, Info                  CSI    00000009@2015/3/21:18:18:14.277 CSI Transaction @0x18f580 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [10]"TI6.0_0:0/"
    
    2015-03-21 13:18:14, Info                  CBS    Scavenge: Begin CSI Store
    2015-03-21 13:18:14, Info                  CSI    0000000a Performing 1 operations; 1 are not lock/unlock and follow:
      Scavenge (8): flags: 00000017
    2015-03-21 13:18:14, Info                  CSI    0000000b Store coherency cookie matches last scavenge cookie, skipping scavenge.
    2015-03-21 13:18:14, Info                  CSI    0000000c ICSITransaction::Commit calling IStorePendingTransaction::Apply - coldpatching=FALSE applyflags=7
    2015-03-21 13:18:14, Info                  CSI    0000000d Creating NT transaction (seq 2), objectname [6]"(null)"
    2015-03-21 13:18:14, Info                  CSI    0000000e Created NT transaction (seq 2) result 0x00000000, handle @0x120
    2015-03-21 13:18:14, Info                  CSI    0000000f@2015/3/21:18:18:14.448 CSI perf trace:
    CSIPERF:TXCOMMIT;12523
    2015-03-21 13:18:14, Info                  CBS    Scavenge: Completed, dis
    2015-03-21 13:18:14, Info                  CSI    00000010@2015/3/21:18:18:14.448 CSI Transaction @0x18f580 destroyed
    2015-03-21 13:18:14, Info                  CBS    Reboot mark refs: 0
    2015-03-21 13:18:14, Info                  CBS    Idle processing thread terminated normally
    2015-03-21 13:18:14, Info                  CBS    Ending the TrustedInstaller main loop.
    2015-03-21 13:18:14, Info                  CBS    Starting TrustedInstaller finalization.
    2015-03-21 13:18:14, Info                  CBS    Ending TrustedInstaller finalization.
    
    I am not a pro at reading those logs, so any help would be appreciated. Does this provide a clue? "No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending."

    Thanks


    Saturday, March 21, 2015 6:35 PM
  • Step 3 produced an error 5 on high grade win7 both from log in and the root.
    Sunday, March 22, 2015 7:09 AM
  • Ditto for me. That is it doesn't work.
    Sunday, March 22, 2015 7:10 AM
  • I believe this is a bad update from Microsoft. I have a VERY bare bones Windows 7 Home Premium 64 bit install that attempted to install this update automatically and it failed. Now it repeatedly tries to install it and it fails every time. It reverts back, every time.

    I went through every troubleshooting suggestion from Microsoft to no avail.

    I have seen multiple errors in the event viewer regarding this, however this particular one appears most commonly. Also received a 80070002 on it.

    For the moment I have hidden the update to stop the endless failures.


    Me too.
    Sunday, March 22, 2015 7:11 AM
  • This update is known for reboot loop. Do not install it until Microsoft correct it. There is no reason for testing current version of update as there is a massive failure is variety of users.

    However, if you have a good knowledge of Windows troubleshooting, Windows internals, tshoot tools... and have time enough, try to find a remedy.

    Regards

    Milos

    Sunday, March 22, 2015 7:43 AM
  • For rvnlord (https://social.technet.microsoft.com/profile/rvnlord/?ws=usercard-mini:)

    I had the same problem. Windows 7 32-bit.
    But now all OK! Thank You very much!
    Your assumption is correct. "
    Failure was caused by Customized Boot Loader. " You are quite right.
    I have more than one OS on my computer on two different hard discs.  I just unplug second one. But i don't understand, why Microsoft is conseal this problem?




    • Edited by uprassk Sunday, March 22, 2015 9:17 AM
    Sunday, March 22, 2015 8:48 AM
  • I had the same issue with KB3033929 and dual boot Ubuntu and Windows 7 on two separate hard-disks. Windows was able to update without problems after I physically removed the hard-disk containing Ubuntu. 

    KevMat


    • Edited by kevMat Monday, March 23, 2015 9:12 AM
    Monday, March 23, 2015 9:12 AM
  • I had posted the below on the answers.microsoft.com forum some days ago with no response, so will repost it it here.

    Below is an extract of the CBS log file after a KB3033929 manual installation failure.  With my limited knowledge, it appears it fails to copy (C:\Windows\boot\PCAT\bootmgr) to the System Reserve partition which when I installed Windows 7, created a 100 MB partition.  I believe the error 0x70 indicates there is no space available on the partition. 

    This may the reason some Windows 7 updates fail the KB3033929 installation, while some have no problem.

    Can anyone shed any light on the log entries and how I might fix the problem, or is this a M/S problem caused by installing Window 7 SP1 and only creating a 100 MB partition that should have been larger? 

    CBS LOG FILE EXTRACT:


     BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr,  \\?GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 60 of 60) Last Error = 0x70BFSVC:

    Error copying boot files from C:\Windows\boot\PCAT to  \\?GLOBALROOT\Device\HarddiskVolume1\Boot! Last Error = 0x70"][gle=0x80004005]
     2015-03-20 14:34:01, Info                  CSI    0000002c Calling generic command executable (sequence 2): [24]"C:\Windows\fveupdate.exe"
         CmdLine: [35]""C:\Windows\fveupdate.exe" /memtest"
     2015-03-20 14:34:01, Info                  CSI    0000002d Done with generic command 2; CreateProcess returned 0, CPAW returned S_OK
         Process exit code 0 resulted in success? TRUE
         Process output: [l:248 [248]"BitLockerUpdate: Running.BitLockerUpdate: Service request is for memtest.exe.BitLockerUpdate: BitLocker Drive

    Encryption is not turned ON on the OS volume.BitLockerUpdate: No servicing was performed on the OS volume.BitLockerUpdate: Done."]
     2015-03-20 14:34:01, Info                  CSI     0000002e@2015/3/20:19:34:01.770 CSI Advanced installer perf trace:
     CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-BootEnvironment-Core-MemoryDiagnostic, Version = 6.1.7601.18741, pA =

    PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral,

    PublicKey neutral;34776454
     2015-03-20 14:34:01, Error      [0x018007] CSI    0000002f (F) Failed execution of queue item Installer: Generic Command ({81a34a10-4256-436a-89d6-

    794b97ca407c}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will not be ignored: A rollback will be initiated after all the operations in the

    installer queue are completed; installer is reliable (2)[gle=0x80004005]


    • Edited by Old_Ben Wednesday, March 25, 2015 8:48 PM
    Wednesday, March 25, 2015 8:43 PM
  • I tried this, and it told me access denied. 

    I keep getting error code 8024200D or 80246007 (or 800F0829, but not since 2014)

    Nothing I have tried has worked. I have enough space so that cannot be the problem. I don't know what to do. Please help!

    Wednesday, March 25, 2015 9:24 PM
  • Can I kiss you? Thanks, this finally worked!
    Thursday, March 26, 2015 11:41 AM
  • No it's not just a dual Boot problem. It's also a problem with any windows 7 system.

    Leave it to Microsoft, Imagine the issues that Windows 10 will have.

    Saturday, March 28, 2015 1:03 PM
  • Hello, bobapunk

    It's not always to discern information in a long "unanswered" thread like this one, but I suspect Art Barnwell's 17Mar15 post above may confirm your suspicions:

    Make sure that the trusted installer service is set to run automatically (both in services and Group Policy).  See:
    ~http://support.microsoft.com/en-us/kb/968440
    AND
    ~http://blogs.technet.com/b/roplatforms/archive/2011/04/28/installation-failures-cbs-store-corruptions-uncommon-issues-and-troubleshooting.aspx

    Monday, March 30, 2015 4:12 AM
  • Based on the results of my CBS.log file, I decided to spend some time to re-visit this issue today.  My failure seems to point to the update being unable to write a file to the system reserve partition as it was full.  It was set up for 100 MB when I installed Windows 7.  Using Partition Wizard (free), I expanded the system reserve partition from 100 MB to about 400 MB.  I again ran the manual installation file for KB3033929 and it installed without any problems.

    After it was completed, I again plugged in my second HD with Windows XP, reset my boot loader with EasyBCD and all is now back to normal with dual boot menu to either Windows 7 or Window XP.

    Finally....hope this might work for others that are having a problem.

    Tuesday, March 31, 2015 9:19 PM
  • Thanks to the friends who wrote their suggestions there, with it I could solve the problem:

    I use dual boot machine with two OS on  separate hard drives, with a boot loader on the hard other than the windows hard.

    What I've done was to change the boot sequence (in bios) to make the machine boot directly from the hard where windows is installed without passing through the boot loader on the other hard. and that's it ! the update was installed smoothly in the first try without any problem or delay!!

    Not forget to mention that I used the standalone update pack this time, maybe that had a role in the success.

    Thanks again to all who wrote their suggestion, and good luck to all the other who are trying until now. 

    Thursday, April 02, 2015 11:14 PM
  • To change the boot order worked for me to solve this problem! No need to go to BIOS or disconnect hardware. In my system you can temporarily change the boot order by pressing F12 when the computer starts. Just make sure your system boots from the windows drive once the update is loaded. Thank you very much for the solution. It works!

    I have Win7 on one drive and Ubuntu (+ the GRUB loader) on the other.

    On the other laptop I have Win7 and Ubuntu on the same drive. There was no problem with that computer.

    Saturday, May 09, 2015 10:37 AM
  • Removing my Linux drive and installing the update also worked for me!

    Ubuntu 14.04 with Windows 7 x64 Pro

    Thank you very much!


    Wednesday, June 03, 2015 8:37 PM
  • This worked for me too, using gparted to change the boot flag temporarily.
    Friday, June 19, 2015 9:31 PM
  • I also have only one OS on my drive, although there appears to be a "recovery" partition (3.39 GB), put there by Dell (Dimension 9100) several years ago. I applied all your changes and re-ran Windows Update, but it still fails with code 800B0100. I DO already have the pre-req updates (KB2952664 and KB3035583), which show up in the list of installed updates. So I still can't get KB3033929 to install.

    Doc-OS


    More info: This PC has NEVER had any other OS on it nor has it had a different boot loader. It's my wife's system and is original MS software only.
    • Edited by Doc-OS Saturday, June 20, 2015 9:02 PM clarification
    Saturday, June 20, 2015 8:59 PM
  • I also have only one OS on my drive, although there appears to be a "recovery" partition (3.39 GB), put there by Dell (Dimension 9100) several years ago. I applied all your changes and re-ran Windows Update, but it still fails with code 800B0100. I DO already have the pre-req updates (KB2952664 and KB3035583), which show up in the list of installed updates. So I still can't get KB3033929 to install.
    More info: This PC has NEVER had any other OS on it nor has it had a different boot loader. It's my wife's system and is original MS software only.

    Doc-OS

    Saturday, June 20, 2015 9:07 PM
  • No dual boot, no non-MS boot loader. TrustedInstaller started. Permissions on WinRESUME changed as above. Update still fails.

    Doc-OS

    Saturday, June 20, 2015 9:15 PM
  • * HOW TO FIX *

    The easy way to fix this is to temporarily set the boot flag on for the windows partition.

    The following instructions relate to grub2 which I have installed to /dev/sda - My windows partitions are msdos1,msdos2 & msdos3 grub is installed on logical partition (5)

    Personally I add the following to the boot selection directly in /boot/grub/grub.cfg:

    parttool (hd0,msdos1) hidden- boot+

    This ensures that the windows drive is visible and that the bootflag is set.

    You can easily add these options into /etc/grub.d/30_osprober (or equivalent) which will ensure that new OS's added will easily be found and added correctly even on grub updates.

    I also recommend hiding (hidden+) the windows partitions you are NOT using, perhaps msdos2,3 etc... This will stop them messing with your other windows installations.

    I'll post the relevant section of the 30_osprober file (I use Jessie but similar for all) later on - (I'm currently in windows making sure this fix works!)

    Hope this helps you all

    Steve

    Northumberland IT Computer Services

    19 Park Avenue

    Bedlington

    01670 898333

    • Proposed as answer by Stevie A Thursday, July 23, 2015 10:41 AM
    Thursday, July 23, 2015 10:33 AM
  • 1. Open a Command Prompt (Run as Administrator).

    2. Type: cd %windir% and press enter.

    3. Type: net stop wuauserv and press enter.

    4. Type: ren softewaredistribution softwaredistribution.old and press enter.

    5. Type: net start wuauserv and press enter.

    6. Type: Exit and press enter.

    7. Try installing the updates once again.


    Carey Frisch

    I know this thread is old, but this DID work for me. 

    Key notes: make sure you're running as administrator, make sure you already have SP1 installed

    Monday, June 27, 2016 12:06 PM
  • I’ve come across several servers that have had issues installing Windows Updates.  This typically happens on Server 2008 R2, and is usually tied to an update rollup package.  The error code is 80004005

     

     

    I have found this to be a somewhat generic problem, and MANY people have run into it.  Often, they have to reinstall Windows to fix the problem.  The common element is that it is tied to disk space.

     

    First and foremost, make sure your primary OS partition (C:) has a fair amount of free space.  If you’re lucky, that will fix it.  Often times it does not, and the issue is disk space on a semi-hidden partition.

     

    Here is an example of a server that is out of disk space on the “Hidden” partition:

     

    In this example, you see a “System Reserved” partition on the computer’s single hard disk that is set to 100MB in size, and that drive is completely full.  What’s on that drive?  The only way to really see is to assign a drive letter to it.  I’ll assign “E”.  Once I’ve done that, I can browse to the drive and see there is only 1 folder, and it takes up only 14 MB.

     

    Turning on hidden/system files doesn’t change the view.  If I use a program like WinDirStat to see disk usage, it’s also not much help:

     

    This shows “Unknown files” are 85.7% of the disk usage.  You can’t browse to them or access them in anyway.  This does show us the problem, so we are half way toward fixing.

     

    First of all, what is this partition for?  Windows started creating a dedicated boot partition fairly recently in Windows (Windows 7/2008, I believe).  This partition gets the boot files that are used to instruct Windows on how to boot up, which OS to load, etc, much like the old boot.ini files used to do.  I’ve read that having journaling turned on can fill this partition, but that’s not what I have found on any servers (journaling had already been disabled).  Some other “junk” files get stored there – perhaps logs of some kind – but they are impossible to remove.

     

    So how do you fix?  It’s actually not too difficult.  Follow these steps (all assuming your OS is installed on the “C” partition):

     

    1.       Open an administrative command prompt

    a.       Run the following:  bcdboot c:\windows /s c:

    b.      This will create all the boot files on the “c” drive.

    2.       Using the disk management utility, right-click the “C” drive, and select “Mark as Active”.

    a.       This tells Windows, on its next restart, to get the boot files from the C drive

    b.      It is normal to get a warning when you do this.  As long as you completed the first step without error, this warning is ok to ignore

    3.       Reboot

    4.       After reboot, return to disk management

    a.       Right click the partition earlier set to “E”, and select “Format” (Quick format is fine)

    5.       Open an administrative command prompt

    a.       Assuming your OS is on the “C” drive and you labeled the hidden partition “E”, run the following:  bcdboot c:\windows /s e:

    b.      This will recreate all the boot files on the “e” drive.

    6.       Reboot

     

    This should resolve the issue.  I apologize for no pictures, but Microsoft has yet to verify my account, allowing me to add pretty graphics.

    Thursday, March 09, 2017 11:20 PM
  • Great job! It works like a charm!

    Thank you so much, problem solved!

    Wednesday, May 17, 2017 9:34 AM
  • I run sfc /scannow, system update readiness tool, chkdsk c: /f /r  and found no error.

    finally,
    it was DELL "RECOVERY" partition, that was set as active partition instead of C: drive

    so to make my C: drive to be "system partition"

    I using the disk management utility, right-click the “C” drive, and select “Mark as Active”.

    run bcdboot c:\windows /s c:
    run bcdedit /store c:\boot\bcd     ( to check that {bootmgr} is on c: drive and windows is on c: drive )

    reboot windows
    run System Update Readiness tool again to fix all error ( https://support.microsoft.com/en-us/help/947821/fix-windows-update-errors-by-using-the-dism-or-system-update-readiness-tool )

    now I can install all those problem,  security monthly quality rollup windows update

    Tuesday, June 20, 2017 9:01 PM
  • Works for me on my Dell precision M4800.

    Thank you very much !

    Tuesday, April 17, 2018 6:49 PM