I think that both environment varaiables and file and folder names are case insensitive,
i.e. Temp = TEMP = temp.
At my first attempt I only did half the job and only altered the "User Variables", and subsequently realised that "System Variables" also merit changing.
The consequence was that BEFORE the User has logged into Windows anything written to %TEMP% actually writes to the system drive
(Something like C:\Windows\System32\Temp\ I think - but Google probably knows for sure)
Another possible consequence might be that some application that runs before you log in (e.g. Antivirus, DropBox, etc.) might adopt that initial default as its "scratchpad".
I dread to think of Trident, the I.E. engine that is built into Windows.
Is it possible that you have also only done half the job ?
This is a simple guide with GUI screen-shots for changing both User and System variables
http://forums.overcl...howtopic=184591
This is a concise guide which fits on the screen without scrolling
http://blogs.msdn.co.../15/513134.aspx
N.B. I first relocated my %TEMP% after a VMWARE Virtual Machine misfired and aborted.
When I closed various Windows and looked at Windows Explorer I saw a great big RED bar across system drive C:\
and I found that 12 GB of free space had been reduced to a few dozen MB due to a constipated %TEMP%.
I was thankful that Windows was still running (creeping) but feared it might never boot again with such little free space so I deleted the %TEMP% junk.
I rebooted and all was well, and I then Googled for a way to relocate %TEMP% and ensure it would never again put my system drive in jeopardy.