Well that's a blunder, update installed and prompted for a restart so since the last few updates have somehow asked for a restart even after finishing installation until updates are paused and then resumed so the OS forcefully re-checks and finds everything OK I decide to pause updates after it's done with the initial step before reboot. So the OS then finds the already installed update and decides to start the entire process over, fails and on reboot it complaints the update couldn't be installed because the system was powered off and it's time to just start over from the beginning. Well at least I know not to do that again. Oops. Seems to be some minor fixes going by the Windows 10 update history page, being cumulative though it still takes a while to process since it has to compare against some thousand or so files. Going to be a longer night than I thought though it's a learning experience if nothing else.
Yeah. I'm on the release preview branch so the first cumulative and then the first public update to .42 I think it was had the issue where it listed as still pending. I see now that this is fixed and this entire little attempt to be smart and get that out of the way early since a pause and resume prompts for a immediate update check well that could have been avoided. Didn't expect that to bug the entire process, at least it worked fine during the second attempt and it's now up to date to version 17134.82 EDIT: Well I'm probably not explaining very well, everything is working now but that caught me by surprise. EDIT: Or am I confusing it with 17133.x and it getting a update, well it's after midnight so I'm pretty tired but I wanted to get this out of the way, really hadn't expected a update outside of the usual patch Tuesday once a month routine and even release preview updates are not too frequent anymore.
Yep, 17133.1 and then a cumulative for that and then 17134 as a full new build because errors with something with Windows Update I think. It had a cumulative update before 17134 though with this same issue showing a installed update as still pending, I can't explain at all I guess and just make it sound really confusing at the moment. EDIT: Well that just shows how badly I'm remembering at the moment. EDIT: Which means 17134.5 and it starting this little error (Should just clean install for RS5) then .48 and the error persisting with updates showing as pending (Probably local so something on my end.) and now with .81 it's fixed and all of this could and should have been avoided. Just tiredness I guess, trying to speed it up a bit and it bugged and then all this because I can't remember the details correctly and making a mess of the entire thing trying to recall info that's completely wrong. Well, that too is useful experience. (Well I still can't really explain things well but eh, just have to be more careful when posting in the future.) EDIT: No point making yet another post but that was a really terrible way to turn everything on it's head on this page, making it seem like there's multiple more updates is just confusing and a full cascade of errors and inconsistencies post after post for what started as a incorrect version number, too late now to fix so what a mess I managed to turn this into and it shouldn't have gotten that far at all if I had slowed down a bit more, I can do better. (Well I can stick to reading at least or double checking or something to try and avoid the same thing next time, I found a fun little glitch possibly but yeah the rest was just one error after the next trying to post about it.) EDIT: Guess I can't delete these posts either, might just make it more confusing though well a few more replies as this topics moves along and back on track and this can get buried on a previous page and that's going to be that. (Best course of action probably, just have this entire little episode left behind and forgotten.)