RTM/GA or Insider - What are you going to do?

dencal said:

Wyn...If your update shows, but there is no movement indicating it is downloading, leave it running.
Then do as you state above with one exception,you must click STOP, as your updating is already alive, all you are doing is giving it a kick start, it should immediately go back to running again without the need to click restart.
Then go back to your Updating in Services, turn off and restart, then try downloading.

Ain't no way I'll ever click on Stop again, Dencal! I clicked on Stop, rather than Restart and Update no longer worked for me. From day before yesterday until this afternoon; frozen on 0% isn't something I ever want to repeat again! I checked periodically to see if wauserv had started running again and it wasn't until an hour or so ago. I was just about to do a clean install . . .

Lappy 17 skipped 10158 and is now installing 10159!

Ztruker said:

Insider - anything else would be boring.

Absolutely! Just look at all the excitement my upgrades (if you can call them that) have given us. :)

Wynona said:

Ain't no way I'll ever click on Stop again, Dencal! I clicked on Stop, rather than Restart and Update no longer worked for me. From day before yesterday until this afternoon; frozen on 0% isn't something I ever want to repeat again! I checked periodically to see if wauserv had started running again and it wasn't until an hour or so ago. I was just about to do a clean install . . .

Lappy 17 skipped 10158 and is now installing 10159!

Wyn...A lot of the problem were caused by M$ releasing the two updates close together, Updating normally being done in sequence,this caused Error 0x80246017.
M$ have since rectified this as your above last sentence confirms by bypassing 10158..

dencal said:

Wyn...A lot of the problem were caused by M$ releasing the two updates close together, Updating normally being done in sequence,this caused Error 0x80246017.
M$ have since rectified this as your above last sentence confirms by bypassing 10158..

. . .again that nasty Microsoft. . .whatever.

Lee said:

. . .again that nasty Microsoft. . .whatever.

An explanation, not a criticism.

dencal said:

Wyn...A lot of the problem were caused by M$ releasing the two updates close together, Updating normally being done in sequence,this caused Error 0x80246017.
M$ have since rectified this as your above last sentence confirms by bypassing 10158..

I know that, Dencal; however, 10159 wasn't even on the horizon when my problems started. Mine were a combination of things, not the least of which was that my Internet speed had dropped from 14.x to 2.79 Mbps. And while trying to fix a problem I wasn't aware of (Internet speed), I pressed Stop instead of Restart. Thus, Lappy 17 spent the next (approximately) day and a half with wauserv stopping instead of an instant Restart.

So, yeah, once everything was back to normal (wauserv got tired of stopping and restarted), the time had passed (Microsoft stopped distro) for 10158 to be downloaded and installed. Naturally, at that time I got 10159.

Bottom line, my problem with Lappy 17 was strictly a comedy of errors! Nothing to do with Microsoft, but most likely had a lot to do with my ISP.

Lee said:

. . .again that nasty Microsoft. . .whatever.

Not this time, Lee, as you'll see from my explanation of what happened with Lappy 17 from start to finish.

BunnyJ said:

Ok.. My plan is the following...(Subject to Change)
1. Continue to test the previews until around mid July and then re-install Win8.1.
2. Upgrade to Win10 from WIn8.1 and drop out of the insider program.

Why?? Well... I just want to live with the OS at that point. If I can use the preview in a VM environment then that would be fine but I want a stable OS to work with from the 29th on.

I hope that clears my plans up.. a bit.

Bunny signing out.

Sounds good to me, Jeff.

I will stay with the Insider Program as well as upgrade Windows 8.1.

Why? Because I like to live dangerously, but not so dangerously that I can't backtrack. :)