That was for different reasons you can't compare the two... and im pretty sure Microsoft ethics have changed this isn't the XP days man people cant let that OS goo... The reason they skipped 9 is because Windows 8 was already in the 9K builds they wanted to sync Kernel, and build, Windows 10 was born. The way ballmer/sinofsky ran the team was complete garbage...
That's my question as well. Do we HAVE to go back to 10130 then upgrade to whatever the new build(s) will be, then continue to upgrade (instead of clean install) up to RTM?
Before thinking to an eventual downgrade, wait that Gabe release something before, at least you can try to update the build 147 and see what happening.
They average around 3-5 builds every 2-3 days at least that's what i've counted most of the time most of the updates they do to the OS have nothing to do with winmain.wim or impressive
"They" say you have to be on 130 to upgrade, the rest would be speculation since there hasn't been a new official build in about a month to test it with.
hm, simply wait and see if any future official build runs upon your leaked one. If not you easily can reinstall 10130 and upgrade just normal
Pretty sure Gabe said you will be able to upgrade from any build, the only problem with upgrading from a leaked build is that some problems that occur in that build might carry over to the **next** release build... i went back to 10130 from 147 because of that reason.
I don't think anybody would ever want to upgrade to the final code from a test build anyway because you would never know what testing code might be left over in it. If they for some reason force you to upgrade before you can download the iso (and it seems that IS what they are saying) then do the upgrade, download the is and format your disk and start over. Of course somebody else will have long ago already downloaded and posted it so you can avoid that upgrade to begin with.
Sorry i didn't mean official i meant next build.. I intend on doing a fresh reformat when the final code comes
Do an upgrade from 10130 or even 10135 to 10147 and you'll get those graphical bugs on the desktop along with the stuck Spartan icon on the taskbar. You can then go into Recovery in that install and do a full refresh and it'll be a fully clean install that clears out anything left over (bug-wise) from the upgrade install and you got the option to keep anything if you wanted to. Or just simply download the ISO of the next official release and skip all that and just do a clean install. If you're going to take the time to test an operating system, you HAVE to deal with doing clean installs and constantly backing up. It gets old seeing people whine and complain about that. You're supposed to be TESTING IT. Stop running it on main systems or at least constantly back up anything important if you do. Common freaking sense. Some of you beg and beg for new builds. They release one and first thing you do is complain about now having to back everything up and all the stuff you'll have to re-install again. Like it takes hours. Sorry if your systems are slow. I can go from setup to everything of mine installed in under an hour and that's with massive stuff and a laptop that's 2.5 years old. 30 minutes on my desktop. An hour if I install any of my games.
Alright, so this happens when using a pin to login to Windows (instead of a password). If you use a pin (on updated 10130 and out-the-box 10147 builds), connecting to network resources that need authentication will fail. It'll work fine on a non-updated 10130 build, so I guess some update on that build breaks the functionality. If using a password to login, all seems to be well (at least on 10147; soon to verify on 10130).
I freshly installed build 10147 and i couldn't get the pin to work at all i always had to use the regular password but PIN works amazingly on 130 and the network / Wifi stability is horrible in 147 that's why i rolled back.
Anyone knows how to keep the Numlock key on after restart / shutdown? I tried with the "Fast Startup" option enabled but everytime I shutdown, the Numlock key is off until I logged into Windows.