[WinServer2012 x64] WU 0x800f0920

S

saldo

Member
Joined
Sep 19, 2017
Posts
7
Hi,
I found this Forum and it helped already alot, but now I got a problem I couldnt resolve myself. Maybe someone could help me with this.

My Windows Server 2012 (not R2) x64 with installed KMS cant install some security updates (KB4034666, KB3102939 & KB3082089). I tried it with the KB4034666 the last times.
We have done a P2V Migration about a year ago on VMWare ESX.
The installation is successfull and requeire a reboot. After the reboot it hangs on 67% for about an hour, then it starts reverting changes.

Thats what I tried:
- sfc /scannow --> no errors found
- Dism /Online /Cleanup-Image /RestoreHealth (also I put an other Server 2012 as source) --> no errors found
- sfcfix --> no errors found
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TrustedInstaller\BlockTimeIncrement changed to 10800 Seconds
- installed KB2770816 & KB2771431 (this updates should fix the error)

In the setupapi.dev.log it seems to be an error with vid.sys (Microsoft Hyper-V Virtualization Infrastructure Driver). We are not using Hyper-V.

I'm sorry for my bad english its not my native language.

I hope someone has an advice for me, thank you.


Regards
 

Attachments

I compared the server with the same OS (2012), that has successfully installed the update. First I tought it was an error with the wvid.inf Driver (Hyper-V), but it also failed with the same error code on the server that has successfully installed the update.

It seems to try to install the update, but fails when no Hyper-V is installed. The update will just continue and install successfully.


Regards
 
Hello and welcome

Due to the precise nature of your corruption, you will receive help from a user named softwaremaniac. He's one of our senior trainees here who's in his final phase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.
 
Hello and welcome! Please follow these instructions:

Add Missing Package
 1. Click the Start button and type cmd.exe in the search box.
2. Right-click on the cmd that comes up and select Run as administrator.
3. Once you are at the command prompt, copy/paste the following line and hit enter.

pnputil -a C:\Windows\WinSxS\amd64_wvid.inf_31bf3856ad364e35_6.2.9200.22229_none_de4ffda58616f5f9\wvid.inf

Let me know the result.
 
Hi Softwaremaniac
Thank you for your Support. I have to mention that the wvid.inf error is also displayed on a system that has successfully installed the update.

That is the result from pnputil:

C:\Windows\system32>pnputil -a C:\Windows\WinSxS\amd64_wvid.inf_31bf3856ad364e35
_6.2.9200.22229_none_de4ffda58616f5f9\wvid.inf
Microsoft PnP Utility
Processing inf : wvid.inf
Adding the driver package failed : The third-party INF does not contain digital
signature information.
Total attempted: 1
Number successfully imported: 0

I checked again the cbs log (see Attachement) and I found, that at 2017-09-22 10:38:39 it tries to update Microsoft-Windows-DynamicVolumeManager multiple times and after it fails everytime, it tries to rollback and fails again multiple times (2017-09-22 11:11:47). Do you got a Tool to analyze the CBS log an set filters?


Thank you very much for your support
 

Attachments

1. Open Command Prompt as Administrator.
2. Enter the following:

Note: Make sure you press Enter after each command.

bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS

bcdedit /set testsigning on

3. Reboot your PC.

4. Follow my instructions posted in the previous post.
 
Hi Softwaremaniac
It got the same error (I also tried it with bcdedit /set testsigning off).
But I think the problem has to with the following error, because I got the wvid.inf error also on a Server (with the same OS) that has installed the update successfully:

Code: 
2017-09-22 10:38:40, Info                  CSI    00000011 Begin executing advanced installer phase 34 (0x00000022) index 7 (sequence 42)
    Old component: [ml:326{163},l:324{162}]"Microsoft-Windows-DynamicVolumeManager, Culture=neutral, Version=6.2.9200.16384, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    New component: [ml:326{163},l:324{162}]"Microsoft-Windows-DynamicVolumeManager, Culture=neutral, Version=6.2.9200.22228, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {1b265fd2-721c-4e59-ad55-9d102a5d1d7f}
    Installer name: [12]"SppInstaller"
2017-09-22 10:38:40, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Percent progress: 67.
2017-09-22 10:53:40, Info                  CBS    Startup: Timed out waiting for startup processing to complete
2017-09-22 10:53:40, Info                  CBS    Current global progress. Current: 2, Limit: 4, ExecuteState: CbsExecuteStateResolvePending
2017-09-22 10:53:40, Info                  CBS    Previous global progress. Current: 0, Limit: 1, ExecuteState: ExecuteStateNone
2017-09-22 10:53:40, Info                  CBS    Clearing HangDetect value
2017-09-22 10:53:40, Info                  CBS    Saved last global progress. Current: 2, Limit: 4, ExecuteState: CbsExecuteStateResolvePending
2017-09-22 10:53:40, Info                  CBS    Setting HangDetect value to 1
2017-09-22 10:53:40, Info                  CBS    Startup: will attempt a restart to recover.
2017-09-22 10:53:40, Info                  CBS    Startup: A system shutdown was initiated while waiting for startup to complete
2017-09-22 10:53:40, Info                  CBS    Startup: Attempting to terminate the startup thread.
2017-09-22 10:54:19, Info                  CSI    00000001@2017/9/22:08:54:19.157 [89]"SPP Installer: CSLAPIContext::Initialize->SLOpen (attempt 0) completed with hr=0xc0000022"

Regards
 
I started the Server without the driver signature enforcement and could install the Driver.

I will try to install the update in a downtime.

Thats what is shown in setupapi.dev.log

Code: 
[Boot Session: 2017/09/26 11:07:44.488]
>>>  [SetupCopyOEMInf - C:\Windows\WinSxS\amd64_wvid.inf_31bf3856ad364e35_6.2.9200.22229_none_de4ffda58616f5f9\wvid.inf]
>>>  Section start 2017/09/26 11:10:02.022
      cmd: pnputil  -a C:\Windows\WinSxS\amd64_wvid.inf_31bf3856ad364e35_6.2.9200.22229_none_de4ffda58616f5f9\wvid.inf
     sto: {Import Driver Package: C:\Windows\WinSxS\amd64_wvid.inf_31bf3856ad364e35_6.2.9200.22229_none_de4ffda58616f5f9\wvid.inf} 11:10:02.022
     sto:      Driver Store   = C:\Windows\System32\DriverStore [Online] (6.2.9200)
     sto:      Driver Package = C:\Windows\WinSxS\amd64_wvid.inf_31bf3856ad364e35_6.2.9200.22229_none_de4ffda58616f5f9\wvid.inf
     sto:      Architecture   = amd64
     sto:      Flags          = 0x00000000
     inf:      Provider       = Microsoft
     inf:      Class GUID     = {4d36e97d-e325-11ce-bfc1-08002be10318}
     inf:      Driver Version = 06/21/2006,6.2.9200.22229
     inf:      Version Flags  = 0x00000001
     flq:      Copying 'C:\Windows\WinSxS\amd64_wvid.inf_31bf3856ad364e35_6.2.9200.22229_none_de4ffda58616f5f9\vid.dll' to 'C:\Users\cz9cif\AppData\Local\Temp\{1e4c26c0-0cd8-0446-85ff-f65649c34779}\vid.dll'.
     flq:      Copying 'C:\Windows\WinSxS\amd64_wvid.inf_31bf3856ad364e35_6.2.9200.22229_none_de4ffda58616f5f9\Vid.sys' to 'C:\Users\cz9cif\AppData\Local\Temp\{1e4c26c0-0cd8-0446-85ff-f65649c34779}\Vid.sys'.
     flq:      Copying 'C:\Windows\WinSxS\amd64_wvid.inf_31bf3856ad364e35_6.2.9200.22229_none_de4ffda58616f5f9\wvid.inf' to 'C:\Users\cz9cif\AppData\Local\Temp\{1e4c26c0-0cd8-0446-85ff-f65649c34779}\wvid.inf'.
     pol:      {Driver package policy check} 11:10:02.210
     pol:      {Driver package policy check - exit(0x00000000)} 11:10:02.210
     sto:      {Stage Driver Package: C:\Users\cz9cif\AppData\Local\Temp\{1e4c26c0-0cd8-0446-85ff-f65649c34779}\wvid.inf} 11:10:02.210
     inf:           {Query Configurability: C:\Users\cz9cif\AppData\Local\Temp\{1e4c26c0-0cd8-0446-85ff-f65649c34779}\wvid.inf} 11:10:02.210
     inf:                Driver package 'wvid.inf' is configurable.
     inf:           {Query Configurability: exit(0x00000000)} 11:10:02.210
     flq:           Copying 'C:\Users\cz9cif\AppData\Local\Temp\{1e4c26c0-0cd8-0446-85ff-f65649c34779}\vid.dll' to 'C:\Windows\System32\DriverStore\Temp\{12a25e10-3e64-6f40-bfb2-923a51de2f0d}\vid.dll'.
     flq:           Copying 'C:\Users\cz9cif\AppData\Local\Temp\{1e4c26c0-0cd8-0446-85ff-f65649c34779}\Vid.sys' to 'C:\Windows\System32\DriverStore\Temp\{12a25e10-3e64-6f40-bfb2-923a51de2f0d}\Vid.sys'.
     flq:           Copying 'C:\Users\cz9cif\AppData\Local\Temp\{1e4c26c0-0cd8-0446-85ff-f65649c34779}\wvid.inf' to 'C:\Windows\System32\DriverStore\Temp\{12a25e10-3e64-6f40-bfb2-923a51de2f0d}\wvid.inf'.
     sto:           {DRIVERSTORE IMPORT VALIDATE} 11:10:02.272
!    sig:                Driver package does not contain a catalog file, but user wants to install anyway.
     sto:           {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 11:10:05.443
     sig:           Signer Score = 0x80000000
     sig:           Signer Name  = <unsigned>
     sto:           {DRIVERSTORE IMPORT BEGIN} 11:10:05.443
     bak:                Create system restore point:
     bak:                     Description = Device Driver Package Install: Microsoft System devices
     bak:                     Time        = 15ms
     bak:                     Status      = 0x8007007E (FAILURE)
     sto:           {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 11:10:05.459
     cpy:           {Copy Directory: C:\Windows\System32\DriverStore\Temp\{12a25e10-3e64-6f40-bfb2-923a51de2f0d}} 11:10:05.459
     cpy:                Target Path = C:\Windows\System32\DriverStore\FileRepository\wvid.inf_amd64_99e44fc0f4be55d7
     cpy:           {Copy Directory: exit(0x00000000)} 11:10:05.475
     idb:           {Register Driver Package: C:\Windows\System32\DriverStore\FileRepository\wvid.inf_amd64_99e44fc0f4be55d7\wvid.inf} 11:10:05.475
     idb:                Created driver package object 'wvid.inf_amd64_99e44fc0f4be55d7' in SYSTEM database node.
     idb:                Created driver INF file object 'oem7.inf' in SYSTEM database node.
     idb:                Registered driver package 'wvid.inf_amd64_99e44fc0f4be55d7' with 'oem7.inf'.
     idb:           {Register Driver Package: exit(0x00000000)} 11:10:05.490
     idb:           {Publish Driver Package: C:\Windows\System32\DriverStore\FileRepository\wvid.inf_amd64_99e44fc0f4be55d7\wvid.inf} 11:10:05.490
     idb:                Activating driver package 'wvid.inf_amd64_99e44fc0f4be55d7'.
     cpy:                Published 'wvid.inf_amd64_99e44fc0f4be55d7\wvid.inf' to 'oem7.inf'.
     idb:                Indexed 2 device IDs for 'wvid.inf_amd64_99e44fc0f4be55d7'.
     idb:           {Publish Driver Package: exit(0x00000000)} 11:10:05.490
     sto:           {DRIVERSTORE IMPORT END} 11:10:05.490
     sto:           {DRIVERSTORE IMPORT END: exit(0x00000000)} 11:10:05.490
     sto:      {Stage Driver Package: exit(0x00000000)} 11:10:05.490
     sto:      Driver Store Filename = C:\Windows\System32\DriverStore\FileRepository\wvid.inf_amd64_99e44fc0f4be55d7\wvid.inf
     sto: {Import Driver Package: exit(0x00000000)} 11:10:05.506
     inf: Driver Store Path: C:\Windows\System32\DriverStore\FileRepository\wvid.inf_amd64_99e44fc0f4be55d7\wvid.inf
     inf: Published Inf Path: C:\Windows\INF\oem7.inf
<<<  Section end 2017/09/26 11:10:05.506
<<<  [Exit status: SUCCESS]

Regards
 
Hi,
the update fails with the same error, after installing wvid.inf manually.
The CBS Logs shows the same error
Code: 
2017-09-27 10:08:22, Info                  CSI    00000012 Begin executing advanced installer phase 34 (0x00000022) index 7 (sequence 42)
    Old component: [ml:326{163},l:324{162}]"Microsoft-Windows-DynamicVolumeManager, Culture=neutral, Version=6.2.9200.22228, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    New component: [ml:326{163},l:324{162}]"Microsoft-Windows-DynamicVolumeManager, Culture=neutral, Version=6.2.9200.16384, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {1b265fd2-721c-4e59-ad55-9d102a5d1d7f}
    Installer name: [12]"SppInstaller"
2017-09-27 10:23:23, Info                  CBS    Startup: Timed out waiting for startup processing to complete
2017-09-27 10:23:23, Info                  CBS    Current global progress. Current: 2, Limit: 4, ExecuteState: CbsExecuteStateResolvePending | CbsExecuteStateFlagRollback
2017-09-27 10:23:23, Info                  CBS    Previous global progress. Current: 3, Limit: 3, ExecuteState: CbsExecuteStateStageDrivers | CbsExecuteStateFlagRollback | CbsExecuteStateFlagAdvancedInstallersFailed
2017-09-27 10:23:23, Info                  CBS    Clearing HangDetect value
2017-09-27 10:23:23, Info                  CBS    Saved last global progress. Current: 2, Limit: 4, ExecuteState: CbsExecuteStateResolvePending | CbsExecuteStateFlagRollback
2017-09-27 10:23:23, Info                  CBS    Setting HangDetect value to 1
2017-09-27 10:23:23, Info                  CBS    Startup: will attempt a restart to recover.
2017-09-27 10:23:23, Info                  CBS    Startup: A system shutdown was initiated while waiting for startup to complete
2017-09-27 10:23:23, Info                  CBS    Startup: Attempting to terminate the startup thread.
2017-09-27 10:24:02, Info                  CSI    [EMAIL="00000001@2017/9/27:08:24:02.629"]00000001@2017/9/27:08:24:02.629[/EMAIL] [89]"SPP Installer: CSLAPIContext::Initialize->SLOpen (attempt 0) completed with hr=0xc0000022"

Regards
 

Attachments

Please, perform a Clean Boot and then attempt to install only one of the updates that won't install and then provide the CBS.log if it fails. Please tell me which update you have attempted.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top