I checked my slic previously Windows 7 system, both with KB3074686 since the 24th of July and KB3081424 since August 5th. Today's the 10th, still activated.
You shouldn't believe everything that you read on the internet. Them updates are old and he was speculating due to what someone else said. I've already said that I've got a solution should something ever happen, so it's not an issue either way.
I am running MS Office 2010 which I'm activating using a Microsoft Toolkit - older version. What are the chances that Microsoft will detect the KMS server and de-activate my Windows too?
Low, as far as experience can tell. Of course, you should care about A/V, be concerned about them if you don't add KMS activators component to exclusions. And these depends on which KMS activator you are using and which antivirus.
For my part, I activated Office 2013 using KIS 2015 original with no exclusions, ditto for Win Diffender.
And when should we change legacy to UEFI? Legacy doesn't support GPT. I want to have UEFI Win10 x64 but Loader doesn't support UEFI
As far as I understand, use Daz in legacy mode, upgrade to 10 with legacy mode -> get HWID in MSFT servers ( activated for life on that PC ). Now, change BIOS to UEFI only and make sure clean install is done through UEFI mode W10 USB stick and you will have genuine UEFI W10 !
I'd like to know, 1. after the upgrade, does Win10 overwrite the loader entry in boot code or does it remain & continue to load slic2.1 before Win10 and 2. can the loader be installed on a clean install of Win10 (activated via upgrade first)? I'm aware that unlike the OEM activated Win7, the upgraded Win10 no longer looks for the Win7's slic2.1 in bios/uefi & in any case once the HW ID is registered as activated in M$ DB it doesn't matter anymore but there's always the possibility of M$ pushing a WAT update to recheck slic2.1 for those coming from OEM Win7. Actually, with M$'s forced update policy it's pretty simple to target those having the generic Win10 OEM key coming from Win7 & verify if there's slic2.1 still present. And IMO, with very few sales of retail Win10 expected (well, anyone already having hardware capable of Win10 already has Win7 / Win8 installed so why not just upgrade when M$ is giving away permanent Win10 for free to everyone, even to those with temporary kms license, and then there's the free insider's program) their quarterly statement might just force them to do it. And with this being labeled the final version of windows to be ever sold & supported for the lifetime of the devices, when their all-in gamble on profits from the Windows store fail they're bound to turn towards pirates with M$ already having hinted at upgrade offers for pirates. In that case, this database of activated systems that M$ is building now could turn out to be the tool to permanently blacklist the HW ID's of the pirated pcs from ever being activated through any other method esp VL/KMS method using Win10 MAKs, currently their only weak link which they haven't been able to do much about till now to avoid agitating the IT sector (their only cash cow apart from the OEMs) to shift towards linux! THIS DATABASE OF HW IDs COULD VERY WELL BECOME THE WEAPON TO SEGREGATE THE IT SECTOR PCs FROM THE TOOLKIT ACTIVATED ONES! So isn't it better to ensure that the loader remains even after the upgrade?
The loader is gone after the install of Windows 10 MS is not checking for the SLIC after upgrade so no use anymore