Puzzles me why anyone would want to use that 'lite' theme, when other programs/websites etc are using dark themes to prevent being blinded
Sadly i not know enough about sysprep'ing a system, so cannot really help. Sysprep and me are not the best of friends
Appearently sysprep and I arent friends either atm It gives me an OOBE EULA error, it took me some time and googling to figure out "it is" MRP o V1809 thats causing the issue.. I'll keep trying, i bet it works just fine if I add it to *.wim or iso after hand...
Why do you put MRP in before sysprep/capture? When i sysprep a wim in VMWare, i never use MRP for it, i install windows in audit mode, do my things, sysprep and capture it and next i put the MRP stuff in the wim/iso. ps, where did you find that MRP is the cause?
I make a reference image, fully updated and some basic applications. Its captured and added to MDT (For PXE Deployment) I deploy the same reference image to a computer (wether it be a VM, laptop or my mainpc) Install drivers automatically (Done by MDT) I then sysprep it so the end user can create their own user account I also never use MRP before end user deployment or capture, like I wrote. Edit: I just figured MRP has something to do with "C:\Windows\System32\oobe" folder, i found that EULA's are placed there and so does MRP. If its right or wrong, I dont know but not copying MRP to Setup\scripts made OOBE config work An update: I mounted Home x64 1809 and manually copied MRP to "Setup\Scripts", Saved changes and added the wim to WDS, It did not work! I will try the same with 1803 Another Update: I did the same with 1803. It worked.
As mentioned, MRP will auto clean up the scripts folder after completion, but only on a signout/reboot phase after the desktop has appeared as it uses runonce registry + cmd script to tidy it up which cannot be done when the folder is in use it has always done that so doubt that is the cause.
\Windows\System32\oobe the only files put there are into the Info folder for the .theme which is standard practice or it not work! Nothing is put into the oobe folder itself.
I also doubt it but I made a quick, most likely false connection and removed MRP from being copied and it worked. I edited my last post regarding mounting and copying MRP to Scripts folder in both 1809 and 1803. It worked just fine on 1803 but not 1809 oO The reference images are built the same way. I'll try original wim's now
It seems to be pointing to something that has changed in 1809, what is that 'something' i not know of at this moment in time... I am out for a few hours and will take a deeper look (if i can) to see what changes i can see when i get back. As i not personally use other tools to deploy an image out side of normal iso/usb installs i can only detail things i can 'see' -- technically the project should work, but i know it is not compatible with the "OEM Recovery Partition Creator for Windows" tool that is in the MDL Applications section as The_Guardian found out.
Something has definitly changed but what. I'll keep trying myself. I'd love to keep using MRP and the way I install OS the same way as "always" Edit: It doesnt work an original untouched wim either Edit2: Works with untouched ISO, putting the $OEM$ folder in sources