Odd black registry update after start up

I installed updates on my tower last night for the first time since late June of this year. It included some Microsoft Security Essentials definition updates, a bunch of the generic security updates. IE11 security updates, and MS Office 2007 suite security updates. I downloaded and installed everything, rebooted, and wen on with my night like normal. Everything updated and continued running like normal. When the computer came back online it rand the blue "configuring windows updates" screen that anyone with Win7 has seen. Everything was fine. Shut it down last night and turned it on today. The Asus screen came up like normal, than the Windows loading bar for 2 seconds before it normally goes to the log on screen. Except today it didn't go to the log on screen. Went to an all black screen with white lettering similar to the old dos screens. The messege was large and read something along the lines of "Update operation xxxx of 2292....C:\Windows.....\registry\curr..."
I've long been a MS pc tech, network admin, imaging and deployment tech for multiple companies. I've never in my life seen Win7 update this way. I've not noticed any issues with my PC today after I seen this. I'm using it right now to write this post. No security threats have been found, nothing deleted, hijacked, or acting odd in the slightest. I basically just want to make sure this was a legit update from Microsoft. I've been working in Window's since the first NT platform and I still don't like having to modify personal or client registries because one miss key and you no longer have a PC. Has anyone encountered this or am I worried over nothing?

Edit: Win 7 Home Premium x64, AMD FX-8350 on Asus board.

Hi:

Until someone more expert comes along, trying to install 5 months worth of patches all at once sounds like a recipe for problems.

If this were my system, I would probably roll back to a System Restore Point before attempting all of that and then try again, in stages (Windows Security Patches first, and saving .NET Framework patches for last).

If that doesn't resolve the issue, you might want to start with the advice in this tutorial:
Windows Update Posting Instructions
And then create a new post in the Windows Update section?

OTOH, if you have been using this box for > 5 months unpatched, then perhaps you are in the right place, as it's certainly possible that you could be infected.
We would need to wait for someone more expert in these matters to advise you as to how best to proceed.

Just a thought,
MM

I see the same - usually after a .NET framework update or any update the makes file/ registry changes on boot as those changes cannot be made once Windows has loaded and the files are in use.

I often see registry changes on boot after applying windows updates if I enable a certain tool that monitors registry changes on boot.