Announcing Windows 10 Insider Preview Build 14342 for PC Insider
-
I had this frustrating problems for quite some time until I installed a copy of 1511 with my Windows 8.1 key into a VM and immediately joined the Insiders Preview program. Lastest builds showed up in less than a day - usually a few hours. Then install the ESDtoISO program from this site and copied the ISO to an external Hard Drive I had mounted on the VM. This is how I do now - works great (using VMware WS 12 Pro probably makes it a bit easier but VB or Hyper-V should also work well)
-
-
I prefer to take the bull by the horns (and wrestle him to the ground), rather than wait for him to fall down on his own. :)
I've gotten so used to ESD to ISO that I can do it in just a few minutes. Once that's done, I can clean install and go about the business of testing, rather than wasting time waiting on MS to deliver the goods.
The problem here has been only seeing a quick flash on the screen when trying to use the tool for that. Still haven't been able to determine the cause but simply end up seeing what looks like a command prompt window open for a split second and then nothing when having tried out the tool in Kari's guide several times. That is with all system protections shutdown as well as other background processes to avoid any possible sources of interference as well as tried out on the second desktop where almost nothing but the present build would be running.
-
Just checking.
1) Did you run the script with admiinistrator priveledges?
2) Did you copy the ESD file into the same directory (I just use c:\esd) as the rest of the unzippped ESDtoISO file?
Likely you did so that the problem "might" be hardware related. If you wander around the Net you might find the ESD on another site (or even on some MS site) - maybe downloadable from Mega.
-
If a PC is refusing to update to the next build, you won't have a (local) copy of the ESD.
Originally Posted by
OilerNut
So still no ISO released for 14342, quite annoying...
Not sure why it's so hard for them to release an iso. Yeah I know I can make my own with the ESD converter, but still would be nice to download an official ISO.
Originally Posted by
Wynona
I prefer to take the bull by the horns (and wrestle him to the ground), rather than wait for him to fall down on his own. :)
I've gotten so used to ESD to ISO that I can do it in just a few minutes. Once that's done, I can clean install and go about the business of testing, rather than wasting time waiting on MS to deliver the goods.
As you can see, I was replying to OilerNut who seems to be waiting for the ISO of 14342 to drop for us, rather than being unable to get the update. (Sorry, OilerNut, if I misunderstood and you really can't get the update.) :)
At any rate, I hadn't thought of that before, but it makes perfect sense to me that if I can't update to the next Build, I won't have the Install.ESD file for it.
-
-
The problem here has been only seeing a quick flash on the screen when trying to use the tool for that. Still haven't been able to determine the cause but simply end up seeing what looks like a command prompt window open for a split second and then nothing when having tried out the tool in Kari's guide several times. That is with all system protections shutdown as well as other background processes to avoid any possible sources of interference as well as tried out on the second desktop where almost nothing but the present build would be running.
I had the same question as Marty, but when I think about it, ESD to ISO does that for me. :)
I have a Windows 10 folder on my external HDD. In that one, I keep a folder for each Build, one for Rufus (to create the bootable USB stick) and one for ESD to ISO. When it's time, I move the install.esd file into its individual Build folder for safe keeping. Once I'm ready to finish the job, I copy install.esd into the ESD to ISO folder and click on the ESD Converter and away we go. Once finished, I move the ISO into its Build folder and delete the install.esd file.
Edit: I didn't tell the silly thing to post yet!
The main reason I place the install.esd file into its Build folder is so that I'll be very sure which Build it goes with and won't have to worry about grabbing the wrong file.
Edit #2:
When the Command Prompt Window comes up, it asks me how I want to do this. I always choose #1.
-
So still no ISO released for 14342, quite annoying...
Not sure why it's so hard for them to release an iso. Yeah I know I can make my own with the ESD converter, but still would be nice to download an official ISO.
If you have an official upgrade you have the official ESD which you can convert to official ISO.
-
Just checking.
1) Did you run the script with admiinistrator priveledges?
2) Did you copy the ESD file into the same directory (I just use c:\esd) as the rest of the unzippped ESDtoISO file?
Likely you did so that the problem "might" be hardware related. If you wander around the Net you might find the ESD on another site (or even on some MS site) - maybe downloadable from Mega.
The guide was followed to the letter as far as the instructions with the admin privileges included and still the same thing was seen every time. It was when not having any protections running a Bing ing around for an alternative option when the cmd file failed I got hit with a bug!
I had the same question as Marty, but when I think about it, ESD to ISO does that for me. :)
I have a Windows 10 folder on my external HDD. In that one, I keep a folder for each Build, one for Rufus (to create the bootable USB stick) and one for ESD to ISO. When it's time, I move the install.esd file into its individual Build folder for safe keeping. Once I'm ready to finish the job, I copy install.esd into the ESD to ISO folder and click on the ESD Converter and away we go. Once finished, I move the ISO into its Build folder and delete the install.esd file.
Edit: I didn't tell the silly thing to post yet!
The main reason I place the install.esd file into its Build folder is so that I'll be very sure which Build it goes with and won't have to worry about grabbing the wrong file.
Edit #2:
When the Command Prompt Window comes up, it asks me how I want to do this. I always choose #1.
The windows never even stayed opened more then a split second to do anything. For several builds I simply ended up saving the entire "~BT" or "~WS" if not QT on one occasion folder for the manual install or put the TH2 on first and allowed the Get insider builds option to go for the latest.
The upgrade attempt by BT folder on VM ended up seeing 7 to TH2 replaced with the clean install only having found the Upgrade option greyed out on the test VM set up for trying that out. The BT acts more like the Reset PC option then anything else as found with that test. Most builds still see the Install.esd while several also ran into the Install.wim file alternate. Presently however I decided to wait now for the Redstone 1 iso for keeping the main there while the second pc will remain running with each newer build from that point forward as well as some VM projects.
-
Actually for me the script starts executing so fast that I'm not sure I could choose any other option but #1:) My own habit is to use AOEMI Backkupper to make an image of the OS before and after installing the new build, create an ISO in the virtual machine (I'm thinking I don get offerred the new build anymore on my physical machine because I have alsmost 100 programs <keep updated using Sumo>. After that I use Disk Cleanup to free up some disk space and Unlocker to finish the job on Windows.old. It's taken awhile to develop this methold and it works for me so I don't see a compelling reason to change. Buildfeed show MS latest build is
10.0.14354.1000.rs1_release.160524-1700
I'm thinking that or perhaps 14355 for Friday. I'd like to see MS scale back on developing for Mobile which has < 1% share. Well I guess they have - just laid off 1,800.
-
As you can see, I was replying to OilerNut who seems to be waiting for the ISO of 14342 to drop for us, rather than being unable to get the update. (Sorry, OilerNut, if I misunderstood and you really can't get the update.) :)
At any rate, I hadn't thought of that before, but it makes perfect sense to me that if I can't update to the next Build, I won't have the Install.ESD file for it.
Ah I am successfully on 14342, but for work purposes I always prefer using the proper released ISOs. Have a bunch of test surfaces, other tablets, desktop, notebooks that I have been playing with and would prefer the real ISOs compared to ones extracted from the ESD files. Perhaps I am just a bit too OCD, haha
-
-
took for 4 times to get upgraded to this buid. failed 3 times. turns out the upgrade process didnt like the fact I had hacked together theme files.
once I reverted the theme files back. the upgrade completed on the 4th time.