The machine runs build 1607 on a metered connection.
Twice recently, the machine has suddenly stopped, had to be rebooted. Each time the Windows Event log just reported the machine had restarted after an unexpected stop.
The windows update log has 10,164 lines. The first 61 lines look like this ...
EventTrace, Header, 0, 2, 0, 0, 0, 0, 0x0000000000000000, 0x00000004, 0x000018A8, 0, , , {00000000-0000-0000-0000-000000000000}, , 131583436993858259, 615, 0, 4096, 83951626, 14393, 1, 131583458677391386, 156250, 128, 0x11002009, 34, 1, 8, 14195, 1995, 0x9, 0x6, 131583434544906821, 1948614, 131583436993858259, 0x1, 0, "WindowsUpdate_trace_log", "C:\Windows\Logs\WindowsUpdate\WindowsUpdate.20171221.092819.369.169.etl"
EventTrace, BuildInfo, 0, 2, 0, 0, 66, 0, 0x0000000000000000, 0xFFFFFFFF, 0xFFFFFFFF, 0, , , {00000000-0000-0000-0000-000000000000}, , 131583436993858259, 0, 0, "14393.953.amd64fre.rs1_release_inmarket.170303-1614"

The remaining 10,103 lines are copies (except "clock-time") of this:
Unknown, 119, 119, 0, 0, 0, 0, 0, 0x0000000000000000, 0x000001B4, 0x00000810, 0, , , {00000000-0000-0000-0000-000000000000}, , 131583458354926936, 0, 0, "Unknown", "", "Unknown( 119): GUID=e62b40d0-122f-3ac6-8b50-0b2c053df757 (No Format Information found).", "", "", {e62b40d0-122f-3ac6-8b50-0b2c053df757}, "119", "", 0, "", "", "1601-01-01T00:00:00.000000000Z", {00000000-0000-0000-0000-000000000000}

And BTW, "clock-time" isn't a Unix timestamp, how to convert it to a human-readable datetime value?
Any ideas?
The laptop uses Win 10 just as an OS---no Microsoft browsing, email or office software runs on it. Do i need to move this laptop to an unmetered connection to allow an update to 1709?

Thx.