Make Education ISO Since I don't feel like wasting bandwidth uploading an EDUCATION iso I'll just explain how to create it. First, make sure you have a Pro iso (x64 or x86). Extract all of its contents to a folder on the root of the hard drive Then open elevated cmd and run the command Code: dism /mount-image /imagefile:c:\esd\install.wim /index:1 /mountdir:c:\esd1 The /imagefile refers to the path of your wim (Where you extracted ISO files) The mountdir refers to where you want to store your new Education ISO Then run the following command Code: dism /image:c:\esd1 /Set-Edition:Education c:\esd1 refers to where you're new education ISO is. Then run the following command Code: Dism /Commit-Image /MountDir:C:\test\offline Done. Edit: Almost forgot the flags Put in elevated cmd Code: imagex /flags "Education" /info d:<Path_To_Your_New_Wim> 1 "Windows 10 Education x64" "Windows 10 Education x64"
After resetting the OS which solved the aforesaid problems, however my original registered MS Account still could not log in the Mail and a dialogue box shown : Something went wrong, we're sorry, but we weren't able to do that. Error Code : 0x8000ffff! Well you can add another Account to the Mail.
Test I just did in a new VM, no previous Windows installation: 1. Install insider build 10130 and activate. 2. Using release ISO, upgrade from within 10130 to build 10240. Product key skipped, it activated online. 3. Format hard disk. 4. From a homebrew ISO of build 10525 (converted from ESD), clean install build 10525. Product key skipped, it activated online. Only local account was used, at no point was a Microsoft Account enabled on the machine. There is quite a bit of confusion in this thread, so based on what we know already about build 10240, and based on the test above, here is a summary of the rules as I understand them. Most of this is not new: 1. Activation behaviour of build 10525 is identical to 10240. In particular, it is not tied to a Microsoft Account. 2. Activation of build 10240 is based on hardware ID. If the machine is marked as eligible, clean installs of build 10240 (and therefore 10525) are possible by skipping product key. No Microsoft Account is necessary. 3. For the hardware ID to be recorded and the machine to be marked, you need to successfully upgrade to and legitimately activate 10240 (i.e. not using KMS). No Microsoft Account is necessary. 4. Upgrades to build 10240 from an activated Windows 7, 8, 8.1 or Windows 10 Insider builds 10074 and 10130 end up activating 10240, and therefore recording the hardware ID and marking the machine. 5. For the insider build 10525 to be offered via Windows Update, insider builds must be enabled in windows update advanced settings, and a Microsoft Account that has joined the Insider program must be linked to the machine. Note that only item 5. requires a Microsoft Account. Also note that item 5. is independent of the other items. The issue of activation is therefore entirely separate from the issue of whether Windows Update offers a new insider build. You can upgrade to 10525 and be activated without a Microsoft Account if not using Windows Update, and conversely, you can use Windows Update to upgrade to 10525 using a Microsoft Account without being activated. So it's really quite simple and can be summarised in just two statements: Golden Rule I: Activation in builds 10240 and 10525 is based just on hardware ID, i.e. a legitimate upgrade to build 10240 (or 10525). Golden Rule II: Windows Update offers insider build 10525 based just on Microsoft Account (and insider build setting in windows update) and is not related to activation.
little bit off topic, if it's possible to natively change title color (and other added (or fixed) features) , it's theoretically possible to port these feature to RTM .240 !!
A friend of mine wants to install Enterprise LTSB N x64 this week. Should he wait for this build in october or he is fine to install the version i mentioned and then install this one like na update? I know that a clean install is always better.
What MS posted [h=2]We do have a few known issues with this build.[/h]Part of the fun of being a Windows Insider is getting to tinker with prerelease software before the rest of the world, but you should be very aware as an Insider that prerelease software will come with bugs and things that are incomplete. Make sure you know and accept what you’re opting in to when you join the program, and of course make sure to back up all of your personal data before you begin. Mobile hotspot doesn’t work in this build. When sharing the Internet from your device with mobile broadband using Mobile Hotspot, it will fail to get a valid IP address from your device and will show no internet access. An update to Movies & TV application from the Store will be required to fix an issue with video playback. Optional languages packs will not be available during the initial launch of this flight, it will be available later this week.
Of course it's time bombed, I never said or implied it wasn't. It's a completely regular build 10525, and the build itself is timebombed, just like any other insider preview build before this (except 10240). This has nothing to do with activation.
Your saying you'll come out with permanently activated image, try and see Or you mean to just get it on your puter to play with