It will run automated, resulting in an Enterprise only ISO, containing an install.esd with the SSU/CU integrated and dotnetfx3 pre-enabled, it will take some time to complete, depending on the hardware, the script is running on
Do i need to install any additional updates after the installation? The hardware is not the issue, my laptop is Octa Core i7,3.8ghz processor with 16GB RAM
You will receive the latest dotnetcu and flash update, those are not provided by the UUP system. When you create the UUP folder inside the main unzipped folder, and put in those 2 updates (in .cab format), at forehand, they will be integrated too.
One more thing please ,is this release stable? Because am installing all my telecommunication software's on it which cost me lot of money to obtain.most of the license are tied to my laptop.Please I don't want to be reinstalling Windows OS always.reinstalling new windows will make me lose my licenses and will cost me a lot of money to get my license back
18362.10019 still is a beta OS, in the IP SLOW ring. For stable you better use 18362.356, it's in the Retail Release ring (no IP).
I will give it a try. I observed two folders were created "bin" and "UUPs". Am yet to see "dotnetcu" and "flash" update
kb4517211 installed without issue. On reboot WU wanted to download and install the update again, and then again after that. The 2nd and 3rd installs did not require a reboot. WU is now clear.
how the hell do u use the cab files you linked @Enthousiast I tried uup converter but it asks for the uup file paths i give it the path where those 3 files are and it says it is not a valid uup source I just want the regular cab files so i can update anyway I can get those?
Save this code as a .cmd file, put in the same folder as updates, Run As Admin. Code: @echo off rename "adb48974-2bb2-4971-968d-5581b5822d41" "Windows10.0-KB4501374-x64.cab" rename "0f2d4dbc-d02b-4396-a2c4-50971f1e70a5" "Windows10.0-KB4517211-x64.cab" rename "1d43ee84-8644-4769-9b8a-e6eec35f33e2" "Windows10.0-KB4520390-x64.cab"
You have to download those updates yourself. Honestly and no offense but if you aren't going to read the stickies and educate yourself, maybe this stuff isn't for you. UUP Dump is a dead simple site to use to generate ISO's. You don't expressly need to make an Enterprise only ISO, you could've simply selected Pro, clicked the relevant button on the final download page to create virtual editions and checked only the Enterprise box. Download it, extract it, run the script as is and wind up with an ISO containing 2 indecies (Pro and Enterprise) . There is no need to enable dotnet3, you can simply do it after installation and save a ton of time. Likewise there is no need to integrate dotnet CU's or flash updates, you can simply let Windows Update do it after installation and again save time. Anyway, there are some good stickies in this forum you should check out. In particular the one with the non-IP 18362 release if that's what you want as I don't even think that you are aware that this is a thread for a prerelease version of Windows 10. You could even get a download link to the Business ISO that would've saved you even more time! There is another sticky about downloading and using UUP files that is way more pertinent and conducive to discussions of how to use them UUP files! Good luck!
I understand you my friend,every master was once a novice so I don't see anything wrong in helping someone who don't understand.
I took your advise and am currently downloading the stable release 18362.356. I observed that sometime the connection is lost.My question is "do I need to delete the files it has downloaded before connection lost and start a new download" or each time connection is lost,I should just run" arial_download_windows" to continue my download
After you've renamed the extensionless file to the shown cab filename, you can integrate it online/offline by using W10UI or manually: Code: dism /online /Add-Package /PackagePath:xxxxxxxxx.cab or use the GUI tool by @adguard: https://forums.mydigitallife.net/th...ow-rp-19h1_release.79259/page-62#post-1516261
Is for holo: Code: <assemblyIdentity name="Microsoft-Windows-Holographic-OasisAssets-Package" not applicable to normal sku's.