[SOLVED] Unable to finish updates, reverting changes.

NumberFiveee

NumberFiveee

Well-known member
Joined
Dec 27, 2019
Posts
62
Hello Sysnative peeps,

Recently we changed some machines on a client, some were cloned, others were installed from scratch..
All the cloned machines are now unable to be updated..

All the cumulative updates from August until now always fail (Win10 21H2 is the version on the PCs)..

The updates install, and after reboot, upon reaching 97% I get the message: "Unable to finish updates, reverting changes." (always at 97%)..
Ran DISM, SFC, all the standart stuff, to no avail..

Ran SFCFix, came back clean..

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-10-18 15:45:33.357
Microsoft Windows 10 Build 19044 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2022-10-18 15:58:53.691
----------------------EOF-----------------------

I've attached the CBS logs from 1 of the machines..

Also the ComponentsScanner report

ComponentsScanner Version 1.5.1.0 by sysnative.com
Windows Version: Windows 10 21H2 x64 (10.0.19044.1826)
Start time: 2022-10-18T16:41:57
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 81815
Number of values: 313060

==== Critical Errors ====
None

==== Corrupt Key Names ====
None

==== Corrupt Value Names ====
None

==== Corrupt Value Data Type ====
None

==== Corrupt Value Data ====
None

==== Repair Log ====
No possible repairs

==== Warnings ====
None


Storing 0KB in C:\Users\Contabilidade\AppData\Local\Sysnative\ComponentsScanner

Finish Time: 2022-10-18T16:42:18. Corruption scan time: 10,5640507s
===========================EOF===========================

Maybe if I can solve one, I'll be able to solve the rest..

Would appreciate some help.

Kind Regards.
 

Attachments

Hi,

Open an elevated command prompt and run the following commands and post the result.
Code: 
Diskpart
list disk
select disk 0
list partition
 
Good day Maxstar,

Really sorry, forgot to update..
Machines in question were having some other weird issues, so we ended up bitting the bullet and formating all of them...

Thank you anyway..
Feel free to close the thread..
 
Hi,

Thanks for letting us know, it seems there was a problem with the system partition that causes the rollback. I will mark this topic as solved... (y)
 
I'm not able to edit the first post, so I'll post bellow.
Same problem, a cloned machine fails to installed cumulative updates:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-11-17 15:04:59.442
Microsoft Windows 10 Build 19045 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2022-11-17 15:05:31.500
----------------------EOF-----------------------


ComponentsScanner Version 1.5.1.0 by sysnative.com
Windows Version: Windows 10 22H2 x64 (10.0.19045.2251)
Start time: 2022-11-17T15:04:24
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 77424
Number of values: 268426

==== Critical Errors ====
None

==== Corrupt Key Names ====
None

==== Corrupt Value Names ====
None

==== Corrupt Value Data Type ====
None

==== Corrupt Value Data ====
None

==== Repair Log ====
No possible repairs

==== Warnings ====
None


Storing 0KB in C:\Users\ffilipe\AppData\Local\Sysnative\ComponentsScanner

Finish Time: 2022-11-17T15:04:44. Corruption scan time: 9,6994364s
===========================EOF===========================
 

Attachments

Hi,

1. Open an elevated command prompt and run the following commands.
2. Replace 0 with the actual number for the HDD/SSD where your Windows is installed
Rich (BB code): 
Diskpart
list disk
select disk 0
list partition
3. Post the result in your next post.
 
Last edited:
Thank you for the quick reply..

Diskpart image attached..
 

Attachments

  • diskpart.png
    diskpart.png
    7.9 KB · Views: 11
Hi,

Could you please post a screenshot of diskmgmt.msc as well.
 
Last edited:
It seems this system was initial installed with a MBR layout, and is later converted to GPT I guess. Can you confirm that?
 
Honestly I don't know..
We cloned the machine, after that we rebuilt the boot partition to allow the OS to boot..
Not sure if it was MBR prior to that..
 
Okay, let's run FRST to look at the BCD data.

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link
  • Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  • Right-click to run the tool as administrator. When the tool opens click Yes to disclaimer.
  • Note: Ensure that the List BCD check box is checked at the bottom of the form within the Optional Scan area.
    637796067a7b1-list-bcd.png
  • Press the Scan button.
  • Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
  • Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.
 
As expected, this issue is related to the BCD. So we need to restore the EFI bootloader.

Rich (BB code): 
ATENÇÃO: ==> Não foi possível acessar BCD.  -> The boot configuration data store could not be opened.
NÆo ‚ poss¡vel encontrar o dispositivo de sistema pedido. > The requested system device cannot be found.

==================== BCD ================================

1. Open an elevated command prompt and run the following commands.
2. Replace 0 with the actual number for the HDD/SSD where your Windows is installed.
Rich (BB code): 
Diskpart
list disk
select disk 0
list partition
list volume
3. Post the result in your next post.
 
Maxstar said:
As expected, this issue is related to the BCD. So we need to restore the EFI bootloader.

Rich (BB code): 
ATENÇÃO: ==> Não foi possível acessar BCD.  -> The boot configuration data store could not be opened.
NÆo ‚ poss¡vel encontrar o dispositivo de sistema pedido. > The requested system device cannot be found.

==================== BCD ================================

1. Open an elevated command prompt and run the following commands.
2. Replace 0 with the actual number for the HDD/SSD where your Windows is installed.
Rich (BB code): 
Diskpart
list disk
select disk 0
list partition
list volume
3. Post the result in your next post.
Click to expand...
As requested:
 

Attachments

  • diskpart2.png
    diskpart2.png
    17 KB · Views: 7
Original machine was a Fujitsu..
The dell recovery partition is a remnant from the cloning process..
I'll try this method and let you know..
 
I followed the steps on the link you've provided, it showed the bootrec /fixboot command has been completed successfully.

Upon trying to update again, same symptom occurs (Update starts to install, pc reboots, goes to 30%, reboots again and upon reaching 97% messagem switches from updating to UNABLE TO UPDATE, REVERTING CHANGES).

-------------- EDIT ---------------
I think I missed a final step on the link.
I'll try it again and update.
 
Open an elevated command prompt and run the following command and post the result.
Code: 
bcdedit
 
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