Yes, but it will hard-select it? Or does it install the branded theme, too, to be selected later if desired? Am a bit dense tonight.
OK, I think I need to make it a bit more verbose: There is a difference between creating a branded theme and actually pre-selecting it. It should get created/prepared (I don't want to stop adding it to the OS), just not automatically applied (selected), especially on upgrading (as it is very unfriendly to change any Desktop setting when merely upgrading - looking at you, MS). As I understand, the option in the MRP INI tool or leaving out OEMs.7z prevents creating such a theme in the first place, something I don't want. Granted, you could say - just switch back to your previous theme after upgrading. Oh, it was an unsaved one - Oopsie daisy... Maybe it's possible to make immediately applying the theme optional - there could even be a Desktop icon to switch themes if desired (delete icon if not).
That i can't help you with, the branding tool can do a lot but not a applying a full theme, i have to leave this to the old chap himself.
I't only a question - if it ain't possible then it ain't. Maybe the tool for live systems might be used for this, later.
The project is the same in its theme adding process as it was when first created by Searchengine. As for mrp not inserting the branding at time of install and allowing it later is not a easy task, because the method used does not work in same way, i have tried a few times in my own mrp type project before i took over this one. Mine was quite basic and not user friendly. I get what you mean Carlos, something like a theme pack that can be 'run' later. I was trying for that as part of the new branding tool but creating the packs 'on the fly' was unreliable as there are differences between vista/7, 8.x and 10, 8.x/10 share similar pack structure and those packs are not older os friendly. Will see if i can find a way, cant promise as i doubt m$ will make things easy and i know some changes in the oem branding is being changed. For example in 20h2 the old show basic system info is being removed and put in 'settings>about' which not show some brand images etc. If anyone has ideas on this theme pack stuff please let me know.
It seems defender is getting aggressive again, targeting other files within the qt folder. The files not been changed for months as they still servicable. Ifssd is as its name shows, detects if system drive is a ssd or not, there is a backup way so not important. Its a autoit program, odd it not been flagged before as it been in the qt for well over a year! Chkav's vbs just finds the name(s) of any av programs, can't see why its just now been flagged either. Might see if i can find another way, i avoided pshell as returning info back to a batch script is a bit fussy. I am working on the next qt so will see what i can do.
I have now removed the chkav vbs file in the next qt and just using WMIC instead, that *should* prevent Defender flapping about that file. Missing operand could be a cosmetic error due to some file being nabbed by Defender.
If i could find another method to detect a SSD or not in batch it would be easier, autoit was easiest at the time as it has a internal command to check for one.
Re QT v113 - (work in progress) -- I have found a method to detect a SSD or HDD but it is only for w8.x/10 as older than 8.0 OS's does not have the 'Media Class ' available within WMIC or even the native Powershell, so on w7 and below there is another method use but if that gets nabbed by Defender then no info about the 'BusType' or the Drive's SSD/HDD state will be shown. IfSSD.exe has now been removed from the QT folder - that eliminates one of Defender's aggressive behaviours As Win 7 gets further and further less updated/used then i see no reason to fight m$ trying to get around things, sorry but that is the way it is.
Hello, To my knowledge, Alphawaves' Branding tool 1.21 keeps working on Windows 7 and 8.x, so you could just concentrate your work to Windows 10. Indeed, it would be a great bonus adding the feature to insert branding in Live systems without formatting.
The mrp branding tool was originally designed for w10 only, but as it is a fairly simple code base it also works on below w10 too. This is designed for 'live' branding changes. Its not a full brand change but a few bits of it, remember it a simple design and use. W2000, xp and some older servers are not supported. The tool will most likely be a community thing as i not really have that much time to work on it along side usual mrp projects. The tool works and is stable, will release soon when i get a bit of time to finish off little bits.
Yes, the tool is stable, I had a look on your latest beta ! I meant a complete branding insertion in Live sytem, as MRP does during fresh installation : theme (OK, very easy to do it manually), OEM infos and logos (OK with the tool), and User Account pictures (more difficult).
That is why i said the mrp branding tool uses simple code Complete branding on a live install 'on the fly' using scripting of any sort is not as easy as it seems, theme packs seem to be the way to go in that case and even those do not do any 'Account Picture' parts as that is quite complicated mainly because they are stored in a few odd places in Windows 10 and 'System' protected once the OS has booted. I don't think Alpha's tool did the account picture side or most of the theme side? I can see why he left it as it was - i guess coding in C#/VBnet is not as simple either, more so to have the code backward and forward compatible as well!
The majority of the MRP branding that is done during the OS install is not possible in a easy form when a system is already up and running, OS permissions can be a issue, certain areas are system locked and do not like being messed with, i have tried and failed so gave that a miss
Have you tried a custom signed exe to get passed some av flags? Just curious. If you need info on it let me know. I have easy steps to making a custom signed exe now. You know where to find me. On hard to change system files have you tired changing login as system to get access? That is easy as well if you need info on it. No admin rights needed then. Sorry I haven't been around much but found out I have blood cancer so fighting the good fight. I go March 17 for surgery.
Gez sorry to hear that news, hope it caught early enough and it can be cured or controlled so it not get worse. About signing exe's i had ventured into that area a while ago but i never perfected it, was always hit and miss, majority a miss. Plus defender does not seem to like mrp or the qt im sure, so even with that signed method used m$ will still nab files it not like. I did think about setting defender's exclusion path but the reg keys are now protected. Easy to do in a way but then it could get flagged because of that method! Will have a play. Hmm 'system' login, i got into a right mess playing with things like that, remember my sysprep fun and games The branding tool is going to be open to let anyone continue or clone as i not have time to do much more to that. Alpha may even update his program, i would of tried but i not able to learn c# or vbnet due to limited time and i struggle now to remember new things.
