on the elevated Command Prompt enter SET HOMEPATH=C:\Temp And because you'll get an error message about the missing HOMEDRIVE just SET HOMEDRIVE=C: And all is well. ... View more

Puzzled. Did your answer change? Ok you get full marks. I set HOMEPATH to C:\Temp and the then missing HOMEDRIVE to C: which seems to have solved my issue. ... View more

Hi MHibbin Your answer was only part of the solution. I still can't get used to the fact that starting a command prompt as "Administrator" is not the same as opening a Command Prompt with an administrative account via: runas /user:domain\user * cmd Your answer solved the popup problem but not the HOMEPATH issue. Following is the Command Prompt output after using splunk help clean C:\Program Files\Splunk\bin>splunk help clean Could not look up HOMEPATH variable. Auth tokens cannot be cached. An error occurred: Could not determine user's home directory because HOMEPATH shell variable is not set. There are various homepath variables defined in the C:\Program Files\Splunk\etc\system\default\indexes.conf file , but what to change? I currently have no indexes.conf file in the C:\Program Files\Splunk\etc\system\local directory, because I am still using the basic installation. And I have no Homepath in my environment variables. Thanks for the first hint. Looking forward to the complete solution. Regards, John ... View more

Hi MHibbin Your answer was part of the solution. I still can't get used to the fact that starting a prompt as "Administrator" is not the same as opening a Command Prompt with an administrative account via: runas /user:domain\user * cmd Your answer solved the popup problem but not the HOMEPATH issue. Following is the output after using splunk help clean C:\Program Files\Splunk\bin>splunk help clean Could not look up HOMEPATH variable. Auth tokens cannot be cached. An error occurred: Could not determine user's home directory because HOMEPATH shell variable is not set. ... View more