Hi guys, I have two different .iso of Windows 10, one for the home version and the other for professional. Is it possible to make one single iso which contains both of them? Thanks
Hi, is there a way in Windows 10 AutoUnattend.xml to configure the "customize settings" at the oobe at the end on the install ? I want to set all of the options to off (smartscreen, error report ... etc). View attachment 37557 View attachment 37558 In Windows 8.1 i used to cancel the screen where it says "Hi", and with the color changing background with this registry entry in the "setupcomplete.cmd", does it work also in Windows 10 to pass that stage ? Code: reg.exe add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\StartPage" /v OpenAtLogon /d 0 /t REG_DWORD /f
Does anyone have an AutoUnattend.xml template for Windows 10. There should be new customization options to disable new data collection options, to customize new start menu etc.
Download the ADK & custom build it yourself using Windows System Image Manager (SIM). Links to the RTM are in this thread.
Does anyone encounter problems in the RTM with deployed imaged that was captured (from audit mode)? When I use that wim I always the error during OOBE: "windows could not complete the installation. to install on this computer restart the installation" I deployed the same things in my windowa 8.1 installation without problems in Audit mode and the installation went smooth. Does anyone know?
Sysprep /oobe /generalize then booting to winpe for capture? Works for me. Maybe something in your unattend? In one of the MS guides they make the provisioning package then sysprep WITHOUT /generalize - don't know why though...
No, I decided to test them with VM, shutdown after the audit mode, attach the virtual disk file, capture it (I use the dism from the installation) and replace the install.wim file, labeled as "Windows 10 Pro". On both VBox and Hyper-V the outcome was the same
You say your script doesn't run, but you also state it doesn't copy the $OEM$ folder contents. Having the file exist helps alot when trying to run it The only reason i can think of that your $OEM$ folder doesn't copy over is that you used an OEM\bios key for your install, as that disables oobe.cmd, setupcomplete.cmd, and i think copying the $OEM$ folder at all. How i get around this is running setup.exe with the switch /m:"path to oem folder" and it will copy the folder like normal. I think. I'm half asleep.
$oem$ is copy same as other win 7 and win 8 ... done it successfully... i wonder if hyper-v can be install via autounattend file.... if someone know pls let me know... else i'll skip it and install own...
Is it just me, or is it not possible anymore to remove the payload of features using DISM? command: dism /image:G:\WIM /disable-feature /featurename:xxx /remove For Windows 8.1 images the features would show up as "Disabled with Payload Removed", but with Windows 10 it just shows "Disabled", which indicates the files are not removed.
Yeah I noticed this too, I have been trying to figure out what has changed or if something different has to be done.
damn windows update auto restart... lol i have a list of software to install after login windows... but it just restart half way installing.... anyone notice this? ask windows update to be disable... access denied
I suppose this is a fairly basic question, but is it still necessary to build a separate UEFI and Legacy image or is there a way of unifying deployments so they will run on any system irrespective of the BIOS setup they use?
You can apply the same image to both platforms. Partition structure is different of course. Use BCDboot to make it bootable.