locked
KB4556853 keeps rolling back RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    kb4556853 keeps rolling back after saying it successfully installed.  I ran sfc /scannow and it showed that it could not repair an issue.  I then ran 'DISM /Online /Cleanup-Image /RestoreHealth' and that was able to perform a repair, hoever the update will still not install.  Running sfc /scannow does not reveal any corruption needing repair, but the DISM command does still show a repair needs to be performed.  I've run this command a couple more times and it still shows a repair needed each time I run it.  I think tried to install the latest monthly cumulative update for Windows Server 2012 R2 kb4556846 and that update also reverts.  I don't see anything in the application of system event logs that indicates the root cause of the issue.
    Tuesday, June 2, 2020 10:06 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I finally got the latest patch installed.  The last log entry I posted was from the WER report setupapi.dev.log file located in the ProgramData\Microsoft\Windows\WER\ReportQueue folder.
    I then found this post discussing a similar problem.  https://marc.info/?l=patchmanagement&m=150596585519031
    The solution there was to copy the folder ntprint.inf_amd64_595c853c76796f44 from a server that hadn't been updated and then re-run the update.  All my other servers had been updated and I didn't have a way to restore that file without going to tape.  Instead I copied the new inf folder ntprint.inf_amd64_182652d18d7b86f5 from one of the updated servers to this server and renamed it ntprint.inf_amd64_595c853c76796f44.  Then I re-ran the update and this time the update did not roll back.

    • Marked as answer by Hollisorama Friday, June 12, 2020 7:53 PM
    Friday, June 12, 2020 7:53 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Hollisorama,

    Thanks for your posting.

    Please consider referring to the following steps:
    1. Open the command prompt as an administrator, and enter the following command in turn:
    DISM.exe /Online /Cleanup-image /Restorehealth
    sfc /scannow

    Reference link: https://support.microsoft.com/en-us/help/10164/fix-windows-update-errors

    2. Please consider referring to the link below to reset the Windows component:
    https://docs.microsoft.com/en-us/windows/deployment/update/windows-update-resources

    3. Please consider installing SSU - KB4540725, and then installing this update.

     

    If you have any updates, 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.

    Wednesday, June 3, 2020 6:00 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you.  I've performed these steps and the latest SSU is installed.  I just tried installing the standalone version of the update and it also fails.
    Wednesday, June 3, 2020 9:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Hollisorama,
     
    Thanks for your posting.
     
    Please consider checking that the client has the latest Monthly Rollup installed. If the customer has installed the latest Monthly Rollup, there is no need for the client to install Security-only updates -KB4556853
     
    Please note that the latest Monthly Rollup of Window Server 2012R2 is KB4556846
     
    If you have any updates, 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.

    Thursday, June 4, 2020 3:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    After this latest security only update failed, I tried the latest monthly cumulative and it also fails.  We have a robust patching strategy for our environment.  This is the only server that is having a problem this month
    Thursday, June 4, 2020 3:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
      

    Hi Hollisorama,

    Thanks for your posting.

    Please consider the following steps for simple typographical errors：
    1. Run the Windows Update troubleshooter
    If there is any error, post it in the forum.

    2. Delect software distribution folder
    Open the command prompt as an administrator, enter the following command in turn:

    net stop bits
net stop wuauserv
     

    Delete the following path folder:C:\Windows\SoftwareDistribution
    Restart BITS and automatic updates services

    3. Open the command prompt as an administrator, enter the following command in turn:

    DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow

    Once you've done this, please consider reinstalling the latest Monthly Rollup. If the installation still fails, consider checking for the error in Windowsupdate.log. The following images are the parts of the log where the errors are made:



    If you check any error code in the log, please consider retrieving this error information.

    If you have any updates. 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.

    Thursday, June 4, 2020 6:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Hollisorama,
     
    Thanks for your posting.
     
    To avoid misunderstandings, please help to check how the client installs updates. For example, the WSUS, Microsoft Update catalog, or other means
     
    Regards,
    Rita

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

    Thursday, June 4, 2020 8:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The primary way we deploy updates is through Microsoft Endpoint Manager (SCCM).  I have also tried installing this update through the normal Windows Update channel as well as with the standalone package and The update rolls back using all methods.
    Saturday, June 6, 2020 3:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Hollisorama,
     
    Thanks for your posting.
     
    Please consider checking clients Windowsupdate.log and CBS.log with reference to the links below:
    https://docs.microsoft.com/en-sg/windows/deployment/update/windows-update-logs
     
    If you have any updates, 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 8, 2020 6:32 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Here are the noteworthy CBS.log entries.  I didn't see anything of note in the windowsupdate.log file

    2020-06-12 12:28:20, Info                  CBS    TI: --- Initializing Trusted Installer ---
    2020-06-12 12:28:20, Info                  CBS    TI: Last boot time: 2020-06-12 12:28:16.484
    2020-06-12 12:28:20, Info                  CBS    Starting TrustedInstaller initialization.
    2020-06-12 12:28:20, Info                  CBS    Ending TrustedInstaller initialization.
    2020-06-12 12:28:20, Info                  CBS    Starting the TrustedInstaller main loop.
    2020-06-12 12:28:20, Info                  CBS    TrustedInstaller service starts successfully.
    2020-06-12 12:28:20, Info                  CBS    Winlogon: Registering for CreateSession notifications
    2020-06-12 12:28:20, Info                  CBS    Starting TiWorker initialization.
    2020-06-12 12:28:20, Info                  CBS    Ending TiWorker initialization.
    2020-06-12 12:28:20, Info                  CBS    Starting the TiWorker main loop.
    2020-06-12 12:28:20, Info                  CBS    TiWorker starts successfully.
    2020-06-12 12:28:20, Info                  CBS    Universal Time is: 2020-06-12 17:28:20.764
    2020-06-12 12:28:20, Info                  CBS    Loaded Servicing Stack v6.3.9600.19651 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19651_none_fa3af1939b2c2558\cbscore.dll
    2020-06-12 12:28:20, Info                  CSI    00000001@2020/6/12:17:28:20.779 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffce32b7f69 @0x7ffce4ee4a44 @0x7ffce4ee427b @0x7ff6bc80d69a @0x7ff6bc80e55b @0x7ffceca32113)
    2020-06-12 12:28:20, Info                  CBS    Could not load SrClient DLL from path: SrClient.dll.  Continuing without system restore points.
    2020-06-12 12:28:20, Info                  CBS    SQM: Initializing online with Windows opt-in: False
    2020-06-12 12:28:20, Info                  CBS    SQM: Cleaning up report files older than 10 days.
    2020-06-12 12:28:20, Info                  CBS    SQM: Requesting upload of all unsent reports.
    2020-06-12 12:28:20, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
    2020-06-12 12:28:20, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
    2020-06-12 12:28:20, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
    2020-06-12 12:28:20, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
    2020-06-12 12:28:20, Info                  CBS    Startup: BlockTime: 10800000ms, BlockTimeIncrement: 900000ms
    2020-06-12 12:28:20, Info                  CBS    SetProgressMessage: progressMessageStage: 0, ExecuteState: ExecuteStateNone, SubStage: 0
    2020-06-12 12:28:20, Info                  CBS    Retrieved original failure status: 0x80070003, last forward execute state: CbsExecuteStatePrimitives
    2020-06-12 12:28:20, Info                  CBS    SetProgressMessage: progressMessageStage: 0, ExecuteState: ExecuteStateNone, SubStage: 0
    2020-06-12 12:28:20, Info                  CBS    Startup: current ExecuteState is CbsExecuteStateFailed
    2020-06-12 12:28:20, Info                  CBS    SetProgressMessage: progressMessageStage: 0, ExecuteState: CbsExecuteStateFailed, SubStage: 0
    2020-06-12 12:28:20, Info                  CBS    Disabling LKG boot option
    2020-06-12 12:28:20, Info                  CBS    Startup: Initializing driver operations queue.
    2020-06-12 12:28:20, Info                  CBS    Startup: Initializing advanced operation queue.
    2020-06-12 12:28:20, Info                  CBS    Winlogon: TiCoreOnCreateSession has been called
    2020-06-12 12:28:21, Info                  CSI    00000002 CSI Store 1005362319728 (0x000000ea14439170) initialized
    2020-06-12 12:28:21, Info                  CBS    Startup: Waiting for SC autostart event
    2020-06-12 12:28:21, Info                  CBS    Startup: SC autostart event signaled
    2020-06-12 12:28:21, Info                  CBS    SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateFailed, SubStage: 0
    2020-06-12 12:28:21, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 0 out of 0. Rollback.
    2020-06-12 12:28:21, Info                  CBS    Startup: Changing logon timeout to a static timeout: 10800000
    2020-06-12 12:28:21, Info                  CBS    Winlogon: TiCoreOnCreateSession has been called
    2020-06-12 12:28:22, Info                  CBS    Winlogon: TiCoreOnCreateSession has been called
    2020-06-12 12:28:23, Info                  CBS    Cancelling: 1 CBS transactions
    2020-06-12 12:28:23, Info                  CSI    00000003 Cancelling transactions: [1:[87]"TI4.30818518_2773322258:4/Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.19701.1.10"[1]"]"
    2020-06-12 12:28:23, Info                  CBS    Winlogon: TiCoreOnCreateSession has been called
    2020-06-12 12:28:24, Info                  CSI    00000004 Creating NT transaction (seq 1), objectname [6]"(null)"
    2020-06-12 12:28:24, Info                  CSI    00000005 Created NT transaction (seq 1) result 0x00000000, handle @0x28c
    2020-06-12 12:28:24, Info                  CSI    00000006 Poqexec successfully registered in [ml:30{15},l:28{14}]"PoqexecCmdline"
    2020-06-12 12:28:24, Info                  CSI    00000007@2020/6/12:17:28:24.212 Beginning NT transaction commit...
    2020-06-12 12:28:24, Info                  CSI    00000008@2020/6/12:17:28:24.259 CSI perf trace:
    CSIPERF:TXCOMMIT;46498
    2020-06-12 12:28:24, Error                 CBS    Doqe: Marked package Package_646_for_KB4556846~31bf3856ad364e35~amd64~~6.3.1.10 as failed. [HRESULT = 0x00000000 - S_OK]
    2020-06-12 12:28:24, Info                  CBS    Removed poqexec from Configuration key.
    2020-06-12 12:28:24, Info                  CBS    Configured poqexec to pend to SetupExecute.
    2020-06-12 12:28:24, Info                  CBS    Attempting to remove poqexec from SetupExecute
    2020-06-12 12:28:24, Info                  CBS    Removed poqexec from SetupExecute.
    2020-06-12 12:28:24, Info                  CBS    Doqe: Enabling Device installs
    2020-06-12 12:28:24, Info                  CBS    Clearing HangDetect value
    2020-06-12 12:28:24, Info                  CBS    Saved last global progress. Current: 1, Limit: 1, ExecuteState: CbsExecuteStateFailed
    2020-06-12 12:28:24, Info                  CBS    WER: Generating failure report for package: Package_646_for_KB4556846~31bf3856ad364e35~amd64~~6.3.1.10, status: 0x80070003, failure source: DOQ, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
    2020-06-12 12:28:24, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200608111533.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200604040334.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200603211253.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200603210356.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200602215314.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Not able to add %windir%\winsxs\pending.xml to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-06-12 12:28:24, Info                  CBS    Not able to add %windir%\winsxs\pending.xml.bad to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-06-12 12:28:24, Info                  CBS    Startup: Package: Package_646_for_KB4556846~31bf3856ad364e35~amd64~~6.3.1.10 completed startup processing, new state: Staged, original: Staged, targeted: Installed.  hr = 0x80070003
    2020-06-12 12:28:24, Info                  CBS    WER: Generating failure report for package: Package_for_KB4556846_RTM_GM~31bf3856ad364e35~amd64~~6.3.1.10, status: 0x80070003, failure source: DOQ, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
    2020-06-12 12:28:24, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200608111533.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200604040334.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200603211253.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200603210356.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200602215314.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Not able to add %windir%\winsxs\pending.xml to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-06-12 12:28:24, Info                  CBS    Not able to add %windir%\winsxs\pending.xml.bad to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-06-12 12:28:24, Info                  CBS    Startup: Package: Package_for_KB4556846_RTM_GM~31bf3856ad364e35~amd64~~6.3.1.10 completed startup processing, new state: Staged, original: Staged, targeted: Installed.  hr = 0x80070003
    2020-06-12 12:28:24, Info                  CBS    WER: Generating failure report for package: Package_for_KB4556846_RTM~31bf3856ad364e35~amd64~~6.3.1.10, status: 0x80070003, failure source: DOQ, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
    2020-06-12 12:28:24, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200608111533.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200604040334.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200603211253.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200603210356.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200602215314.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Not able to add %windir%\winsxs\pending.xml to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-06-12 12:28:24, Info                  CBS    Not able to add %windir%\winsxs\pending.xml.bad to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-06-12 12:28:24, Info                  CBS    Startup: Package: Package_for_KB4556846_RTM~31bf3856ad364e35~amd64~~6.3.1.10 completed startup processing, new state: Staged, original: Staged, targeted: Installed.  hr = 0x80070003
    2020-06-12 12:28:24, Info                  CBS    WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.19701.1.10, status: 0x80070003, failure source: DOQ, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
    2020-06-12 12:28:24, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200608111533.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200604040334.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200603211253.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200603210356.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20200602215314.cab to WER report.
    2020-06-12 12:28:24, Info                  CBS    Not able to add %windir%\winsxs\pending.xml to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-06-12 12:28:24, Info                  CBS    Not able to add %windir%\winsxs\pending.xml.bad to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-06-12 12:28:24, Info                  CBS    SQM: Reporting package change completion for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.19701.1.10, current: Staged, original: Staged, target: Installed, status: 0x80070003, failure source: DOQ, failure details: "Driver servicing operation failed", client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 1462, first merged sequence: 1462, pending decision: Unknown, primitive execution context: PSRL
    2020-06-12 12:28:24, Info                  CBS    SQM: Unable to gather perf datapoints because there are no active sessions.
    2020-06-12 12:28:24, Info                  CBS    SQM: Upload requested for report: PackageChangeEnd_Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.19701.1.10, session id: 142862, sample type: Standard
    2020-06-12 12:28:24, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard
    2020-06-12 12:28:24, Info                  CBS    Startup: Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.19701.1.10 completed startup processing, new state: Staged, original: Staged, targeted: Installed.  hr = 0x80070003
    2020-06-12 12:28:24, Info                  CBS    Retrieved original failure status: 0x80070003, last forward execute state: CbsExecuteStatePrimitives
    2020-06-12 12:28:24, Info                  CBS    Startup: Package: Package_1009_for_KB4556846~31bf3856ad364e35~amd64~~6.3.1.10 completed startup processing, new state: Staged, original: Staged, targeted: Installed.  hr = 0x800f0826
    2020-06-12 12:28:24, Info                  CBS    Retrieved original failure status: 0x80070003, last forward execute state: CbsExecuteStatePrimitives
    2020-06-12 12:28:24, Info                  CBS    Startup: Package: Package_1010_for_KB4556846~31bf3856ad364e35~amd64~~6.3.1.10 completed startup processing, new state: Staged, original: Staged, targeted: Installed.  hr = 0x800f0826
    2020-06-12 12:28:24, Info                  CBS    Retrieved original failure status: 0x80070003, last forward execute state: CbsExecuteStatePrimitives
    2020-06-12 12:28:24, Info                  CBS    Startup: Package: Package_1011_for_KB4556846~31bf3856ad364e35~amd64~~6.3.1.10 completed startup processing, new state: Staged, original: Staged, targeted: Installed.  hr = 0x800f0826
    2020-06-12 12:28:24, Info                  CBS    Retrieved original failure status: 0x80070003, last forward execute state: CbsExecuteStatePrimitives
    2020-06-12 12:28:24, Info                  CBS    Startup: Package: Package_1012_for_KB4556846~31bf3856ad364e35~amd64~~6.3.1.10 completed startup processing, new state: Staged, original: Staged, targeted: Installed.  hr = 0x800f0826
    2020-06-12 12:28:24, Info                  CBS    Retrieved original failure status: 0x80070003, last forward execute state: CbsExecuteStatePrimitives
    2020-06-12 12:28:24, Info                  CBS    Startup: Package: Package_1029_for_KB4556846~31bf3856ad364e35~amd64~~6.3.1.10 completed startup processing, new state: Staged, original: Staged, targeted: Installed.  hr = 0x800f0826
    2020-06-12 12:28:24, Info                  CBS    Retrieved original failure status: 0x80070003, last forward execute state: CbsExecuteStatePrimitives
    2020-06-12 12:28:24, Info                  CBS    Startup: Package: Package_1042_for_KB4556846~31bf3856a

    Friday, June 12, 2020 5:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I think I may have found the issue, but I'm not 100% sure what to do about it

         sto: {Publish Driver Package: C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_182652d18d7b86f5\ntprint.inf} 13:31:12.697
         sto:      Driver Package = ntprint.inf_amd64_182652d18d7b86f5
         idb:      {Publish Driver Package: C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_182652d18d7b86f5\ntprint.inf} 13:31:12.697
         idb:           Changing active driver package from 'ntprint.inf_amd64_595c853c76796f44' to 'ntprint.inf_amd64_182652d18d7b86f5'.
         cpy:           Unpublished 'ntprint.inf'.
    !    inf:           Unable to load INF: 'C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_595c853c76796f44\ntprint.inf'(00000003)
    !    inf:           Error 3: The system cannot find the path specified.
    !!!  inf:           Failed to open INF file "C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_595c853c76796f44\ntprint.inf". Error = 0x00000003, Line = 0
    !!!  sto:           Failed to get driver package file list. Error = 0x00000003, Filename = C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_595c853c76796f44\ntprint.inf
    !!!  idb:           Failed to update driver package files for 'ntprint.inf_amd64_595c853c76796f44'. Error = 0x00000003
    !!!  idb:           Failed to publish 'C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_182652d18d7b86f5\ntprint.inf'. Error = 0x00000003
         idb:      {Publish Driver Package: exit(0x00000003)} 13:31:12.712
    !!!  sto:      Failed to publish driver package. Error = 0x00000003
         sto: {Publish Driver Package: exit(0x00000003)} 13:31:12.712
    !!!  sto: Failed to publish all driver updates. Error = 0x00000003
    <<<  Section end 2020/06/12 13:31:12.712
    <<<  [Exit status: FAILURE(0x00000003)]
    >>>  [Unstage Driver Updates]

    Friday, June 12, 2020 7:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I finally got the latest patch installed.  The last log entry I posted was from the WER report setupapi.dev.log file located in the ProgramData\Microsoft\Windows\WER\ReportQueue folder.
    I then found this post discussing a similar problem.  https://marc.info/?l=patchmanagement&m=150596585519031
    The solution there was to copy the folder ntprint.inf_amd64_595c853c76796f44 from a server that hadn't been updated and then re-run the update.  All my other servers had been updated and I didn't have a way to restore that file without going to tape.  Instead I copied the new inf folder ntprint.inf_amd64_182652d18d7b86f5 from one of the updated servers to this server and renamed it ntprint.inf_amd64_595c853c76796f44.  Then I re-ran the update and this time the update did not roll back.

    • Marked as answer by Hollisorama Friday, June 12, 2020 7:53 PM
    Friday, June 12, 2020 7:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Hollisorama,
     
    I am glad to hear that your issue was successfully resolved. Thanks for your sharing. 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.

    Monday, June 15, 2020 2:18 AM