This probably needs its own thread but here goes. I know the purpose of MDT (MS Deployment Toolkit) is to have as much as possible automated but Id still want to use OOBE (Create username, Wi-Fi and computername, language settings) Is that possible? Also what kind of settings is usable/best to automate MDT? Also. I have OEM-files to be copied, can I copy them during postinstall, right before sysprep? (Its MRP-Project) /Andpe
You can just install win10 & then install your IRST driver or Optane. No need to waste time loading or integrating drivers.
you cant install intel optane memory if i installed intel rst driver after installation... thats why i am asking.
For Optane memory, you install the OS to your HDD first, then run SetupOptaneMemory to install drivers & enable it...
Once again, a huge thanks to JFX (author of GetWAIKTools, WinNTSetup, etc.) He did a test with ImageX from the 17754 ADK preview, and it seems the buggy behaviour with direct apply of UUP files has been fixed. Until now, we were forced to use ImageX version 15063 for things like this: Code: imagex /apply e:\pro.esd 3 c: /ref e:\*.* I know most people here probably go the "convert to iso" route, but direct apply of UUP files can be handy, and it's nice to see Microsoft has finally done something to fix the issue. [BTW, I just tested this as well and can confirm 17754 seems to work OK]
I have done some tests with ImageX from the 17754 ADK preview. As a test, I did repeated applies of the UUP files of Windows 10 Insider Preview 17751 x64 from PE, using an old test PC with conventional HDs. I used two test scenarios, the only difference between the two is the version of ImageX: either 15063 or the new 17754. The first unexpected result is that the new one seems to be a LOT faster! 5m00s for 15063, 3m00s for 17754. Wow, that's a 40% speed increase! The second issue is very weird: For both apply tests, I do a dir list to a file, and as expected, both lists are the same (except for some folder creation time stamps). So far so good... What's really driving me crazy though: With the 17754 apply, my registry changes do not work anymore when I run them from a batch file (!!). This is the batch I use (let's call it "do-registry.cmd"): Code: reg load hklm\temp c:\windows\system32\config\software reg import q:\apply\myreg-software.reg reg unload hklm\temp The .reg file in that batch does some "pre-boot" registry changes (disable defender, disable system restore, etc), and running a batch like this has worked for all the applies I've done over the last few years. But with the apply done with ImageX 17754, running the batch does NOT apply the changes! When I run the 3 lines of code 1-by-1 from the command line, it DOES work. As I said, this is driving me nuts, I can't figure out what could be different between the two applies. Maybe something to do with different permissions or something, assigned by the new ImageX? But then why does it work when I run the commands one by one? Any help, or tips on other stuff to test, would be greatly welcomed.
...more testing, tried Erwan.l's excellent "OfflineReg" which (of course) did the reg changes flawlessly after the new ImageX 17754 UUP apply (from PE): Code: offlinereg.exe "c:\windows\system32\config\software" " " run commands.txt Spoiler: Commands.txt: Code: "Microsoft\Windows NT\CurrentVersion\Image File Execution Options\MicrosoftEdge.exe" setvalue "Debugger" "NUL" 1 "Microsoft\Windows\CurrentVersion\DriverSearching" setvalue "SearchOrderConfig" 0 4 "Microsoft\Windows\CurrentVersion\Policies\System" setvalue "EnableLUA" 0 4 "Microsoft\Windows\CurrentVersion\Policies\System" setvalue "EnableFirstLogonAnimation" 0 4 "Microsoft\Windows Defender" setvalue "DisableAntiSpyware" 1 4 "Microsoft\Windows Defender\Real-Time Protection" setvalue "DisableRealtimeMonitoring" 1 4 "Microsoft\Windows NT\CurrentVersion\SystemRestore" setvalue "DisableSR" 1 4 "Microsoft\Windows NT\CurrentVersion\Winlogon" setvalue "EnableFirstLogonAnimation" 0 4 "Policies\Microsoft\Windows Defender" setvalue "DisableAntiSpyware" 1 4 But my original question remains: why does this not work anymore when using "reg load/ import/ unload" from a batch file?
Well, I guess this ImageX issue is quite a "niche" problem, but let's try to wrap up some things I've found until now: (1) Using an x86 PE to apply an x64 OS (using ImageX) was never a problem, neither was using "reg load/ import/ unload" in a batch file after apply. (2) With ImageX 17754, for unknown reasons this does not work (for me, at least). It's not clear WHY, all the files seem to be there, "reg.exe" does not return an error, but still the registry is NOT modified. (3) Version differences between the PE source used and the ImageX version do not matter (using 17754 x86 PE has the same result as, say, 17134). (4) Using x86 PE to apply x86 OS, or x64 PE to apply x64 OS, there are no problems at all.