Registry Backup

[Dougcuk]

I have been checking out your Registry Backup utility and have a question regarding the restore operation.

I have used the ERUNT registry backup utility for many years and realized that (with Win7) it only rarely included the COMPONENTS registry file - as this hive is not normally loaded when the backup runs. I also understand that your utility includes ALL the registry files in the backup - as it uses the VSC service.

My question is does your program offer any protection or warnings about restoring the COMPONENTS registry file?
I ask this as my research suggests that in most cases restoring an older copy of the COMPONENTS registry will most likely break the Windows Update and WinSxS component store systems. The WinSxS folder and the COMPONENTS registry are inter-locked and have to be considered as an integrated pair.

You can view the discussion on this topic in this thread from the Sysnative forum 
http://www.sysnative.com/forums/windows-7-%7C-windows-vista/11691-restoring-a-backup-of-the-components-hive-what-are-the-issues.html#post85579

DougCuk - Tech Support Engineer - London UK

[Shane]

My question is does your program offer any protection or warnings about restoring the COMPONENTS registry file?
I ask this as my research suggests that in most cases restoring an older copy of the COMPONENTS registry will most likely break the Windows Update and WinSxS component store systems. The WinSxS folder and the COMPONENTS registry are inter-locked and have to be considered as an integrated pair.

No it doesn't give any warning, but you make a very very valid point. Of course depending how long the user goes back even the hkey_local_machine can kill a system if it goes back to far and a lot of changes have been made.

Perhaps a warning should be added when a backup is over a certain age as well? Thoughts?

Shane

[Dougcuk]

I don't pretend to understand all the possible issues when restoring the COMPONENTS hive - but from the answers in the thread I linked it would appear that any updates to the Windows system files could be a potential problem.

The most likely problem situation would be a patch Tuesday update having occurred since the backup was taken.
The other possibility might be a Visual C++ or Net Framework update installed as part of  another application.
All of these will install new files and data into WinSxS and update the COMPONENTS registry. 
I suspect that both could result in problems that might be difficult to fix - but I am no expert on this topic. 

A corrupted COMPONENTS registry file will not normally stop windows from booting or running.
You will only know you have a problem when installing an application or running Windows Update fails.

The safest option when restoring the registry might be to default to keeping the existing COMPONENTS registry file
- as it potentially matches the WinSxS folder and gives the best chance for a functioning system
- and offer the restore of COMPONENTS as a user selected option with warnings.

The staff over at Sysnative.com specialise in analyzing and fixing Windows Update and Component Store corruptions
- so it might be good to ask them for some guidance. My existing thread might be a good starting point
- if you want to clarify the best way to proceed.