NSIS $TEMP Has Different Value
I have been noticed $TEMP param has different value when you:
- run the installer.exe manually (by double clicking)
- run from Application with Admin rights.
Running manually will result $TEMP = C:/Users/username/AppData/Local/Temp
Running from App with Admin rights = C:/Windows/Temp
CONDITION:
I have an installer that requires system reboot to finish the process.
To achieve that, I make a copy of installer in the $TEMP, and put the path in RunOnce
PROBLEM:
The function works fine (after reboot, the program is updated with new version).
However, at the end of installation process, I am unable to delete the copy of installer because the $TEMP = C:/Users/username/AppData/Local/Temp when running the installer by RunOnce.
In fact, the copy of installer is located in C:/Windows/Temp
QUESTION:
Is it possible to force the $TEMP to always be = C:/Windows/Temp ?
Is there any better solution to workaround the case of installation with system reboot?
windows installation nsis temp runonce
asked Nov 22 '18 at 2:03
undoundo
112
add a comment |
I have been noticed $TEMP param has different value when you:
- run the installer.exe manually (by double clicking)
- run from Application with Admin rights.
Running manually will result $TEMP = C:/Users/username/AppData/Local/Temp
Running from App with Admin rights = C:/Windows/Temp
CONDITION:
I have an installer that requires system reboot to finish the process.
To achieve that, I make a copy of installer in the $TEMP, and put the path in RunOnce
PROBLEM:
The function works fine (after reboot, the program is updated with new version).
However, at the end of installation process, I am unable to delete the copy of installer because the $TEMP = C:/Users/username/AppData/Local/Temp when running the installer by RunOnce.
In fact, the copy of installer is located in C:/Windows/Temp
QUESTION:
Is it possible to force the $TEMP to always be = C:/Windows/Temp ?
Is there any better solution to workaround the case of installation with system reboot?
windows installation nsis temp runonce
asked Nov 22 '18 at 2:03
undoundo
112
What is yourRequestExecutionLevelattribute set to?
– Anders
Nov 22 '18 at 3:00
add a comment |
I have been noticed $TEMP param has different value when you:
- run the installer.exe manually (by double clicking)
- run from Application with Admin rights.
Running manually will result $TEMP = C:/Users/username/AppData/Local/Temp
Running from App with Admin rights = C:/Windows/Temp
CONDITION:
I have an installer that requires system reboot to finish the process.
To achieve that, I make a copy of installer in the $TEMP, and put the path in RunOnce
PROBLEM:
The function works fine (after reboot, the program is updated with new version).
However, at the end of installation process, I am unable to delete the copy of installer because the $TEMP = C:/Users/username/AppData/Local/Temp when running the installer by RunOnce.
In fact, the copy of installer is located in C:/Windows/Temp
QUESTION:
Is it possible to force the $TEMP to always be = C:/Windows/Temp ?
Is there any better solution to workaround the case of installation with system reboot?
windows installation nsis temp runonce
asked Nov 22 '18 at 2:03
undoundo
112
I have been noticed $TEMP param has different value when you:
- run the installer.exe manually (by double clicking)
- run from Application with Admin rights.
Running manually will result $TEMP = C:/Users/username/AppData/Local/Temp
Running from App with Admin rights = C:/Windows/Temp
CONDITION:
I have an installer that requires system reboot to finish the process.
To achieve that, I make a copy of installer in the $TEMP, and put the path in RunOnce
PROBLEM:
The function works fine (after reboot, the program is updated with new version).
However, at the end of installation process, I am unable to delete the copy of installer because the $TEMP = C:/Users/username/AppData/Local/Temp when running the installer by RunOnce.
In fact, the copy of installer is located in C:/Windows/Temp
QUESTION:
Is it possible to force the $TEMP to always be = C:/Windows/Temp ?
Is there any better solution to workaround the case of installation with system reboot?
windows installation nsis temp runonce
windows installation nsis temp runonce
asked Nov 22 '18 at 2:03
undoundo
112
asked Nov 22 '18 at 2:03
undoundo
112
asked Nov 22 '18 at 2:03
undoundo
112
asked Nov 22 '18 at 2:03
undoundo
112
asked Nov 22 '18 at 2:03
undoundo
112
112
What is yourRequestExecutionLevelattribute set to?
– Anders
Nov 22 '18 at 3:00
add a comment |
What is yourRequestExecutionLevelattribute set to?
– Anders
Nov 22 '18 at 3:00
What is your
RequestExecutionLevel attribute set to?– Anders
Nov 22 '18 at 3:00
What is your
RequestExecutionLevel attribute set to?– Anders
Nov 22 '18 at 3:00
add a comment |
1 Answer
1
active
oldest
votes
NSIS gets its $Temp variable like this:
First it tries GetTempPath. That function tries (in order): %TMP%, %TEMP%, %USERPROFILE%, and %WINDIR%, and it returns the first variable that exists.
NSIS then tries to write to this directory and if that fails NSIS uses %WINDIR%Temp.
Admin vs non-admin nor UAC elevation is not really the cause of what you are seeing. Sounds more like a configuration or Anti-Virus issue.
You can force $Temp to a specific directory if you really want to in NSIS 3:
Function .onInit
UnsafeStrCpy $Temp "$WindirTemp"
CreateDirectory $Temp
/*
#--# Uncomment to apply the same %TEMP% to child processes #--#
System::Call 'KERNEL32::SetEnvironmentVariable(t"TEMP",t"$Temp")'
System::Call 'KERNEL32::SetEnvironmentVariable(t"TMP",t"$Temp")'
*/
FunctionEnd
I don't actually understand your issue though because the RunOnce entry can tell what it's path is by using $ExePath.
answered Nov 26 '18 at 21:54
AndersAnders
69.5k1074127
Yes, I guess it's not really because of Admin rights. Because the installer is executed by other app (update manager), which is out of my scope. So, I'm not really sure how it becomes C:/Windows/Temp. Anyway, I did a workaround by putting the copy of installer in ProgramFiles, instead of Temp. Thanks for your comments.
– undo
Nov 28 '18 at 2:41
It probably inherited this temp from the update manager. You can inspect the environment of a process with Process Explorer.
– Anders
Nov 28 '18 at 3:07
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422905%2fnsis-temp-has-different-value%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
NSIS gets its $Temp variable like this:
First it tries GetTempPath. That function tries (in order): %TMP%, %TEMP%, %USERPROFILE%, and %WINDIR%, and it returns the first variable that exists.
NSIS then tries to write to this directory and if that fails NSIS uses %WINDIR%Temp.
Admin vs non-admin nor UAC elevation is not really the cause of what you are seeing. Sounds more like a configuration or Anti-Virus issue.
You can force $Temp to a specific directory if you really want to in NSIS 3:
Function .onInit
UnsafeStrCpy $Temp "$WindirTemp"
CreateDirectory $Temp
/*
#--# Uncomment to apply the same %TEMP% to child processes #--#
System::Call 'KERNEL32::SetEnvironmentVariable(t"TEMP",t"$Temp")'
System::Call 'KERNEL32::SetEnvironmentVariable(t"TMP",t"$Temp")'
*/
FunctionEnd
I don't actually understand your issue though because the RunOnce entry can tell what it's path is by using $ExePath.
answered Nov 26 '18 at 21:54
AndersAnders
69.5k1074127
Yes, I guess it's not really because of Admin rights. Because the installer is executed by other app (update manager), which is out of my scope. So, I'm not really sure how it becomes C:/Windows/Temp. Anyway, I did a workaround by putting the copy of installer in ProgramFiles, instead of Temp. Thanks for your comments.
– undo
Nov 28 '18 at 2:41
It probably inherited this temp from the update manager. You can inspect the environment of a process with Process Explorer.
– Anders
Nov 28 '18 at 3:07
add a comment |
NSIS gets its $Temp variable like this:
First it tries GetTempPath. That function tries (in order): %TMP%, %TEMP%, %USERPROFILE%, and %WINDIR%, and it returns the first variable that exists.
NSIS then tries to write to this directory and if that fails NSIS uses %WINDIR%Temp.
Admin vs non-admin nor UAC elevation is not really the cause of what you are seeing. Sounds more like a configuration or Anti-Virus issue.
You can force $Temp to a specific directory if you really want to in NSIS 3:
Function .onInit
UnsafeStrCpy $Temp "$WindirTemp"
CreateDirectory $Temp
/*
#--# Uncomment to apply the same %TEMP% to child processes #--#
System::Call 'KERNEL32::SetEnvironmentVariable(t"TEMP",t"$Temp")'
System::Call 'KERNEL32::SetEnvironmentVariable(t"TMP",t"$Temp")'
*/
FunctionEnd
I don't actually understand your issue though because the RunOnce entry can tell what it's path is by using $ExePath.
answered Nov 26 '18 at 21:54
AndersAnders
69.5k1074127
Yes, I guess it's not really because of Admin rights. Because the installer is executed by other app (update manager), which is out of my scope. So, I'm not really sure how it becomes C:/Windows/Temp. Anyway, I did a workaround by putting the copy of installer in ProgramFiles, instead of Temp. Thanks for your comments.
– undo
Nov 28 '18 at 2:41
It probably inherited this temp from the update manager. You can inspect the environment of a process with Process Explorer.
– Anders
Nov 28 '18 at 3:07
add a comment |
NSIS gets its $Temp variable like this:
First it tries GetTempPath. That function tries (in order): %TMP%, %TEMP%, %USERPROFILE%, and %WINDIR%, and it returns the first variable that exists.
NSIS then tries to write to this directory and if that fails NSIS uses %WINDIR%Temp.
Admin vs non-admin nor UAC elevation is not really the cause of what you are seeing. Sounds more like a configuration or Anti-Virus issue.
You can force $Temp to a specific directory if you really want to in NSIS 3:
Function .onInit
UnsafeStrCpy $Temp "$WindirTemp"
CreateDirectory $Temp
/*
#--# Uncomment to apply the same %TEMP% to child processes #--#
System::Call 'KERNEL32::SetEnvironmentVariable(t"TEMP",t"$Temp")'
System::Call 'KERNEL32::SetEnvironmentVariable(t"TMP",t"$Temp")'
*/
FunctionEnd
I don't actually understand your issue though because the RunOnce entry can tell what it's path is by using $ExePath.
answered Nov 26 '18 at 21:54
AndersAnders
69.5k1074127
NSIS gets its $Temp variable like this:
First it tries GetTempPath. That function tries (in order): %TMP%, %TEMP%, %USERPROFILE%, and %WINDIR%, and it returns the first variable that exists.
NSIS then tries to write to this directory and if that fails NSIS uses %WINDIR%Temp.
Admin vs non-admin nor UAC elevation is not really the cause of what you are seeing. Sounds more like a configuration or Anti-Virus issue.
You can force $Temp to a specific directory if you really want to in NSIS 3:
Function .onInit
UnsafeStrCpy $Temp "$WindirTemp"
CreateDirectory $Temp
/*
#--# Uncomment to apply the same %TEMP% to child processes #--#
System::Call 'KERNEL32::SetEnvironmentVariable(t"TEMP",t"$Temp")'
System::Call 'KERNEL32::SetEnvironmentVariable(t"TMP",t"$Temp")'
*/
FunctionEnd
I don't actually understand your issue though because the RunOnce entry can tell what it's path is by using $ExePath.
answered Nov 26 '18 at 21:54
AndersAnders
69.5k1074127
answered Nov 26 '18 at 21:54
AndersAnders
69.5k1074127
answered Nov 26 '18 at 21:54
AndersAnders
69.5k1074127
answered Nov 26 '18 at 21:54
AndersAnders
69.5k1074127
69.5k1074127
Yes, I guess it's not really because of Admin rights. Because the installer is executed by other app (update manager), which is out of my scope. So, I'm not really sure how it becomes C:/Windows/Temp. Anyway, I did a workaround by putting the copy of installer in ProgramFiles, instead of Temp. Thanks for your comments.
– undo
Nov 28 '18 at 2:41
It probably inherited this temp from the update manager. You can inspect the environment of a process with Process Explorer.
– Anders
Nov 28 '18 at 3:07
add a comment |
Yes, I guess it's not really because of Admin rights. Because the installer is executed by other app (update manager), which is out of my scope. So, I'm not really sure how it becomes C:/Windows/Temp. Anyway, I did a workaround by putting the copy of installer in ProgramFiles, instead of Temp. Thanks for your comments.
– undo
Nov 28 '18 at 2:41
It probably inherited this temp from the update manager. You can inspect the environment of a process with Process Explorer.
– Anders
Nov 28 '18 at 3:07
Yes, I guess it's not really because of Admin rights. Because the installer is executed by other app (update manager), which is out of my scope. So, I'm not really sure how it becomes C:/Windows/Temp. Anyway, I did a workaround by putting the copy of installer in ProgramFiles, instead of Temp. Thanks for your comments.
– undo
Nov 28 '18 at 2:41
Yes, I guess it's not really because of Admin rights. Because the installer is executed by other app (update manager), which is out of my scope. So, I'm not really sure how it becomes C:/Windows/Temp. Anyway, I did a workaround by putting the copy of installer in ProgramFiles, instead of Temp. Thanks for your comments.
– undo
Nov 28 '18 at 2:41
It probably inherited this temp from the update manager. You can inspect the environment of a process with Process Explorer.
– Anders
Nov 28 '18 at 3:07
It probably inherited this temp from the update manager. You can inspect the environment of a process with Process Explorer.
– Anders
Nov 28 '18 at 3:07
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422905%2fnsis-temp-has-different-value%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What is your
RequestExecutionLevelattribute set to?– Anders
Nov 22 '18 at 3:00