I have this exact issue, restarted numerous times (both manually and scheduled) and system comes back up within 2 min as 180703.
EDIT - I do have the folder "windows.old" and it is NOT empty, contains 2 directories: "Cleanup" and "WINDOWS", both populated. Also, the "pause" updates is no longer available...
I am having the same issue. I do not have a Windows.old folder. I do have a bootable ISO for build 17713 that I created prior to hitting Restart to complete the update. Can I use this to get the update? should I use the bootable ISO or just run the update from Windows using the ISO itself?
I recently had this show up when trying get over the 17692.1000 to 17692.1004 hump. The only way I could fix my problem was by doing the download and install using the Windows Update MiniTool (WUMT). It got stuck on the restart needed item. Neither the built-in nor the downloadable .CAB file for troubleshooting Windows Update, nor following the manual WU reset tutorial got me past this. Once again: WUMT did the trick. Here's my Windows Enterprise Desktop blog post on that topic: Dell Venue Pro 11 7130 Strange Upgrade Issues.
HTH,
--Ed--
Last edited by EdTittel; 23 Jul 2018 at 15:00. Reason: Shorten URL
I ran the Download and Update using this tool. In the log it shows: Downloading updates: Succeeded with errors (0x00240003). What do I do with that? Also what location it's downloading into?
I tried it again. This time I said download only. Then I did Download and Update. It did start update. I wasn't watching what it was doing, but when I got back to the computer it was a message saying Update complete, restart. I did and nothing got chnaged. Everything is the same. Should I keep trying?
Probably time for a complete Windows Update reset. There's a TenForums tutorial for that: Reset Windows Update in Windows 10. Takes a while to work through, but almost always does the trick. If that fails, it's time for an upgrade repair install. There's a tutorial for that, too: Repair Install Windows 10 with an In-Place Upgrade.
HTH,
--Ed--
<Probably time for a complete Windows Update reset
That is what I did, and it helped. Thanks for help, everyone.
Quote