Spoken like a true enthusiast Unfortunately most of the people coming here now, don't won't to learn, they just want it to work.
I've been told that using an MSDN serial on the TP would activate and allow a clean install afterwards ?
Now I have Windows 8.1 activated with key via DreamSpark. The question is - to upgrade now to the latest preview version, or it's better to wait 29 July, upgrade first and then do a clean install? I'm writing this because I can't wait for 29 July , so I need your opinion on this.
I've had several friends ask me about going from W7 to W10, and I've told them all to do the upgrade in a couple of weeks so the first round of post-release patches are out, but prepare to do a clean install shortly after. Do the upgrade to make sure your license transfers and register their MSA, then backup and do a clean install because while an upgrade will work, there are always settings that don't cleanly transfer and other cruft left behind -- like a 4gb or so unneeded hidden directory as well as a Windows.old. While you can use DISM to clean and restore, when doing a massive OS upgrade, the clean approach ends up with a system that runs better and easier to troubleshoot because there are no leftovers from a previous install that may or may not be part of the problem. Just common sense if you ask me... T
Even if I upgrade on preview now? That will be cool. By the way I already have downloaded the official Windows 10 Build 10162 ISO and burned to a dvd
for what i have notice upgrade vs clean install is 50- 50 thing some upgrade go excellent with out any issues other go horrible and your force to do a clean install.
Spoken like a person who like to manage his computers and dont want to be managed by them. And knowledge is the best way to do it. Sure, iPhones (and alike) ruined the younger generations. Most of them are button pusher, or little more...
Good point! Theoretically, there should be no difference between Win10 builds progressively installed through upgrading, one on top of the other. And of course, that's because upgrading should just "work" properly otherwise there'd be no sense in Microsoft ever telling anyone to "upgrade" or offering the function, and doubly because these are all builds of the same OS--Win10 on Win10 (instead of Win10 on top of Win7/8)... But there is a big difference, as I discovered yesterday. I can only conclude that the internal "flight" upgrades between Previews are very bugged as a process, and if Microsoft had not made 10162 available as an iso I wouldn't have known just how bugged my upgrades were and would have chalked all of the differences I see between 10162 upgraded from 10159, and 10162 clean installed from the iso, as bugs still present in the build! For instance, in my upgraded installation, the AMD CCC problem resurrected and I could not keep the CCC up--it always crashed shortly after boot and would not come back, no matter what I did to try and correct the problem. I thought it was either a 10162 bug or else a bug in the AMD driver. It was neither. That problem completely disappeared in the clean-installed build! The only thing I can conclude from this is that, again, the Preview "flight" (internal) upgrades have probably *never* worked right/well from the start, which means Microsoft may have been chasing its tail to some extent because of bug reports about problems caused by the upgrade process itself. That's reason enough to discontinue the internal upgrade process moving past RTM and simply release everything in iso format. I'm seeing features here and there that I did not see in the upgrade 10162, and everything runs much faster/better than it did after the internal upgrade to 10162--even after I've installed the same programs and the registry sizes are essentially the same. In the past in both Win7 & Win8, I never could notice any difference between upgraded installations & clean-installed ones, except of course for the fact that right after a clean install the registry is very small and the OS seems snappier because of that--but when I'd reinstall my programs I found things to be just as they were after the upgrade. I never saw these kinds of bugs after an upgrade install! But I was upgrading through iso images, only, unlike the internal Insider Preview upgrades. I hope that moving forward Microsoft goes exclusively to iso format and drops these internal upgrades completely. I sent Microsoft some feedback abut this and I'm certain I'm not alone...
I have ZERO issues upgrading from Windows 8.1 Update 1 with all patches to Build 1030 then to build 10162,, i just had to reinstall a couple programs.