Let me think a search engine that has been used to DDOS sites. Ya what the hell I totally trust baidu. What could possibly go wrong XD Ooo Homebrew I'm feelin lucky like all the ppl who use tinder.
so final test was upgrading from pro to enterprise and that worked without issue so all is good this build much more stable the 10056
If I have downloaded an created a ISO from the 10061 ESD (enterprise x64) from windows update would that be against MDL rules?
Anyone has seen th germen x64 ESD file? so i will not at first install 10041 and then upgrade to 10061.
Does anyone has a direkt link to 10061.0.150410-2039.fbl_impressive_CLIENTENTERPRISE_VOL_x86fre_de-de.esd? I want to create a WinTo go USB drive and test touch on m Baytrail tablet (this is why I need 32Bit Enterprise)
Weirdly, doing a slmgr /ipk with the usual Ent key does allow you to activate later. No idea why inputting the same key in the UI is rejected when the slmgr way isn't.
So now we're stuck with boring gray for the titlebar. Can't even change the titlebar color anymore. This is getting worse by each build
I think you should change the name of patched file to something different than the original name. Like this: Code: xdelta3 -d -s 10061.0.150410-2039.fbl_impressive_clientpro_ret_x64fre_en-us.esd 10061_x64.xdelta 10061.0.150410-2039.fbl_impressive_CLIENTPRO_RET_x64fre_en-us-PATCHED.esd
Updating Windows 10 release 10049 x86 italian version to Windows 10 release 10061 x86 on VmWare machine can i use esd decrypt to create iso?
Seems i won't violate that rule. The ESD was downloaded from Windows Update and is official. I'll upload it to my Mega and generate Checksums for it sometime tomorrow if somebody hasn't beat me too it already. P.S. If you couldn't tell I'm new, however i have been following the other windows 10 threads.