Has anyone tried a Th2 RTM clean install (CI) on a (wiped) activated build 10240 Pro? Thought I'd shortcut the process of updating then CI the Th2 build by just wiping & CI w/o updating first. Seems like it should work
Not sure if anyone mentioned, but the BitLocker encryption method has changed in this build, as compared to 10240. Now BitLocker uses XTS-AES for fixed drives instead of AES alone as is teh case in 10240. Guess it's one of these "under the hood" changes that MS made in this build.
i really want to know with what kind of mind did they install ltsb version and how can they demand that it should upgraded?
Does anyone know which method is the best to activate windows 10 now? I had the slmgr /skms kms.xspace.in but it doesn't work now and my windows got deactivated after upgrading edit: nevermind, I just loaded toolkit and pressed activate on the w10 enterprise and it worked
Thanks for reporting. On both computers I've seen this issue the 10586 install was an upgrade (home via WU, Pro via iso). Don't know if a clean install will solve. Also, when starting in safe mode the Get Started App throws an error right after log in on the same machines. sfc /scannow doesn't find issues.
I have the same experience as Superfly. You've definitely got something going on locally, then...hasn't happened to me in any build, actually & 10586 I installed twice without incident--once through WU and then through the Microsoft ISO locally.
Tried a wipe W10 x64 RTM then install W10 x64 Th2 RTM off a DVD, took 25.5 minutes to hit the desktop. After the cumulative W10 update I am at build 10586.3 & its activated. It has taken awhile to tweak the .NET (feature) stuff & get Win Photo Viewer setup (.reg fix) Nice when it comes together
I am away from MDL cause since yesterday i've gone to hell and back. First, I was in the 05oct Build. But i've decided to do a clean install, just to remove the junk of the update process. Here the HELL begins On the "Refreshed" Windows -Sfc found errors that couldn't repair -Dism was unable to locate the source -Laggy a$$ boot. (Windows Logo and dots - BLACK SCREEN - Windows Logo and Dots) -They changed my user folder to "andre" instead of "Andre", i want the capital A. - Did the process to change the username - Start Menu doesn't open, Taskbar is frozen, and the computer was laggy. Checked the HD with the tool someone here posted, it was healthy. Let's do a Clean Install - Download the Creation Tool, and burned the iso. - Everything happened except the Start Menu error and etc. Caos - Wiped the whole windows partition, formated and installed like a first OS. But the Sfc error was there Found out about a In-Place Upgrade and finally it got things straighten. But as of now i'm facing errors downloading and updating store apps. I am really really LOST!
How did you wipe or cleaned the disk? I usually do a diskpart /clean command twice and works flawless all the time.
I really dont know why is that. I think its an issue, like they assume you are on SSD and you wont notice this but if you are in a regular HDD like 90% of us, we note this. Like hybrid 'solve' the booting timing problem but they over use this, so, now, if you boot/restart it takes more then 3 times than 7 (on 7 this machine from cold boot takes 19 seconds on a regular drive, and 8 takes 32 seconds, with 10 takes more than 2 minutes and half...)