In my clean install of Home SKU, it was enabled from the start. Could change at any time. However, this means WMIC detection on build alone won't work.
M$ like to make things over complicated when in this case with WMIC it was simply to leave it alone! It has its flaws but over the years we come to get around most of those, mainly 32-bit limitations in numeric results.
Heck, they made a Windows 10 version of the Windows 3 File manager (WINFILE.EXE), I'm sure they could easily fix WMIC.
I agree but as we know ms has some very weird people who work for them who have the most stupid of ideas that they get the programmer's to do the changes which totally are counterproductive. Then we have to find workarounds to bypass those silly changes.
Thanks Will release QT 121 soon , as with extensive testing it appears the new DMI branding routine is fully operational and checks in a new order which also prevents that "SystemX" being selected by mistake when that brand was not the actual one of the computer. The routine looks for the exact brand name so "System Product Name" is not interpreted as "SystemX" etc. There may be the odd one that slips through the new checks, i will deal with them as they arise. *edited*
Will correct my post(s) - it is v120 that was released, 121 is the currently being finalized one It because of the long delay in working on the projects this time due to my neck injury etc. All is on target for release soon
MRP 141 is at RC1 stage no new options but have updated a few old ones to work with later builds. QT 121 is at RC6 stage. Uploaded for beta testers. Both have had a update for TPM detection, it should hopefully show the VendorID (intel, Micron etc), converting the numeric value was the bit that took a while to compile from number to name... May not of got all the Vendors but a good majority of the main name players. Example: Code: Trusted Platform Module : 2.0, [Enabled, Activated, Owned], VendorID: Intel If not converted it will show the numeric value instead.
As for the 'Your Phone' reversion not working that may be because the App was also selected to be removed? If you think you are going to use the Your Phone app at some point in time: a) Make sure you not select the box to remove the app as well because reversion may be a bit hit and miss as you will need to reinstall the App from the Store and sometimes it not as straight forward as we would like. b) Make sure to select the option 'Allow Your Phone - Add a phone {RS3+}' found on tab [ Win 1x {1} ] of the MRPConfigCreator.exe so that the app's registry entries are not affected.
Interesting that mrp will attempt to re run and complete when a reboot mid way through oobe, either by user reboot or some other error, that causes setup to crash and re run.