Windows server 2019 Fail Updates
- Thread starter Zenkuh
- Start date
- Status
- Aug 13, 2021
- 3,338
The Software hive supplied has a problem loading due to a mismatch between its primary and secondary sequence numbers.
Can you please supply me with a copy of your Software file from an earlier backup (say a week earlier) ..... you can post me the link to the new file in the PM we've been conversing in.
Can you please supply me with a copy of your Software file from an earlier backup (say a week earlier) ..... you can post me the link to the new file in the PM we've been conversing in.
- Aug 13, 2021
- 3,338
Thanks.
The second backup file you posted was a better match than the first (after preliminary checks), and seems to be the same version as your current live server (which simplifies things a lot), however it still has mismatched sequence numbers (which we should be able to fix), so I think we'll be able to use that.
Still got a lot of checks to do on it, and I am going to need to consult with one of my more experienced colleagues (who has done this kind of thing before), so it may be a while before I get back to you. I will be as quick as I can, but can't give any reliable estimate on exactly when it will be.
The second backup file you posted was a better match than the first (after preliminary checks), and seems to be the same version as your current live server (which simplifies things a lot), however it still has mismatched sequence numbers (which we should be able to fix), so I think we'll be able to use that.
Still got a lot of checks to do on it, and I am going to need to consult with one of my more experienced colleagues (who has done this kind of thing before), so it may be a while before I get back to you. I will be as quick as I can, but can't give any reliable estimate on exactly when it will be.
- Aug 13, 2021
- 3,338
Having some problems fixing the mismatched sequence numbers (usually it's a pretty easy fix), so it's going to take a bit longer than I thought to get back to you.
Sorry about the extra delay, I will get back to you just as soon as I can.
Sorry about the extra delay, I will get back to you just as soon as I can.
- Aug 13, 2021
- 3,338
Just to keep you in the loop, and to let you know that we haven't forgotten you.
We've now fixed the mismatch sequence number problem, and I'm now waiting for advice from one of the most experienced helpers, on how best to use what we've got.
There are several ways in which we can use the repaired SOFTWARE hive from your backup, but all have advantages and disadvantages, and none are a perfect choice, so it's a matter of which is likely to minimise the chances of any possible knock on issues.
We've now fixed the mismatch sequence number problem, and I'm now waiting for advice from one of the most experienced helpers, on how best to use what we've got.
There are several ways in which we can use the repaired SOFTWARE hive from your backup, but all have advantages and disadvantages, and none are a perfect choice, so it's a matter of which is likely to minimise the chances of any possible knock on issues.
- Aug 13, 2021
- 3,338
Sorry to have kept you waiting so long. As I said in my last post, I wanted to consult one of my more senior and experienced colleagues.
Sadly he has not been present on the forum, so I've been unable to do so, so at this point, rather than keep you waiting around, I think the best way forward is to explain the options available to us, and let you decide which one you'd like to follow.
1st option ... You restore your server using the same backup as the one you gave me the 2nd Software hive from. We can then (if necessary) replace the Software hive from that with the modified Software hive we've created.
The advantage of this option, is that the Software hive we've modified will "synchronise" exactly with the rest of the Registry, since both were essentialy created at the same time, so there are unlikely to be any "knock on" problems to deal with.
Disadvantage being that your server will not reflect any changes you may have made to it since that backup was created.
2nd option ... you provide me a copy of your Current Software hive, and I strip the CBS hive from the modified hive we've created, and use that to patch your current hive, which we can then use to replace your current one.
Advantage of this option, you do not lose any changes made to your current server since the last backup, and we have minimised (as much as we can) any chances of lack of synch between our patch and the host Registry.
Disadvantage being that minimised does not mean removed, and there may be differences between the two which may cause knock on errors which we may (or possibly may not) be able to resolve.
3rd option ... I provide you with the Software hive we've modified, and you use it to replace the Software hive on your live server.
Advantage of this method is it is quick and simple.
Disadvantage being that because we're replacing more keys, there's an increased chance of a lack of synch with the patch and the host Registry, so the chances of knock on problems increases.
Sadly there is no "perfect" solution. As things stand, your whole CBS hive is absent, and there is no way to repair it, other than to patch it with a replacement from an earlier backup, and doing that involves a fairly unpredictable element of possible risk, whatever we choose to do.
So ..... please read through the above options, and let me know which (if any) you'd prefer to take, and then once you've let me know, I can provide you with instructions on how we'll proceed.
Sadly he has not been present on the forum, so I've been unable to do so, so at this point, rather than keep you waiting around, I think the best way forward is to explain the options available to us, and let you decide which one you'd like to follow.
1st option ... You restore your server using the same backup as the one you gave me the 2nd Software hive from. We can then (if necessary) replace the Software hive from that with the modified Software hive we've created.
The advantage of this option, is that the Software hive we've modified will "synchronise" exactly with the rest of the Registry, since both were essentialy created at the same time, so there are unlikely to be any "knock on" problems to deal with.
Disadvantage being that your server will not reflect any changes you may have made to it since that backup was created.
2nd option ... you provide me a copy of your Current Software hive, and I strip the CBS hive from the modified hive we've created, and use that to patch your current hive, which we can then use to replace your current one.
Advantage of this option, you do not lose any changes made to your current server since the last backup, and we have minimised (as much as we can) any chances of lack of synch between our patch and the host Registry.
Disadvantage being that minimised does not mean removed, and there may be differences between the two which may cause knock on errors which we may (or possibly may not) be able to resolve.
3rd option ... I provide you with the Software hive we've modified, and you use it to replace the Software hive on your live server.
Advantage of this method is it is quick and simple.
Disadvantage being that because we're replacing more keys, there's an increased chance of a lack of synch with the patch and the host Registry, so the chances of knock on problems increases.
Sadly there is no "perfect" solution. As things stand, your whole CBS hive is absent, and there is no way to repair it, other than to patch it with a replacement from an earlier backup, and doing that involves a fairly unpredictable element of possible risk, whatever we choose to do.
So ..... please read through the above options, and let me know which (if any) you'd prefer to take, and then once you've let me know, I can provide you with instructions on how we'll proceed.
Good morning,
I think we will go with the 1st option by restoring an old version of our VM.
I have a second VM which seems to have the same problem, can we see together if it is "easily" repairable or if I need to restore an old Backup as well?
Perhaps you prefer that I open another topic for this ?
I think we will go with the 1st option by restoring an old version of our VM.
I have a second VM which seems to have the same problem, can we see together if it is "easily" repairable or if I need to restore an old Backup as well?
Perhaps you prefer that I open another topic for this ?
- Aug 13, 2021
- 3,338
Since I last posted, the colleague I was talking about has had the chance to look at things, and has made the following observation ...
"Since your Software hive was corrupted and not able to load, then it would not be able for it to "update" and therefore it's likely that we can replace your current Software hive with the repaired backup Software hive without any problems."
I leave it to you whether you want to attempt that or not.
If we did, then we would of course create a backup before we made any changes, so that we can restore to it if unexpected problems do occur.
"Since your Software hive was corrupted and not able to load, then it would not be able for it to "update" and therefore it's likely that we can replace your current Software hive with the repaired backup Software hive without any problems."
I leave it to you whether you want to attempt that or not.
If we did, then we would of course create a backup before we made any changes, so that we can restore to it if unexpected problems do occur.
- Aug 13, 2021
- 3,338
OK, so please do the following ....
First .... before doing anything, backup your machine, as a precaution in case of unforseen problems occurring.
Next .... once you've created a backup ....
Next ...
Next ....
First .... before doing anything, backup your machine, as a precaution in case of unforseen problems occurring.
Next .... once you've created a backup ....
- Download SOFTWARE.ZIP and save to your Desktop.
- Right-click on it and select Extract all....
- Make sure the Show extracted files when complete is checked and click Extract.
- You should now have the SOFTWARE file that we will be using to replace your current one.
Next ...
- Navigate to C:\Windows\System32\config
- Right-click on the current SOFTWARE file and select Rename.
- Rename it to SOFTWARE.old
- Note .... If you get an error that the file is in use, reboot your computer and then try again.
- Take the file from the SOFTWARE folder on your desktop and paste it into C:\Windows\System32\config
Next ....
- Click Search button and type Command Prompt
- From the results, right click on the Command Prompt icon, and select Run as administrator
- A Command Window will open.
- Copy paste the command below into it, then press Enter
- Dism /Online /Cleanup-Image /RestoreHealth
- Once DISM has finished running ...
- Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
- If the file is too large, upload it to a file sharing service, and post me the link.
- Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
- Status
Has Sysnative Forums helped you? Please consider donating to help us support the site!