It only still exists in case I need or use it, if I decide not to it will disappear. The setup sounds fine. Possibly changes in the way I do things. Not sure but it really was not intended to work via network drive. EZ-Activator and things use TEMP and assume they work on a local PC. Sorry, .NET 4 is required now.
Automatic Windows Activation I have noticed that in Office Toolkit 2.2 there is an option to activate Windows. As far as I understand it, it's a new feature. However, I was surprised it's quite hidden and automatically turned on. Well, I'm one of those who before running a function go through settings and readme file of the program, so I turned it off. But I guess not everyone is like me and there might be some who can be unpleasantly surprised if they found out that the Office Toolkit played with activation data of their legally activated Windows. Correct me please if it works differently. I'm not criticizing, just giving an idea for consideration.
It has been there for several versions and applies to AutoKMS only. Basically if your Windows is KMS ready it will (re)activate windows via KMS.
Look in the keys for Windows in the toolkit. KMS ready means it can install a KMS key AND it has the KMS key installed. So Enterprise is KMS ready out of the box since the key it has after a fresh install is KMS.
Trying to download latest V2.2 but kaspersky antivirus software say containg a virus and it's denied.
The changes in V2.2 are likely to shift AV blame from KMSEmulator to Office 2010 Toolkit.exe and AutoKMS.exe. I didn't think RAM Exec would end AV issues but at least the issues are less likely to occur mid activation. You'll just have to exclude AutoKMS/Toolkit. You should have no need to exclude AutoRearm since it doesn't contain KMSEmulator or the RunPE code that is now in V2.2 that is causing AV alerts. PS: Just to point out its now more like Phazor. He uses a different way to run his KMS Keygen from RAM, and AV doesn't kill it, but I get AV alerts on his exe, like toolkit is doing now.
Only reporting to developers of this wonderful app, avast! are deleting AutoKMS.exe of Office 2010 Toolkit v2.1.6 after rebooting the computer (I know that it is a false positive, adding an exception on avast! works fine). However, the v2.0 beta 4 aren't recognised as a virus nor false positive...
I use this great tool for Office, but do I understand correctly that it will also activate Win7 Enterprise, and thus get around any UEFI Bios issues with the standard loader injection?
Doesn't make any noticeable difference. Basically what I do is start a process then inject into that process. So task manager thinks it is vbc.exe but it is really KMSEmulator. No extra RAM is used. Not sure what you mean, as it does KMS windows activation in AutoKMS and KMS has no issues with BIOS. You are thinking of OEM Loader activation. The nature of things have changed, there is no KMSEmulator.exe but AutoKMS.exe/Office 2010 Toolkit.exe take the heat for using memory injection code. Doesn't change much, as you used to have to exclude the Keygen, now it is AutoKMS to exclude.
Yeah, installing AutoKMS will activate it as long as you have KMS Key installed, which you can install via the toolkit by selecting it. By default the KMS key is installed. You can only activate windows currently with AutoKMS. A new tool I plan to make will give most of the Office toolkit functions to windows, as in the activate button, rearm, etc.
Can you explain AutoKMS for me in relation to emulator and any services or tasks I never understood AutoKMS and would like to better Thanks