May be difficult in rearm case since the error is not consistent. Can't remember who posted but whoever got the AutoKMS null exception needs to post their log and INI.
Well I have had it happen rarely since I implemented that feature, but never in a finished release (it does not happen to everyone and I cannot seem to make it happen). The only reasoning for it is that it is not restoring the backup it takes when it starts (since the first time we get the right rearm count but end up with none, so it is not restoring). As I said an actual failure in the restore would almost certaintly throw an error, so I don't think it is doing it, but that means I don't have the slightest clue as to what's screwed up as I cannot find an error in the code itself (rearm check is very simple).
Thing about the deleting is, my debugging proves if the backup gets deleted before restore starts, it will say the backup wasn't found. The delete code for that backup does not occur until after restore function returns so I don't see how that could mess it up. My other theory of a failing restore is based upon the fact that when I restore I make another backup. If the restore fails, I restore the temp backup (this one would have zero rearms, as it is not the Rearm Check Temp Backup). Thing is is the code is supposed to say the restore failed but a temp backup was restored, just like doing the restore yourself.
Yep, when i use the older version (before v2.1) and push available button, it will create a Backups folder, but newer version not. However, i love this toolkit and save older version in my harddisk.
With all the refinements being given the Toolkit, I'm baffled as to why the single biggest problem - being flagged as a virus/trojan in numerous AV programs - isn't being addressed at all. Are there any plans on modifying AutoKMS or KMSEmulator so that Norton, BitDefender, McAfee, ESET, Panda, Malwarebytes, Webroot (Sophos) and probably others, don't recognize this as a virus/trojan? Having virtually any of the well-known AV programs recognizing these files as being infected keeps Toolkit from reaching its potential, since I think many people are leery when virtually any AV program sees the same problem. On the other hand, is this just a cat-and-mouse game with the AV programs? Thanks.
That's because I send all "Temp" backups to the temp folder now. (As in %TEMP%\Backups\TempBackupName). Language/Architecture are irrelevant.
Yes, we really can't totally solve it. If they want to flag us they will. The newer KMSEmulator and AutoKMS were getting free passes with my NIS but it seems like that is ending. The FP rate on Virustotal has radically gone down but its the popular AV's doing most of the flagging.
Yes, it's a cat and mouse thing. AutoKMS has been flagged, changed to a non flagged state, flagged again, and so on. We tried but the AVs always flag our latest version within a couple of weeks, and there are some parts of the code that can't be changed enough to don't seem as a threat because we have to do things in the system. Hope it's clear why it
I've been debugging the rearm thing, and it seems any of my theories do get handled. If the backup is gone it says it is gone, meaning you lose your rearms but an error is shown. If the restore fails and it has to restore back, it shows the error. Why people are losing their rearms when restore succeeds is strange, but I have a feeling OSPPSVC or something doesn't time right. Do note that I determine a failed restore by having a "Broken" office. A restore not going through all the way, and leaving the system as is, would then check and see office is not "Broken" but in grace. Though it is really hard for me to detect success in this case without a second rearm check (as you could have been fresh when you did the check).
Can someone with the rearm issue do the following: Take a state where you have KMS activated and you know you have 5 rearms (If you have done a repair+reactivate, you should be good). Take a backup named PreTest, then run the Available, if it says 5 rearms but you check and you are in grace, take a Backup named PostTest. If you have both backups, send me both of them zipped up. I'm trying to see if some of the backup is restoring. My theory is OSPPSVC interfering somewhere and it not getting detected (Registry most likely as it seems to catch files pretty well).
Your tokens.dat is the same but cache.dat isn't and neither is the registry. I'm adding more specific detection to backup/restore and I'd like someone getting AutoKMs null error to try V2.1.5 when I finish it.
A changelog would be great. I'm still using Mini KMS activator v1.072fixed because I don't really know if CODY's KMS emulator has been improved over that or if it's just the original ZWT emulator without changes. It's hard to justify changing to another program if you just don't know what it does! Regards.
Thanks! I've just seen the readme (it's inside the executable, I hadn't thought of that, doh!). But I cannot figure out how to install a KMS server using this. Does this tookit offer that functionality (installing a KMS server to handle activation requests from other clients in the network) ?? Kind regards.