Seems anybody will have the same reaction on the messages you've sited: in my list most part of them are indicated by a lot of #, comment character in PShell. I've started with "Geographical location".
Query Tool v35 uploaded and first post password updated. + Added extra Reason Codes (now at 398). + Added check for eMMC and NVMe (experimental). No other changes made.
Yet not works NVMe-support: HDD Mode/Partition - [Undefined, possible customized chipset.] / [GPT, Secure Boot: Enabled]
hmm i did say it was experimental lol. the next thing is to use another tool to obtain said info about SSD's and types... just got to work a way to save the data and parse that. Are you using v35 i not long uploaded? seems like your using an older version. it should of said: HDD Mode/Partition - [NVMe/eMMC] / GPT etc
Code: MRP - OEM Query Tool v35.0 Enhanced -- ma 27-11-2017 -- 9:49pm ------------------------------------------- - Basic OEM Information For This Computer - ------------------------------------------- OS Name - Windows 10 Home x86 OS Edition {Registry} - Core OS Edition {WMIC} - 15, OS Build Number - 16299 OS Update Build Revision - 64 OS Language Name/Code - nl-NL / Dec:1043 {Hex:413} OS Locale - nl-NL OS Language Value - NLD OS Installation Date - 22-11-2017 03:29:19 CPU Name - Intel{R} Atom{TM} CPU Z3740 @ 1.33GHz CPU Description - x64 Family 6 Model 55 Stepping 3 CPU Architecture - 32/64 Bit Instruction Set CPU Cores/Threads - [4] / [4] HDD Mode/Partition - [NVMe/eMMC] / [GPT, Secure Boot: Enabled] Bios Version - [T100TA.314, 08/13/2015] Total Physical Memory - [1933 Mb] Available Memory - [141 Mb] GPU Primary Adaptor Name - [Intel{R} HD Graphics] -------------------- - Scanned DMI/BIOS - -------------------- #01 CSProduct Name - T100TA #09 SLIC Version - No SLIC Table Detected #02 CSModel Name - T100TA #10 Product Key - Not Shown On Saved Report #03 CSBaseboard Prod - T100TA #11 MSDM Key - Not Shown On Saved Report #04 CSProduct Vendor - ASUSTeK COMPUTER INC. #11 MSDM Edition - Win 8.1 Core #05 CSManufacturer - ASUSTeK COMPUTER INC. #11 MSDM Brand Name - Asus #06 Baseboard MFR - ASUSTeK COMPUTER INC. #12 BIOS/Boot Mode - UEFI/GPT #07 Serial/Service Tag - Not Shown On Saved Report #13 Certificate - Not Present #08 BIOS or SLIC ID - _ASUS_ #14 License Status - Licensed {Retail/Digital License} ----------- - Summary - ----------- OEM Theme/Branding - Asus [id: #04] OEM Activation Vista/7 - Asus [id: #08] Valid OEM Consumer OS - Win8.x/Win10 Only MSDM Check Method Used - {M1} .Net Versions Detected - v1.1.4322 v2.0.50727 v3.5 v4.0.30319 v4.7.02556 Powershell Version{s} - 1.0, 2.0, 3.0, 4.0, 5.0, 5.1 License Status Reason - 0x4004F401: This computer has a valid Digital/Store License. Other Notes: - [#9] SLIC Version may not show correctly with UEFI/Secure Boot enabled. - Possible Edition switch detected. ** End of Query Tool report. ** - Possible Edition switch detected. (no switch, only 8.1 Core upgrade to 10 Home)
Available Memory - [141 Mb] possible edition switch hmm ah i see why it has 15, as WMIC detection , hence QT sees it as not a match with Registry. OS Edition {Registry} - Core OS Edition {WMIC} - 15,
150mb for that candy crap! gez i know had to download it for a friends daughter, and she still not got past level 5 (3 months later).
Yes, I have both, v33 and v35 and seems have clicked an old one, sorry. v35 issues: Code: Basic OEM Information For This Computer ======================================= OS Name - Windows 10 Pro for Workstations Insider Preview x64 OS Edition {Registry} - Professional OS Edition {WMIC} - ProfessionalWorkstation OS Build/Update Revision - 17046 / 1000 OS Language Name/Code - en-US / Dec:1033 {Hex:409} OS Locale/Language Value - en-US / ENU OS Installation Date - 2017-11-22 22:45:44 CPU Name - Intel{R} Core{TM} i7-7700HQ CPU @ 2.80GHz CPU Description - Intel64 Family 6 Model 158 Stepping 9 CPU Architecture - 32/64 Bit Instruction Set CPU Cores/Threads - [4] / [8] HDD Mode/Partition - [NVMe/eMMC] / [GPT, Secure Boot: Enabled] BIOS Version - [N1UET41W (1.15 ), 10/20/2017] MEMORY Total/Available - [32590 Mb] / [29784 Mb] GPU Primary Adaptor Name - [Intel{R} HD Graphics 630]
The Pro and ProWS part? That's because you did a licence change, ie just insert the ProWS key. In the summary section at the bottom it would of mentioned Possible License switch. Basically it shows that Professional was installed first then the 'upgrade' to ProWS, it is not an error. The NVMe/eMMC is because i use a simple check, at some point i will expand this part, but for now that top section is just basic information. When i do a total re-write with a GUI interface the detection's will hopefully be more accurate.
Certainly, it is Insider system and I've used official ProWS keys for Insiders since 16257 and at one moment, don't remember already in which build, I've got a digital certificate. P.S: when I've refused Skip ahead and set fast ring, immediatly digital certificate activation happend. Am not sure but maybe even in16257 or somewhat later build.
Been playing about with Server 2016 and the lock/log-in screen not working like it does on Windows 10... Have now managed to get it to work! it may also work on other Server OS's too (apart from S2012 win8.0 kernel as that uses solid color only). Had to reinstall the S2016 on the test pc as i forgot the password i used the other day. The Reg entries i have used are (via a admin command prompt) : Code: Reg.exe add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Personalization" /v "LockScreenImage" /t REG_SZ /d "C:\Windows\Web\Screen\img100.jpg" /f Reg.exe add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Personalization" /v "LockScreenOverlaysDisabled" /t REG_DWORD /d "1" /f First line is to set the lock/log screen image location, the 2nd is to untick the box about adverts etc, not sure if they are shown on a Server 2016 lock screen but added it to make sure none are shown anyway. The above was tested on a running server. Hmm the only 'problem' is that the lock/login change part in the Settings app is now greyed out so they are 'locked' to the image that has been set. Not that you can change them in the Settings app anyway, it not change the screen even if you do via settings! * M$ have dropped the ball there i think, why have the setting to allow you to personalize the lock/login yet it does not do anything? Would this cause problems for those that use the MRP with a Server install? So i will hold off adding the lines for now until i get some feedback. Obviously to revert the policy change you just need to go into the registry and delete the above entries and you can then change the screens via the settings app. (* well you can but they not work as mentioned above!)
You ccould add this to the MRPConfig under specific server setting? - "Set MRP/OEM as lockscreen image?" Yes or no
once you have created the MRPConfig.ini file place it in the Scripts folder where oobe.cmd, Decompile.exe and OEM's.7z are. it is mentioned in the readme somewhere. unless i uploaded the wrong text file again Yeah berk me not got the right text file i think the one in the archive still references the old method. Will get it sorted for next release. But once you have created the config.ini file using the Creator program, just copy/move the ini to the scripts folder as mentioned above. MRP will detect and parse it then action on it as it processes.