Please insert to the MRP package script for enable and disable Windows Update automatic driver installation. I am unsuccessfully trying revert settings in Windows 10 1709.
These are the revert reg entries to allow drivers etc via WU... Spoiler: WU Driver Block - Revert script Code: @echo off REM Revert Driver Blocks reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\DriverSearching" /v "DontSearchWindowsUpdate" /t REG_DWORD /d "0" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Device Metadata" /v "PreventDeviceMetadataFromNetwork" /t REG_DWORD /d "0" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\DriverSearching" /v "DriverUpdateWizardWuSearchEnabled" /t REG_DWORD /d "1" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\DriverSearching" /v "SearchOrderConfig" /t REG_DWORD /d "1" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d "0" /f >NUL 2>&1 Reg add "HKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d "0" /f >NUL 2>&1 REM For x64 systems use above lines also. reg add "HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\DriverSearching" /v "DontSearchWindowsUpdate" /t REG_DWORD /d "0" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\Device Metadata" /v "PreventDeviceMetadataFromNetwork" /t REG_DWORD /d "0" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\DriverSearching" /v "DriverUpdateWizardWuSearchEnabled" /t REG_DWORD /d "1" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\DriverSearching" /v "SearchOrderConfig" /t REG_DWORD /d "1" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\WindowsUpdate" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d "0" /f >NUL 2>&1 Reg add "HKLM\SOFTWARE\WOW6432Node\Microsoft\WindowsUpdate\UX\Settings" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d "0" /f >NUL 2>&1 That is why the tool tip in the config creator, (when you hover the mouse pointer over that option), has a yellow warning symbol that it changes polices. If unsure you wish to use that option then don't tick the box. I have added a script in the 'Optional' folder called RevertWUDriverBlocks.cmd for the next release, this as the name says, will revert the WU driver blocks if you had used the option to block them via the Config Creator. The revert script needs to be ran 'as Administrator' and a reboot will be required after to allow the OS to accept the changes.
@JanCerny , Looking at that site about ReFS enabling, doing the registry edit is easy enough although the other commands to format etc are not possible within MRP. For a test - In Oobe.cmd add this line above the DEL line at the bottom of the script so it looks like below: Spoiler: ReFS Reg Edit {Experimental} Code: Reg add "HKLM\SYSTEM\CurrentControlSet\Control\MiniNT" /v "AllowRefsFormatOverNonMirrorVolume" /t REG_DWORD /d "1" /f >NUL :CLOSE DEL /F /Q "%0%" >nul As this is for Windows 8.x/10 the above line should not be added to a Windows 7 or below OS, it probably would be ignored by those older OS's but to be safe it is best not to clutter the Registry with it. Use at your own risk! The line needs to be added to the Oobe.cmd as during the Windows Setup there is a restart stage which would 'activate' that registry insertion just before the username creation etc is shown. If added to SetupComplete.cmd it would not be 'active' until a system reboot is manually done after Windows Setup/MRP has completed. I have finalized the code for MRP 84 and it is already archived ready to release shortly, so i wont be adding the option this time. If the above test line works then i will add the new option in for v85. Nice to see that the QT does detect the NVme Boot Drive Information - BusType: NVMe Not sure why the SLIC line has a blank area for the name but that a minor glitch, the main thing is that the SLIC version 2.4 is detected.
MRP v84.0 Baseline has been uploaded and 2nd post link updated, also new password and hash information. Spoiler: Quick Summary + Added a new WMIC OS Version check (experimental) which hopefully will show the Version better also will display the SKU Code number in {xx} form next to the Version and Registry Edition lines. + Updated some error checking routines. + Fixed a little bug that if the OEM's.7z file is deleted some elements gave errors. Due to new routines that upset some variables. + Added some new Editions to the database that should cover the new Editions that will become available in either RS4 or RS5 Insider branches. + A few slight rewording here and there. + Tidied up of some redundant/duplicate/test code. Within the Optional folder of the MRP archive you will see a new script called 'RevertWUDriverBlocks.cmd' this will revert the WU Driver blocks if you used the option to block them via the Config Creator and wish to use WU to obtain any drivers later. Run this script as Administrator, (or it will fail to set the registry/policies), and then reboot your computer. The Config Creator has been updated with some new information on the tool-tips (when you hover the mouse pointer over an option). No other changes made. Also the readme for the Creator has been updated too.
General Information for MRP 85.0.Txx Have added the option for Enabling ReFS via Config Creator (v2.4), it will only work on OS's that are capable of using the new filing system such as: Windows 8.x/10 (it may be limited to the Edition installed and may not function if not supported ie Home/Core) Server 2012, 2012R2, 2016 onwards. Windows Vista, 7 and Servers based on those older kernels will disable the option within MRP automatically to prevent any odd effects. Note: This will be a experimental option -- use at your own risk! Beta testing will begin soon, however if during testing the option does not work as intended it will be removed. I have mentioned that you can test the ReFS 'option' in a previous post by manually adding the REG entry via oobe.cmd - see here but note that there are no safeguards with that method and may cause the OS to act in a non wanted way if it does not support ReFS. Also added the registry fix to show the full 30 days grace remaining on Vista/7/Servers if no SLIC is present or if you use the Retail.txt file method to bypass OEM activation. Thanks @Carlos Detweiller for the 'show 30 days' reg entry information.
in testing i got the message: ReFS file system is not supported on this device. Format failed. Command used: Format F: /u /fs:refs /i:enable (F: being the test HDD i was using.) Tested on Windows 10 Pro (RS3 16299.125). Not tried the VHDX and Storage Spaces (Create Pool) stuff... But it does set the Registry entry correct. As i have never used ReFS before it might just be me not doing something in the right order. At least the option appears to 'work' Spoiler: Snipped Project.log 85 T1 Code: [CTNAB] Block Cortana tweak applied. [XREFS] Enable ReFS {Resilient File System} tweak has been applied. [AUTDN] MRP Auto System Drive rename option enabled, 'Local Disk' changed to 'Windows_10_Pro'. More testing and research is needed...
Afaik only supported on ProWS and Enterprise Client SKUs . Was removed from Pro to have an argument for ProWS . EDIT: Not sure regarding Education (might have it too).
Ah no wonder lol. Typical m$ change the goalposts as always. Well i am not going to spend too much time on that option with loads of error/edition checking so if it works then it's a bonus, if not then blame m$
Confirmed formatted the F drive as ReFS under ProWs (however the OS needed to be activated before it would work!)... It now shows F: as ReFS as its Filing System Not sure what i am going to do with it but at least it worked. Edit: Updated ToolTip in ConfigCreator to reflect that the ReFS option may be limited to some Editions.
hi, @mxman2k does it make any difference if i use your $oem$ with win 10 pro vl iso to activate win 10 pro oem licence? and similar with win 8.1 pro vl and win 7 pro vl? and on similar but another subject, if i have a hwid digital licence for win 10 pro, and i use win 10 pro vl iso, will i be able to activate it?
MRP will detect what OS/Edition being installed and if no OEM activation can be done then only branding will be carried out (if it can detect what make the mainboard is). Or use the CustomTheme to choose a brand, say your PC is a Acer you can tell MRP to use Alienware, (or one of the other 130+ brands available). With regards to VL, the project will just attempt to sort out the logo's/branding side etc as activation will not be OEM related. If you have a HWID and use a VL edition then the HWID will be ignored because that is for retail versions. You would still need to use either a MAK key or a KMS solution to activate the OS. It is all to to with Licensing. If you have a HWID for Pro there is really no need to use a VL edition of Pro because you will have to use another method to activate it. Just install a OEMRET version of Pro and MRP will do all the branding, (if possible), and when you go online the OS will automatically activate using the HWID you have.
thanks for confirming that, user can not activate oem, hwid digital licence using vl iso's. thats what i wanted to know.
OEM - uses a retail/COA key , SLIC/MSDM or HWID. Volume - uses a MAK/gVLK key, (or KMS solution). MRP is designed for OEM/Retail systems. It will work on a Volume edition and will attempt to determine a brand, but obviously not be able to activate it due to the licensing channels. Sorry if my replies are a bit 'fuzzy' , not long woke up
Code: Multi-OEM/Retail Project Version : 180226-R84.0 - BaseLine [MRP via MDL Forum ONLY] Required project files extracted successfully. DeCompile has detected a 'VMware' Virtual Machine. OEM's folder detected, structure appears OK. Detected Config File - Checking For User Options... Config Creator Version Used - v2.3 - Options Pre-Check Completed. MRP Logging Mode : Enhanced Confirm File Delete : Enabled W10 TitleBar Color : Enabled - Title Bars will be colorized to Grey. Hi-Lite Colorization : Enabled - Hi-Lited Text will be colorized to Grey. CustomTheme option : Enabled - Using 'CZC' defined in the MRPConfig file. No Lock/Login Screen : Enabled - Lock/Login Screen's will NOT be replaced. Show 'ThisPC' On Desktop : Enabled OS Installation Date/Time : 03/02/2018 {UTC} -- 10:05pm [OSINF] ======================= [OSINF] Detected OS Information [OSINF] ======================= [OSINF] Version {SKU} : Windows 10 Home N {98} [OSINF] Edition {Registry} : CoreN {98} [OSINF] Edition {CBS} : CoreN [OSINF] Architecture : 64 Bits [OSINF] Build Information : 17112.1.amd64fre.rs4_release.180227-1537 [OSINF] Update Build Revision : 1 [OSINF] Edition Language/Code : en-US / 1033 {409h} [OSINF] Locale : en-US [OSINF] Language Name Value : ENU [OSINF] ======================= [MBINF] ======================= [MBINF] Motherboard Information [MBINF] ======================= [MBINF] #01 CS Product Name : [VMware Virtual Platform] [MBINF] #02 CS Model Name : [VMware Virtual Platform] [MBINF] #04 CS Vendor Name : [VMware, Inc.] [MBINF] #05 CS System Name : [VMware, Inc.] [MBINF] #06 Baseboard Name : [Intel Corporation] [MBINF] #08 BIOS or SLIC ID : [INTEL - 6040000] [MBINF] #09 SLIC Information : [No SLIC Table Present] [MBINF] #11 MSDM Information : [No MSDM Table Present] [MBINF] ======================= [CMINF] ======================= [CMINF] CPU/Memory Information [CMINF] ======================= [CMINF] CPU Name/Type : [Intel{R} Core{TM} i7-3770 CPU @ 3.40GHz] [CMINF] CPU Description : [Intel64 Family 6 Model 58 Stepping 9] [CMINF] CPU Architecture : [32/64 Bit Instruction Set] [CMINF] CPU Cores/Threads : [2] / [2] [CMINF] Total Physical Memory : [4703 Mb] [CMINF] Available Memory : [4322 Mb] [CMINF] ======================= [HDTYP] Info: HDD Detected. [SATOU] List user options enabled or applied... [FEXTS] Show File Extensions option enabled. [REMSC] Remove '-Shortcut' reference from icons option enabled. [AMSRT] Disable 'Malicious Software Removal Tool' tweak applied. [NOWUR] Disable 'Automatic WU Restart After Updates' tweak applied. [GO2TP] Launch To 'ThisPC' instead of 'Quick Access' view option enabled. [APPDT] Apps use 'Dark Theme' option enabled. [REMPB] Remove 'People Band' option enabled. [REM1D] Prevent One Drive from installing tweak enabled. [REM6F] Remove 'Library Folders' from 'ThisPC' view tweak applied. [REM3D] Remove '3D Objects Folder' from 'ThisPC' view tweak applied. [MTTBT] Extra TaskBar Transparency option enabled. [AWLBM] Use 'F8 Legacy Boot Menu' tweak applied. [NOAMT] Disable 'Automatic Computer Maintenance Tasks' tweak applied. [NOFBT] Disable Fast Boot tweak applied. [NODRS] Driver Searching tweak disabled as a 'Core' Edition detected. [CTNAB] Block Cortana tweak applied. [USRDN] User System Drive rename option enabled, 'Local Disk' changed to '17112_1_MRP'. [PKEIC] -> PID.txt/ei.cfg Detection. [PKEIC] The PID.txt file was not detected. [PKEIC] The ei.cfg file "D:\Sources\ei.cfg" was detected. [CKDMI] Querying BIOS for any manufacturer brand information. [VMDMI] Default DMI VMware VM detected with no valid SLIC or MSDM present. [THMOK] VMware [VMware] manufacturer detected. [THMCT] Detected user defined CustomTheme 'CZC' will be used. [UDPNA] User defined 'Computer Model Name' option has been enabled. [CHKMN] Computer Model Name: '17112 MRP Build Test' has been applied. [BRND1] -> Branding Extra Checks Section. [FTHWD] CustomTheme processing. [USRFT] User selected CustomTheme 'CZC' will be applied. [THMMS] -> OEM Brand Transfer Management Section. [WPCHK] Wallpaper.jpg transferred. [BGDFC] Desktop backgrounds folder created. [BGDFC] BackgroundDefault.jpg created from Wallpaper.jpg. [W8XAP] -> Windows 10: User Account Picture Management {1}. [RMXML] OOBE.xml file processed. [UBREP] User.bmp replaced. [UPREP] User.png replaced. [UPREP] User-40.png replaced. [WXAP2] -> Windows 10: User Account Picture Management {2}. [UPREP] User-32.png replaced. [UPREP] User-48.png replaced. [UPREP] User-192.png replaced. [NLLSA] Note: Using Windows default Lock/Log-In Screens as the ChangeLockLoginScreens 'No' option was enabled. [OTFTS] -> OEM Theme Files Transfer Section. [OTFTS] OEM theme folder has been created. [OTFTS] OEM files have been transferred. [USCTA] User specified 'CZC' theme has been applied. [BSHCS] Branding script has completed. [ADMAN] Add-On Manager: Started. [SATOU] -> Show User options applied. [FEXTS] Show File Extensions tweak applied. [REMSC] Remove '-Shortcut' on icons tweak applied. [REMPB] Remove 'People Band' tweak applied. [GO2TP] LaunchTo 'ThisPC' instead of 'Quick Access' tweak applied. [APPDT] Apps use 'Dark Theme' tweak applied. [REM1D] Prevent One Drive from installing tweak applied. [MTTBT] Extra TaskBar Transparency tweak applied. [USRAC] Windows 10: Enhanced Log-On screen has been enabled. [WXSTB] Windows 10: Title Bar 'Grey' Colorization applied. [WXSHL] Windows 10: Hi-Lite 'Grey' Text Color applied. [USRAC] 'User Account Picture' registry entry applied. [USRRO] Windows 'Registered Owner' {Winver} registry entry corrected. [USRD0] Detected 'defaultuser0', removal process started. [RDUPM] Removal of 'defaultuser0' account completed. [AMBPS] -> Checking BIOS/Boot mode and OS HDD/SDD partition type. [AMBPS] BIOS/Boot Mode : Legacy [AMBPS] Partition Type : MBR [AMHDC] Controller Mode : AHCI [CHKLS] -> Check if Windows is activated/licensed. [CHKLS] License Status: Notification [OSLRC] License Status Reason Code: 0xC004F034 [OSLRT] License not found/invalid or could not connect to the Activation Server. [CHKLS] Online connection maybe required to complete activation. [ADMAN] Add-On Manager: Completed. [CLNUP] MRP Clean Up Routine Processed. ========================================================================================= = Please Note: It is advisable to logout or reboot your computer when possible to = = allow the Windows OS installed to finalize any settings. = = = = If you have used any tweak options within the configuration file then = = it is required to do a log out or reboot cycle to allow these options = = to take effect. = ========================================================================================= The Multi-OEM/Retail Project has completed.