I want a Windows 10 build that is as stable as possible. I don't care about latest features or anything. I have been using 16299.15 (Enterprise) for a while, and it has a problem when first installing where State Repository Service consumes all the CPU and lags everything out, until creating a new user account and doing some trickery then going back to the old one. I'm experiencing FPS issues in games that I can't seem to fix and the occasional BSOD and want to reformat but go with a more stable build this time. I don't see any way of downloading an ISO of this build and I've read some things that suggest it's possible to somehow install an older version and patch it up to this point. I'll be modding a lot with WinAeroTweaker and using Start10 and disabling all the telemetry garbage, etc.. I don't like Cortana or any of that metro stuff. I just want to keep full control over when/which updates area downloaded and installed (as I have now) and have a stable system with no tacky UI annoyances. What do I need to do in order to get a nice, stable install of Windows 10 these days? Thank you! EDIT: I'd probably be happy with 16299.192. I found an ISO for 16299.125. Wouldn't I need the VL edition in order to activate Windows without a valid key? How could I update .125 to .192?
16299.125 is the most current officially released ESD/ISO, 16299.192 will be a homebrew iso, not advised to use. For any proper KMS solution like this one there is no need to install a VL edition, it will insert a gVLK and activate it. PS, tinkering with the install won't make it more stable, nor will it gain performance
Thanks, I have no idea what to do with those ESDs. I've got the following ISOs downloaded: Code: EA214EE684A5BB8230707104C54A3B74D92F1D69 *en_windows_10_multi-edition_version_1709_updated_dec_2017_x64_dvd_100406711.iso 1851A0007321FA084145EA24B8D30BF7A72BF1C6 *en_windows_10_multi-edition_vl_version_1709_updated_dec_2017_x64_dvd_100406172.iso I'm actually using KMS_VL_ALL currently with 16299.15 (but IIRC I had to use "slmgr /ato" in a command prompt to make things work properly for some reason). All I would need to do is install using the normal ISO of 16299.125 listed above and activate with KMS_VL_ALL, right? I want to be sure that I can indefinitely disable Windows updates and use wushowhide.diagcab to manually pick ones I don't want, if any when it does come time to install updates.
(removed quote because it contains links, which I can't post because of low post count) I'm looking to reformat and do a clean reinstall so I figured I'd try to make improvements in this area. Thanks for the guide, I tried searching for that but the search results don't seem very helpful here What would I gain from using a VL ISO?
Nothing except KMS_VL_ALL v19 doesn't need to pre-insert the proper gVLK check my previous reply, i've added the answer there
Thanks so much, and I see a lot of mixed answers all the time on flash drive partitioning. What do you recommend for putting the W10 ISO on a flash drive with Rufus (as far as partition scheme and file system)?
For UEFI and Legacy BIOS installs just format the USB FAT32 and extract the iso to it. For Legacy BIOS installs, just format the USB NTFS and extract the iso to it. To be able to fit the FAT32 max file size it's advised to either compress the install.wim to install.esd or split it into multiple install.swm files. That's why the use of the ESD's or MCT is advised, it will create the ISO with install.esd by default (MCT), when using @abbodi1406 ESD>ISO tool you'll get the option to go for iso with install.wim or install.esd.
Yeah it isn't working with FAT32. In the past I just used NTFS because it was defaulting to that when selecting the ISO. That seems to work fine so I think I'll just do that instead of learning a new method for now. Thanks for all the help .
there are tools which are capable of split install.wim into multiple swm files automatically when it comes to create bootable drive with iso that is bigger than 4 GB as WinSetupFromUSB tool which i recommand.
No need for tools: Code: Dism /Split-Image /ImageFile:x\install.wim /SWMFile:x\install.swm /FileSize:3500 All windows setups can handle split wim files (7 and up, vista i never tried).
that's exactly why the tool is useful, it splits install.wim automatically while creating bootable drive without the need of doing it manually with command lines.
yes that's true but sometimes in certain circumstances, you need to do things quickly so you choose the easiest and fastest way to accomplish this.
What is 16299.249 and how to get it? Just now, few minutes ago finished the clean install and I got 16299.248.