Hello ! I need to know what "DeCompile.exe" create, I want to try with my Recovery Project, It is to avoid having files of the same names Thanks !
not quite sure what you mean... Decompile.exe basically extracts the internal files to a specific folder, much like 7zip, WinRar etc would do. It just makes distribution easier.
Dear Brothers, when we add $$OEaM$$. In sources folder of windows setup, after installation is completed in windows 10 we get the same pictures for lock screen and for desktop background, Is there any way to get a different different image for lock screen and for desktop background in oem folder.
Me again ! I tested with my project and is work, but you delete my script folder in OOBE mode, I need to run my SetupComplete.cmd
Your setupcomplete.cmd should be left alone till mrp is done and reached the desktop (when the cmd already should have ran). Make sure there are no hard exit commands in the setupcomplete.cmd.
setupcomplete.cmd is called by the Windows Setup/oobe system, MRP does not run/call or do anything with that batch script, it only detects if it is present. It is up to the end user to make sure that any commands used within setupcomplete.cmd do not run shutdown.exe that will trigger the auto cleanup of the scripts folder on the next reboot. It is all explained in the read me files that the clean up is auto performed on a reboot/logout-login cycle once the desktop appears - when windows setup has completed.
Ok ok ! Because in OOBE I install drivers and software for the end user, and I must reboot anytime for perform the installation. After that, I run sysprep and the system is ready. I am in Administrator session. Don't worry I can copy my script folder before run sysprep
ah i had an idea it may of been something with sysprep. If you sysprep the OS with all drivers/programs before using MRP you should be ok.
IS WORK ! Thanks As OOBE.cmd is called twice, I modified my script to run DeCompile.exe the second time and it works, I'm quiet like that
Just wondering on the config creator if "disable driver searching" is related to device installation settings "yes or no"? As I keep having driver issues with sound/headphones where Dell/Realtek drivers don't work. It will show the popup when headphones are plugged in but no sound. If I do a frean install or rollback to Microsoft drivers its fine, but once it auto updates there is no sound. So wondering if not already if that could be added to the project or what the registry setting is and I could do it that way.
I believe the two parts are interlinked. The main thing for the MRP option was to prevent any drivers being auto downloaded/installed. However any manually installed OEM/branded made driver etc should work as normal on the hardware it was written for as the MRP option just prevents m$ related ones from WU from being used. Realtek drivers can be a bit strange as some seem to have specific hardware the driver is designed for, one may install ok but bits of it not work as expected. As can be seen in this Realtek driver thread the amount of different versions for different PC makers etc - can be a bit bewildering to say the least! The 'Disable driver searching' MRP option uses the registry to set policies etc to prevent any downloading of drivers via Windows update, plus even if you 'right click' a item within Device Manager and select the search for a driver online.... On Windows 10 Home that is ignored and would still blindly download any 'updated' driver, only on Professional and above Editions the MRP option should 'block' any drivers. If you not use the MRP option then the normal behaviour of driver downloads with WU will happen. Along with using the 'Set connections to metered' option it should prevent any enforced drivers being downloaded. However m$ may have other plans and could revert any settings to default, ON etc... If you use NVidia's own drivers from their website then the update mechanism within that seems to bypass WU and would download and install direct from NVidia. Not sure if AMD graphics drivers do the same. This is then up to the end user to allow those graphics driver updates or not etc which is what should happen, we are given the choice. There is a WU Drivers revert script within the MRP archive in "\Optional\Misc_ExtraScripts\Windows10_Kernels" folder. This should revert all the registry/policy settings. Reboot is required, it may take a couple of reboots before Windows registers the actual changes. I cannot guarantee the revert is 100% but technically it should.
Sorry for delay in replying... Sadly this would make for a whole new re-write in that section of MRP and the OEM's archive stuff which at present i cannot do. I will add it to the 'to-do' list, although sometimes Windows 10 does not like changes to the lock screen section via other methods than the Settings App. If i remember @The_Guardian had a few challenges to get the Lock screen to set as it does now. One reason i left it alone, "if it isn't broke, don't fix it!" -- Pity a certain software company does not have that idea, as they love to break stuff that worked perfectly for ages.
When I sysprep and create custom recovery partitions before I capture the image I copy over MRP to the sources folder so it can run after captioning is done. It's then guaranteed to work every time.