I've just checked the MRT.log file and found that all was well. However, like mentioned above, the Reliability History says that MRT.exe crashed. I then ran MRT.exe manually (quick scan), and all was well, including the log file. Strange...
However, this was with the 1607 build updated earlier today; I'm still awaiting 1703.
MRT.exe crash here as well, v1703.. in fact I see 3 errors in Event Viewer after this update.
Thanks @Brink
Updated two computers to 10.0.15063.138, no issues and was really fast to update.
I see NO traces of any MRT errors, people have reported, anywhere in any of my systems.
I do however still get errors for MicrosoftEdgeCP.exe and Microsoft.BingWeather errors, and some other COM object errors. I guess I have to study these and see if there is a fix to be found. I bet it's a permission or a configuration error as usual. It's a minor glitch that does not affect overall system stability. I have fixed these before, into a state where I receive no errors at all in Event Log, without removing nor affecting the application functionalities in any way.
Somewhat odd component cleanup, I usually get 2x100% or 20% and completed, but 9,6%, that is a new.
I have just noticed on the screen, that component store is corrupted, RestoreHealth still does not work.
I have had 3 total lock ups on my desktop since I installed update this morning, this has never ever happened before.
Nothing showing up in Event Viewer except Kernel Power due to reboot
Hi there
For those who have installed CU upgrade / update the next set of cumulative updates seem to be available via normal Windows update.
Cheers
jimbo
Knows issue. See...
Creators update component store shows corruption but unable to repair
Quote
