I don't believe a leaked build will auto update to the next official. You probably wouldn't want to anyway. You might well retain some "leak bugs" into your latest official build. Never a good practice to break the chain of build updates/fixes. Simplest course for you would be to enjoy 10147, and when next build drops, re-image (restore) the last 10130 you have and let it update naturally. Clean, of course is best.
My setup is two separate SSD,s one for W8.1 and the other for W10.
Switching drives is done either by clicking F8 for choice of setup, or by changing the boot order via the bios.
If not able to switch drives it was my intention to disconnect one or the other in order to retain W8.1 as well as being able to continue as a Windows Insider
Being like yourself wary about mixing O/S,s, I chose not to use EasyBCD.....Reason see latest post from GABE.
i don't know why people keep saying this. every leak has updated thus far. so why do you guys keep saying it won't? each leak has updated to the next official build, and while it is not a sure thing, i would bet that this one will as well. and again, if it will not, then easily roll back the build to 10130 and update. this isn't rocket science.
DENCAL, just a note, i use to run my dual boot on separate ssd's as well, and while it is easily done, i found that the dual booting system runs better when both boot partitions are on the same ssd (of course if you have room). but i never had to go through all of that to switch drives. you can easily set it up to give you a quick choice while booting. just make sure win 10 is the last partition loaded. and if you don't already use it, macrium works very well for imaging and restoring partitions. cheers.
What they mean is that it won't automatically update via Windows Update. Many leaks have not updated to the next official build when it was available. The reason is that the leaks are often on a different build branch than fbl_impressive, so they would only update to a new build in the same branch they are in, which the user doesn't have access to typically so no updates would come.
However, 10147 is an fbl_impressive branch, so it should update, unless there happens to be a bug preventing it.
Dual BOOT on same disk, different partitions, only if you must because an error or change on first partition would ruin both OSes. On separate disks, you can always have at least one OS working and better chance to repair or salvage either one.
that's why i have backup images. never had an entire disk screw up. only a partition, and never has it affected the other os. just fyi. on different ssd's i regularly had trouble with the system either losing one of them, or corrupting the start up and not showing it when i booted. but then i read several articles saying that it was a better idea to put both os's on the same disk. this seemed strange to me, because i was always told not to, for the same reasons you listed. but i tried it anyway, with bu images in hand and it has worked to perfection for quite a while now. the confidence comes from having several backup images, and the experience i have had with it.
yeah, i get what they mean, but it isn't necessarily true. i have loaded most of the leaks, and they all updated from windows update, whether they said they wouldn't or not. because of the different branches i fully expected to have to roll back the build when the time came, but i never have had to.
Stevae You are missing the point. dual booting after updating W8.1 to W10 when finally released and being an Insider will not be possible according to Gabe. See Attached Thumbnail in post #372. for confirmation.
Quote