I chose custom to wipe all partitions from last install. Made sure just one line with unallocated space, the drive is new so there was no hidden partitions on it. No av just windows installed. So technically nothing was on the drive. The first attempt it didnt run the project because it bypassed it as i forgot the ei.cfg to allow to choose edition. Never had this problem on windows 10 installs before as i never slipstream as it not worth it as the new way the cumulative updates work. Mx Ps I blame that Cortana I'm sure she hates me lol Trust me to have a damn pc that wont play nice (or in this case a possible ISO - I know it not corrupted as i have updated my main rig with it)
After some reading it seems M$ messed something up with the activation method they implemented. We might have to wait for a fix in the iso. Seems there are lots of ppl complaining they cant activate the new win10 but others can. Maybe a hardware id issue. I am curious if files are still in the setup folder...if so then something stopped it. I have used in vmware and didnt experience this. I used the win10 pro vl x86 and x64 and both installed the project. If need be can we do a teamview session so I can see for myself what happened? If so let me know in pm. So much for my vacation. lmao!
I download from the MS website Windows 10 International English (en-gb) x64 . It should of had Home(Core) and Pro --- However.... Have just looked in the ESD with DISM and it has Home/Pro which i saw on the setup edition chooser, BUT it also has Single Language and Education???? Those was NOT shown on the edition chooser screen! I bet someone at MS has made a screw up. I can try downloading again, not sure if the Techbench site works or has the new version yet. But it will take a while to download it / reinstall etc. Maybe someone else will have better results in the meantime for you. Mx Edit I have just checked the windows\setup folder and yes the scripts files are all there. OEM's folder, and four other files. Will PM you with TeamV ID/Pw in a few once i can get this *&^%&ing edge to work lol
Then something odd happened but without knowing more I cant tell you how to fix it. I would start with downloading iso again and check it before using. If not fixed on their behalf then best advice is to give it some time for them to fix the iso. I think M$ is rushing the new version. This is only my opinion but it doesnt seem stable. There are many complaints on M$ site so I expect them to update the iso's soon. -activation issues. -hdmi issues. -usb drive issues. -random crashes. The list goes on. lol I am going to test the retail x64 version of win10 to see my results in vmware. Stay tuned...
Oh, I just remembered, do not use the Retail.txt file in the scripts folder since your machine came with win10 th2. You can use that key to activate but use the ei.cfg and the pid.txt file only so oobe.cmd runs when called during the install process. By the way, I just tried the retail win10 x64 1607 and it installed correctly so its your oem machine stopping the oobe.cmd file from running thus why we need the pid.txt file to bypass the disabling of the oobe.cmd file. Let me know your progress.
Just downloading the ISO via the mediacreation tool... made sure it was x64 and not the N or single language one. Shall i put the msdm key from the bios in the pid.txt so that it auto activates or use the other home key? 49% dloaded - just hope it not bunk out with an error like it did a few minutes ago lol
I'm using KMS to activate when i finish installing user pic and login screen is there and fine but after a few restarts login screen and user pic is gone but from setting user pic is there MicroCrap will never do anything right!
Downloaded the iso again... Copied out the esd file to check what is inside it and guess what... have more than home/pro yet again lol Spoiler D:\>Dism /Get-wimInfo /wimfile:\install.esd Deployment Image Servicing and Management tool Version: 10.0.10586.0 Details for image : D:\install.esd Index : 1 Name : Windows 10 Pro Description : Windows 10 Pro Size : 14,440,586,483 bytes Index : 2 Name : Windows 10 Home Description : Windows 10 Home Size : 14,283,712,175 bytes Index : 3 Name : Windows 10 Home Single Language Description : Windows 10 Home Single Language Size : 14,267,982,168 bytes Index : 4 Name : Windows 10 Education Description : Windows 10 Education Size : 13,947,202,038 bytes The operation completed successfully. Well i will give it a try again..... Will use the PID.txt with the MSDM key from bios and the ei.cfg to force it to Home for this laptop... The TH2 one didnt have this many problems. Ok it wasnt perfect but gez it was a lot more stable(ish), than this pile of <censord>. I'm using TH2 on this pc i downloaded on to hence why the dism version...
I know for a fact that I will tell my friends NOT to update to this version yet because of all the random issues. Think it is best to wait till next iso update. I am glad I am still running win8.1 on my lappy. Like the saying goes, if it's not broken, give it time and M$ will mess things up. lmao! Its the truth. lol
I have another problem since Win10 come out I install Win10 with English interface and Arabic Egypt as location and time etc, But MicroCrap keep adding Arabic Saudi Arabia for me after each restart and the only solution is to add Arabic Saudi Arabia Manually and remove it again in each restart This only happen with every laptop so far not with normal PC Can someone please tell MicroCrap i don't live in Saudi Arabia Lol
Here is a list of the win10 iso's I got yesterday so others know what ISO's I have been testing... -SW_DVD5_WIN_ENT_10_1607_32BIT_English_MLF_X21-07101 -SW_DVD5_WIN_ENT_10_1607_64BIT_English_MLF_X21-07102 -SW_DVD5_Win_Pro_10_1607_32BIT_English_MLF_X21-07253 (VL) -SW_DVD5_Win_Pro_10_1607_64BIT_English_MLF_X21-06988 (VL) -Win10_1607_English_x32 (retail) -Win10_1607_English_x64 (retail) -Win10_1607_SingleLang_English_x32 (retail) -Win10_1607_SingleLang_English_x64 (retail)
Created the new iso>usb , done PID.txt (msdm key) , done ei.cfg >> editionid i tried HOME, setup borked out, so changed it to CORE, same thing , so last ditch attempt set it to nothing as it was before. Channel set to retail, VL 0 Then found your ei.cfg file within the project optional folder so used that. ok then ... round 4 LOL This time i noticed the disk label has changed to ESD-ISO instead of the long JCC...... one... Fingers crossed this one lets the project complete. I won't give up lol
It's the program you used to edit the iso. You can change it back if you desire. The iso will still run no matter what the program named it.