Windows 8.1 errors before Windows 10 upgrade

I don't see an error in the file cbs.log.
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt again and report the result.
 
Remove Update Manually
  1. Click on the Start button and in the search box, type Command Prompt.
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator.
  3. When command prompt opens, copy and paste the following command into it, then press enter.
    wusa /uninstall /KB:2976978
  4. Let me know if it says it was successful or if there are any errors.
 
1638547857033.png

This error is the Main problem faced on this update since the start...

Don't know if useful, but anticipated FRST64.exe search of KB2976978... You have SearchReg joined to this message

Thanks again for the support
 

Attachments

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Complete cycle done ...
Fixlog joined.
Rebooted and new update status
1638602765298.png
unfortunaltely : not such a success as they still reappear in WU :
1638603897939.png

sfc /scannow after reboot and results joined (had to long wait for cbs rebuilding that processed after end of sfc /scannow)

This is really driving me nuts ;)
 

Attachments

It looks like you tried to install KB5007247 and KB2976978 after running the last fix. Is that correct ?
 
In fact no, when i run a reboot just after fixing for example or running a sfc /scannow it is always trying to install those 2 kb's.
I did not try to run the update, nor forced it.. I cannot stop this installation (as it's a reboot stage), and it is always ending either in error, either successful, but after reboot, install wants to proceed again.

There is a weird thing in this update thing...
And for information, windows 10 upgrade ends systematically in error (Win 10 is the main aim of all these updates)

Do you think we need to concentrate on Windows 10 errors only ?
 
Go to Control Panel - Windows Update - Change settings.
Select Download updates but let me choose whether to install them.
Click OK.
 
Ok this is done... what must i do here on ?
Had an Antivirus update, that passed during that time... and am rebooting the computer.
 
Last edited:
Try to install KB2976978 only and report the result.
 
1638826364697.png

Seems ok indeed :
1638826703276.png


Code: 
Package_for_KB2976978~31bf3856ad364e35~amd64~~6.3.24.1                                              | Install‚      | Update          | 06/12/2021 21:22

And last but not least :
1638826966298.png
 
Last edited:
Great. Try to install KB5007247 and report the result.
 
Still present in WU: 1638830771357.png
but announced it installed
1638830810800.png

Package list seems to confirm it did not install :
Code: 
Package_for_KB4601058~31bf3856ad364e35~amd64~~6.3.1.3396                                            | Interm‚diaire | Update          | 30/04/2021 16:05   
Package_for_KB5001403~31bf3856ad364e35~amd64~~6.3.1.1                                               | Install‚      | Security Update | 27/04/2021 11:27   
Package_for_KB5004118~31bf3856ad364e35~amd64~~6.3.1.3460                                            | Install‚      | Update          | 15/07/2021 19:02   
Package_for_KB5004754~31bf3856ad364e35~amd64~~6.3.1.3475                                            | Interm‚diaire | Update          | 07/10/2021 23:32   
Package_for_KB5006067~31bf3856ad364e35~amd64~~6.3.1.3495                                            | Install‚      | Update          | 09/11/2021 08:29   
Package_for_KB5007154~31bf3856ad364e35~amd64~~6.3.1.3515                                            | Install‚      | Update          | 09/11/2021 22:35   
Package_for_KB976002~31bf3856ad364e35~amd64~~6.3.1.0                                                | Install‚      | Update          | 27/10/2014 17:21
 
Just reboot the machine again.
Check Windows Update and report the result.
 
1638895815180.png

Weird : After reboot, it is not the awaited KB that got installed (KB5007247) but KB3185331...
Rebooted once more, searching WU if waiting updates...

For information : DISM Package list : here are new installs made since reboot
Code: 
Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20174.1.16                                       | Interm‚diaire | Security Update | 07/12/2021 16:36  
Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.18509.1.4                                        | Install‚      | Security Update | 07/12/2021 16:38

And finally still same package awaiting install ..
1638896602433.png
 
Last edited:
Did some investigation :
windows Event :
System Restore :
Code: 
Échec de la création d’un point de restauration (Processus = C:\Windows\system32\svchost.exe -k netsvcs ; Description = Windows Update ; Erreur = 0x80070422).
Échec de la création d’un point de restauration (Processus = C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\TiWorker.exe -Embedding ; Description = Programme d’installation pour les modules Windows ; Erreur = 0x80070422).

WER :
Code: 
Récipient d’erreurs , type 0
Nom d’événement : WindowsWcpOtherFailure3
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : 6.3.9600
P2 : udom_microdom.cpp
P3 : RtlCreateMicrodom
P4 : 4255
P5 : c000a083
P6 : 0x161d9f31
P7 :
P8 :
P9 :
P10 :

Fichiers joints :

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_6.3.9600_14347849e7dfadb6c30a04f21bde3f8fb74e96_00000000_0abf29f7

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : 4f6958c1-5787-11ec-8083-4c72b98a4783
Statut du rapport : 4100
Récipient avec hachage :

Code: 
Récipient d’erreurs 2219304162176285339, type 5
Nom d’événement : WindowsWcpOtherFailure3
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : 6.3.9600
P2 : udom_microdom.cpp
P3 : RtlCreateMicrodom
P4 : 4255
P5 : c000a083
P6 : 0x161d9f31
P7 :
P8 :
P9 :
P10 :

Fichiers joints :

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_6.3.9600_14347849e7dfadb6c30a04f21bde3f8fb74e96_00000000_16472d91

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : 4f6958c1-5787-11ec-8083-4c72b98a4783
Statut du rapport : 0
Récipient avec hachage : 9ef6e7d59cd201613ecc8d608b103a9b

WER :
Code: 
Récipient d’erreurs 1830164848410881799, type 5
Nom d’événement : CbsPackageServicingFailure2
Réponse : Non disponible
ID de CAB : 0

Signature du problème : 
P1 : 6.3.9600.19991
P2 : Package_584_for_KB5007247
P3 : 6.3.1.16
P4 : amd64
P5 : unknown
P6 : 80070003
P7 : DOQ
P8 : Staged
P9 : Installed
P10 : WindowsUpdateAgent

Fichiers joints :
C:\Windows\Logs\CBS\CBS.log
C:\Windows\Logs\CBS\CbsPersist_20211207175524.log
C:\Windows\Logs\CBS\CbsPersist_20211207172345.log
C:\Windows\Logs\CBS\CbsPersist_20211207170321.log
C:\Windows\Logs\CBS\CbsPersist_20211206222851.log
C:\Windows\Logs\CBS\CbsPersist_20211206214558.log
C:\Windows\servicing\Sessions\Sessions.xml
C:\Windows\WinSxS\poqexec.log
C:\Windows\Inf\setupapi.dev.log

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_6.3.9600.19991_6959fcf32e85889e364f93909c19d4e93daa63_00000000_0f00922d

Symbole d’analyse : 
Nouvelle recherche de la solution : 0
ID de rapport : ae859da9-5788-11ec-8085-4c72b98a4783
Statut du rapport : 0
Récipient avec hachage : 4fd29e1d2ca80b2599660d3ba5efef07


Code: 
Récipient d’erreurs 1788937791211767917, type 5
Nom d’événement : CbsPackageServicingFailure2
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : 6.3.9600.19991
P2 : Package_for_RollupFix_GM
P3 : 9600.20174.1.16
P4 : amd64
P5 : unknown
P6 : 80070003
P7 : DOQ
P8 : Staged
P9 : Installed
P10 : WindowsUpdateAgent

Fichiers joints :
C:\Windows\Logs\CBS\CBS.log
C:\Windows\Logs\CBS\CbsPersist_20211207175524.log
C:\Windows\Logs\CBS\CbsPersist_20211207172345.log
C:\Windows\Logs\CBS\CbsPersist_20211207170321.log
C:\Windows\Logs\CBS\CbsPersist_20211206222851.log
C:\Windows\Logs\CBS\CbsPersist_20211206214558.log
C:\Windows\servicing\Sessions\Sessions.xml
C:\Windows\WinSxS\poqexec.log
C:\Windows\Inf\setupapi.dev.log

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_6.3.9600.19991_1e76b43d3c2b41912a25556c41dcb96ebec6f72_00000000_0f54bcb8

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : ae859daa-5788-11ec-8085-4c72b98a4783
Statut du rapport : 0
Récipient avec hachage : 838d470726c3aa89a8d395716273086d
 
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.
  8. Attach the file <date>_<time>.zip which is on your desktop also.
 

Attachments

Last edited:
Provide the file Fixlog.txt also.
 
You must log in or register to reply here.
Back
Top