POWIS - Powerful Windows Setup

operating-system · driver · office · archiver · recovery · Windows · PlayStation · George King

This is from: POWIS - Powerful Windows Setup - Create Windows Setup with Drivers, Software, etc. (youtube.com) POWIS Po werful Wi ndows S etup ​ This tool was developed to bring new user experience into Windows setup, supporting all Windows versions from Vista and newer. What features are added by POWIS? 1. Windows Recovery Environment boot menu option 2. Multi-Unattended selector 3. Dynamic drivers folder 4. DriverPacks solution using Snappy Driver Installer 5. RunOnceEx setup phase a. Certificates installing from any *.CER files b. Microsoft Office installing – 2007 or 2010 – 2016 or 2019 / 365 using YAOCTRI c. MSI Packages installing d. Products activation using Multi-OEM/Retail Project {MRP} - Mk3 or your own custom Activate.cmd e. Updates installing f. Applications installing g. Apply personal settings from any *.REG files h. DriverStore cleanup i. Scripts execution from any *.PS1 or *.BAT or *.CMD files​ 6. ESD support for Windows Vista and Windows 7 What is supported? 1) Any architecture, build and language ISO or extracted setup of Windows Vista SP2*, Windows 7, Windows 8.0, Windows 8.1 and Windows 10. Servers are untested but they should work too. This could be pointed to bootable USB too. 2) Only clean installations are supported 3) Fully Unattended * NOTE: For dynamic drivers folder and automated skipping product key in Windows Vista is needed Windows 8.0 setup engine, if you want these features enable ESDSUPPORT option in config.ini How to use POWIS? 1) Download and extract this tool, for example to C:\POWIS directory 2) Prepare plugins folder. This folder needs your attention a) driverpacks – place any compressed *.7z DriverPacks here. Snappy Driver Installer install compatible drivers before first reboot of deployed system. All available languages in SDI v1.21.2.2102 are mapped to Windows language codes. So perfect multilanguage support is available. If someone translate SDI , these new translations are needed to be hardcoded in Launch.cmd . You can find log files in %WINDIR%\Logs. Download DriverPacks here or here or here . b) drivers – if you want to apply drivers to deployed system before first boot. Place drivers in INF format into certain folders. All directory is for architecture independent drivers, x64 for 64bit drivers and x86 is for 32bit drivers c) oem – This folder is for Multi-OEM/Retail Project {MRP} - Mk3 which is compatible with POWIS solution from v137.1 , Download and extract this project. Needed files are DeCompile.exe, OEM's.7z and OOBE.cmd , then rename OOBE.cmd to OEM.cmd. You can find log files in %WINDIR%\Logs . On Windows 8 and newer you can see black screen during setup for a while. Don’t worry MRP is installed on background. This is caused by Windows setup design, on Windows 7 is this process different and you can see screen with “Setup will continue after restarting your computer“ instead. d) office – All Office versions are supported. For Office 2007 place unattended setup into All subfolder. This Office version is only 32bit and it will be installed on both x86 and x64 systems. For Office 2010 – 2016 create x86 and x64 subfolders and place unattended setup into them. If you want to force 32bit Office on x64 systems place setup into All folder instead. For Office 2019 / 365 is supported YAOCTRI installation method. Just place generated setup directly into office folder. See pictures below e) setup – This folder is here for your own *.CER , *.PS1 , *.BAT , *.CMD , *.REG , EXE and MSI files During setup process is setup folder dynamically scanned, so you can add / remove files perfectly on the fly directly on your USB setup media. You need to follow some rules when adding installers. If your applications have EXE installer for both architecture it must have –all in filename. If there exist standalone installers keep – x86 and –x64 in filename instead. To define silent switch create simple TXT file with same name as application installer, but without architecture identificator. So for WinRAR-x86.exe and WinRAR-x64.exe is needed WinRAR.txt with /S inside as only single line. MSI packages are installed automatically with /quiet /norestart switch. If you want to use your own switches do it in same way as you do for EXE installers. *.CER , *.PS1 , *.BAT , *.CMD , *.REG are silently launched and applied. In scripts don't forget to exit them. f) unattended – place any Unattended files here, if you do it, you will be prompted for selection when setup begin g) updates – place any updates files *.MSU , *.CAB , *.MSP here and they will be silently installed. Just keep - x86 and -x64 in filename, simply follow the same logic as applications installers 3) Configure options in Config.ini 4) Launch POWIS.cmd as Administrator, then drag and drop extracted Windows setup path or ISO or already created bootable USB into console window. You can also use POWIS directly from CMD in your own scripts. See POWIS.cmd /? for more informations. When you point already created bootable USB, it mu