28000.1 + 28000.1450 CU ---> 28000.1450 ------------------------------------------------------------------------------------------------- 28000.4 + 28000.1371 CU + 28020 Enablement ---> 28020.1371
I created a beta x86 phone pack a year ago to create this pack which allows sending and storing SMS messages without using VoIP, but via the SIM card and a 2G/3G/4G/5G modem. The code was taken from a Windows Phone ARM32 and converted to x86. I'm missing the reg key(s) for telephony. The phone number (99-99-99-99-99) in Windows isn't recognized for making calls. If anyone knows the reg key(s), please share it.
constructed 19045.6809 x64 enterpriseg by MUCS 4 editions which don't require esu bypass/patch and you can successfully install updates online are: enterpriseg, enterprise ltsc, enterprise ltsc n and iot enterprise ltsc. i choose enterpriseg (there is no defender by product policy), specifically 19045 build. in 19044 windows update will find lcu, but 19045 is better for my surface laptop 7 intel.
"windows setup could not configure windows to run on this computer's hardware" error with constructed images when apply-image in hyperv
no "windows setup could not configure windows to run on this computer's hardware" error in hyper when install constructed image from iso why apply-wim do not work in hyperv?
Hello i don't understand how create my windows 10 starter x64. I followed the procedure posted on the front page. I have already modified install.wim, now how do I create the ISO?
There are many ways to create an ISO. You can use programs like Wintoolkit, MSMG Toolkit, and others to create a Windows ISO image. Now, if you're asking "where to put install.wim?", it should be in the "sources" folder.
I downloaded the Enterprise 2016 LTSB version. I copied install.wim to the EntS_to_Starter_14393_x64_StyleLTSB folder and the language pack file to the lp folder. Now that I have modified install.wim, do I need to put it back in the Enterprise folder and create an ISO?