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\setupapi.dev.log 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

Run Fix Windows Update: http://support.microsoft.com/kb/971058/
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~~6.3.1.14
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)
cleanmgr.exe
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 http://chentiangemalc.wordpress.com/...-8-1-update-1/ 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.

*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.

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 MBAEhttps://forums.malwarebytes.org/inde...owtopic=146368
***

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.

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

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.