I honestly thought it would work this way from the start. I had a bugged early Insider build on my system though could not update to a newer one so when full release came out I did a fresh install and went to enter my Win 7 Pro key... Luckily I had a spare SSD around to Quickly, or so I thought, install Win 7 Pro 64bit and upgrade + then swap out to my new 850 Pro 500GB with the clean install to insta-activate it. That Bloody Win 7 Pro install took neigh on 10 hours to get it updated enough that it would Actually consider itself worthy of a Win 10 upgrade... The Win 7 SP1 update was bugged, took a short while to figure that out and find the fix for it etc etc through the night waking up enough to prod the updates to the next step -.-""" And Then... damn Upgrade to Win 10 to absolutely Hours on a Vertex 4 256GB (still pretty damn fast) on a Hex core CPU. Complete Nightmare and waste of time >_< I think MicroShaft should apologise profusely for putting people through that hell for one of their little foibles! Really feel sorry for less tech savy people trying to figure out the Win 7 SP1 update they just successfully installed was not registered as installed etc. That and MS changing the sound driver stack at the last minute, must have been a lot of people with no sound for a while after that. Not smooth, not smooth at all.

I honestly thought it would work this way from the start. I had a bugged early Insider build on my system though could not update to a newer one so when full release came out I did a fresh install and went to enter my Win 7 Pro key... Luckily I had a spare SSD around to Quickly, or so I thought, install Win 7 Pro 64bit and upgrade + then swap out to my new 850 Pro 500GB with the clean install to insta-activate it. That Bloody Win 7 Pro install took neigh on 10 hours to get it updated enough that it would Actually consider itself worthy of a Win 10 upgrade... The Win 7 SP1 update was bugged, took a short while to figure that out and find the fix for it etc etc through the night waking up enough to prod the updates to the next step -.-""" And Then... damn Upgrade to Win 10 to absolutely Hours on a Vertex 4 256GB (still pretty damn fast) on a Hex core CPU. Complete Nightmare and waste of time >_< I think MicroShaft should apologise profusely for putting people through that hell for one of their little foibles! Really feel sorry for less tech savy people trying to figure out the Win 7 SP1 update they just successfully installed was not registered as installed etc. That and MS changing the sound driver stack at the last minute, must have been a lot of people with no sound for a while after that. Not smooth, not smooth at all.

Microsoft broke Win Update on 7, which is why it took 10 hours. I think they've fixed it since then. But it used to use like 90% CPU and go slow as balls.

I honestly thought it would work this way from the start. I had a bugged early Insider build on my system though could not update to a newer one so when full release came out I did a fresh install and went to enter my Win 7 Pro key... Luckily I had a spare SSD around to Quickly, or so I thought, install Win 7 Pro 64bit and upgrade + then swap out to my new 850 Pro 500GB with the clean install to insta-activate it. That Bloody Win 7 Pro install took neigh on 10 hours to get it updated enough that it would Actually consider itself worthy of a Win 10 upgrade... The Win 7 SP1 update was bugged, took a short while to figure that out and find the fix for it etc etc through the night waking up enough to prod the updates to the next step -.-""" And Then... damn Upgrade to Win 10 to absolutely Hours on a Vertex 4 256GB (still pretty damn fast) on a Hex core CPU. Complete Nightmare and waste of time >_< I think MicroShaft should apologise profusely for putting people through that hell for one of their little foibles! Really feel sorry for less tech savy people trying to figure out the Win 7 SP1 update they just successfully installed was not registered as installed etc. That and MS changing the sound driver stack at the last minute, must have been a lot of people with no sound for a while after that. Not smooth, not smooth at all.

it was intended to be but the update haven't been as easy as they think, this is why they used the "B plan" called Media Creator and so... There was also the "Pentium K fail to install" isuue (because of wrong DLL used in the package)... btw the latest insider ***565 cause problem with tool to remove the leak of data on M$ server right now (is this intentional lol?)

Microsoft broke Win Update on 7, which is why it took 10 hours. I think they've fixed it since then. But it used to use like 90% CPU and go slow as balls.

Yup, sounds about right, was chewing on about 45% CPU usage on 6core/12thread Xeon @ 4GHz for hours on end. Glad it is something they fixed for others 🙂

it was intended to be but the update haven't been as easy as they think, this is why they used the "B plan" called Media Creator and so... There was also the "Pentium K fail to install" isuue (because of wrong DLL used in the package)... btw the latest insider ***565 cause problem with tool to remove the leak of data on M$ server right now (is this intentional lol?)

could say that again xD and very happy not to have to do it again (on a laptop a friend is giving me that needs a new HDD and some serious TLC - nice i7 gaming laptop issues aside ^^ )

I couple months back, I had a machine in to fix, and they wanted 7 back on it, so after install, I set it away updating, that night it was still going, so I left it running overnight, the next morning, still updating I had to end installer processes in task manager to get it to move on to the next update, I think it was the Redistribs that were causing the massive hang, ending them started the next updates, which were quick until it hit another redistrib

MS should have done this from the start. Also with OEM copy of Windows 7 that you would get from Dell or HP they allow you to install the OS first then enter the product key. I feel that MS should have made this work the same way.