Anyone know if there is a command line switch to allow a task to run on Battery Power when using schtasks /Create from a CMD Prompt
KMService returns an Error CODYQX4,timesurfer,Bosh Please let me know if anybody could provide some insight why my Office 2010 does not activate. I have been lurking in the forum reading as much as possible and have not gain any traction in resolving my scenario. Here are the quick bullet points about my situation. Windows 7 x64 Eset NOD 32 Antivirus; AntiVirus/Firewall - Off Windows Firewall – Off Office Toolkit 2.16 and Office Toolkit 2.17 Beta 1 Office 2010 Professional Plus Volume Edition. Main Error: Could not access KMSEmulator path set in Settings, using default installation path. Failed to start C:\Windows\KMSEmulator.exe Office 2010 installed and activated after a clean format; then the activation expired and Office 2010 could no longer be rearmed. I uninstalled Office 2010 and began the process again. The activation process would not succeed citing that KMSEmulator was missed; though KMSEmulator is in the default path, C:\Windows. I tried starting the KMSEMulator by double-clicking and received a permissions error. Then I tried the KMS Activator v1.3 hoping that it would reintall. It gave me the following messages when installing. Installing Code: Copyright (C) Microsoft Corporation. All rights reserved. ========================================================= KMService will be installed on your computer. Continue? [y/n]: Y ################################################## ## ## ## Install KMService ## ## ## ################################################## Copyng files... status: Error Installing service... status: OK Updating registry settings... status: OK Running service... status: OK Press any key to exit... Uninstalling Code: Microsoft (R) Windows Software Licensing. Copyright (C) Microsoft Corporation. All rights reserved. ========================================================= KMService will be removed from your computer. Continue? [y/n]: Y ################################################## ## ## ## Uninstall KMService ## ## ## ################################################## Shutting down process... status: Error Service stopping... status: Error Uninstalling service... status: OK Deleting files... status: OK Press any key to exit... I have been troubleshooting this situation for several days. It appears that the KMSEmulator cannot be started or stopped through the Toolkit; TaskManager - Service tab; or replaced with a fresh copy. My fear is that some registry values may prevent Windows and the Toolkit from utilizing KMSEmulator. I even changed the permissions of the KMSEmulator without luck. Please let me know if you have any insight.
The problem here is ESET Smart Security, it has several protection modes (real time protection, document protection, etc), you have to enter the advanced configuration and disable all of them. I know because I use ESS 4 and disabling everything is the only way to properly run KMSEmulator.
Hi. If i have installed Older version of Office 2010 Toolkit and EZ Activator, how can i update or upgrade or install newer version of the Office 2010 Toolkit and EZ Activator? For Example: If i use Office 2010 Toolkit and EZ Activator v2.1.4 and want to update to latest version of Office 2010 Toolkit and EZ Activator v2.1.6. What i want to do? Note: I want to do this without uninstalling Microsoft Office 2010.
You uninstall AutoKMS or AutoRearm and install the newer one from the newer toolkit. For toolkit itself. copy exe over the old one, and reset your settings since they may be lost if i've changed them in the new one.
But the Office is already activated by kms for 180 days. After replacing exe/removing auto kms,do i have to run EZ activator again to use the latest version changes in toolkit? If i run EZ Activator again with the new version, will it accept/gets an error?
No you are just updating the activator to fix bugs/add features. Update is not necessary if things already work.
Then its k... Thanks. I would suggest you to create a uninstall option in latest versions of the Activator to remove the whatever the toolkit had done in the office and PC(similar to Windows 7 Loder by Daz). This option will be useful for many as they would like to use the latest version always. And this will also encourage many to use and whenever you publish latest version, people will like to use it eventhough they have old version.
I'm not sure if an uninstall is needed but would be nice to have some clarity on what the upgrade process should be and how frequent. As mentioned by Cody, if it ain't broke, don't fix it Procedure seems simple... it seems there's a requirement to remove the old version first then install the new one.
Basically if you don't have issues you don't need to update. I either fix bugs or add features for more choice or convenience. The tool continues to serve its purpose whether you update it or not, but you just uninstall the tool.
Bosh, Some solutions are so simple.Your suggestion worked splendidly.I thought that I had kill the NOD process through the task manager; and did not realize these additional settings. Office has a license status of grace period with 5 rearms. Thanks! I have another question about rearming. I chose the AutoKMS custom task; yet the task scheduler does not seem to have this entry. Let me know how I could check if the AutoKMS is active. I could have installed it with NOD Active; thus it may have never register.
About killing the NOD process it can't be done because it's restarted by the ESET service, you would have to disable this service althouhg when I tried that I had permission problems . Anyway, I'm glad it worked Now about the task, There's some misunderstanding about the AutoKMS task (that happened to me the first ime I used it). Here's how it works: Install AutoKMS: this will automatically create a task named AutoKMS, this task is overwritten if it's changed, to ensure AutoKMS will always run. Install AutoKMS Custom Task: this will erase AutoKMS task and create AutoKMSCustom task and make AutoKMS.exe not to overwrite the AutoKMSCustom task, you have to add a trigger to the task because the custom task has none, for example to run every Wednesday at 9:00 am.