something went a bit wrong.... MRP started the Addon-Manager but something caused it to abort part way.... did the Setupcomplete.cmd have a shutdown timer left in which caused a delayed reboot?
How about sharing the setup complete command file for us to look at. At this point the only thing we can do is guess. I'm on my phone I don't have a computer at this moment so I can't do a VM install with capturing.
Something i have been privately testing.... Spoiler: Testing... Code: [TBTMS] =========================================== [TBTMS] ===[ Brand Transfer Management Routine ]=== [TBTMS] =========================================== [RMXML] OOBE.xml file has been processed. [WPFSN] Note: The 'Wallpaper.jpg' file size was greater than 256kb. [BGDFC] Desktop 'Backgrounds' folder has been created. [BGDFC] The 'BackgroundDefault.jpg' file was created from 'Wallpaper.jpg'. [BGFSN] Note: The 'BackgroundDefault.jpg' file size was greater than 256kb. [W8XAP] ============================================== [W8XAP] ===[ Main User Account Picture Management ]=== [W8XAP] ============================================== [UBREP] User.bmp replaced. [UPREP] User.png replaced. [WXAP2] ===================================================== [WXAP2] ===[ Additional User Account Pictures Management ]=== [WXAP2] ===================================================== [UPREP] User-32.png replaced. [UPREP] User-40.png replaced. [UPREP] User-48.png replaced. [UPREP] User-192.png replaced. [X8LLR] ==================================== [X8LLR] ===[ Lock/Login Screen Routines ]=== [X8LLR] ==================================== [WX8LS] Lock Screen 'img100' replaced with 'LockScreen.jpg'. Original renamed as img0100. Still work in progress but the lock screen does change from the Log-On screen if that 'LockScreen.jpg' file is detected within the brand's folder, this is ONLY for W8.1 to 10. The 256kb note is just for information as that does not affect w8.1+ i will most likely have flags that suppress that message on 8.x and later. Once i am happy that all works as it should and not affect anything else i will give more details. Hopefully one new 'feature' for v114 MRP
Bringing the updates, as usual Do you guys and girls remember I had issues deploying V1809 with MRP earlier? I got a "Something went wrong OOBEEULA" error and I couldn't do anything. The past days I've been experimenting once again and found that when Im not using MRPConfig.ini everything works perfectly. Now, I/we would need to know if any option in that config would cause an issue with EULA or OOBE? I find it highly unlikely tho. Attached is a list of all options I ticked Yes for. I can probably see BlockCortana doing something fishy.
Can you share the ini file? I had some issues with oobe errors before, but with full ticked (test) ini's, but only when i applied the image, using a specific script, murphy78's diskpart and image apply script, not when using the normal windows setup. I solved that issue by first installing the os in audit mode, sysprpep and capture it, now it works using that script too
Its attached. Im not using any script like murphy yet. In the attached I've set blockcortana to no. Edit: It was not BlockCortana and searh continues tomorrow
I have been careful to make sure that the MRP's .ini can be universally created for all supported OS's, so that if a option is not designed for what is being installed then it will be ignored during the Windows installation. So for example anything designed for W8.1 that is not possible/needed etc on other OS's like the 'Thin Borders' it will be auto ignored on any other OS. If the OOBE EULA failure message only happens on Windows 10, it may be one of the 'Safe Apps' removals, as Windows is so picky on removing them these days. It may even be a timing problem... I have encountered that error, and another very similar to it, a couple of times. Just guessing it is one of the 'safe apps' -- but because it not do it constantly, this makes pin pointing the fault awkward. Once it can be nailed to a particular option i can put a warning note/message popup when that option is selected. Or have it auto disable a known problem option when combined with another that causes that error to happen during install...
Since Im using MDT its a "LiteTouch" variant. Its weird. I tried both on a clean ISO and my updated. I'll keep looking Im going through changes and will soon try those bloody apps! I dont know why MS put those apps there, they're horrific. Its just annoying and you shoudnt worry too much about it for now
Thats what MS does all the time Its one of the fckers causing the issue: Block Ads Remove Edge shortcut Dont allow Update Diagnostic Never Edit: May have noticed something weird, 1 or 2 last syspreps wallpapers wasnt set Edit2: Replaced OEM-folder and it seems fine now. last option Im trying now is "BlockAdverts" All else didnt cause an error. WinTel.cmd is present Edit3: BlockAdverts=Yes caused the issue! I will try one more time with Wintel removed and one time with my regular settings ticked Edit4: Going back to initial MRPConfig and unticking Blockadverts fails! Also fails with BlockCortana. Edit5: 12 May Now its even dumber! Now I can only have General Options selected. Nothing else Spoiler FUUUU MS
MRP 114 Progress report... Have sorted the use of a separate "Lock Screen" image for Windows 10! Windows 8.1 may not work as expected so MRP will ignore changing the Lock Screen via this new method for that OS. More details later.. Also testing a new Win 10 (19H1+) option - disable the 'over the top' blurred log on background screen - So far results have been promising. A revert script for the new option will be added in the "\Optional\Misc_ExtraScripts\Windows10_Kernels" folder if required once it has passed all testing and m$ not decide to remove that policy!
MRP 114 is at Test Version 8 and is close to Release Candidate 1 status. QT 95 is at RC5 and soon be ready... Quite a bit of code updates done internally, also some extra tidying and enhanced error checking etc. More details a bit later...