Great stuff, thank you for sharing. Have you got a screenshot (or several) to show regarding BlackThemeToolkit? I can see that a lot of work went into it and lots of modifications. But prior to any significant mods, I would prefer to see a screenshot first. Thank you.
I would be careful in trusting these tools. At least 1 of them will direct your Windows install to use a Chinese website. Spoiler: Oh noes! Instructs to add the following registry, which ends up using their site to "activate" via KMS remotely via their site, thus reporting your install to them. PHP: Reg.exe add "HKLM\TK_HKLM_SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform" /v "KeyManagementServiceName" /t REG_SZ /d "***********" /f > nul 2>&1 I have not dug in further, but that alone gave me 'pause' (concern).
I'd that file already on my To Do List! Thanks for the find, means I don't need to go further! The simple fact is, using an 'outsider' KMS Server for activation, will send the used Mac Addresses of that Applicant to the Owner of that KMS Server! That simply means I open my system for attacks from the outside which may be automatically considered as authorized! Together with that Mac Addresses also the Network IP, Computername and other data are sent! No, thanks, for that kind of tools!
@dhjohns No need to include any 3rd party KMS server while installing GVLK - link is removed for now.
I decided to try your apps and they do not seem to like Windows 10 Enterprise LTSB (Your OS is NOT COMPATIBLE With This Toolkit). A shame, I would have liked to see a dark theme.
I actually develop this in virtualcustoms.net. The link I just sent contains some themes, and will work on every W10 release. I just plan to stop work on that model, and continue on the previous in my toolkit which only just enables the ability to add 3rd party themes, but contains none of its own. I just don't feel it is necessary to continue support of every W10 release in the same package, especially the older ones which are being dropped from support by MS anyway.
I would like it if you included support for LTSB 2016 (please) since that will continue to be supported until 2019. It is after all a long term support release.
Yes, I know, but which development do you plan on continuing? I think the point I was seeking was the basic one found in post #1 which does not add a theme, but rather only patches the system. Which if I am not mistaken and have read correctly, is the one you plan on continuing. OR have misunderstood?
You are correct. Everything is basically staying the same with the builds so far. So, actually unless MS changes something everything is at a standstill. I will update version 3.0, the one in the toolkit, if necessary.
Thanks, @dhjohns for answering my question. I hope if you do release v3 you continue to support LTSB as it is a long-term release. I can understand wanting to forget the other unsupported releases.