You have to understand what decades of a blue E has done to the minds of the simple users, the ones that the rest of us wonder how they ever managed to turn a computer on. To them, the blue E means the internet.

No it doesn't ... Those people still install the internet from their AOL CDs. While the rest of the middle ground have been quietly moved to Chrome by one of the myriad of Java updates.

MS wanted/needed to make a break from the past, and to distance their new baby from the stigma that is the 'Blue E' ... Which they just failed at completely IMO.

Anyone know how to get Windows 10 to update immediately? I've checked for updates and it often says "We found updates, we'll download them later."

Uh, no. Now is good for me, thanks. But I can't seem to find the option to force it to download now.

I'm on the fast ring, with "Delay Updates" disabled.

Anyone know how to get Windows 10 to update immediately? I've checked for updates and it often says "We found updates, we'll download them later."

I've got 3 Win 10 VMs here at the office. One I'd left running and it had it (10158) ready to go yesterday morning. I just fired up one of the others, hit check for updates, and it came up with another newer build (10159) yesterday.

Maybe your check fell in between the build updates that were oddly (emergency?) close together?

I've got 3 Win 10 VMs here at the office. One I'd left running and it had it (10158) ready to go yesterday morning. I just fired up one of the others, hit check for updates, and it came up with another newer build (10159) yesterday.

Maybe your check fell in between the build updates that were oddly (emergency?) close together?

Odd version number too?

Since one of our lab machines won't upgrade from 10130 (failed 3 times), I'm experimenting with this now:
http://www.zdnet.com/article/how-to-turn-your-windows-10-upgrade-into-an-iso/

Fairly quick and easy way to create a current ISO.

Yeah, on TenForums that tool has been around for quite some time.  It sucks an iso out of the erd mess.  I ran it once and it worked.  What kills me on this laptop is doing stuff in a VM with all the file clutter when you first try to update or whatever, stuff barely runs.  Once I can clean out all the rubbish and defrag the VM and the host OS file system, then stuff is slow but at least it doesn't crash or stutter.  But it's too painful to really do anything.

A Windows 7 Vista or Linux a little bit different story.  The VMs run well enough to try them out a bit.  The HD in this is only a Sata II so that tends to make VMs slog. 

Build 10159

Bit late on that news ... Scroll ^up^ to 7:45 this morning.

Yet another updated version was pushed out to the "fast ring" today, build 10162:

Hi everyone,

We have one more surprise for you this week – Build 10162, releasing to the Fast ring.

We’re at the point in the development of Windows 10 where nearly every build is getting out to our internal rings, and passing the criteria for release to Windows Insiders. We’re focused at this point on bug fixing and final polish, so it’s much easier for each build to get all the way through than earlier in the cycle when we’re adding big new features. So now we find ourselves in a great situation, with an abundance of build candidates. We’re deciding how long to let each build stay with Windows Insiders so you can really exercise them and send feedback on any problems that you’re hitting. I know many of you have said you’d love daily builds, but it is actually important sometimes to get a few days on a build so that all of the code that does deferred work (like OneDrive sync, search indexing, background updating, etc.) can run and we can get feedback and error reports.

We just released Build 10159 with our new wallpaper and logon UI on Tuesday, but this is a holiday weekend in the US and we thought that some of you might want to get an even fresher build on your PCs to play with over the long weekend. Build 10162 is another great one. In fact, our testing and internal telemetry metrics show it has better reliability, performance, battery life, and compatibility than any Windows 10 Insider Preview build so far.

We haven’t forgotten about Windows Insiders in the Slow ring either – we’re looking at Build 10162 as a candidate and unless we see any issues emerge in the Fast ring we’ll look to publish it to Slow (with ISOs) early next week.

We’re getting close now! We hope you’re as excited as we are about how Windows 10 is shaping up.

Thanks,
g

Anyone else have problems with Windows Update saying "Downloading updates 0%" forever? Is the download so huge that an hour later it is still at 0%?

I finally managed to get my netbook to show some progress, but it interrupted itself and said it couldn't install some updates because some updates were being installed. Then it said it might help if I reboot. I rebooted, and Windows Update told me the same thing again, so this time I clicked retry and now it says "Preparing to install updates 35%" and has been "stuck" there for quite a while.

But my VM with Windows 10 is still at 0% and has been for about an hour.

EDIT: Just after I submitted this, I went to the VM and clicked around a bit and went back to Windows Update and it refreshed the screen and now it's saying 24%. So maybe it just sometimes has problems updating the progress bar or percentage/text while it's doing its thing.

Build 10162 just released to fast ring

Really, they have no fun anymore over there.
They couldn't name it "Gollum's Ring"?

Has anyone else had activation issues with 10? All 5 of mine were activated up to build 10158, but even after switching to the updated key, neither build 10159 or 10162 will activate for me.

It doesn't complain about the key which is posted everywhere and therefore presumed valid. It just keeps saying "Windows can't activate. Try again later".

I'm running four 10 pros, and one 10 home. some are signed up (and verified) for the Windows Insider Club, some are not, and one is still using a strictly LM account ... And nobody will activate with any of the TP keys I've seen to date.


Ideas?

I wonder if some people will have to threaten to sue Microsoft to keep the Win 10 virus out of their computer or whether it won't take no for an answer. Did Microsoft really learn their lesson with Windows 8? If it is going to be free for a year, does that mean they expect it to be buggy for that long?

Well, I take exception to using the word "virus" even in sarcasm, because viruses don't normally run your whole computer with real software!

I'd settle for any of the other slants of MS just being slimy and so on. I really don't like their hubris of "haha, we'll wreck the comps of the piddly little home consumers (eew), make them do implicit forced bug testing for free, and 30,000 BSOD's and lost data later, oh look, it's nice and safe for our Valued Business Customers!"