Broken chain reaction after installing new RAID drive and restoring from backup

We recently installed new Drives into the server RAID array and restored from a backup. This was about a month ago. The first issue we had was that WSUS wasn't working so we attempted to remove the WSUS role but couldn't due to errors that it couldn't find the database. So we changed the GP to let all pcs handle their own update. The next issue we had was that the server kept wanting to restart minutes after the previous restart. After investigating there were several Pending errors showing in the update log. Windows Update Error 80242014. Have tried to remove the Software Distrabution folder, looked for the pending.xml but it doesnt exist/. At this point we started getting .Net Framework Error 1023. Downloaded the .net repair too but failed saying that there is a pending update restart. The same things happened when I tried to repair the SQL database it said it couldn't perform the repairs because there is a pending update restart. Now there are broken processes that is stopping out Exchange from working.
tganusAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

pgm554Commented:
How did you restore from backup?
0
tganusAuthor Commented:
Using Acronis Bootable Media.

The big issue right now is that we can't get the pending updates to go away which is stopping us from using the SQL to repair itself. We've tried dism.exe, tried removing pending.xml(which didn't even exist in out winxsx folder), renaming and deleting the SoftwareDistribution folder, shutting down BITS and wuauserv and clearing the BITS queue.

The broken .Net issue has been resolved so everything is backup and running but the SQL.
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
The broken .Net issue has been resolved so everything is backup and running but the SQL.
What's the error message?
0
tganusAuthor Commented:
They all just list Error Details : Code 80242014
0
tganusAuthor Commented:
So WSUS is fixed and running again, all computers seen and having updates pushed to them. The server is still in the same state for updates through, immediately after every restart it just comes up and says there are updates waiting to be applied and a restart is required. Checking the update history still shows the same 23 updates as Pending and when double clicking on a pending update it lists Error Details: Code 80242014
0
Iamthecreator OMCommented:
Search for the key RebootRequired in
 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\

If found, back up the key and remove it
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tganusAuthor Commented:
Thanks! Finally the server is back to updating like it should!!!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.