@jack2lantern Allow permissions override the deny rule you set up. You will need to take ownership of the file/folder first then edit those allow rules for admin, system and authenticated users one by one to add the deny rule. After setting ownership of the file to administrator group:
Not all products can be phone activated. You cannot phone activate KMS product. What this feature does is you enter MS's code,, and the toolkit saves it (meaning you could rearm and phone activate again without having to enter the code).
I wouldn't count on permissions to stop AV. If it thinks a file is bad enough, it can probably override the permissions anyway (many AV do this).
That's exactly what mine, (Trend Micro) is doing. After a scan, I must shut down he AV and reinstall AutoKMS.exe. Real hassle.
Same here with ESET Smart Security. It quarantined the files and then I went into the ESET Settings and added the files/directories to the exclusions list and restored the files from quarantine and now it's working like a charm
Under Tab: "Activation" "Rearm Office 2010" "Rearm" "Available" If i clic "Available", this deactivate my Office 2010. To reactivate, i cannot say exactly what i have done, but i am again AutoKMS activated. I do not dare to clic "Available"!! Is this normal? Sorry if i miss a solution to that in the 268 pages.
Available is just suppose to give rearm status hence how many rearms available. Did you stop it in the middle of it's function?
This is exactly what I have always been doing. However since two weeks or so AutoKMS.exe is quarantined anyway.
With 2.1.3 or 2.1.4? You could take a backup before using available, as it seems to be screwing that up but I cannot figure out why. I added a delay in 2.1.4.
Yes CODY, Confirmed. My copy was also deactivated when i checked available rearms. v2.1.4. Moreover, after that if i just clicked attempt activation i.e., without installing ez-activator, autokms or auto rearm, office does not activate: "Failed to set KMS Host" is the error msg Please look into this. Thanks.
It's strange as the only logical possibility is it doesn't restore the backup after the fact. Any kind of failure to do is is supposed to throw an error, which indicates it might not even be trying, due to it possibly deleting the backup (unlikely but I added a delay anyway). I cannot figure it out, but you can get around the issue by taking your own backup from now on, then restoring that manually. You'll have to reactivate if it deactivated you.
Just to try and eliminate the possibility of it being the delete. I'll change the code so it doesn't delete it at the end., rather at the beginning (delete a leftover backup from last time). I'll try to see if I can solve that AutoKMS issue (exception) but I could use some info on that since there are some scenarios I can't test myself.
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.