Results 1 to 3 of 3
  1. #1
    3 Star Lounger
    Join Date
    Dec 2009
    Fresno, California, USA
    Thanked 93 Times in 57 Posts

    KB2919355 issues being tracked

    1. Issues getting the update installed – fails at 12% and rolls back

    If the patch fails to install, get the log files located at %windir%\Logs\CBS\*.* and %windir%\Logs\DISM\*.*, and C:\Windows\inf\ zip them up place them in a onedrive/skydrive or other shared file location and post here in the forum.

    Run the following DISM command from an elevated command prompt and see if the patch will install after you run the DISM command

    Dism /Online /Cleanup-Image /RestoreHealth

    (see for more details.)

    This is starting to be the trending solution for dealing with failure 80073712:

    Download offline installers: to a location on the drive
    Windows8.1-KB2919355-x64.msu 690.8 MB
    Windows8.1-KB2932046-x64.msu 48.0 MB
    Windows8.1-KB2934018-x64.msu 126.4 MB
    Windows8.1-KB2937592-x64.msu 303 KB
    Windows8.1-KB2938439-x64.msu 19.6 MB

    Run Fix Windows Update:
    Run Scan Windows system components:
    Click start, find the command icon and right mouse click and run as administrator
    sfc /scannow
    Next Remove KB2919355 package by running the following command on the x64 platform (change this to x86 for 32bit platform. Again do this from an command icon where you have right mouse click and run as administrator
    dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35 ~amd64~~
    Clean up the WinSxS folder before attempting a reinstall. (Again needs an elevated command prompt)
    dism /online /cleanup-image /startcomponentcleanup /resetbase
    Clean up disk with system files remove: (Again needs an elevated command prompt)
    Restart computer
    Run offline installer from the location you installed from before in the following order: These KB's must be installed in the following order: KB2919442, KB2919355, KB2932046, KB2937592, KB2938439, and KB2934018. KB2919442 is a prerequisite for Windows 8.1 Update and should be installed before attempting to install KB2919355

    NOTE this may not fix this. It is still being investigated at this time.

    2. Someone moves folders and it failed to install

    See Which is also an excellent blog post regarding debugging. Please note if you also moved anything else or deleted system folders, you may have issues installing this update. This update needs folders and files in the location that the system was originally installed with.

    3.On Server 2012 R2 interaction with Veeam software

    Issue with Windows Server 2012 R2 Update KB 2919355 | view topic:

    Veeam has worked on a fix last weekend and indicated it should be out by Tuesday.

    4. Windows 8.1 Update prevents interaction with WSUS 3.2 over SSL - WSUS

    Product Team Blog - Site Home - TechNet Blogs:

    *Microsoft plans to issue an update as soon as possible that will correct the issue and restore the proper behavior for Windows 8.1 Update scanning against all supported WSUS configurations. Until that time, we are temporarily suspending the distribution of the Windows 8.1 Update to WSUS servers.*

    You may still obtain the Windows 8.1 Update from the Windows Update Catalog or MSDN. However, we recommend that you suspend deployment of this update in your organization until we release the update that resolves this issue. You may also find the workarounds discussed in this article to be useful for testing the Windows 8.1 Update for your organization. Thank you for your patience during this time

    5. If you installed from MSDN download you will see a small KB2919355 being offered up.

    This is expected as it appears that KB2934018 (one of the sub patches that gets installed as you install KB2919355) is replacing KB2949621 that was manually installed in the MSDN package. This appears to be a bitlocker update that in the MSDN release was not installing unless bitlocker role was installed. This is expected, go ahead and install the offered KB2919355.

    6. You are unable to uninstall IIS after you install KB2919355 in Windows 8.1 or Windows Server 2012 R2:

    7. Error 0x80071a91 when installing update 2919355 in Windows:

    8. Make sure you have enough space to install it (at least 3 gigs if not more)

    Windows 8.1 update 1 _KB2919355 Error: 0x80070070:

    9. To fix an issue with the Internet Explorer Enterprise Mode feature which occurs after the update is installed, visit the following Microsoft website

    10. Make sure you move back folders:

    "The following actions fixed it for me:

    Try going to: "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\System Tools"

    If this folder does not exist (because you changed a few folders around to make the start screen look better for example)

    You just go to: "C:\ProgramData\Microsoft\Windows\Start Menu\Programs"

    and add a new folder "System Tools"

    The update installed flawlessly after that.

    Tracking issues with error 80073712 - please see this post and see if it fixes your issue:

    AndrewB - Windows 8.1 Update: KB2919355 Error 80073712 Potential Fix:

    12. Failure code 0x800F0922 check the following:

    Check your log for ETW Provider of DWM:

    My log showed:

    2014-04-13 15:18:04, Info CSI 0000051f Begin executing advanced installer phase 38 (0x00000026) index 1011 (0x00000000000003f3) (sequence 1050)
    Old component: [ml:336{168},l:334{167}]"Microsoft-Windows-DesktopWindowManager-uDWM, Culture=neutral, Version=6.3.9600.16483, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    New component: [ml:336{168},l:334{167}]"Microsoft-Windows-DesktopWindowManager-uDWM, Culture=neutral, Version=6.3.9600.17031, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {3bb9fd2b-351e-4b9c-b1fc-ed0758805998}
    Installer name: [6]"Events"
    2014-04-13 15:18:04, Error CSI 0000000b (F) Logged @2014/4/13:13:18:04.787 : [ml:300{150},l:298{149}]"events installer: online=1, install=1, component=amd64_Microsoft-Windows-DesktopWindowManager-uDWM_31bf3856ad364e35_6.3.9600.17031_neutral_relea se__."
    2014-04-13 15:18:04, Error CSI 0000000c (F) Logged @2014/4/13:13:18:04.802 : [ml:244{122},l:242{121}]"EventAITrace:Provider Microsoft-Windows-Dwm-Udwm is already installed with GUID {98583af0-fc93-4e71-96d5-9f8da716c6b8}.

    2014-04-13 15:18:04, Error CSI 0000000d (F) Logged @2014/4/13:13:18:04.802 : [ml:168{84},l:166{83}]"WmiCmiPlugin manproc.cpp(657): InstrumentationManifestAssert failed. HR=0x80073aa2."
    2014-04-13 15:18:04, Error CSI 0000000e (F) Logged @2014/4/13:13:18:04.802 : [ml:166{83},l:164{82}]"WmiCmiPlugin eventloghandler.cpp(192): ProcessEventsInstall failed. HR=0x80073aa2."
    2014-04-13 15:18:04, Error CSI 0000000f (F) Logged @2014/4/13:13:18:04.802 : [ml:170{85},l:168{84}]"WmiCmiPlugin eventloghandler.cpp(212): EventLogHandlerInstall failed. HR=0x80073aa2."
    2014-04-13 15:18:04, Error CSI 00000010@2014/4/13:13:18:04.802 (F) CMIADAPTER: Inner Error Message from AI HRESULT = HRESULT_FROM_WIN32(15010)

    A genius of another board suggested me to backup and afterwards delete the following reg-key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\WINEVT

    After that i made a restart and then installed the update without problems!!

    Update was installed via MS Update, not previously downloaded, therefore i would suggest that there is no problem with corruption of the files provided by MS Update.

    13. Uninstall antivirus before installing this update and reinstall it afterwards.
    Check with your a/v vendor to see if the are ready for this update
    Windows 8.1 Update 1 problem opening IE11/Office with MBAE

    This update is a mandatory update in order to continue to receive security updates in May. Thus it's very important to test quickly and deploy this. It's not a normal service pack, but consider it more like a monthly security update.
    Last edited by SusanBradley; 2014-04-15 at 00:48.

  2. The Following 6 Users Say Thank You to SusanBradley For This Useful Post:

    CLiNT (2014-04-08),jwitalka (2014-04-09),MartinT (2014-04-10),mrjimphelps (2014-04-09),rmonroe36 (2014-04-09),ruirib (2014-04-09)

  3. #2
    WS Lounge VIP mrjimphelps's Avatar
    Join Date
    Dec 2009
    Thanked 462 Times in 431 Posts
    Susan, this is very helpful information. Thank you.

  4. The Following User Says Thank You to mrjimphelps For This Useful Post:

    hrsteeley (2014-04-09)

  5. #3
    Star Lounger
    Join Date
    Dec 2009
    Thanked 20 Times in 2 Posts
    This patch was installed automatically by Windows Update before I thought of hiding it.

    I just backed out this update because half of my auto-start programs were not starting. There was some variability about what did or didn't start on a reboot, and I am not quite sure what the cause was, but I am guessing it was either:

    a. Lack of quotation marks around registry entries in the HKLM/Software/Microsoft/Windows/CurrentVersion/Run etc. keys; or
    b. A change to how the Windows code that actually starts these programs accesses the registry to find out what to start; or
    c. A change related to Windows Fast Start Up; or
    d. Something else entirely.

    The only help I could find on the internet for similar problems was to disable Fast Start Up - but this did not help with the patch installed. I tried a recovery-point roll-back, but that didn't help. Then I uninstalled the patch - still not fixed. Then I disabled Fast Start-Up again and my auto-start programs were starting again.

    So, no idea what the cause was, but going to hold off from re-install for a bit and see whether anyone else has similar issues.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts