Windows update couldn't install

Status
Not open for further replies.
Please try updating Windows, but do not allow your computer to reboot

Now please send me the following logfile ...

C:\Windows\WinSxS\pending.xml

Once you've done that you can reboot, at which point your update will probably fail, but that's OK, the only purpose in attempting an update was to get the pending.xml log
 
Here's the file. Just to note that Windows installed the updates several days ago but i didn't choose "update and restart/shutdown"
pending.zip
 
Can you please send me a new copy of your Components Hive so I can see what changes have been made to it with the latest update attempt.

  • 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.
  • The file will likely be too large to upload here so please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file
 
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.

Next ...

  • Restart the computer.
  • Run the command SFC /SCANNOW in an elevated command prompt and report the result.
  • If it fails, attach a zipped C:\Windows\Logs\CBS\CBS.log to your next reply.

If it fails, please do the following as well ....

  • Please try updating Windows, but do not allow your computer to reboot
  • Now please send me the following logfile ...
  • C:\Windows\WinSxS\pending.xml

Once you've done that you can reboot, at which point your update will probably fail, but that's OK, the only purpose in attempting an update was to get the pending.xml log
 

Attachments

Gary, sorry for appearing longer than expected. I took a trip to grandparent's home for family gathering.

Here's the SFC log:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-09-12 22:32:34.067
Microsoft Windows 10 Build 19043 - amd64
Using .zip script file at C:\Users\asus\Desktop\SFCFixScript.zip [0]
Not using an additional text script file.




AutoAnalysis::
ERROR: File Placement Mode failed to identify destinations for all files and folders.
SFCFixScript.txt
te_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\


Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1_none_6ab72e7ea4dfef1b\dbupdate.bin
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1_none_6ab72e7ea4dfef1b\dbxupdate.bin
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\dbxupdate.bin
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\r\dbxupdate.bin
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\f\dbxupdate.bin

Successfully copied file C:\Users\asus\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1_none_6ab72e7ea4dfef1b\dbupdate.bin to C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1_none_6ab72e7ea4dfef1b\dbupdate.bin.
Successfully copied file C:\Users\asus\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1_none_6ab72e7ea4dfef1b\dbxupdate.bin to C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1_none_6ab72e7ea4dfef1b\dbxupdate.bin.
Successfully copied file C:\Users\asus\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\dbupdate.bin to C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\dbupdate.bin.
Successfully copied file C:\Users\asus\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\dbxupdate.bin to C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\dbxupdate.bin.
Successfully copied file C:\Users\asus\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\r\dbxupdate.bin to C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\r\dbxupdate.bin.
Successfully copied file C:\Users\asus\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\f\dbxupdate.bin to C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\f\dbxupdate.bin.

Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1_none_6ab72e7ea4dfef1b\dbupdate.bin
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1_none_6ab72e7ea4dfef1b\dbupdate.bin
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1_none_6ab72e7ea4dfef1b\dbxupdate.bin
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1_none_6ab72e7ea4dfef1b\dbxupdate.bin
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\dbxupdate.bin
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\dbxupdate.bin
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\r\dbxupdate.bin
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\r\dbxupdate.bin
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\f\dbxupdate.bin
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_10.0.19041.1880_none_294d9e3cbae1ff57\f\dbxupdate.bin
AutoAnalysis:: directive failed to complete successfully.




Failed to process all directives successfully.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 57 datablocks.
Finish time: 2022-09-12 22:32:38.368
Script hash: 18FK7yczzvt8mFe8epa6IJNXj3BbEq1sjYGcIepTYRQ=
----------------------EOF-----------------------
 
Looks like part of the previous fix didn't process, so let's try it again ....

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download the attachment SFCFix.txt and also save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.txt file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.
 

Attachments

Ok here's the new SFCFix log:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-09-13 07:10:07.018
Microsoft Windows 10 Build 19043 - amd64
Using .txt script file at C:\Users\asus\Desktop\SFCFix.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_none_61cafe17eb0be6c0\10.0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_none_ec19a0e4eb255a12\10.0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_none_b21c3a64bdd6da08\10.0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-b..ager-pcat.resources_31bf3856ad364e35_qps-ploc_a2f690030b281236\10.0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_none_f66e4b371f861c0d\10.0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-b..re-bootmanager-pcat_31bf3856ad364e35_none_b71848465845c7f0\10.0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-b..ggertransport-kdnet_31bf3856ad364e35_none_3b9cd4fa538d01b9\10.0.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_none_61cafe17eb0be6c0\10.0.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_none_ec19a0e4eb255a12\10.0.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_none_b21c3a64bdd6da08\10.0.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-b..ager-pcat.resources_31bf3856ad364e35_qps-ploc_a2f690030b281236\10.0.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_none_f66e4b371f861c0d\10.0.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-b..re-bootmanager-pcat_31bf3856ad364e35_none_b71848465845c7f0\10.0.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-b..ggertransport-kdnet_31bf3856ad364e35_none_3b9cd4fa538d01b9\10.0.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_none_61cafe17eb0be6c0\10.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_none_ec19a0e4eb255a12\10.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_none_b21c3a64bdd6da08\10.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-b..ager-pcat.resources_31bf3856ad364e35_qps-ploc_a2f690030b281236\10.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_none_f66e4b371f861c0d\10.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-b..re-bootmanager-pcat_31bf3856ad364e35_none_b71848465845c7f0\10.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-b..ggertransport-kdnet_31bf3856ad364e35_none_3b9cd4fa538d01b9\10.0.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 64 datablocks.
Finish time: 2022-09-13 07:10:07.922
Script hash: t53qHAxKb9B1tOS9fK6fUbExwVTP/13Wv5gJ3Bmb+2E=
----------------------EOF-----------------------



 
In your pending.zip report, there's been a change in the version of one of the files that being flagged as being in error, so we need to look at the Registry settings associated with it.

  • 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.
  • The file will likely be too large to upload here so please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file
 
Gary, I apologize. I think it was last wednesday night that the PC went into "update and restart" option because before that i had had a notif from nvidia saying to update my graphics drive. So when it finished updating and automatically restarted, the windows update also began. And just this morning i left the PC turned on but apparently the battery ran out, it shut down, and when i turned it on again it went into "update and restart". So maybe these are what caused the changes.
Do you still need the COMPONENTS file?
 
Let your computer update if it can. If successful please let me know.

If not, then please send me your Components file.
 
Thanks.

So I take it that Windows failed to successfully update ????
 
I'm sorry to be the bearer of bad news, but I do not believe we're going to be able to trace what is causing your update problems, so what I suggest we do is to attempt to perform an in place upgrade.

The other option is to perform a clean install of Windows.

The advantage of an in place install is that you will keep your personal files, and your Apps, but not any installed programs. You'd have to re-install them. The disadvantage is that an in place upgrade is not guaranteed to work (though it usually does).

The advantage of a clean install is that it is simpler, and more likely to succeed. The disadvantage is you would lose all your personal files, your Apps, and your installed programs.

To do either we'll need to create what's known as an ISO file, which is really just a copy of Windows which can be used to upgrade and repair Windows

Now there are two methods we can use to create the necessary ISO file ....

  • Using Windows Media Creation Tool - this is the simpler of the two methods, and will create an ISO file for W10 21H2. When that is installed on your machine, you'd then need to update to the latest configuration.
  • Using UUP Dump - this is slightly more complicated, but you can create an ISO file for W10 21H2 which comes with all the latest updates pre-installed. So when installed your machine would be up to date.

So what I'd like to know is ....

  • Would you prefer to perform a clean install, or an in place upgrade ?
  • If the latter. do you feel confident that you can attempt to perform it ?
  • If so, which method would you prefer to create the necessary ISO file ?

Please be aware ....

Performing an in place upgrade is not without risk, and although it is usually reliable, there is no guarantee that will be the case with your machine, and because of that it would be best if you could create a System Image to external media, that we can recover from if things go awry.

I know you have Macrium Reflect, and that earlier you were having problems creating a backup with it ........ is that still the case, or can you now create one on external media ?


When I know what you want to do, I will provide you with appropriate instructions.
 
It is now 9 days since my last post and I have not heard back from you ....... do you still need my help ?

If I have not heard from you within 24 hours I will presume you do not, and will close this topic.
 
Due to lack of activity.

THIS TOPIC IS NOW CLOSED
 
Status
Not open for further replies.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top