[SOLVED] Issue with windows update in Server 2019 : Rollback after reboot

T

Thierry

Contributor
Joined
Apr 27, 2022
Posts
8
Hello,

Cumulative updates on a Windows server 2019 keeps failing with error code 0x80070003 the install is successful but after reboot it does a rollback. I had a look on the CBS and I saw this error :
Perf: Doqe: Uninstall started.
2022-04-26 19:37:03, Info CBS Doqe: [Forward] Uninstalling driver updates, Count 25
2022-04-26 19:37:03, Info CBS DriverUpdateUninstallUpdates failed [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2022-04-26 19:37:03, Info CBS Doqe: Failed uninstalling driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2022-04-26 19:37:03, Info CBS Perf: Doqe: Uninstall ended.
2022-04-26 19:37:03, Info CBS Failed uninstalling driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2022-04-26 19:37:03, Error CBS Startup: Failed while processing non-critical driver operations queue. [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2022-04-26 19:37:03, Info CBS Startup: Rolling back KTM, because drivers failed.

I had a look on the setupapi.dev.log file :

>>> [Uninstall Driver Updates]
>>> Section start 2022/04/26 19:33:06.597
cmd: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.2865_none_56bbe6f3993dfb16\TiWorker.exe -Embedding
sto: Image State = Specialized
sto: Image Architecture = amd64
sto: Transaction = CbsDriversAndPrimitives
sto: Driver Updates = 25
! inf: Unable to load INF: 'C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_18b0d38ddfaee729\ntprint.inf'(00000003)
!!! inf: Invalid INF 'C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_18b0d38ddfaee729\ntprint.inf', parsing error on line 0. Code = 1002
!!! sto: Failed to get version info for driver update 'C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_18b0d38ddfaee729\ntprint.inf'. Error = 0x00000003
<<< Section end 2022/04/26 19:33:06.642
<<< [Exit status: FAILURE(0x00000003)]


I copied the ntprint.inf file from another 2019 server to this one in the ntprint.inf_amd64_18b0d38ddfaee729 folder but unfortunately that didn't fix the problem.

Could you please help me ?

Sorry for my approximative English writing ...

Thank you in advance

Regards,

Thierry
 
Hello,

I ran the sec /scannow ans obtained

C:\Windows\system32>sfc /scannow

Début de l’analyse du système. Cette opération peut nécessiter un certain temps.

Démarrage de la phase de vérification de l’analyse du système.
La vérification 100% est terminée.

La Protection des ressources Windows a détecté des fichiers corrompus, mais n'a pas pu réparer certains d'entre eux.
Pour les réparations en ligne, les détails sont inclus dans le fichier journal de CBS situé à l'emplacement suivant :
windir\Logs\CBS\CBS.log. Exemple : C:\Windows\Logs\CBS\CBS.log. Pour les réparations
hors connexion, les détails sont inclus dans le fichier journal fourni par l'indicateur /OFFLOGFILE.

In the CBS file :

2022-04-28 18:26:47, Info CSI 00005d62 [SR] Beginning Verify and Repair transaction
2022-04-28 18:26:47, Info CSI 00005d63 Hashes for file member [l:11]'ntprint.inf' do not match.
Expected: {l:32 ml:4096 b:93cc2482aced6bf65c1c0969b68a3041c5d793011f278b16e0fb0d026f55e2f3}.
Actual: {l:32 b:46554a1a190dabdd060e80a48edf5bbbf84a601fac2c09e64ba5d2382a8658a3}.
2022-04-28 18:26:47, Info CSI 00005d64 [SR] Cannot repair member file [l:11]'ntprint.inf' of dual_ntprint.inf, version 10.0.17763.1577, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver' in the store, hash mismatch
2022-04-28 18:26:47, Info CBS Appl:Forcing GE on revision on parent:Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~10.0.17763.1
2022-04-28 18:26:47, Info CBS Appl:Forcing GE on revision on parent:Microsoft-Windows-EditionPack-Cloud-Package~31bf3856ad364e35~amd64~~10.0.17763.1
2022-04-28 18:26:47, Info CBS Appl:Forcing GE on revision on parent:Microsoft-Windows-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.17763.1
2022-04-28 18:26:47, Info CBS Appl:Feature On Demand package without explicit comparator, using GE on build version
2022-04-28 18:26:47, Info CBS Appl:Forcing GE on revision on parent:Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.17763.1
2022-04-28 18:26:47, Info CBS Appl:Feature On Demand package without explicit comparator, using GE on build version
2022-04-28 18:26:47, Info CBS Appl:Forcing GE on revision on parent:Microsoft-Windows-Server-Shell-Package~31bf3856ad364e35~amd64~~10.0.17763.1
2022-04-28 18:26:47, Info CBS Appl:Forcing GE on revision on parent:Microsoft-Windows-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.17763.1
2022-04-28 18:26:47, Info CSI 00005d65@2022/4/28:16:26:47.983 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d66 Hashes for file member [l:11]'ntprint.inf' do not match.
Expected: {l:32 ml:4096 b:93cc2482aced6bf65c1c0969b68a3041c5d793011f278b16e0fb0d026f55e2f3}.
Actual: {l:32 b:46554a1a190dabdd060e80a48edf5bbbf84a601fac2c09e64ba5d2382a8658a3}.
2022-04-28 18:26:47, Info CSI 00005d67 [SR] Cannot repair member file [l:11]'ntprint.inf' of dual_ntprint.inf, version 10.0.17763.1577, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver' in the store, hash mismatch
2022-04-28 18:26:47, Info CSI 00005d68 [SR] This component was referenced by [l:80]'Package_2017_for_KB4601345~31bf3856ad364e35~amd64~~10.0.1.7.4601345-3504_neutral'
2022-04-28 18:26:47, Info CBS Appl:Forcing GE on revision on parent:Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.17763.1
2022-04-28 18:26:48, Info CSI 00005d69@2022/4/28:16:26:48.059 Primitive installers committed for repair
2022-04-28 18:26:48, Info CSI 00005d6a [SR] Repair complete
2022-04-28 18:26:48, Info CSI 00005d6b [SR] Committing transaction


There are many lines (more than 1000) like this one in the same CBS file :

2022-04-28 18:26:47, Info CSI 00005d40@2022/4/28:16:26:47.386 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d41@2022/4/28:16:26:47.415 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d42@2022/4/28:16:26:47.425 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d43@2022/4/28:16:26:47.487 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d44@2022/4/28:16:26:47.497 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d45@2022/4/28:16:26:47.508 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d46@2022/4/28:16:26:47.519 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d47@2022/4/28:16:26:47.530 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d48@2022/4/28:16:26:47.540 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d49@2022/4/28:16:26:47.550 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d4a@2022/4/28:16:26:47.563 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d4b@2022/4/28:16:26:47.574 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d4c@2022/4/28:16:26:47.586 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d4d@2022/4/28:16:26:47.596 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d4e@2022/4/28:16:26:47.607 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d4f@2022/4/28:16:26:47.618 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d50@2022/4/28:16:26:47.628 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d51@2022/4/28:16:26:47.639 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d52@2022/4/28:16:26:47.649 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d53@2022/4/28:16:26:47.660 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d54@2022/4/28:16:26:47.670 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d55@2022/4/28:16:26:47.717 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d56@2022/4/28:16:26:47.728 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d57@2022/4/28:16:26:47.742 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d58@2022/4/28:16:26:47.754 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d59@2022/4/28:16:26:47.765 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d5a@2022/4/28:16:26:47.775 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d5b@2022/4/28:16:26:47.840 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d5c@2022/4/28:16:26:47.869 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d5d@2022/4/28:16:26:47.880 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d5e@2022/4/28:16:26:47.893 Primitive installers committed for repair
2022-04-28 18:26:47, Info CSI 00005d5f@2022/4/28:16:26:47.904 Primitive installers committed for repair

I hesitate to launch DSIM commands because I fear to crash the server. Is the common DSIM dangerous ?

Thank you in advance

Thierry
 
Hi and welcome to Sysnative,

Step 1. Upload a copy of the CBS folder.
  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply.


Step 2. Please attach the complete setupapi.dev.log file as well
 
Step 1. Download
56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the System File Checker.
  • Click the Start button and in the search box, type Command Prompt
  • When you see Command Prompt on the list, right-click on it and select Run as administrator.
  • When command prompt opens, copy and paste the following command into it, and press enter.
    Code: 
    sfc /scannow
  • Take a screenshot of the commandprompt window and paste it into your next reply.
 

Attachments

Thank you

the sfcfix.txt in attached file

The return of sfc /scannow :

C:\Windows\system32>sfc /scannow

Début de l’analyse du système. Cette opération peut nécessiter un certain temps.

Démarrage de la phase de vérification de l’analyse du système.
La vérification 100% est terminée.

La Protection des ressources Windows a détecté des fichiers corrompus, mais n'a pas pu réparer certains d'entre eux.
Pour les réparations en ligne, les détails sont inclus dans le fichier journal de CBS situé à l'emplacement suivant :
windir\Logs\CBS\CBS.log. Exemple : C:\Windows\Logs\CBS\CBS.log. Pour les réparations
hors connexion, les détails sont inclus dans le fichier journal fourni par l'indicateur /OFFLOGFILE.

C:\Windows\system32>

Thierry
 

Attachments

Thierry said:
La Protection des ressources Windows a détecté des fichiers corrompus, mais n'a pas pu réparer certains d'entre eux.

Translation: Windows Resource Protection found corrupt files but was unable to fix some of them
Click to expand...

  • Click the Start button and in the search box, type CMD
  • When you see Command Prompt on the list, right-click on it and select Run as administrator.
  • Copy and paste the following command into it, then press enter.
    Code: 
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  • This command will create cbs.txt on your Desktop. Zip this file and attach the zipped cbs.txt to your next post.
 
Still the same issue, please post a copy of the COMPONENTS and DRIVERS hive.

Step 1. Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.


Step 2. Upload your DRIVERS Hive
  • Navigate to C:\Windows\System32\config and locate the DRIVERS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named DRIVERS.ZIP on your desktop.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Hi,

Step 1. Run SFCFix again with the attached ZIP-file.

Step 2. Reboot the system and run the System File Checker, and let me know the result.
Code: 
SFC /Scannow
 

Attachments

Hi,

Good news : No more issues reported by system file checker.

C:\Windows\system32>sfc /scannow

Début de l’analyse du système. Cette opération peut nécessiter un certain temps.

Démarrage de la phase de vérification de l’analyse du système.
La vérification 100% est terminée.

Le programme de protection des ressources Windows n’a trouvé aucune violation d’intégrité.

C:\Windows\system32>

I'm applying windows update again.

I'll keep you in touch.

Thank you

Thierry
 
Hi,

Great, hopefully Windows Update will now work without any problems. If it fails, please attach a new copy of the CBS log..
 
You're a kind of Harry Potter. My server is up to date now.

Thank you so much.

Have the best evening

Happy Thierry
 

Attachments

  • 1651426638830.png
    1651426638830.png
    75.6 KB · Views: 3
Your welcome, glad to hear Windows Update is working correctly and the server is up to date...

Have a nice evening as well.... (y)
I'll mark this thread as solved!
 
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