@galen2 it is easily done, many times when testing the MRP i have forgot the ei.cfg and ended up with the wrong edition installed and no log.
I like how you remove Shawn Brink's info from the .reg file as to give the impression you created it. Anyways...no need to use PowerShell's Start-Process to do this: Code: @="CMD /C TAKEOWN /F \"%1\" && ICACLS \"%1\" /GRANT *S-1-3-4:F /C /L" "IsolatedCommand"="CMD /C TAKEOWN /F \"%1\" && ICACLS \"%1\" /GRANT *S-1-3-4:F /C /L" @="CMD /C TAKEOWN /F \"%1\" /R /D Y && ICACLS \"%1\" /GRANT *S-1-5-32-544:F /T /C /L /Q" "IsolatedCommand"="CMD /C TAKEOWN /F \"%1\" /R /D Y && ICACLS \"%1\" /GRANT *S-1-5-32-544:F /T /C /L /Q" etc.
I think you right . before that post, is originally after windows installed.. and arms count left 3. idk what mean by that.. and how to reset. because windows 7 that I've used is retail. and never using arms/reams toll. this below I've using loader and rebooted. Spoiler: QT40 Code: MRP - OEM Query Tool v40.0 Enhanced -- Tue 12/26/2017 -- 1:40pm ------------------------------------------- - Basic OEM Information For This Computer - ------------------------------------------- OS Version {Registry} - Windows 7 Ultimate x64 OS Edition {Registry} - Ultimate OS Build Number - 7601 OS Language Name/Code - en-US / Dec:1033 {Hex:409} OS Locale - en-US OS Language Value - ENU OS Installation Date - 12/23/2017 5:13:41 AM CPU Name - Intel{R} Core{TM} i5-4210U CPU @ 1.70GHz CPU Description - Intel64 Family 6 Model 69 Stepping 1 CPU Architecture - 32/64 Bit Instruction Set CPU Cores/Threads - [2] / [4] HDD {Boot} Information - [Mode:AHCI, Partition:MBR] Bios Version - [V1.21, 09/24/2014] Total Physical Memory - [4023 Mb] Available Memory - [2141 Mb] GPU Primary Adaptor Name - [NVIDIA GeForce 820M] -------------------- - Scanned DMI/BIOS - -------------------- #01 CSProduct Name - Aspire E5-471G #09 SLIC Information - v2.1 {Emulated?} #02 CSModel Name - Aspire E5-471G #10 Product Key - Not Shown On Saved Report #03 CSBaseboard Prod - EA40_HB #11 MSDM Key - No MSDM Table Detected #04 CSProduct Vendor - Acer #11 MSDM Edition - Undefined #05 CSManufacturer - Acer #11 MSDM Brand Name - Undefined #06 Baseboard MFR - Acer #12 BIOS/Boot Mode - Legacy/MBR #07 Serial/Service Tag - Not Shown On Saved Report #13 Certificate - Present #08 BIOS or SLIC ID - ACRSYS #14 License Status - Licensed {OEM_SLP} ----------- - Summary - ----------- OEM Theme/Branding - Acer [id: #04] OEM Activation Vista/7 - Acer [id: #08] Valid OEM Consumer OS - Vista/Win7 Only .Net Versions Detected - v1.1.4322 v2.0.50727 v3.5 v4.0.30319 v4.6.01055 Powershell Version{s} - 1.0, 2.0 ** End of Query Tool report. ** but now, slic 2.1 and "emulated". what means that? I've used default loader set, not disable partition or things. and maybe in loader sett must check list memory legacy, and must add patch oem table id's maybe
#09 SLIC Information - v2.1 {Emulated?} --> means that he QT has detected a possible emulated SLIC hence the ? at the end as sometimes if you have a dual boot with Linux it can trigger this flag. In your case the Emulated means Daz's Loader was used.
Microsoft making mistakes! never Regarding the HealthStatus i will disable that message line and check code in the next QT. Thanks @abbodi1406 for the extra info regarding this return value.
nope, I dont have dual windows..just one.. so what must I do to eliminate that word "emulate" thing, so just show slic 2.1 without add emulate in bios sure I dont have msdm in acpi..
Don't worry about the emulated part, its only information for the user. The MSDM is for Windows 8.x/10 and not used in a lower OS. The only other way is to have a SLIC mod done for your computer, which would sort that, but flashing a bios can have its risks and I not wish you to possibly 'brick' the computer so it no longer works. The Loader is the safest option. According to Acer's website the model you have originally came with "Linpus Linux" , if that the case then there would be no SLIC or MSDM present in the bios anyway.
wow you had checked my laptop version? thank you, you even checked that well Linux linpus, but in first I buy it, idk linux exist. cause when buy the shop offer me to install windows. So accept it, and when I checked in bios that why he installed windows 8.1 in legacy not uefi. maybe limited tool he haved/not familiar with uefi. because if I reset bios(load setup default) or remove battery inside laptop it default to uefi. but now I used legacy, cause if I missed thing so I can recover. Idk with gpt partition with tool recovery nothing found even with deep scan. well sorry maybe about this session it not a topic
I try to do research as much as possible to give the best answer to most questions. It may be they used a Genuine key for Windows 8.1, if so then you should of been given the key. Legacy/Uefi it not matter to Windows for activation. If the SLIC/MSDM is not present in the bios then no tool will find it. The QT can detect if either is present, corrupt/dummy, (most of the time!). The QT was primarily designed just to show what theme/activation can be used with the main project, however it has expanded into a bit more than a simple theme/activation checker. I know there are other programs that can show the other information but wanted to make the QT enhanced to give that little extra information which could help the user find out why something does not work such as activation etc, or just general information about their computer. Judging by the download totals it looks like the QT is the 'go to' tool!
Regarding DriverSearching... I will only add this option for Windows 10/Server 2016 only because there seems to be different reg entries for other OS's. I found other Registry bits that i use in my personal tweaks that does seem prevent the WU drivers from installing. You must make sure the computer is rebooted after using the option and MRP has completed or the search will start automatically - if you are connected to the Internet. Spoiler: Reg Entries for DriverSearching (W10/Server 2016 ONLY)... Code: reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\DriverSearching" /v "DontSearchWindowsUpdate" /t REG_DWORD /d "1" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\DriverSearching" /v "SearchOrderConfig" /t REG_DWORD /d "0" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Device Metadata" /v "PreventDeviceMetadataFromNetwork" /t REG_DWORD /d "1" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\DriverSearching" /v "DriverUpdateWizardWuSearchEnabled" /t REG_DWORD /d "0" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d "1" /f >NUL 2>&1 :: For 64bit reg add "HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\DriverSearching" /v "DontSearchWindowsUpdate" /t REG_DWORD /d "1" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\DriverSearching" /v "SearchOrderConfig" /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 "1" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\DriverSearching" /v "DriverUpdateWizardWuSearchEnabled" /t REG_DWORD /d "0" /f >NUL 2>&1 reg add "HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\WindowsUpdate" /v "ExcludeWUDriversInQualityUpdate" /t REG_DWORD /d "1" /f >NUL 2>&1 Important Note: If this option is enabled to disable the WU Driver Search the option under 'Advanced System Properties' will be greyed out. If you wish to revert this option, you need to delete the above entries from the Registry and reboot, this will set the WU Driver searching to the default 'ON' setting and you can then select which option in the 'Advanced System Properties' area to your liking. Not all the reg entries may be needed but done them anyway to make sure the drivers are not downloaded!
Have added the new option's code into the main project and will be testing that shortly after a short break for dinner. Knew i not have a total break lol.
just curious maybe have key in bios this laptop . so many tool I try, even with cmd.. well I know that now cause I contact the manufacture. like my old toshiba it about release in year 2005(if I not wrong).. it has key inside bios.. well windows xp key btw new tool release.. not QT(still Qt40) I just used that oem folder.. and other inside tool idk how to use like mrpconfig creator .. say many thanks, cause even you checked my laptop. maybe took your time
If there was a MSDM key (for Windows 8.x/10) in the bios then the QT would of shown you the key found and what OS/Edition it was designed for. With Vista/7/Servers - they require a SLIC to be present to be OEM activated. XP used a different method to activate, retail/VLK key or OEMBIOS.xxx files, totally different to these modern OS's. The ConfigCreator is to allow the end user to control certain elements of how MRP works. There is a readme file and if you hover the mouse pointer over the options you will get a tool-tip appear. Converting the GUI text/saved file to other languages will be done at a later time. For now it is in English.
I wont go so far for example editing bios. and yes QT show all option/info about my hardware.. just keep it that way(originally) if bios and other ok, I'll try later the configcreator, and I think it will be new science for me. I do not know why, if it is related to new science I feel exciting and want to know more learn it.
@mxman2k I'd like to run QT on WinPEs to look and get OEM:DM key and related Win version and edition. You know when the machine is ready for reformat or hdd/ssd swapping BUT it is unbootable.
The only thing is under WinPE that .net 2.0/3.5, (maybe 4.x too), needs to be integrated into the wim as those are required for the QT to operate correctly. The MSDM part is definitely dependant on the .Net framework. For OS's lower than 8.0 .Net 2.x is required, maybe v3.5 if it contains 2.x files. For 8.x/10+ .Net 3.5 & 4.0 is minimum required. Never tested on a non installed OS but if the above is present in the PE then i'm sure the QT would operate... If something the QT requires is not present then it will inform you during the 'run' process.
MRP 80.0 test of the new options, for Windows 10 seemed to have worked. Won't bore you all with the whole log, these are the important parts... Code: [NOWUR] Disable Automatic WU Restart After Updates tweak applied. [NOFBT] Disable Fast Boot tweak applied. [NODRS] Disable Driver Searching tweak applied. FastBoot was not ticked (greyed out) in the Power Options. Driver Search was greyed out in 'Advanced System Properties>Hardware>Device Installation Settings' even before a reboot. Shown as 'No (your device might not work as expected)' in that area. Did updates (only security ones - no drivers found or downloaded! ) , it didn't ask about a reboot, although i didn't leave it long enough to see if that pop up appeared, but after a couple of minutes nothing appeared. No toast pop-out thing either. Normally it would of grizzled about a reboot required. Now testing a Win 7 install.... Obviously the Fast Boot/Driver Search options should be ignored as they are for W10/S2016 only and not show...
Windows 7 Test ok. Only the Disable WU restart option shows along with any general options i had chosen, no w8.x/10 options appear. Happy with the editing/new code as i not upset the rest of the script which is so easy to do. Gez searching for updates takes ages on w7. The button to restart after the updates was installed was there as that normal. I closed the Updates window without pressing restart. No 'You need to restart' type pop up has appeared so far... Also no ! on the shutdown button on the Start Menu which indicates updates.... 45 minutes+ still no 'You need to restart blah blah' pop up. Looks like the tweaks work.
More testing is required to fully ensure everything is working , but seems like the options all work as intended. I cannot guarantee they will on every setup as things depends on hardware and software or even if the OS was 'edited' with other tools prior to using MRP.