With no pending updates, wouldn't have thought there'd be that much difference between Home & Pro.

I'm on Pro and have the latest version.

Did you defer updates?

I have a netbook with Win10 Pro x86 on it ... and it's stuck at v10.0 Build 10240 with no pending updates.  Think I'll have to reinstall that.

On the desktop x64 they are but I've just upgraded the netbook x86 (it doesn't have deferred updates) and it's now sitting at 10586.14 with no pending updates, same as the desktop.

This reminded me to check my netbook. It is still on Build 10240, but Windows update says it has an update available for 1511 10586. It's currently downloading. I'll find out what version number it ends up at when it's done and report back.

Microsoft really needs to stop trying to be "cute".

I opened my laptop this morning to the messages:

• "Hi."
• "We've Updated your computer"
• "All your files are right where you've left them"
• "We have some new features we are excited about" (something like that)

The bad thing?  "Hi" didn't stick around for long.  Neither did the second line.  After I looked up, I saw the third line.  And it stayed there, unresponsive for over 5 minutes!  Thankfully, I knew that I'd told it it could install, so it didn't freak me out too much.  But some people are going bonkers when that comes up, and doesn't give any other information.

Thankfully, I changed it so that it has to ask me in order to restart my computer for installs.  I was notified that it needed to restart, and scheduled it for 3:30 AM.  That sort of straddles the line between leaving it on, and giving them full carte blanche.

That message *did* scare me, however. 

Again, Microsoft needs to stop trying be "cute", and err on the side of being clear.

Microsoft really needs to stop trying to be "cute".

I opened my laptop this morning to the messages:

• "Hi."
• "We've Updated your computer"
• "All your files are right where you've left them"
• "We have some new features we are excited about" (something like that)

The bad thing?  "Hi" didn't stick around for long.  Neither did the second line.  After I looked up, I saw the third line.  And it stayed there, unresponsive for over 5 minutes!  Thankfully, I knew that I'd told it it could install, so it didn't freak me out too much.  But some people are going bonkers when that comes up, and doesn't give any other information.

Thankfully, I changed it so that it has to ask me in order to restart my computer for installs.  I was notified that it needed to restart, and scheduled it for 3:30 AM.  That sort of straddles the line between leaving it on, and giving them full carte blanche.

That message *did* scare me, however. 

Again, Microsoft needs to stop trying be "cute", and err on the side of being clear.

I read a rant on Facebook where someone said he saw those messages and thought his computer was infected by ransomware. e.g., he was expecting something along the lines of "Your files are where you've left them... but you'll have to pay $XXX to get them back!"

I thought he was just trolling for the sake of Microsoft-bashing, since from the very beginning of Windows 10 (and probably Windows 8) Microsoft has been using similar messages during installs/updates. But after reading your experience, I'm starting to feel it's more plausible that he was being sincere (albeit exaggerating somewhat due to frustration).

If you don't like the cuteness, watch out for the new BSOD screen. It shows a sadface emoticon! :P

Quote from: Deozaan on December 22, 2015, 06:09 AM

This reminded me to check my netbook. It is still on Build 10240, but Windows update says it has an update available for 1511 10586. It's currently downloading. I'll find out what version number it ends up at when it's done and report back.

I upgraded it using the 10586.0 ISO and then let it update.

I just finished the update from Windows Update and it's at 1511 10586.36. So now both my Win 10 Pro x64 desktop PC and my Win 10 Pro x86 netbook are at the same version.

Just upgraded a Win7HP x86 system to Win10 x86 using 10586.0 ISO then let it update and it shows v1511 b10586.36 - so go figure 

[attachment 1 not found]

Microsoft Windows 10 active on 200M devices

I wonder how many of the 200 M devices have owners trying to figure out

Just upgraded a Win7HP x86 system to Win10 x86 using 10586.0 ISO then let it update and it shows v1511 b10586.36 - so go figure 

What happened to the "one size fits all" scheme?  It seems every day on Softpedia the Windows 10 news is about some new specialized release.  Or maybe I was behind the door when they abandoned it officially? 

Any tips for upgrading to Windows 10 now?
=> upgrading from 8.1, I'm going try keeping programmes unless advised otherwise.
I've installed all security updates for 8.1 (other updates *not* installed)

TIA 

Any tips for upgrading to Windows 10 now?
=> upgrading from 8.1, I'm going try keeping programmes unless advised otherwise.

Image your drive beforehand

I bit the bullet and told it to 'Download Now, Upgrade Later' ... in my case, Microsoft's definition of 'later' was a bit different from mine.  The download started immediately and when it was finished it said it wanted to restart to perform the upgrade ... WTF!?

So I imaged it before I restarted, not the optimum solution.

Anyway, the upgrade was fine - all installed programs worked after upgrade, (eg. DaemonTools, DOpus, Sony Vegas, Malwarebytes AM, VPN software, etc), even ClassicStart.  I don't have an AV installed apart from Microsoft's.

The only things that screwed up were file associations, it now wanted to use Edge instead of PaleMoon, Reader instead of PDF-Xchange, and a couple of others.

It also had to download a newer video driver but that was all on the hardware side of things.

I bit the bullet and told it to 'Download Now, Upgrade Later' ... in my case, Microsoft's definition of 'later' was a bit different from mine.  The download started immediately and when it was finished it said it wanted to restart to perform the upgrade ... WTF!?

Really? Is that how it works? Is there no backing out at that stage?

Quote from: 4wd on January 07, 2016, 12:09 AM

I bit the bullet and told it to 'Download Now, Upgrade Later' ... in my case, Microsoft's definition of 'later' was a bit different from mine.  The download started immediately and when it was finished it said it wanted to restart to perform the upgrade ... WTF!?

Really? Is that how it works? Is there no backing out at that stage?

No, it just happened to be what that machine did.  I've got two others that i chose the same thing on and they haven't decided to upgrade whether I like it or not.

I made damn sure I chose the right option to start with since I wasn't ready to do it right at that moment.

I just happened to find Murphy waiting around the corner 

Any tips for upgrading to Windows 10 now?

I'd recommend disconnecting your device from the internet once you've downloaded the update. In my experience, it takes forever "Checking for Updates" multiple times throughout the upgrade process when you're connected. I also had problems with failed upgrades which magically resolved themselves when I disconnected the internet connection during my upgrade attempt.

I don't know if that's necessary or if it does any good. All I know is that it helped me get past failed upgrades on two machines. YMMV.

I'd recommend disconnecting your device from the internet once you've downloaded the update. In my experience, it takes forever "Checking for Updates" multiple times throughout the upgrade process when you're connected. I also had problems with failed upgrades which magically resolved themselves when I disconnected the internet connection during my upgrade attempt.

+10 - I've run into that one myself enough times to make it a policy.