Temp folder is not writeable for some applications, resulting app crashes












4















I dont know why, but suddenly many applications in my computer can't start. For example Chrome Portable shows this error on execution:




NSIS Error



Error writing temporary file. Make sure your temp folder is valid




Many other applications just show a Windows error reporting on execution.



Fortunately I had created a Norton Ghost image from the C drive four months ago (when I had absolutely no problem), but after a successful Windows restore, the problem is still the same! Google Chrome is still showing the error above and the other programs still can't be executed.



I searched whole internet for the reason. Most say it's a problem with the %Temp% folder permissions. I took ownership of the folder, set Temp folder owner to "Administrator or the current user", full access for "Admin" and "current user" and "Users" profile, but still it's the same! I have also done these to C:windowsTemp folder.



I even cant execute "Process Monitor" to monitor the problem!



I even changed both %Temp% and C:windowsTemp folders paths to c:Temp but the problem is the same.



It seems many programs can't write files in Temp folder, but I see "Firefox Portable" can do that!



Specs: Win 7 32bit Ultimate SP1





I installed a new fresh windows 7 yesterday, but the problem is still there! i found something interesting: If i move Chrome Portable directory to upper roots of F drive, the program will start normally!! it seemes that windows has problems with specific paths, for example most of the applications on F:programsInstall on my computer cant access Temp and result in error. i checked Permissions on F and Install folder, everything is just like other drives. some said use ICACLS F: /setintegritylevel H but it does not change anything. for now, the only way to get ride of this problem is to downgrade to Win XP so no Permissions and other damn security stuff won't work. please help me out of this headache.










share|improve this question




















  • 1





    If taking ownership of the folder does not solve the problem ( horrible idea this shouldn't be required unless your entire system's permission system is toast ) and even it was toast a restoration of a previous backup would resolve the problem. So it sounds like your backup wasn't what you think it was.

    – Ramhound
    Oct 7 '13 at 18:51






  • 1





    i'm absolutly sure the image is for 4 months ago as its modification date is 4 months ago, desktop icons are less (because desktop icons grow by the time lol :D) and the anti virus database is dated 4 months ago. i'm really surprised too that image restoring didnt worked. i think file permission settings are stored in another place than the windows drive. but where?!

    – Alireza
    Oct 7 '13 at 19:49
















4















I dont know why, but suddenly many applications in my computer can't start. For example Chrome Portable shows this error on execution:




NSIS Error



Error writing temporary file. Make sure your temp folder is valid




Many other applications just show a Windows error reporting on execution.



Fortunately I had created a Norton Ghost image from the C drive four months ago (when I had absolutely no problem), but after a successful Windows restore, the problem is still the same! Google Chrome is still showing the error above and the other programs still can't be executed.



I searched whole internet for the reason. Most say it's a problem with the %Temp% folder permissions. I took ownership of the folder, set Temp folder owner to "Administrator or the current user", full access for "Admin" and "current user" and "Users" profile, but still it's the same! I have also done these to C:windowsTemp folder.



I even cant execute "Process Monitor" to monitor the problem!



I even changed both %Temp% and C:windowsTemp folders paths to c:Temp but the problem is the same.



It seems many programs can't write files in Temp folder, but I see "Firefox Portable" can do that!



Specs: Win 7 32bit Ultimate SP1





I installed a new fresh windows 7 yesterday, but the problem is still there! i found something interesting: If i move Chrome Portable directory to upper roots of F drive, the program will start normally!! it seemes that windows has problems with specific paths, for example most of the applications on F:programsInstall on my computer cant access Temp and result in error. i checked Permissions on F and Install folder, everything is just like other drives. some said use ICACLS F: /setintegritylevel H but it does not change anything. for now, the only way to get ride of this problem is to downgrade to Win XP so no Permissions and other damn security stuff won't work. please help me out of this headache.










share|improve this question




















  • 1





    If taking ownership of the folder does not solve the problem ( horrible idea this shouldn't be required unless your entire system's permission system is toast ) and even it was toast a restoration of a previous backup would resolve the problem. So it sounds like your backup wasn't what you think it was.

    – Ramhound
    Oct 7 '13 at 18:51






  • 1





    i'm absolutly sure the image is for 4 months ago as its modification date is 4 months ago, desktop icons are less (because desktop icons grow by the time lol :D) and the anti virus database is dated 4 months ago. i'm really surprised too that image restoring didnt worked. i think file permission settings are stored in another place than the windows drive. but where?!

    – Alireza
    Oct 7 '13 at 19:49














4












4








4








I dont know why, but suddenly many applications in my computer can't start. For example Chrome Portable shows this error on execution:




NSIS Error



Error writing temporary file. Make sure your temp folder is valid




Many other applications just show a Windows error reporting on execution.



Fortunately I had created a Norton Ghost image from the C drive four months ago (when I had absolutely no problem), but after a successful Windows restore, the problem is still the same! Google Chrome is still showing the error above and the other programs still can't be executed.



I searched whole internet for the reason. Most say it's a problem with the %Temp% folder permissions. I took ownership of the folder, set Temp folder owner to "Administrator or the current user", full access for "Admin" and "current user" and "Users" profile, but still it's the same! I have also done these to C:windowsTemp folder.



I even cant execute "Process Monitor" to monitor the problem!



I even changed both %Temp% and C:windowsTemp folders paths to c:Temp but the problem is the same.



It seems many programs can't write files in Temp folder, but I see "Firefox Portable" can do that!



Specs: Win 7 32bit Ultimate SP1





I installed a new fresh windows 7 yesterday, but the problem is still there! i found something interesting: If i move Chrome Portable directory to upper roots of F drive, the program will start normally!! it seemes that windows has problems with specific paths, for example most of the applications on F:programsInstall on my computer cant access Temp and result in error. i checked Permissions on F and Install folder, everything is just like other drives. some said use ICACLS F: /setintegritylevel H but it does not change anything. for now, the only way to get ride of this problem is to downgrade to Win XP so no Permissions and other damn security stuff won't work. please help me out of this headache.










share|improve this question
















I dont know why, but suddenly many applications in my computer can't start. For example Chrome Portable shows this error on execution:




NSIS Error



Error writing temporary file. Make sure your temp folder is valid




Many other applications just show a Windows error reporting on execution.



Fortunately I had created a Norton Ghost image from the C drive four months ago (when I had absolutely no problem), but after a successful Windows restore, the problem is still the same! Google Chrome is still showing the error above and the other programs still can't be executed.



I searched whole internet for the reason. Most say it's a problem with the %Temp% folder permissions. I took ownership of the folder, set Temp folder owner to "Administrator or the current user", full access for "Admin" and "current user" and "Users" profile, but still it's the same! I have also done these to C:windowsTemp folder.



I even cant execute "Process Monitor" to monitor the problem!



I even changed both %Temp% and C:windowsTemp folders paths to c:Temp but the problem is the same.



It seems many programs can't write files in Temp folder, but I see "Firefox Portable" can do that!



Specs: Win 7 32bit Ultimate SP1





I installed a new fresh windows 7 yesterday, but the problem is still there! i found something interesting: If i move Chrome Portable directory to upper roots of F drive, the program will start normally!! it seemes that windows has problems with specific paths, for example most of the applications on F:programsInstall on my computer cant access Temp and result in error. i checked Permissions on F and Install folder, everything is just like other drives. some said use ICACLS F: /setintegritylevel H but it does not change anything. for now, the only way to get ride of this problem is to downgrade to Win XP so no Permissions and other damn security stuff won't work. please help me out of this headache.







windows-7 windows permissions crash nsis






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 18 '13 at 17:44







Alireza

















asked Oct 7 '13 at 18:43









AlirezaAlireza

33126




33126








  • 1





    If taking ownership of the folder does not solve the problem ( horrible idea this shouldn't be required unless your entire system's permission system is toast ) and even it was toast a restoration of a previous backup would resolve the problem. So it sounds like your backup wasn't what you think it was.

    – Ramhound
    Oct 7 '13 at 18:51






  • 1





    i'm absolutly sure the image is for 4 months ago as its modification date is 4 months ago, desktop icons are less (because desktop icons grow by the time lol :D) and the anti virus database is dated 4 months ago. i'm really surprised too that image restoring didnt worked. i think file permission settings are stored in another place than the windows drive. but where?!

    – Alireza
    Oct 7 '13 at 19:49














  • 1





    If taking ownership of the folder does not solve the problem ( horrible idea this shouldn't be required unless your entire system's permission system is toast ) and even it was toast a restoration of a previous backup would resolve the problem. So it sounds like your backup wasn't what you think it was.

    – Ramhound
    Oct 7 '13 at 18:51






  • 1





    i'm absolutly sure the image is for 4 months ago as its modification date is 4 months ago, desktop icons are less (because desktop icons grow by the time lol :D) and the anti virus database is dated 4 months ago. i'm really surprised too that image restoring didnt worked. i think file permission settings are stored in another place than the windows drive. but where?!

    – Alireza
    Oct 7 '13 at 19:49








1




1





If taking ownership of the folder does not solve the problem ( horrible idea this shouldn't be required unless your entire system's permission system is toast ) and even it was toast a restoration of a previous backup would resolve the problem. So it sounds like your backup wasn't what you think it was.

– Ramhound
Oct 7 '13 at 18:51





If taking ownership of the folder does not solve the problem ( horrible idea this shouldn't be required unless your entire system's permission system is toast ) and even it was toast a restoration of a previous backup would resolve the problem. So it sounds like your backup wasn't what you think it was.

– Ramhound
Oct 7 '13 at 18:51




1




1





i'm absolutly sure the image is for 4 months ago as its modification date is 4 months ago, desktop icons are less (because desktop icons grow by the time lol :D) and the anti virus database is dated 4 months ago. i'm really surprised too that image restoring didnt worked. i think file permission settings are stored in another place than the windows drive. but where?!

– Alireza
Oct 7 '13 at 19:49





i'm absolutly sure the image is for 4 months ago as its modification date is 4 months ago, desktop icons are less (because desktop icons grow by the time lol :D) and the anti virus database is dated 4 months ago. i'm really surprised too that image restoring didnt worked. i think file permission settings are stored in another place than the windows drive. but where?!

– Alireza
Oct 7 '13 at 19:49










3 Answers
3






active

oldest

votes


















2














If you run a program (that is you, as in your account, not the OS/System) then I expect it to write to your temp folder. By default that is %osdrive% (aka C:) usersusernameAppDatalocaltemp.



You can verify that with starting cmd.exe and typing echo %tmp%



This should be different from the OS temp files! Else a user could modify files in the OS temp files and compromise the system.






share|improve this answer


























  • i didnt get what you said but i checked echo %tmp% in and it was pointing to c:temp (as i changed default temp path, its poining to the currect path)

    – Alireza
    Oct 7 '13 at 19:52











  • Do you have rights to write to C:temp. (Where 'you' is 'your user-account').

    – Hennes
    Oct 7 '13 at 19:58











  • yes current user and Admin both have full access to C:temp

    – Alireza
    Oct 7 '13 at 20:02



















0














Here's what happened to me and what I did.



I couldn't install anything.




  1. Made a new local admin user - logged on tried install - same temp file access error.


  2. installed windows updates and ran malware bytes to see if some sneaky process had taken control - no change.


  3. Made myself owner of
    %USERPROFILE%appdatalocaltemp
    (c:usersyournameappdatalocaltemp) - no change


  4. I then tried deleting the accursed temp folder but 'no go' even in safe mode.





So I left it and created a new folder in the same location called tmp



Then I changed the install paths



(right click my computer / advanced system settings / advanced /environmental variables)



edited temp to %USERPROFILE%appdatalocaltmp
and (similarly) tmp to %USERPROFILE%appdatalocaltmp



Installs started working again - it looks like temp folder was either corrupted or in control of some other process that wouldn't let it go....



Conor






share|improve this answer


























  • ...For what it's worth, in my case, I suspect it was actually dropbox that caused me to loose access to the folder...

    – user510132
    Oct 16 '15 at 9:45



















0














The following solved the issue for my portable Firefox installation. You should look up Icacls and Integrity Levels before running this blindly.



firefox_lowIntegrity.bat



icacls "D:{PATH_TO}FirefoxPortableFirefoxPortable.exe" /setintegritylevel low
REM DOWNLOADS:
icacls "C:Users{USER}Downloads" /setintegritylevel (OI)(CI)low /t /c

REM TEMP:
icacls "C:Users{USER}AppDataLocalTemp" /setintegritylevel (OI)(CI)low /t /c

REM add data LOCAL:
REM icacls "C:UsersYourWindowsUserAccountAppDataLocalMozilla" /setintegritylevel (OI)(CI)low /t /c

REM add data ROAMING:
REM icacls "C:UsersYourWindowsUserAccountAppDataRoamingMozilla" /setintegritylevel (OI)(CI)low /t /c

REM FLASH:
REM icacls "C:UsersYourWindowsUserAccountAppDataRoamingMacromediaFlash Player" /setintegritylevel (OI)(CI)low /t /c

REM PORTABLE:
icacls "D:{PATH_TO}FirefoxPortableAppFirefoxfirefox.exe" /setintegritylevel low
icacls "D:{PATH_TO}FirefoxPortableApp" /setintegritylevel (OI)(CI)low /t /c
icacls "D:{PATH_TO}FirefoxPortableData" /setintegritylevel (OI)(CI)low /t /c





share|improve this answer


























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f655630%2ftemp-folder-is-not-writeable-for-some-applications-resulting-app-crashes%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2














    If you run a program (that is you, as in your account, not the OS/System) then I expect it to write to your temp folder. By default that is %osdrive% (aka C:) usersusernameAppDatalocaltemp.



    You can verify that with starting cmd.exe and typing echo %tmp%



    This should be different from the OS temp files! Else a user could modify files in the OS temp files and compromise the system.






    share|improve this answer


























    • i didnt get what you said but i checked echo %tmp% in and it was pointing to c:temp (as i changed default temp path, its poining to the currect path)

      – Alireza
      Oct 7 '13 at 19:52











    • Do you have rights to write to C:temp. (Where 'you' is 'your user-account').

      – Hennes
      Oct 7 '13 at 19:58











    • yes current user and Admin both have full access to C:temp

      – Alireza
      Oct 7 '13 at 20:02
















    2














    If you run a program (that is you, as in your account, not the OS/System) then I expect it to write to your temp folder. By default that is %osdrive% (aka C:) usersusernameAppDatalocaltemp.



    You can verify that with starting cmd.exe and typing echo %tmp%



    This should be different from the OS temp files! Else a user could modify files in the OS temp files and compromise the system.






    share|improve this answer


























    • i didnt get what you said but i checked echo %tmp% in and it was pointing to c:temp (as i changed default temp path, its poining to the currect path)

      – Alireza
      Oct 7 '13 at 19:52











    • Do you have rights to write to C:temp. (Where 'you' is 'your user-account').

      – Hennes
      Oct 7 '13 at 19:58











    • yes current user and Admin both have full access to C:temp

      – Alireza
      Oct 7 '13 at 20:02














    2












    2








    2







    If you run a program (that is you, as in your account, not the OS/System) then I expect it to write to your temp folder. By default that is %osdrive% (aka C:) usersusernameAppDatalocaltemp.



    You can verify that with starting cmd.exe and typing echo %tmp%



    This should be different from the OS temp files! Else a user could modify files in the OS temp files and compromise the system.






    share|improve this answer















    If you run a program (that is you, as in your account, not the OS/System) then I expect it to write to your temp folder. By default that is %osdrive% (aka C:) usersusernameAppDatalocaltemp.



    You can verify that with starting cmd.exe and typing echo %tmp%



    This should be different from the OS temp files! Else a user could modify files in the OS temp files and compromise the system.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Feb 11 at 16:47









    Mikey T.K.

    2,18231941




    2,18231941










    answered Oct 7 '13 at 18:46









    HennesHennes

    59.3k793144




    59.3k793144













    • i didnt get what you said but i checked echo %tmp% in and it was pointing to c:temp (as i changed default temp path, its poining to the currect path)

      – Alireza
      Oct 7 '13 at 19:52











    • Do you have rights to write to C:temp. (Where 'you' is 'your user-account').

      – Hennes
      Oct 7 '13 at 19:58











    • yes current user and Admin both have full access to C:temp

      – Alireza
      Oct 7 '13 at 20:02



















    • i didnt get what you said but i checked echo %tmp% in and it was pointing to c:temp (as i changed default temp path, its poining to the currect path)

      – Alireza
      Oct 7 '13 at 19:52











    • Do you have rights to write to C:temp. (Where 'you' is 'your user-account').

      – Hennes
      Oct 7 '13 at 19:58











    • yes current user and Admin both have full access to C:temp

      – Alireza
      Oct 7 '13 at 20:02

















    i didnt get what you said but i checked echo %tmp% in and it was pointing to c:temp (as i changed default temp path, its poining to the currect path)

    – Alireza
    Oct 7 '13 at 19:52





    i didnt get what you said but i checked echo %tmp% in and it was pointing to c:temp (as i changed default temp path, its poining to the currect path)

    – Alireza
    Oct 7 '13 at 19:52













    Do you have rights to write to C:temp. (Where 'you' is 'your user-account').

    – Hennes
    Oct 7 '13 at 19:58





    Do you have rights to write to C:temp. (Where 'you' is 'your user-account').

    – Hennes
    Oct 7 '13 at 19:58













    yes current user and Admin both have full access to C:temp

    – Alireza
    Oct 7 '13 at 20:02





    yes current user and Admin both have full access to C:temp

    – Alireza
    Oct 7 '13 at 20:02













    0














    Here's what happened to me and what I did.



    I couldn't install anything.




    1. Made a new local admin user - logged on tried install - same temp file access error.


    2. installed windows updates and ran malware bytes to see if some sneaky process had taken control - no change.


    3. Made myself owner of
      %USERPROFILE%appdatalocaltemp
      (c:usersyournameappdatalocaltemp) - no change


    4. I then tried deleting the accursed temp folder but 'no go' even in safe mode.





    So I left it and created a new folder in the same location called tmp



    Then I changed the install paths



    (right click my computer / advanced system settings / advanced /environmental variables)



    edited temp to %USERPROFILE%appdatalocaltmp
    and (similarly) tmp to %USERPROFILE%appdatalocaltmp



    Installs started working again - it looks like temp folder was either corrupted or in control of some other process that wouldn't let it go....



    Conor






    share|improve this answer


























    • ...For what it's worth, in my case, I suspect it was actually dropbox that caused me to loose access to the folder...

      – user510132
      Oct 16 '15 at 9:45
















    0














    Here's what happened to me and what I did.



    I couldn't install anything.




    1. Made a new local admin user - logged on tried install - same temp file access error.


    2. installed windows updates and ran malware bytes to see if some sneaky process had taken control - no change.


    3. Made myself owner of
      %USERPROFILE%appdatalocaltemp
      (c:usersyournameappdatalocaltemp) - no change


    4. I then tried deleting the accursed temp folder but 'no go' even in safe mode.





    So I left it and created a new folder in the same location called tmp



    Then I changed the install paths



    (right click my computer / advanced system settings / advanced /environmental variables)



    edited temp to %USERPROFILE%appdatalocaltmp
    and (similarly) tmp to %USERPROFILE%appdatalocaltmp



    Installs started working again - it looks like temp folder was either corrupted or in control of some other process that wouldn't let it go....



    Conor






    share|improve this answer


























    • ...For what it's worth, in my case, I suspect it was actually dropbox that caused me to loose access to the folder...

      – user510132
      Oct 16 '15 at 9:45














    0












    0








    0







    Here's what happened to me and what I did.



    I couldn't install anything.




    1. Made a new local admin user - logged on tried install - same temp file access error.


    2. installed windows updates and ran malware bytes to see if some sneaky process had taken control - no change.


    3. Made myself owner of
      %USERPROFILE%appdatalocaltemp
      (c:usersyournameappdatalocaltemp) - no change


    4. I then tried deleting the accursed temp folder but 'no go' even in safe mode.





    So I left it and created a new folder in the same location called tmp



    Then I changed the install paths



    (right click my computer / advanced system settings / advanced /environmental variables)



    edited temp to %USERPROFILE%appdatalocaltmp
    and (similarly) tmp to %USERPROFILE%appdatalocaltmp



    Installs started working again - it looks like temp folder was either corrupted or in control of some other process that wouldn't let it go....



    Conor






    share|improve this answer















    Here's what happened to me and what I did.



    I couldn't install anything.




    1. Made a new local admin user - logged on tried install - same temp file access error.


    2. installed windows updates and ran malware bytes to see if some sneaky process had taken control - no change.


    3. Made myself owner of
      %USERPROFILE%appdatalocaltemp
      (c:usersyournameappdatalocaltemp) - no change


    4. I then tried deleting the accursed temp folder but 'no go' even in safe mode.





    So I left it and created a new folder in the same location called tmp



    Then I changed the install paths



    (right click my computer / advanced system settings / advanced /environmental variables)



    edited temp to %USERPROFILE%appdatalocaltmp
    and (similarly) tmp to %USERPROFILE%appdatalocaltmp



    Installs started working again - it looks like temp folder was either corrupted or in control of some other process that wouldn't let it go....



    Conor







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Oct 16 '15 at 8:20

























    answered Oct 16 '15 at 8:05









    user510132user510132

    12




    12













    • ...For what it's worth, in my case, I suspect it was actually dropbox that caused me to loose access to the folder...

      – user510132
      Oct 16 '15 at 9:45



















    • ...For what it's worth, in my case, I suspect it was actually dropbox that caused me to loose access to the folder...

      – user510132
      Oct 16 '15 at 9:45

















    ...For what it's worth, in my case, I suspect it was actually dropbox that caused me to loose access to the folder...

    – user510132
    Oct 16 '15 at 9:45





    ...For what it's worth, in my case, I suspect it was actually dropbox that caused me to loose access to the folder...

    – user510132
    Oct 16 '15 at 9:45











    0














    The following solved the issue for my portable Firefox installation. You should look up Icacls and Integrity Levels before running this blindly.



    firefox_lowIntegrity.bat



    icacls "D:{PATH_TO}FirefoxPortableFirefoxPortable.exe" /setintegritylevel low
    REM DOWNLOADS:
    icacls "C:Users{USER}Downloads" /setintegritylevel (OI)(CI)low /t /c

    REM TEMP:
    icacls "C:Users{USER}AppDataLocalTemp" /setintegritylevel (OI)(CI)low /t /c

    REM add data LOCAL:
    REM icacls "C:UsersYourWindowsUserAccountAppDataLocalMozilla" /setintegritylevel (OI)(CI)low /t /c

    REM add data ROAMING:
    REM icacls "C:UsersYourWindowsUserAccountAppDataRoamingMozilla" /setintegritylevel (OI)(CI)low /t /c

    REM FLASH:
    REM icacls "C:UsersYourWindowsUserAccountAppDataRoamingMacromediaFlash Player" /setintegritylevel (OI)(CI)low /t /c

    REM PORTABLE:
    icacls "D:{PATH_TO}FirefoxPortableAppFirefoxfirefox.exe" /setintegritylevel low
    icacls "D:{PATH_TO}FirefoxPortableApp" /setintegritylevel (OI)(CI)low /t /c
    icacls "D:{PATH_TO}FirefoxPortableData" /setintegritylevel (OI)(CI)low /t /c





    share|improve this answer






























      0














      The following solved the issue for my portable Firefox installation. You should look up Icacls and Integrity Levels before running this blindly.



      firefox_lowIntegrity.bat



      icacls "D:{PATH_TO}FirefoxPortableFirefoxPortable.exe" /setintegritylevel low
      REM DOWNLOADS:
      icacls "C:Users{USER}Downloads" /setintegritylevel (OI)(CI)low /t /c

      REM TEMP:
      icacls "C:Users{USER}AppDataLocalTemp" /setintegritylevel (OI)(CI)low /t /c

      REM add data LOCAL:
      REM icacls "C:UsersYourWindowsUserAccountAppDataLocalMozilla" /setintegritylevel (OI)(CI)low /t /c

      REM add data ROAMING:
      REM icacls "C:UsersYourWindowsUserAccountAppDataRoamingMozilla" /setintegritylevel (OI)(CI)low /t /c

      REM FLASH:
      REM icacls "C:UsersYourWindowsUserAccountAppDataRoamingMacromediaFlash Player" /setintegritylevel (OI)(CI)low /t /c

      REM PORTABLE:
      icacls "D:{PATH_TO}FirefoxPortableAppFirefoxfirefox.exe" /setintegritylevel low
      icacls "D:{PATH_TO}FirefoxPortableApp" /setintegritylevel (OI)(CI)low /t /c
      icacls "D:{PATH_TO}FirefoxPortableData" /setintegritylevel (OI)(CI)low /t /c





      share|improve this answer




























        0












        0








        0







        The following solved the issue for my portable Firefox installation. You should look up Icacls and Integrity Levels before running this blindly.



        firefox_lowIntegrity.bat



        icacls "D:{PATH_TO}FirefoxPortableFirefoxPortable.exe" /setintegritylevel low
        REM DOWNLOADS:
        icacls "C:Users{USER}Downloads" /setintegritylevel (OI)(CI)low /t /c

        REM TEMP:
        icacls "C:Users{USER}AppDataLocalTemp" /setintegritylevel (OI)(CI)low /t /c

        REM add data LOCAL:
        REM icacls "C:UsersYourWindowsUserAccountAppDataLocalMozilla" /setintegritylevel (OI)(CI)low /t /c

        REM add data ROAMING:
        REM icacls "C:UsersYourWindowsUserAccountAppDataRoamingMozilla" /setintegritylevel (OI)(CI)low /t /c

        REM FLASH:
        REM icacls "C:UsersYourWindowsUserAccountAppDataRoamingMacromediaFlash Player" /setintegritylevel (OI)(CI)low /t /c

        REM PORTABLE:
        icacls "D:{PATH_TO}FirefoxPortableAppFirefoxfirefox.exe" /setintegritylevel low
        icacls "D:{PATH_TO}FirefoxPortableApp" /setintegritylevel (OI)(CI)low /t /c
        icacls "D:{PATH_TO}FirefoxPortableData" /setintegritylevel (OI)(CI)low /t /c





        share|improve this answer















        The following solved the issue for my portable Firefox installation. You should look up Icacls and Integrity Levels before running this blindly.



        firefox_lowIntegrity.bat



        icacls "D:{PATH_TO}FirefoxPortableFirefoxPortable.exe" /setintegritylevel low
        REM DOWNLOADS:
        icacls "C:Users{USER}Downloads" /setintegritylevel (OI)(CI)low /t /c

        REM TEMP:
        icacls "C:Users{USER}AppDataLocalTemp" /setintegritylevel (OI)(CI)low /t /c

        REM add data LOCAL:
        REM icacls "C:UsersYourWindowsUserAccountAppDataLocalMozilla" /setintegritylevel (OI)(CI)low /t /c

        REM add data ROAMING:
        REM icacls "C:UsersYourWindowsUserAccountAppDataRoamingMozilla" /setintegritylevel (OI)(CI)low /t /c

        REM FLASH:
        REM icacls "C:UsersYourWindowsUserAccountAppDataRoamingMacromediaFlash Player" /setintegritylevel (OI)(CI)low /t /c

        REM PORTABLE:
        icacls "D:{PATH_TO}FirefoxPortableAppFirefoxfirefox.exe" /setintegritylevel low
        icacls "D:{PATH_TO}FirefoxPortableApp" /setintegritylevel (OI)(CI)low /t /c
        icacls "D:{PATH_TO}FirefoxPortableData" /setintegritylevel (OI)(CI)low /t /c






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Aug 13 '16 at 15:24









        Twisty Impersonator

        18.7k146799




        18.7k146799










        answered Aug 13 '16 at 11:11









        1AabS2QqsQ1AabS2QqsQ

        1




        1






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • 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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f655630%2ftemp-folder-is-not-writeable-for-some-applications-resulting-app-crashes%23new-answer', 'question_page');
            }
            );

            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







            Popular posts from this blog

            How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

            is 'sed' thread safe

            How to make a Squid Proxy server?