I am done editing the post above with info. Think I included everything I could find. Using my wifes lappy right now. Good thing she is in a good mood. lol Update: No log file either. Now I am done with results. lol
Just did a file compare with 16th jan release and the beta one, nothing changed in MRPinstall.cmd MRPfirstboot same, just the administrator bit added. I not touched oobe.cmd No idea what gone wrong?? Will do a few tests tomorrow as its gone midnight here.
Here is the problem in the oobe.cmd file... IF EXIST "%windir%\Setup\scripts\Install.cmd" CALL "%windir%\Setup\scripts\Install.cmd" Wrong file name. Just checked to make sure I did not mix anything up and I have the 1-8-2017 mrp version but added the decompile.exe to it. The oobe.cmd has the line above thus will not run if using the new beta decompile.exe unless you change the file name to MRPInstall.cmd in the above line. Differences in the decompile.exe's.
Ah you was using an older oobe.cmd Was wondering how it worked in the VM then not on a real pc... Was thinking i bet mshaft changed things again in a sneaky update so that its ok in a VM but not on a actual pc!! Yeah i changed the filenames
I only got the decompile.exe from you not the entire package so I added the decompile.exe to the mrp 1-8-2017 version I had. Differences in files names seems. Is there a newer version on first post? I thought I had to newest public version of mrp but maybe not... Nevermind I see 1-16-2017 on first post so let me grab it. You did name changing and thats it. I will update and add the beta decompile.exe you gave me and try.
The new one is in the first post, 51s, just copy over the decompile i did for you to that and all will be ok. sorry about that i never thought. so much on my mind at moment
I promise i not going to update it for a while, i know i said it before. 52s is a special one off at the moment.
Yep looks ok, as the firstboot is the add-on module that calls user and serverskus (if server is installed). And not forgetting UserTweaks.cmd if a user wishes to use that in the project to do other fancy things
I noticed after a restart the reg entry wasnt there when I entered audit mode again. Trying in my wifes lappy with vmware and will report results.
odd it all worked in VM before... Even in my testing on vbox. in audit mode a regonce entry for mrpfirstboot is present. Then once out of audit and no longer Administrator name, it carrys on and runs the rest of the script(s), including the cleanup bit.
This is with build 1607 without updates. I am going to use windows media downloader and when its in audit mode I will get all updates and see differences. Things are being added all the time for win10. Not really a final product by no means. We are all beta testers. lol
Up to now, the project has run as normal with current updates integrated, including the latest insider builds, can gather that may change when the new W10 is out this year, as we know M$ like to muck about with stuff at the last minute.
I know the project works. That isnt the issue. My issue is with the new method of recovery and bringing images and logos back. This is what I am trying to figure out. When you do a full reset nothing carries over period. I might have to use a different image capturing method to get around M$ bullsh*t. lol
Ok, after much reading and testing, this project cannot be used if creating recovery partition. When you reset (recover) no oem info is transferred. M$ sets everything to its own defaults regardless of what you tried to edit. Not only that but depending if you use 1511, 1607 or windows media creation tool, they all have different results when used with this project. I hate to say it but using this project with recovery tools is senseless and a waste of time. I have tried many different methods to get the images to carry over on a reset but no go. I am going to redo my lappy again and just use windows defaults instead to avoid this game. M$ insist on M$ branding, not oem. This is true on my wife lappy as well. No oem images carried over when she upgraded. M$ wants its brand only. So be it. At least we tried. lol Note: You can edit the recovery image but that is just to much work for a recovery partition. Not only that most users dont want to edit everything when before win10 you just recovered and everything was in its correct location. M$ seems to have targeted this project which doesnt surprise me.
If I can find someone to share the windows 10 opk we might find a workaround to this issue with recovery partitions and its method. No need for above tool. I think I found the workaround for recovery deployment with all needed apps and user profile info. Testing now... Thanks M$ for the handy info on this subject. I am going to have to write a book on how to setup and deploy recovery image for win10. lol