You're missing the point, osLoaderDuration appears to be an atomic item with no further details available. _*That*_ is the problem.
I am most probably missing the point
, but still you decided to NOT follow the "standard" set by MagicAndre (which is the only one that I know that may read and understand a trace and the one that actually "invented" this approach to troubleshoot this kind of issues).
So, you are also missing it
If MagicAndre asks for a full trace, unless you know more than him on the specific topic, you should provide him with a full trace, then do whatever tests he may suggest.
Otherwise, logically, you would have been capable of solving the issue by yourself.
More or less we are within the "common sense advice" points #f.:http://reboot.pro/to...82-board-rules/
Does this provide us with any clues as to what to try next? Check the full screenshot above, looks like the customer may have nuked everything actually.
The OP seemingly admitted having deleted the WinRE.wim:http://www.zipmagic....t=52&p=109#p107
so IMHO not really a "surprising" output of reagentc /info.
Until he procures a copy of WinRE.wim (from a backup, an install DVD or a downloaded .iso) there is nothing that can be tried next.
Once it has it, it should be just a matter of running reagentc setting the WinRE.wim location properly:http://technet.micro...y/hh825204.aspx