Announcing Windows 10 Insider Preview Build 16215 PC + 15222 Mobile Insider
-
just wondering if anybody else see's this as an unusual and crazy thing? And does anyone know anything about it? I just checked my update history, and my system downloaded and updated the same two updates many, many, many times. I have included a screen shot below.
Is this in build 16125 or cu?
-
-
Is this in build 16125 or cu?
Says 1607, so must be 14393.
-
![]()
I have a triple boot setup and have NEVER had any problems with updating from build to build since December 2014 (When I joined Insider) or January 2015 (When I joined Tenforums). That includes one computer with UEFI and two with legacy bios. So that is not the issue with updating to this particular build. There is a problem with 215 that is at issue and at fault. I have been able to update to 215 on all of my systems, but have returned to199 on two of them. I left one, my oldest laptop, with 215 installed so I can 'play' with it and examine this build for what good it may have.
When you say you triple boot, single drive? or multi-drive? ( I meant physical drives).
The main reason I installed removable drive trays on my PCs is so that I can pull out the other drives before doing an update/upgrade. It's easier that way than taking risks and try to fix problems when the other installation got affected. Also, to avoid update/upgrade complications. Especially if you have linux mixed in. So my suggestion is to pull out the other drives before updating and see if that helps.
-
Is anybody testing in a Linux/Windows Multiboot environment? A non-NTFS filesystem may be giving the update fits although I upgraded from 193 to 199 without any problem.
I guess I'm not understanding why any Build wouldn't install on a multiboot system. In my system, the Creative Update is on one partition and Windows Insider Updates is on another partition. In my experience, there's never been a crossover of any kind.
-
-
When you say you triple boot, single drive? or multi-drive? ( I meant physical drives).
The main reason I installed removable drive trays on my PCs is so that I can pull out the other drives before doing an update/upgrade. It's easier that way than taking risks and try to fix problems when the other installation got affected. Also, to avoid update/upgrade complications. Especially if you have linux mixed in. So my suggestion is to pull out the other drives before updating and see if that helps.
Three separate SSD's -- never had problem with any update
-
I guess I'm not understanding why any Build wouldn't install on a multiboot system. In my system, the Creative Update is on one partition and Windows Insider Updates is on another partition. In my experience, there's never been a crossover of any kind.
Marty has a Linux/Windows cohabitation setup. I've never tried that, and have no intentions to.
-
Says 1607, so must be 14393.
couldn't see the small print --- a problem when you go to 4K monitor, even when fonts are enhanced to 150% still small print.
-
I guess I'm not understanding why any Build wouldn't install on a multiboot system. In my system, the Creative Update is on one partition and Windows Insider Updates is on another partition. In my experience, there's never been a crossover of any kind.
-
If I do an install of an IP from an ISO the Windows Bootloader will temporarily disable the BTBM Bootloader and it will be a standard Windows Server/Windows Desktop dual boot. Later I can run EasyBCD from the Windows Server 2016 OS and install a Windows Bootloader to the Windows Desktop OS - disentangle them. The Siduction appears in the Boot Menu. I'm kinda rushed right now so this isn't the clearest explanation. In any event, 16215 is still up on the Fast Ring and although 16222, compiled Monday, is up as the buildfeed canary I don't expect anything this week based on the last Webbast.
-
-
Marty has a Linux/Windows cohabitation setup. I've never tried that, and have no intentions to.
Linux isn't dual boot friendly. It can coexist with Windows but not until an update comes into play.
Multiple windows is ok most of the time if you auto-multi boot. If you pull out one drive or remove a partition, that's when the problem usually arise.
Quote