OK, lot's of stuff being flagged in this log, going to take me a while to go through everything and make sense out of what the log is telling me. Will get back to you as soon as I can.
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.
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 ...
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.
Unfortunately we've had issues, which have resulted in the server being rebooted, an now it's stuck in a "Getting Windows ready, don't turn off this computer", "Stopping services" reboot loop.
Due to this issue I'm not able to get into safe mode, only to "Repair Your Computer". Please could you advise me of how to get out of the reboot loop?
It's okay Gary, I tried a few of the more simple fixes with no luck. I've ended up having to restore the server from back-up.
I had to go back to before we started making the change, so I assume it will have undone all the changes we made regarding the updates. Do you want me to run the previous fixes to get us back to where things where, or will it require stating again? (or is it all a cyclical process, so it doesn't really matter?)
If you've done a restore from backup, then we pretty much have to start from the beginning.
However, that does not mean that it's safe to re-run our previous fixes, as they were specific to the conditions reported on your machine at that time, and may not be reproduced in the backup.
So we kinda need to start from the beginning, and see where that leads us. Good thing is, if the same things do crop up again, then I already have things sourced, so producing a new fix tailored to the conditions in the current logs, should be a whole lot easier and faster.
Anyway, let's get started, and see how things go.
So ..... please post me your CBS.log, and please post me a current copy of your Components hive ...
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, if so please upload to a file sharing service.