Windows 10: My Insider build 11102 won't update to 14257

The Insider build will have the watermark on it while the TH2 being a general release wouldn't. It was actually about a week and a half earlier at the end of October the 10586 was first seen with the TH2 out on 11/11 right on time for Veteran's Day. The MC Tool still only sees what is the latest general release being the update for the previous RTM being the 10240 and why things may tend to vary at the Tech Bench Program there as far as seeing other builds. Unlike the 10565 and possibly 10576 builds I doubt you will be seeing anything other then MSDN or TechNet direct download links for anything other then the TH2 at this point anyways and would simply have to work with the November update until you start getting the Insider builds in with the updates.

This time however it was taking a bit longer for the 14257 to arrive not having the test build running while having been a little busy finishing up another project. That was the thought at first until hearing others were seemingly "put on hold" as well. It was beginning to look as is you had to do both as far as leaving everything set for automatic as well as conducting manual checks on updates every few hours until it finally showed up. When you are not right on top of things that suggests you get bumped to the back of the waiting line.

 

Deleted all partitions of SSD that contained Win 10 ver 11102 and used new Media Creation Tool on boot able USB to install a clean ver of Win 10 which is ver. 1511 (10586). Waited for Insider fast ring update to build 14267 and downloaded and tried to run/install. Same problem all goes well until the install program "skips" something and ends up on a page where you choose your language. Select English and program quits and revert back to build 11102. Also created an ISO from the downloaded 14267 on to a boot able USB using Rufus. Again, I wiped the entire SSD where Win 10 is located and tried to use USB to install 14267. Got hung up because it could not find a partition to install to. All other SSD's are unplugged. I also unplugged all USB cables, printer, camera, external HDD etc. I also remover a Intel NIC card and reverted back to the NIC build into my ASUS V GENE mob. Still same problem. I don't understand what I am missing.

 

Wiped it how? Inside the booted Win10 install routine (using Custom Install), I hope.

 

Yes, with custom install. Also, using MiniTool deleted all partions on SDD drive.

 

Yes, with custom install. Also, using MiniTool deleted all partions on SDD drive. I get error code 0xC1900101-0x20017. "The installation failed in the SAFE_OS phase with an error during BOOT operation.

 

You may need to try it with a 3rd party partitioning program instead with both of you running into the exact same problem?! Another thing that immediately comes to mind is the UEFI factor! Since SSDs and usb flash drives have a common element excluding which bus usb or sata is in use you still have static memory in comparison to the average mechanical drive with platters.

Besides the type of drive being different you also have to take into account the limit on how many writes can be seen as the information goes on SSDs. First you may need to slave the intended OS drive to one already OSed and then see the new primary created while booted into Windows on a second drive using the Disk Management tool as an alternative. Or you go with Partition Wizard, Partition Magic, Paragon Hard Disk manager, or even boot live with a Linux distro to use the Gnome Partition Editor which can create Fat and NTSF primaries as well VFat partitions.

Using the last option I have been able to custom install ubuntu, Linux Mint, and a few others directly onto flash drives to have a fully installed OS on them rather then just simply seeing a flash drive made bootable while seeing a disk image written to one for live sessions only. That is done when making up a full fledged data recovery stick with the second larger data partition and having all functions available.

Of course I still run into anything like what you are seeing while I have had times when a previous version didn't go on so easy at first. That was mostly seen back when you had to boot from either a 5.25 or 3.5 floppy boot disk back when the OS cds were not bootable items! *Roflmao2You had to rough it back then!

Here still running the large mech drives and going to prep any new drive I will first boot live from either a live distro or the latest GParted cd to avoid seeing the System Reserves 400mb partition created from not using the drive tools on the permanent Windows install however. On VM or for the second build's main drive I had simply booted live from the usb key and ran with the Drive tools option without a glitch once I had already wipe the original 7 primary off the single drive however.

10 was first seen there when the drive was split up for the intended clean install that followed the upgrade of the first primary. But when adding in a second drive for 7 that was reason to nuke the first. The idea there is to first see if you can get a fresh primary on without any OS but see it temporarily as a second drive you can view while booted from another OS drive. If either of those drives is having a bad day you should find out rather quickly when simply trying to toss a few folder on them.

The other thing of course is how well the 10 media came out! If the write to flash drive or burn to disk wasn't good that will immediately be a cause for concern. Here the last iso seen was for the TH2 written to a couple of USB 2.0 and 3.0 flash drives while the upgrades from the previous 10565 and 10576 builds onto the 10586 Insider and then seeing VM as well as both host drives on both machines see the TH2 go. The second off for a January break saw the 14257 upgrade over the TH2 and then onto the 14267 without any problem. But once again not on any SSD drive.

 

Might be worth a try to just go ahead use MiniTool (bootable) and initialize the disk (as GPT, recommended assuming your BIOS supports UEFI boot) and format as NTFS (just for good measure) and THEN delete that partition in the custom install - I take it you deleted all partitions in MiniTool before attempting Custom Install and I'm not sure if the Win10 install just didn't like that as it didn't know which way to go. I'm only taking a guess here - but if you have the time on your hands....

 

Thank you for your suggestions which I performed. Still will not update. Even uninstalled Nvidia display driver and all drives and USB's.

 

Dump it and call it a day! Grab the MC tool to download the TH2 and let that upgrade to the latest! Whenever I run into anything that stubborn I take a look at possibly seeing it replaced. I had a 10586 Insider VM that didn't upgrade to the 14267 lately and soon after DID upgrade to the 14271.

Why? It had to finish installing all of the latest updates including one stubborn to go Windows Defender update! Once one zamooooooo... !!! 14271 rushed on like lightning already ready to download when rechecking on where the Advanced setting were set. It wasn't! Back in December I was planning to keep the 10586 upgraded to TH2 running on that VM while pushing the second 10 Pro and another 10 Home VM on the other machine pushing ahead.

You are likely running into the exact type of problem if you installed any 3rd party av or firewall app there! That will need to be disabled while checking the updates again to insure any loose uninstalled go on and then watch the latest arrive!

 

Just saw this belatedly. Actually the TH2 Insider version DID NOT have a watermark.. That was how we were pretty certain this was the release version.

 

I didn't have a chance to even take notice at the time since the Insider builds were either the host drive on the second machine used for testing or on one of the VMs being run on the 7 side of the dual boots I have going here. The one thing I did notice in particular at the time however was how smoothly the upgrades by updates went on for the TH2 and still go smooth as silk for the latest builds in comparison to the early buggy upgrades seen between the July 29th 10240 release and the 10565.

The hangups I kept running into on one VM while only a delay on the second newer 10 Pro VM but not on the 10 Home VM was the first 10 Pro VM first not being enabled and secondly the few updates that were failing to go on or incomplete. For a month having the second build turned off keeping the TH2 intact I ended up skipping past a couple of builds until trying to get the 14267 on! That's when the fun began with updates again.

The first VM this time was watched as well as the TH2 on the main build's host drive where the av software was preventing the WD update from going on earlier. And once that was turned off zzzzzing on went the WD and all set from there.

 

I updated today to Insider # 14279 without and problems. I first turned off "Fast Start" in my Asus mob BIOS and in the Win 10 before upgrade. Then I uninstalled Malwarebytes and my Nvidia GTX 660 drivers. I crossed my fingers and it upgraded. No problems so far.

 

Once you removed Malwarebytes you allowed the latest WD update to go on which tends to proceed each new build seen since the TH2! I shutdown VIPRE here to see the latest go on three separate VMs while forgetting to shut the av down on the second machine which was actually the first to see the lastest go right on. For someone else however trying to clean install from converting the install.esd file to an iso the clean install came out bugged and had to be dumped where the suggestion was then made to upgrading over a previous build that would go on since the continual upgrades since the 10586 Insider have been going smooth here each time.