locked
Server 2012 R2 Failing 2 Updates RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    My primary domain controller (Server 2012 R2 Standard) is failing updates kb4556846 and kb4556853. I've done them individually and the update will install, ask for a reboot, and then roll back the changes upon reboot. I've dug through the cbs.log file and discovered this:

    Extraction of file: update.ses failed because it is not present in the container.
    2020-06-03 15:23:01, Info                  DPX    DpxException hr=0x80070002 code=0x020109
    2020-06-03 15:23:01, Info                  CBS    Not able to add file to extract: update.ses [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

    One forum said this error is not fatal and the log does indicate that the process kept going after this error.

    And this error:

    Doqe: Recording result: 0x80070003, for Inf: ntprint.inf
    2020-06-11 14:31:34, Info                  CBS    DriverUpdateInstallUpdates failed [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
    2020-06-11 14:31:34, Info                  CBS    Doqe: Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
    2020-06-11 14:31:34, Info                  CBS    Perf: Doqe: Install ended.
    2020-06-11 14:31:34, Info                  CBS    Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
    2020-06-11 14:31:34, Error                 CBS    Startup: Failed while processing non-critical driver operations queue. [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
    2020-06-11 14:31:34, Info                  CBS    Startup: Rolling back KTM, because drivers failed.

    Both these updates ran fine on my secondary domain controller. As several forums have suggested, I've done the following troubleshooting steps without success:

    Install the update directly from Microsoft (bypassing my WSUS server), ran scf with scan and DISM with repair option, I've stopped the WSUS service and deleted the contents of C:\Windows\SoftwareDistribution and forced a re-download of the updates, copied over the C:\Windows\INF\ntprint.inf file from my working domain controller (since the hashes were different).

    Any help would be appreciated. Thanks!

    Friday, June 12, 2020 3:51 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi AConfusedParticipant,
     
    Thanks for your posting.
     
    Based on the information you provide, this issue may be related to the driver. It is  recommended that you find a Windows Server 2012R2 which updates correctly to copy the folder show path as the following:
    C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_182652d18d7b86f5
     
    Then, the copied folder is pasted into update Rollback Windows Server 2012R2 and renamed this folder. After you've done that, it's recommended that you try to reinstall the update.
     
    Here is link below for your reference:
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/3e7ce230-b8c8-4394-9a50-6a5bf8327485/kb4556853-keeps-rolling-back?forum=winserverwsus
     
    If you have any updates about this issue, please keep us in touch.
     
    Regards,
    Rita

    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, June 15, 2020 2:13 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi AConfusedParticipant,
     
    Thanks for your posting.
     
    Based on the information you provide, this issue may be related to the driver. It is  recommended that you find a Windows Server 2012R2 which updates correctly to copy the folder show path as the following:
    C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_182652d18d7b86f5
     
    Then, the copied folder is pasted into update Rollback Windows Server 2012R2 and renamed this folder. After you've done that, it's recommended that you try to reinstall the update.
     
    Here is link below for your reference:
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/3e7ce230-b8c8-4394-9a50-6a5bf8327485/kb4556853-keeps-rolling-back?forum=winserverwsus
     
    If you have any updates about this issue, please keep us in touch.
     
    Regards,
    Rita

    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, June 15, 2020 2:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Rita,

    Thank you so much for your reply. That's gotten me further along. In my setupapi.dev.log (like they mentioned in your reference), I actually have a different error. It says the driver failed signature validation and code integrity is turned on. I can look into turning it off, but I'm concerned about why the driver doesn't pass signature check. Here's the relevant section of the setupapi.dev.log:


    >>>  [Setup Import Driver Package - C:\Windows\system32\spool\DRIVERS\x64\{9DCF819D-7191-4C4D-8B48-C3B4A2D5FB12}\tsprint.inf]
    >>>  Section start 2020/06/15 11:18:01.113
          cmd: C:\Windows\System32\spoolsv.exe
         inf: Provider: Microsoft
         inf: Class GUID: {4D36E979-E325-11CE-BFC1-08002BE10318}
         inf: Driver Version: 06/21/2006,6.3.9600.17415
         pol: {Driver package policy check} 11:18:01.285
         pol: {Driver package policy check - exit(0x00000000)} 11:18:01.285
         sto: {Stage Driver Package: C:\Windows\system32\spool\DRIVERS\x64\{9DCF819D-7191-4C4D-8B48-C3B4A2D5FB12}\tsprint.inf} 11:18:01.300
         inf:      {Query Configurability: C:\Windows\system32\spool\DRIVERS\x64\{9DCF819D-7191-4C4D-8B48-C3B4A2D5FB12}\tsprint.inf} 11:18:01.300
         inf:           Driver package 'tsprint.inf' is configurable.
         inf:      {Query Configurability: exit(0x00000000)} 11:18:01.300
         flq:      Copying 'C:\Windows\system32\spool\DRIVERS\x64\{9DCF819D-7191-4C4D-8B48-C3B4A2D5FB12}\tsprint.inf' to 'C:\Windows\System32\DriverStore\Temp\{c02465cf-3e3d-2c40-b296-fe833b6947a8}\tsprint.inf'.
         flq:      Copying 'C:\Windows\system32\spool\DRIVERS\x64\{9DCF819D-7191-4C4D-8B48-C3B4A2D5FB12}\tsprint-PipelineConfig.xml' to 'C:\Windows\System32\DriverStore\Temp\{c02465cf-3e3d-2c40-b296-fe833b6947a8}\tsprint-PipelineConfig.xml'.
         flq:      Copying 'C:\Windows\system32\spool\DRIVERS\x64\{9DCF819D-7191-4C4D-8B48-C3B4A2D5FB12}\tsprint-datafile.dat' to 'C:\Windows\System32\DriverStore\Temp\{c02465cf-3e3d-2c40-b296-fe833b6947a8}\tsprint-datafile.dat'.
         flq:      Copying 'C:\Windows\system32\spool\DRIVERS\x64\{9DCF819D-7191-4C4D-8B48-C3B4A2D5FB12}\amd64\tsprint.dll' to 'C:\Windows\System32\DriverStore\Temp\{c02465cf-3e3d-2c40-b296-fe833b6947a8}\amd64\tsprint.dll'.
         sto:      {DRIVERSTORE IMPORT VALIDATE} 11:18:01.316
    !!!  sig:           Driver package does not contain a catalog file, and Code Integrity is enforced.
    !!!  sig:           Driver package failed signature validation. Error = 0xE000022F
         sto:      {DRIVERSTORE IMPORT VALIDATE: exit(0xe000022f)} 11:18:01.316
    !!!  sig:      Driver package failed signature verification. Error = 0xE000022F
    !!!  sto:      Failed to import driver package into Driver Store. Error = 0xE000022F
         sto: {Stage Driver Package: exit(0xe000022f)} 11:18:01.332
    <<<  Section end 2020/06/15 11:18:01.332
    <<<  [Exit status: FAILURE(0xe000022f)]

    Monday, June 15, 2020 8:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Rita,

    That trick worked. I'm sorry, I misread it at first. Here's what I did:

    Copied C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_182652d18d7b86f5 from a patched server. I pasted it on the rollback server and named the directory ntprint.inf_amd64_595c853c76796f44. Then re-downloaded the update and it went through fine.

    Thank you so much Rita!

    Monday, June 15, 2020 9:31 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi AConfusedParticipant,
     
    I am glad to hear that your issue was successfully resolved. If there is anything else we can do for you, please feel free to post in the forum.
     
    Best Regards,
    Rita

    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, June 16, 2020 1:00 AM