[SOLVED] [Win8.1 x64] Unable to install June 2017 security rollup

[Sellfish]

Hello,
I've had issues installing the latest security rollup update (KB4022726) as well as some of the optional updates I never bothered to install before.
The updates first install normally but when restarting, it seems to fail during the "Preparing Windows" step since the following step, preparing updates (until 30%), is missing. After the restart, Windows restarts again and next time it'll revert the changes.
The updates are listed as successful, even though they actually failed to install.

The SFCFix log shows no issues (it fails to generate a zip though), even though it calls Dism, which fails (0x800f081f). As listed in the CBS.log attached in the 7z, the corrupt files (I couldn't find either of these in WinSxS) are as follows :

• amd64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_11.0.9600.18205_none_47f1a95ca0a537e9\jscript9.dll
• wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.0.9600.18212_none_21611e3d397ccabe\mshtml.dll

Manually reinstalling the updates that should contain these files with the exact version string couldn't fix the issue.
sfc /scannow detects no issues.

CBS logs (7-Zip) :
https://www.dropbox.com/s/jh92rd0m5gfdq9c/CBS.7z?dl=1

SFCFix log :

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-06-22 15:06:57.116
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2017-06-22 15:22:39.716
----------------------EOF-----------------------

Thanks in advance!

 

[Sellfish2]

Re: [Win 8.1 x64] Unable to install June 2017 security rollup

I was able to fix the DISM issue by using a network shared Windows directory of another 8.1 PC and now neither sfc nor DISM show any errors.
Unfortunately, the same issue with the update silently failing to install persists as described in the thread. SFCFix can't find any errors, the log output hasn't changed except for the date.

 

[Sellfish2]

Re: [Win 8.1 x64] Unable to install June 2017 security rollup

I've finally fixed this issue, which also occured with the July security rollup.

I'll describe how I fixed it in the following lines (definitely not suitable for beginners) :

Windows Update always failed to update the wvmbusr driver (some Hyper-V stuff) and then rolled back the whole update.
The wvmbusr.inf file found in the according directory in WinSxS has a description on how to install it using devcon (command line : devcon install wvmbusr.inf root\vmbus).
Devcon is in the Windows Driver Development Kit (DDK) that can be downloaded from Microsoft in Tools\x64 (and x86). I used the 8.1 DDK since I use Win 8.1.
But devcon always fails immediately, except when installing the old driver.
Using x64dbg and 2 hours, I tracked the issue down.
The driver installer expected the driver folder wvmbusr.inf_amd64_4732973f9521a087 in System32\DriverStore\FileRepository to exist, even though it didn't copy the files there.
Manually creating that directory and copying the files from the WinSxS folder solved the devcon issue and the driver installed.
"devcon remove root\vmbus" should be used first to remove old devices.

With the driver updated, Windows Update still didn't succeed.
The driver updater puts its log lines to <Drive letter>:\Windows\Inf\setupapi.dev.log. Here is the relevant part that describes the issue :

>>>  [Install Driver Updates]
>>>  Section start 2017/07/12 20:22:40.442
      cmd: C:\windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.18384_none_fa1d93c39b41b41a\TiWorker.exe -Embedding
     sto: Image State        = Specialized
     sto: Image Architecture = amd64
     sto: Transaction        = CbsDriversAndPrimitives
     sto: Driver Updates     = 3
     sto: {Publish Driver Package: C:\windows\System32\DriverStore\FileRepository\stornvme.inf_amd64_8a0d52bd20d1f36f\stornvme.inf} 20:22:40.457
     sto:      Driver Package = stornvme.inf_amd64_8a0d52bd20d1f36f
     idb:      {Publish Driver Package: C:\windows\System32\DriverStore\FileRepository\stornvme.inf_amd64_8a0d52bd20d1f36f\stornvme.inf} 20:22:40.473
     idb:           Changing active driver package from 'stornvme.inf_amd64_92ad9f893b39b63c' to 'stornvme.inf_amd64_8a0d52bd20d1f36f'.
     cpy:           Unpublished 'stornvme.inf'.
     idb:           Deindexed 1 driver file for 'stornvme.inf_amd64_92ad9f893b39b63c'.
     idb:           Deindexed 2 device IDs for 'stornvme.inf_amd64_92ad9f893b39b63c'.
     cpy:           Published 'stornvme.inf_amd64_8a0d52bd20d1f36f\stornvme.inf' to 'stornvme.inf'.
     idb:           Indexed 1 driver file for 'stornvme.inf_amd64_8a0d52bd20d1f36f'.
     idb:           Indexed 2 device IDs for 'stornvme.inf_amd64_8a0d52bd20d1f36f'.
     idb:      {Publish Driver Package: exit(0x00000000)} 20:22:40.489
     sto: {Publish Driver Package: exit(0x00000000)} 20:22:40.489
     sto: {Publish Driver Package: C:\windows\System32\DriverStore\FileRepository\wvmbusr.inf_amd64_4732973f9521a087\wvmbusr.inf} 20:22:40.489
     sto:      Driver Package = wvmbusr.inf_amd64_4732973f9521a087
     idb:      {Publish Driver Package: C:\windows\System32\DriverStore\FileRepository\wvmbusr.inf_amd64_4732973f9521a087\wvmbusr.inf} 20:22:40.489
     idb:           Activating driver package 'wvmbusr.inf_amd64_4732973f9521a087'.
     cpy:           Published 'wvmbusr.inf_amd64_4732973f9521a087\wvmbusr.inf' to 'oem102.inf'.
!!!  idb:           Failed to query driver INF matches for '{4d36e97d-e325-11ce-bfc1-08002be10318}'. Error = 0x0000054F
!!!  idb:           Failed to update driver package device IDs for 'wvmbusr.inf_amd64_4732973f9521a087'. Error = 0x0000054F
!!!  idb:           Failed to publish 'C:\windows\System32\DriverStore\FileRepository\wvmbusr.inf_amd64_4732973f9521a087\wvmbusr.inf'. Error = 0x0000054F
     idb:      {Publish Driver Package: exit(0x0000054f)} 20:22:40.489
!!!  sto:      Failed to publish driver package. Error = 0x0000054F
     sto: {Publish Driver Package: exit(0x0000054f)} 20:22:40.489
!!!  sto: Failed to publish all driver updates. Error = 0x0000054F
<<<  Section end 2017/07/12 20:22:40.489
<<<  [Exit status: FAILURE(0x0000054f)]

I've not been able to find out why that error occurs but since I've tried all combinations of driver uninstalled, old driver installed and driver updated, I've decided to modify the driver update module to make it skip the error.
Using AgentRansack (which doesn't support UTF-16 in-file search), I've searched for dlls with the text "Failed to publish driver package" with both "s and got the result drvstore.dll (C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_...).
Then I used x64dbg (x64dbg) on a copy of that file, searched for referenced strings starting with ("Failed to publish ") and replaced the compare instruction "test ebx,ebx" before the log call with "xor ebx,ebx" to clear the error code to zero.
The last step was saving the patches to a new drvstore.dll and replacing the one in the original path. That finally did the trick and the update installed fine.

For reference, I've uploaded my modified amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.18384_none_fa1d93c39b41b41a\drvstore.dll (use it on your own risk and only if the log looks exactly the same) here : Dropbox - drvstore mod.zip