Excuse me, I have been not focused on this project for a long time and I have a problem to ask… Last time I used this project is about 2012, and there were many OEM certificates under $oem$\$$\Setup\Scripts\Certificates folder to active the Windows license automatically with a specific SLIC BIOS. However, I haven't seen any of these certificates at latest version, perhaps they were removed for a longtime? Is there need to import OEM certificates(.xrm-ms format) manually in CMD after installation completed or it just activated automatically as before? Thanks anyway, I am deeply moved
@Enthousiast: It's probably because of the way the QT is compiled, also it does a lot of registry reading etc so it sees it as a threat. Defender getting a bit smarter in some ways.
The certificate folder has been removed as all certificates are now internally processed within the database file.
It was the b5 release you removed and exchanged with the current one because s1ave77 gave you an enhanced code for it (the current b5 didn't trigger ms defender).
Ah it must be the keyinfo program. As that all that has really been added. Or possibly the two dll files, unsure.
I'm puzzled too as nothing been added as in other than the keyinfo and the two vc 2012 dll files. The code is the same, the same compiler etc. definitely Probably Mshaft targeting the QT now?
Would say let's wait if there will come more users reporting AV flagging the tool. So far it was once and if i got it right not with the current tool version . On the other hand it's futile trying to avoid any flagging. Some needed tools act very offensive and others get flagged by purpose (i.e. KMS:Hacktool). People should get used to always question AV vendors motivation, then their scare tactics won't work.
Please, keep in mind that the one who triggered MS Defender (win 10) is already pulled and exchanged by the current one, which hasn't triggered Defender.
sorry i got confused which version, my fault. I gather the one that was pulled was the one that was about 14mb with all the VCredist stuff.
Thought it was, strange considering its M$ own Vcdist files in that! Maybe because they was the en-gb ones and got flagged.
I use exescript to compile so that bit is right , it must be the way it packs the files, definitely a false-positive.
Well here is a little teaser about MRP, .... Spoiler Code: Multi-OEM/Retail Project Version : 170222-R53.5s-Internal-Testing [MRP/MDL] Files present and extracted successfully. NOTE: This is a Internal Testing release, functional, features may change before BaseLine. Enhanced Log Mode: Activated. > Checking OEM's Folder Structure. OEM's folder detected, structure appears OK. OS Installation Date: 22/02/2017 23:46:39.50 > Checking installed OS name. 23:46:39.53 Windows 10 Home x64 version found. 23:46:39.55 > Checking installed OS Edition/SKU. 23:46:39.60 Core Edition/SKU installed. 23:46:39.60 Build Version: 14393.0.amd64fre.rs1_release.160715-1616 23:46:40.16 Edition Language/Code: en-GB ( 2057 [809h] ) 23:46:40.16 OS Locale: en-GB 23:46:40.16 OS Language Value: ENG -------------------- DMI BIOS Information -------------------- #1 CS Product Name : [90DA*] #2 CS Model Name : [90DA*] #4 CS Vendor Name : [LENOVO] #5 CS System Name : [LENOVO] #6 Baseboard Name : [LENOVO] #8 BIOS ID : [LENOVO] > Detecting if a Solid State or Standard Hard Drive is present. INFO: SSD Detected. 23:46:42.14 > Checking if 'LblDrv' flag is enabled. 23:46:42.14 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_10_Core'. 23:46:42.16 > Checking DMI for manufacture information. 23:46:42.50 Lenovo [#4] manufacture will be used for theme/branding. 23:46:42.50 > Branding Section Part 1. 23:46:42.50 Force theme text file not present. 23:46:42.54 > Checking DMI for Model Name. 23:46:42.55 Model Name: '90DA*' detected and applied. 23:46:42.55 > Branding Section Part 2. 23:46:42.55 Desktop backgrounds folder created. 23:46:42.57 > Windows 8.x/10/Server 2016 User Account Picture Management Section 1. 23:46:42.57 OOBE.xml file deleted. 23:46:42.57 User.bmp replaced. 23:46:42.57 User.png replaced. 23:46:42.57 User-40.png replaced. 23:46:42.58 > Windows 10/Server 2016 User Account Picture Management Section 2. 23:46:42.58 User-32.png replaced. 23:46:42.58 User-48.png replaced. 23:46:42.58 User-192.png replaced. 23:46:42.58 Lock Screen {img105.jpg} replaced. 23:46:42.60 > Theme Management Section. 23:46:42.60 Lenovo theme has been applied. 23:46:42.62 Log-In Background {img100.jpg} replaced. 23:46:42.63 > Transfer Theme Files Section. 23:46:42.63 System32\oobe\Info folder has been created. 23:46:42.65 Required theme files transferred to 'System32\oobe\Info folder'. 23:46:42.65 > Deletion of obsolete files. 23:46:42.77 Branding script has completed. 23:47:37.45 > Add-On Manager in progress. 23:47:39.34 > Detecting if Visual C 2012 DLL's are present. 23:47:42.17 > Visual C 2012 DLL's have been temporarily installed. 23:47:42.17 > Checking BIOS for MSDM Key. 23:47:42.50 > Processing MSDM Key for Edition status. 23:47:45.20 > Show MSDM Key Information. 23:47:45.20 MSDM Key Information: Win 10 RTM Core OEM;DM 23:47:46.58 MSDM key is for the Edition installed, it has been applied and saved. 23:47:46.59 > Temporary Visual C 2012 DLL's used have been uninstalled. 23:47:46.61 See C:\MSDM-Key.txt for your saved MSDM key details. 23:47:47.00 > Checking if computer is a 'default' Virtual Machine. 23:47:48.21 Advanced Log-On screen has been enabled. 23:47:48.25 User Account Pictures registry entry applied. 23:47:48.28 'Registered Owner' registry entry corrected. 23:47:48.28 Detected 'defaultuser0', attempting to remove the folder... 23:47:48.38 Removal of 'defaultuser0' folder successful. 23:47:48.61 > Checking BIOS's mode and System drive's partition type. 23:47:52.19 BIOS Mode: Legacy, Partition Type: MBR 23:47:52.19 > Checking Hard Drive Controller Mode. 23:47:52.30 HDD Controller Mode: [AHCI] 23:47:52.30 > Checking Online Status. 23:47:52.30 Device does not appear connected to the Internet, online license check failed. 23:47:58.13 > Checking if Windows is activated/licensed. 23:47:58.66 License Status: Not licensed. 23:47:58.68 > Checking if 'UserTweaks.cmd' present. 23:47:58.68 'UserTweaks.cmd' present, attempting to apply. 23:47:58.68 UserTweaks.cmd has completed. 23:48:18.19 > Checking if 'WinTel.cmd' present. ================================================================================ = Please Note: It is advisable to logout or reboot your computer when possible = = to allow the User and Log-On background pictures to finalize. = ================================================================================ Enhanced Log Mode: Deactivated. Thank you for using the project, MRP has now completed. Just installing Pro and it should say the MSDM key not for the installed Edition... Spent 2 days now, wondering why no key information, yet manually it all worked... Then tonight realized in oobe mode it didn't work properly for some reason, so moved the MSDM key check/insertion part from the branding script to a new Add-On module that is called AFTER oobe has completed. Sorted! Also i have edited the config file contents from : to ; so that if anyone posts the log you dont end up with loads of 's -- so OEMM is now OEM;DM. Cosmetic i know. Now Pro installed on a Core MSDM: Spoiler Code: Multi-OEM/Retail Project Version : 170223-R53.5s-Internal-Testing [MRP/MDL] Files present and extracted successfully. NOTE: This is a Internal Testing release, functional, features may change before BaseLine. Enhanced Log Mode: Activated. > Checking OEM's Folder Structure. OEM's folder detected, structure appears OK. OS Installation Date: 23/02/2017 0:10:22.51 > Checking installed OS name. 0:10:22.56 Windows 10 Pro x64 version found. 0:10:22.56 > Checking installed OS Edition/SKU. 0:10:22.89 Professional Edition/SKU installed. 0:10:22.89 Build Version: 14393.0.amd64fre.rs1_release.160715-1616 0:10:23.47 Edition Language/Code: en-GB ( 2057 [809h] ) 0:10:23.47 OS Locale: en-GB 0:10:23.47 OS Language Value: ENG -------------------- DMI BIOS Information -------------------- #1 CS Product Name : [90DA*] #2 CS Model Name : [90DA*] #4 CS Vendor Name : [LENOVO] #5 CS System Name : [LENOVO] #6 Baseboard Name : [LENOVO] #8 BIOS ID : [LENOVO] > Detecting if a Solid State or Standard Hard Drive is present. INFO: SSD Detected. 0:10:25.12 > Checking if 'LblDrv' flag is enabled. 0:10:25.12 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_10_Pro'. 0:10:25.14 > Checking DMI for manufacture information. 0:10:25.48 Lenovo [#4] manufacture will be used for theme/branding. 0:10:25.48 > Branding Section Part 1. 0:10:25.48 Force theme text file not present. 0:10:25.52 > Checking DMI for Model Name. 0:10:25.53 Model Name: '90DA*' detected and applied. 0:10:25.53 > Branding Section Part 2. 0:10:25.53 Desktop backgrounds folder created. 0:10:25.55 > Windows 8.x/10/Server 2016 User Account Picture Management Section 1. 0:10:25.55 OOBE.xml file deleted. 0:10:25.55 User.bmp replaced. 0:10:25.55 User.png replaced. 0:10:25.55 User-40.png replaced. 0:10:25.56 > Windows 10/Server 2016 User Account Picture Management Section 2. 0:10:25.56 User-32.png replaced. 0:10:25.56 User-48.png replaced. 0:10:25.56 User-192.png replaced. 0:10:25.56 Lock Screen {img105.jpg} replaced. 0:10:25.58 > Theme Management Section. 0:10:25.58 Lenovo theme has been applied. 0:10:25.60 Log-In Background {img100.jpg} replaced. 0:10:25.61 > Transfer Theme Files Section. 0:10:25.63 System32\oobe\Info folder has been created. 0:10:25.63 Required theme files transferred to 'System32\oobe\Info folder'. 0:10:25.63 > Deletion of obsolete files. 0:10:25.76 Branding script has completed. 0:11:05.56 > Add-On Manager in progress. 0:11:07.26 > Detecting if Visual C 2012 DLL's are present. 0:11:10.18 > Visual C 2012 DLL's have been temporarily installed. 0:11:10.20 > Checking BIOS for MSDM Key. 0:11:10.46 > Processing MSDM Key for Edition status. 0:11:13.14 > Show MSDM Key Information. 0:11:13.15 MSDM Key Information: Win 10 RTM Core OEM;DM 0:11:13.15 MSDM Key is not for the installed Edition, saved but NOT applied. 0:11:13.16 > Temporary Visual C 2012 DLL's used have been uninstalled. 0:11:13.17 See C:\MSDM-Key.txt for your saved MSDM key details. 0:11:13.43 > Checking if computer is a 'default' Virtual Machine. 0:11:14.17 Advanced Log-On screen has been enabled. 0:11:14.22 User Account Pictures registry entry applied. 0:11:14.25 'Registered Owner' registry entry corrected. 0:11:14.25 Detected 'defaultuser0', attempting to remove the folder... 0:11:14.36 Removal of 'defaultuser0' folder successful. 0:11:14.40 > Checking BIOS's mode and System drive's partition type. 0:11:18.18 BIOS Mode: Legacy, Partition Type: MBR 0:11:18.18 > Checking Hard Drive Controller Mode. 0:11:18.31 HDD Controller Mode: [AHCI] 0:11:18.31 > Checking Online Status. 0:11:18.31 Device does not appear connected to the Internet, online license check failed. 0:11:24.14 > Checking if Windows is activated/licensed. 0:11:25.73 License Status: Not licensed. 0:11:25.75 > Checking if 'UserTweaks.cmd' present. 0:11:25.75 'UserTweaks.cmd' present, attempting to apply. 0:11:25.75 UserTweaks.cmd has completed. 0:11:46.12 > Checking if 'WinTel.cmd' present. ================================================================================ = Please Note: It is advisable to logout or reboot your computer when possible = = to allow the User and Log-On background pictures to finalize. = ================================================================================ Enhanced Log Mode: Deactivated. Thank you for using the project, MRP has now completed. Its not perfect and things will change before beta. Beta will probably start early March.
Code: Multi-OEM/Retail Project Version : 170207-R53s-BaseLine [MRP/MDL] Files present and extracted successfully. OEM's folder detected, structure appears OK. OS Installation Date: Fri 02/24/2017 13:01:59.83 Windows 10 Pro Insider Preview x64 version found. 13:02:00.52 Professional Edition/SKU installed. 13:02:00.52 Build Version: 15042.0.amd64fre.rs2_release.170219-2329 13:02:03.81 Edition Language/Code: en-US ( 1033 [409h] ) 13:02:03.81 OS Locale: en-US 13:02:03.81 OS Language Value: ENU -------------------- DMI BIOS Information -------------------- #1 CS Product Name : [P35-DS3R] #2 CS Model Name : [P35-DS3R] #4 CS Vendor Name : [Gigabyte Technology Co., Ltd.] #5 CS System Name : [Gigabyte Technology Co., Ltd.] #6 Baseboard Name : [Gigabyte Technology Co., Ltd.] #8 BIOS ID : [GBT] INFO: Standard HDD Detected. 13:02:07.17 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_10_Pro'. 13:02:07.92 Gigabyte [#4] manufacture will be used for theme/branding. 13:02:09.03 No MSDM key detected in BIOS. 13:02:09.03 Force theme text file not present. 13:02:09.45 Model Name: 'P35-DS3R' detected and applied. 13:02:09.45 Desktop backgrounds folder created. 13:02:09.47 OOBE.xml file deleted. 13:02:09.47 User.bmp replaced. 13:02:09.53 User.png replaced. 13:02:09.53 User-40.png replaced. 13:02:09.55 User-32.png replaced. 13:02:09.55 User-48.png replaced. 13:02:09.55 User-192.png replaced. 13:02:09.56 Lock Screen {img105.jpg} replaced. 13:02:09.72 Gigabyte theme has been applied. 13:02:09.75 Log-In Background {img100.jpg} replaced. 13:02:09.80 System32\oobe\Info folder has been created. 13:02:09.81 Required theme files transferred to 'System32\oobe\Info folder'. 13:02:10.27 Branding script has completed. 13:10:44.16 Advanced Log-On screen has been enabled. 13:10:44.34 User Account Pictures registry entry applied. 13:10:44.40 'Registered Owner' registry entry corrected. 13:10:44.40 Detected 'defaultuser0', attempting to remove the folder... 13:10:44.73 Removal of 'defaultuser0' folder successful. 13:10:53.16 BIOS Mode: Legacy, Partition Type: MBR 13:10:53.91 HDD Controller Mode: [IDE] 13:11:01.69 License Status: Licensed. ============================================================================ Please Note: It is advisable to logout or reboot your computer when possible to allow the User and Log-On background pictures to finalize. ============================================================================ Thank you for using the project, MRP has now completed.
Been having a go at VirtualBox with a 'MSDM' table.... Using: <ExtraDataItem name="VBoxInternal/Devices/acpi/0/Config/CustomTable" value="D:\Vbox\Window10x64\MSDM.BIN"/> Seems to work, well it does with the QTool. Just about to do a test install with the 'new' project. I am not 100% sure i got the checksum part right within the MSDM binary file but will soon see on a real 'virtual' install. You cannot have a SLIC.BIN and MSDM.BIN at the same time as the SLIC one will get ignored, but it looks hopeful for testing.