I am thinking about having the Creator allow the end user to select either Lenovo or Lenovo2 from the 'Custom Theme' listing.... Selecting Lenovo, (or leaving as Automatic and MRP detects Lenovo), then the original Lenovo, {which is the old Blue design}, brand will be used for the theme. Selecting Lenovo2 from the 'Custom Theme' listing will use the Lenovo2, {which is the new Orange design}, brand instead. Having looked at the Creator and MRP code bases it is easy enough to do. This only affects the Lenovo brand and saves having to mess about with the OEM's.7z archive and to prevent mistakes if deleting and renaming within it. If you think this would be a better idea then let me know, i can then make the changes required. See pictures below to see how the Creator would look.
i didn't like the orange design since it was posted first time and i think the original blue one is more professional and classy but if you gonna force the orange design via oem.7z on the pretext of being the new lenovo design then it's better to have both and let the user make the choice, of course this is a good idea, but for me it's better if it's just left as it is and everything is good
Code: License Status Reason - 0x4004F040: OS licensed, verify the products use rights, or there is a invalid SLIC/MSDM present. That message normally appears for KMS activated systems with no SLIC/MSDM at all, which is unusual for systems used with KMS in corporate environments. Still a cosmetic error. If there would be an invalid SLIC table the system would refuse KMS activation completely .
The wording is a bit ambiguous the 'invalid' in this context means it could be missing or dummy/invalid (was short on string length preset ). The QT reason code system picked up that KMS was 'probably' used. Will have to re-think and re-word that line for next release.
OS licensed, verify the products use rights, probably because there is no SLIC/MSDM present. or OS licensed, verify the products use rights, cosmetic error as no SLIC/MSDM present. <-- using this one.