[SOLVED] WIN 2011 SBS with possibly destroyed reg

D

DarkLordSilver

Member
Joined
Feb 12, 2014
Posts
9
Location
Wolfwil, Solothurn, Switzerland
Hi All

Since google led me to this forum, I'd like to ask your support, because it seems that there a lot of know-how around these things here.

Ok, here's what I did until now:
- I was investigating a possible issue with WSUS, because the server wouldn't update. When I was about to uninstall the role of WSUS, I discovered that there were no role nor features to disply, I got the error 0x80073712.
- This error led me to further investiagtions; sfc /scannow didn't work at all and I was about to try the System Update Readyness Tool, when I found this Technet Article: Advanced guidelines for diagnosing and fixing servicing corruption
- After the run, I've been digging into the logs, which I attached.
- I learned, that the there were parts of the reg missing: (f) CSI Missing Root Key 0x00000002 HKLM\Components\CanonicalData\Deployments
- I loaded the Hive from the components file, but it's near empty, no subfolders at all, just some 4 Keys in the top folder. That's where I'm still at.
- My colleague, who was working on this issue last summer (!) did not entirely know, what he did at this time. I found some older Messages, that show a language pack issue and it might be, that he installed said pack and also the lastest patch rollup from MS. The CBS dir is about 6 (!!?) GB in size, one file is 2 GB+ another is 1 GB+ , no idea where this madness comes from, I can't open them, nor copy them. Most of the files are 100 MB+. Does it make sense to upload these too?

View attachment SUR Logs.zip

There should be a pretty much decent backup history, so it should possible to restore an older hive file from like 8 months ago. The questions I have: Is it even possible?

Best regards,
Pesché




 
Hello Pesché, welcome to Sysnative!

Since google led me to this forum, I'd like to ask your support, because it seems that there a lot of know-how around these things here.
Click to expand...

You've come to the right place! But I'm afraid I have some bad news for you.

Code: 
(f)	CSI Missing Root Key	0x00000002	HKLM\Components\CanonicalData\Deployments

The CSI Missing Root Key error can either be relatively simple to fix, or mean your registry is damaged beyond repair. In this case, this problem is simply unsolvable.

There should be a pretty much decent backup history, so it should possible to restore an older hive file from like 8 months ago. The questions I have: Is it even possible?
Click to expand...

I'm afraid not. The components hive contains information about the Windows components installed on your computer and information gets added every time a new update is installed. If you use a hive from 8 months ago, when you've installed updates since then, there will be a mismatch in the data and Windows will get very confused.

As much as I hate to say it, the only way you're going to be able to fix this is if you reinstall Windows.

Sorry I couldn't have been of more help, but there isn't any other option available to us.

Tom
 
Hi Tom, thank you very much!

I was afraid to hear that, but that's what I expected. Since the customer wasn't able to install any updates since back then, when the problem was seen at first, we'll give it a shot with the old hive. But I don't expect it to work, but maybe we're lucky. The fact, that it's a SBS packed with 3rd party software justifys the effort. For the reinstall, i'd say ~80 hours+ in total.

I'll keep you up to date, we have to see when we can do the hive restore.

Pesché
 
Hi Pesché,

Wow, 80 hours is a lot of work! I understand why you want to give this a shot now! If you do go down this route, I suggest you run the System Update Readiness Tool and post the log before attempting to update.

Tom
 
Hi Tom

Yes, that's indeed a lot. I already prepared a migration scenario this morning, it won't be a walk in the park. There are 3-4 business apps on the server as well, and since it's a SBS, everything else too.
The output of the SUR tool stays the same as attached above. -> CSI Missing Root Key is the only entry, because everything below is gone, SUR doesn't even know about it.
When we suceed with the hive restore, i'll run SUR again and post it.

Pesché
 
Hi Pesché,

I don't envy you having to do that! I just hope the migration goes smoothly.

Sorry for the confusion, I meant run the SURT after swapping the hives.

Tom
 
Hi Pesché,

Thanks for keeping me posted, but I'm sorry to hear that! Good luck with the reinstallation!

Tom
 
Hi guys

I recently did the in-place migration. It went pretty smooth. The SBS migration scenario requires the execution of some gathering tools, which made me shiver, but they were running without any problems. Converted the SBS to an VM, reinstalled the hardware with a new SBS instance, migrated from the VM back to the hardware and added another hardware server to the environment.

The only fight i had, was to uninstall the exchange on the old instance. It's nessesary, so you don't have any corpses in your msx-closet. But the worked out after some ugly powershelling.

Thx for the help and see you around here ;)
 
Hi DarkLordSilver,

Thanks for posting back, and I'm glad everything went smoothly! Fingers crossed everything will be fine in the future but if it's not then you know where to come!

Tom
 
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