Server 2012R2 Rolling back updates setupapi.dev says Failed to query processor architecture

Alexandr 1 Reputation point
2020-09-10T13:52:07.597+00:00

I've been trying to get kb4577066 installed on Server 2012 R2.
What I've tried besides an attempt to install, reboot, bang head, and repeat because the install failed are the following:
sfc /scannow (no errors)
dism /online /cleanup-image /restorehealth (no errors, the operation completed successfully)
in setupapi.dev I see error
!!! idb: Failed to query processor architecture for 'prnms003.inf_x86_05c529548388326c'. Error = 0x00000002
what Do I need to do to install updates?

[Boot Session: 2020/09/10 16:37:23.499]

>> [Stage Driver Updates]
>> Section start 2020/09/10 16:37:31.474

  cmd: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19750_none_fa39f32f9b2d0928\TiWorker.exe -Embedding
 sto: Image State        = Specialized
 sto: Image Architecture = amd64
 sto: Driver Updates     = 6
 sto: {Stage Driver Package: C:\Windows\WinSxS\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.19812_none_4e522eafc3216e88\cpu.inf} 16:37:31.490
 inf:      {Query Configurability: C:\Windows\WinSxS\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.19812_none_4e522eafc3216e88\cpu.inf} 16:37:31.553
 inf:           Driver package 'cpu.inf' is configurable.
 inf:      {Query Configurability: exit(0x00000000)} 16:37:31.553
 sto:      {DRIVERSTORE IMPORT BEGIN} 16:37:31.553
 sto:      {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 16:37:31.553
 flq:      Hardlinking 'C:\Windows\WinSxS\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.19812_none_4e522eafc3216e88\amdppm.sys' to 'C:\Windows\System32\DriverStore\FileRepository\cpu.inf_amd64_da992bd58104d459\amdppm.sys'.
 flq:      Hardlinking 'C:\Windows\WinSxS\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.19812_none_4e522eafc3216e88\cpu.inf' to 'C:\Windows\System32\DriverStore\FileRepository\cpu.inf_amd64_da992bd58104d459\cpu.inf'.
 flq:      Hardlinking 'C:\Windows\WinSxS\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.19812_none_4e522eafc3216e88\intelppm.sys' to 'C:\Windows\System32\DriverStore\FileRepository\cpu.inf_amd64_da992bd58104d459\intelppm.sys'.
 flq:      Hardlinking 'C:\Windows\WinSxS\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.19812_none_4e522eafc3216e88\processr.sys' to 'C:\Windows\System32\DriverStore\FileRepository\cpu.inf_amd64_da992bd58104d459\processr.sys'.
 flq:      Hardlinking 'C:\Windows\WinSxS\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.19812_none_4e522eafc3216e88\amdk8.sys' to 'C:\Windows\System32\DriverStore\FileRepository\cpu.inf_amd64_da992bd58104d459\amdk8.sys'.
 flq:      Hardlinking 'C:\Windows\WinSxS\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.19812_none_4e522eafc3216e88\fxppm.sys' to 'C:\Windows\System32\DriverStore\FileRepository\cpu.inf_amd64_da992bd58104d459\fxppm.sys'.
 idb:      {Register Driver Package: C:\Windows\System32\DriverStore\FileRepository\cpu.inf_amd64_da992bd58104d459\cpu.inf} 16:37:31.604
 idb:           Created driver package object 'cpu.inf_amd64_da992bd58104d459' in SYSTEM database node.
 idb:           Registered driver package 'cpu.inf_amd64_da992bd58104d459' with 'cpu.inf'.
 idb:      {Register Driver Package: exit(0x00000000)} 16:37:31.604
 sto:      {DRIVERSTORE IMPORT END} 16:37:31.604
 sto:      {DRIVERSTORE IMPORT END: exit(0x00000000)} 16:37:31.604
 sto: {Stage Driver Package: exit(0x00000000)} 16:37:31.604
 sto: {Stage Driver Package: C:\Windows\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.19806_none_43e61dc3a7949ddc\prnms003.inf} 16:37:31.604
 inf:      {Query Configurability: C:\Windows\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.19806_none_43e61dc3a7949ddc\prnms003.inf} 16:37:31.604
 inf:           Driver package 'prnms003.inf' is configurable.
 inf:      {Query Configurability: exit(0x00000000)} 16:37:31.604
 sto:      {DRIVERSTORE IMPORT BEGIN} 16:37:31.604
 sto:      {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 16:37:31.604
 flq:      Hardlinking 'C:\Windows\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.19806_none_43e61dc3a7949ddc\Amd64\PrintConfig.dll' to 'C:\Windows\System32\DriverStore\FileRepository\prnms003.inf_amd64_c918c7324e70f27d\Amd64\PrintConfig.dll'.
 flq:      Hardlinking 'C:\Windows\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.19806_none_43e61dc3a7949ddc\Amd64\unishare.gpd' to 'C:\Windows\System32\DriverStore\FileRepository\prnms003.inf_amd64_c918c7324e70f27d\Amd64\unishare.gpd'.
 flq:      Hardlinking 'C:\Windows\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.19806_none_43e61dc3a7949ddc\Amd64\unishare-pipelineconfig.xml' to 'C:\Windows\System32\DriverStore\FileRepository\prnms003.inf_amd64_c918c7324e70f27d\Amd64\unishare-pipelineconfig.xml'.
 flq:      Hardlinking 'C:\Windows\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.19806_none_43e61dc3a7949ddc\prnms003.cat' to 'C:\Windows\System32\DriverStore\FileRepository\prnms003.inf_amd64_c918c7324e70f27d\prnms003.cat'.
 flq:      Hardlinking 'C:\Windows\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.19806_none_43e61dc3a7949ddc\prnms003.inf' to 'C:\Windows\System32\DriverStore\FileRepository\prnms003.inf_amd64_c918c7324e70f27d\prnms003.inf'.
 idb:      {Register Driver Package: C:\Windows\System32\DriverStore\FileRepository\prnms003.inf_amd64_c918c7324e70f27d\prnms003.inf} 16:37:31.620
 idb:           Created driver package object 'prnms003.inf_amd64_c918c7324e70f27d' in DRIVERS database node.

!!! idb: Failed to query processor architecture for 'prnms003.inf_x86_05c529548388326c'. Error = 0x00000002
!!! idb: Failed to register driver package 'prnms003.inf_amd64_c918c7324e70f27d' against 'prnms003.inf'. Error = 0x00000002
!!! idb: Failed to register driver package 'C:\Windows\System32\DriverStore\FileRepository\prnms003.inf_amd64_c918c7324e70f27d\prnms003.inf'. Error = 0x00000002
idb: {Register Driver Package: exit(0x00000002)} 16:37:31.620
sto: {DRIVERSTORE IMPORT END} 16:37:31.620
sto: {DRIVERSTORE IMPORT END: exit(0x00000002)} 16:37:31.620
sto: Rolled back driver package import.
!!! sto: Failed to import driver package into Driver Store. Error = 0x00000002
sto: {Stage Driver Package: exit(0x00000002)} 16:37:31.620
!!! sto: Failed to stage all driver updates. Error = 0x00000002
sto: {Unstage Driver Package: C:\Windows\System32\DriverStore\FileRepository\cpu.inf_amd64_da992bd58104d459\cpu.inf} 16:37:31.620
sto: {DRIVERSTORE DELETE BEGIN} 16:37:31.620
sto: {DRIVERSTORE DELETE BEGIN: exit(0x00000000)} 16:37:31.620
idb: {Unregister Driver Package: C:\Windows\System32\DriverStore\FileRepository\cpu.inf_amd64_da992bd58104d459\cpu.inf} 16:37:31.620
idb: Unregistered driver package 'cpu.inf_amd64_da992bd58104d459' from 'cpu.inf'.
idb: Deleted driver package object 'cpu.inf_amd64_da992bd58104d459' from SYSTEM database node.
idb: Driver packages registered to 'cpu.inf':
idb: cpu.inf_amd64_463ee97ec1f2714e
idb: cpu.inf_amd64_bf687b471ff9433e
idb: cpu.inf_amd64_188cbaf1524d655e
idb: {Unregister Driver Package: exit(0x00000000)} 16:37:31.620
cpy: {Delete Directory: C:\Windows\System32\DriverStore\FileRepository\cpu.inf_amd64_da992bd58104d459} 16:37:31.620
cpy: {Delete Directory: exit(0x00000000)} 16:37:31.620
sto: {DRIVERSTORE DELETE END} 16:37:31.620
sto: {DRIVERSTORE DELETE END: exit(0x00000000)} 16:37:31.620
sto: {Unstage Driver Package: exit(0x00000000)} 16:37:31.620
sto: Driver update 'C:\Windows\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.19806_none_43e61dc3a7949ddc\prnms003.inf' is not staged.
<<< Section end 2020/09/10 16:37:31.620
<<< [Exit status: FAILURE(0x00000002)]

Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,588 questions
0 comments

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-09-10T13:59:39.523+00:00

    I'd check the prerequisite SSU has been installed.
    http://www.catalog.update.microsoft.com/Search.aspx?q=KB4566425

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments
  2. Dale Kudusi 3,236 Reputation points
    2020-09-11T02:13:45.813+00:00

    Hi
    You could try these methods:

    1. Install the Servicing stack update (SSU):
      https://support.microsoft.com/en-us/help/4566425/servicing-stack-update-for-windows-8-1-rt-8-1-and-server-2012-r2
    2. Install the update in Clean Boot:
      https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows
    3. Rename the folder in ‘C:\Windows\System32\DriverStore\FileRepository\prnms003.inf_amd64_c918c7324e70f27d ‘ then try to install update again.
      Please note that it’s better to remove external USB devices attached to the machine while updating.

    Please feel free to let us know if you need further assistance.

    Best regards.

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  3. Alexandr 1 Reputation point
    2020-09-11T05:29:32.337+00:00
    1. SSU installed
      PS C:\Windows\system32> dism /online /get-packages | findstr KB4566425
      ????????????? ?????? : Package_for_KB4566425~31bf3856ad364e35~amd64~~6.3.1.1
      PS C:\Windows\system32>
    2. Server is VM with only Microsoft apps there is no other apps to disable. It is already clean boot
    3. There is no such folder ‘C:\Windows\System32\DriverStore\FileRepository\prnms003.inf_amd64_c918c7324e70f27d ‘. I think this folder creates update kb4577066 when replacing prnms003.inf driver(Microsoft print compatibility driver).
      There is no external USB devices attached to the machine and it is VM.
      I Have only such folders:
      prnms003.inf_x86_ab19fc491870a41b
      prnms003.inf_x86_006452645509e257
      prnms003.inf_x86_05c529548388326c
      prnms003.inf_amd64_42a3d67721cb9aa8
      (and they do not rename)
    0 comments
  4. Anonymous
    2020-09-11T09:51:49.007+00:00

    Might check the \windowsupdate.log file for errors related to installation.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments
  5. Alexandr 1 Reputation point
    2020-09-18T10:24:41.227+00:00

    nothing helped.
    I deleted this problem server and installed new server with 2019 OS.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.