10-28-2016, 06:41 AM
When this happens,
1. Look in Services. "Quick Macros" service startup type must be "Automatic", not "Automatic (Delayed start)" or other. If it isn't "Automatic", either the QM setup program failed to install the service correctly, or something modified QM service settings, or system service settings are incorrect or unexpected.
2. Look in registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\quickmacros2. It should contain these values and nothing more:
DisplayName: Quick Macros
ErrorControl: 1
Group: PlugPlay
ImagePath: .......\qmserv.exe
ObjectName: LocalSystem
Start: 2
Type: 16
WOW64: 1
3. Look in registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServiceGroupOrder, value "List". It must contain line "PlugPlay", and the line must be somewhere above line "NetworkProvider". If it is not true, I think this registry value is incorrect.
4. If everything above is correct, I think the reason could be that some "Automatic" service that is set to start before "Quick Macros" service starts very slowly. I don't know how to find it.
In next QM version I'll try to add code to wait until QM service started.
1. Look in Services. "Quick Macros" service startup type must be "Automatic", not "Automatic (Delayed start)" or other. If it isn't "Automatic", either the QM setup program failed to install the service correctly, or something modified QM service settings, or system service settings are incorrect or unexpected.
2. Look in registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\quickmacros2. It should contain these values and nothing more:
DisplayName: Quick Macros
ErrorControl: 1
Group: PlugPlay
ImagePath: .......\qmserv.exe
ObjectName: LocalSystem
Start: 2
Type: 16
WOW64: 1
3. Look in registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServiceGroupOrder, value "List". It must contain line "PlugPlay", and the line must be somewhere above line "NetworkProvider". If it is not true, I think this registry value is incorrect.
4. If everything above is correct, I think the reason could be that some "Automatic" service that is set to start before "Quick Macros" service starts very slowly. I don't know how to find it.
In next QM version I'll try to add code to wait until QM service started.