I must add the UserTweaks batch file is a bit rough and ready, but it does the job. Feel free to edit and enhance it as you wish. As mentioned it is entirely optional if you wish to use it, the project checks if the cmd file is present, if not then carry on to its next stage.
I could swear Internet issues were things of third world countries like mine. But it seems I was wrong...
LOL its rare we have problems but when my cable goes wappy it does rather spectacular like this past 4 days
Have had a few enquiries why the UserTweaks add-on was created, here is a run down why... Before i was using the WinTel.cmd to do my personal extra tweaks etc, which worked up to a point. HKCU tweaks didn't take, after a bit of research found that the CU hive is not set up yet during the OOBE stage , where Wintel.cmd is called from because the OS does not have a username yet! I tried via setupcomplete.cmd but sometimes this failed too, not sure why. So UserTweaks was added to the new add-on stage which is called just after you enter the username, this section is when the OS creates the new user. This allows any HKCU registry edits to take place. With the added SYSTEM benefit, it is run as a sort of Super Administrator - the only down side is the lack of any messages on the screen - hence the warning not to use any non silent program installs in the script or anything that requires the user to click or enter anything. Plus if you force a system reboot at this stage your OS may not be fully initialized, also the userpic/logon backgrounds etc may not take place, (Win 8/10). ------------------------ I have written a small exe program (written in AutoIT - source available if required), that will check if your boot/system drive is a SSD or standard HDD, this sets a system environment variable called 'DrvType' this variable will not be erased on a reboot like most variables in scripts are. This will be added to the UserTweaks archive on next update. You can then use the exe or not, but if you do then you can have 'special' tweaks for each type of drive. Such as turn off indexing/fastboot for a SSD. I will update the script with a line on how it can be used.
Hmm very strange, for the life of me i cannot work out why it picked Fujitsu I know HP/Compaq has always been a pain. But there is nothing there that would indicate Fujitsu in any of #1-6 The only thing for now is to either use the Force theme method and reinstall, or manually edit the windows\system32\oobe\info folder with the correct images with your short time frame to fix it. Also run the HP.reg file manually to reset all the info parts in basic system info screen. Just realised that 2nd option may not alter the user pic I will take another look at the project files and QTool and see why it chose the wrong theme.
Ok, Ill try that if not big deal one issue out of 50+ isn't bad. Thanks again for keeping the project going.
Sorry about that, i have just entered your information into my test QT and indeed it has picked Fujitsu! Looks like it getting the TS part of the name confused with FS of FSC in the database... I have had a few ideas on HP/Compaq conflicts it does add a bit of code to the project but if it works then it be worth the extra few bytes. 1/50 that not bad at all Thank you for bringing this to my attention.
I was close with FS its actually picking TS out of the word Fujitsu, seems there must be in a 'bug' in the way Findstr works. Even though the "\<name\>" instructions are given to technically only pick the full word. I am working on the QTool as the code can be transposed into the main project. There will be a project update if my changes work. Will have to test with Fujitsu info also as a test to see if it not affect that brand and think its a HP This may take a bit of time.... But if the changes work then it will be easier to do conflicts for HP/Compaq, (or other mixed brands), in the future.
Well after almost 6 long hours , it looks like the strange picking of FujiTSu has been cleared. Did several tests and edits with the QTool using the info and sorted it then copied data into the project and tested on a VM with same DMI info. I did 3 test installs of core then pro to make sure. Conclusion : Fixed. Hopefully HP conflict is sorted. Preparing a project update and new Query Tool v14b1.
Project & Query Tool Updated. MRP updated - version 161122-r27f. Query Tool Updated - v14 Build 1. I skipped using v13 as a version marker First post download link(s) refreshed. See change log for details.
Project updates on hold while the forum is being restored. Have made a small change to the variable conflict side, it's a little bit more intelligent when re-checking the DMI #1/#2 stages. It's not 100% foolproof but it does cut down on making wrong choices by about 40% give or take. Testing is still in progress and if it proves to be effective in practice, as it seems to be, it will be integrated into the project itself. If you wish to beta test this version please PM me.
This is how the new log looks, it may change a bit during beta testing, however you can see part of the new conflict resolution in play. [shown in bold text] Spoiler Multi-OEM/Retail Project Version : 161127-r28beta [MRP/MDL] Files present and extracted successfully. OEM's folder detected. OEM's folder structure is OK. OS Installation Date: 27/11/2016 10:38:07.59 Defined Windows 10 Home x64 version found. 10:38:08.16 Defined Core edition found. 10:38:16.83 Build Version: 14393.0.amd64fre.rs1_release.160715-1616 10:38:16.91 Checking for DMI conflicts... 10:38:16.91 Possible [HP ENVY TS m6 Sleekbook] conflict re-checking DMI [#1] resolved as [HP]. 10:38:17.09 Defined HP [#1] manufacture found for theme branding. 10:38:19.07 No MSDM key detected. 10:38:19.08 Force theme text file not present. 10:38:19.80 System Product Name not defined. 10:38:19.80 Backgrounds folder created successfully. 10:38:27.18 Deletion of OOBE.xml file successful. 10:38:27.20 User.bmp backed-up and replaced successfully. 10:38:27.32 User.png backed-up and replaced successfully. 10:38:27.35 User-40.png backed-up and replaced successfully. 10:38:27.37 User-32.png backed-up and replaced successfully. 10:38:27.39 User-48.png backed-up and replaced successfully. 10:38:27.40 User-192.png backed-up and replaced successfully. 10:38:27.42 Img105.jpg backed-up and replaced successfully. 10:38:27.76 Theme backed-up and replaced successfully. 10:38:27.87 Img100.jpg backed-up and replaced successfully. 10:38:30.18 Advanced logon screen for Windows 10 enabled successfully. 10:38:30.20 Info folder created successfully. 10:38:30.26 Files moved to System32\oobe\Info folder successfully. 10:38:33.15 Cleanup reg entry added successfully. 10:38:33.15 Installation script has completed successfully. 10:44:19.76 Windows 10 login user picture registry entry successfully applied. 10:44:19.84 Found 'defaultuser0', attempting to remove folder and fix reg entry. 10:44:19.97 Removal of 'defaultuser0' folder successful. 10:44:20.11 BIOS Mode: Legacy, Partition Type: MBR. 10:44:20.11 Device not connected to the Internet, online activation failed. 10:44:23.37 License Status: Error, not licensed. 10:44:23.39 Cleanup script has completed successfully. 10:44:23.39 UserTweaks.cmd present attempting to apply. 10:44:23.39 UserTweaks.cmd completed. ============================= Windows 10 Users ============================= Please Note: It is advisable to logout or reboot your computer when possible to allow the user/logon background pictures to finalize. ============================================================================ In the example DMI 'HP ENVY TS'.... previously it could pick FUJITSU instead of HP, now with the slightly more enhanced coding, it does a re-check against the database looking for the first word in this case HP and ignoring the TS which it got confused with fujiTSu. Sometimes you may get the possible conflict message appear if there is more than one word in the DMI area being checked, however it 'should' hopefully pick the correct brand/theme. Sadly there will never be a 100% way to get the brand right, so in those rare occasions you will need to use the Force_Theme method. ------------------ Also made a change that it will no longer show the MSDM key, if present, within in the project.log, instead the DM key will be placed within a new file called MSDM-Key.txt on the root of your system drive, this allows you to safely post the project.log file and not have to edit the key out. Your MSDM key is in its own file for your own reference. Windows Vista/7 keys that are known PID keys will still be shown. If you used a retail key please edit this out if it is shown within the project.log BEFORE posting.
You know me too well Mr.X , i'm always working on making the project as best as it can be a few failures along the way that people not see, and can't hear my expletives when something not go to plan lol