Quote:
Originally Posted by TerryNet Otherwise, I'm going to take a back seat and let TheOutcaste respond w/o my hindrance. |
Never a hindrance!
Barring a typo, I don't know why it wouldn't appear on the desktop, though from the screenshot this appears to be a non-english version of Windows.
If your username contains characters other than the standard ASCII characters that might be a factor.
If
%userprofile%\Desktop gets expanded to a folder that doesn't exist, it should give this error:
The system cannot find the path specified.
If you didn't get an error, the file was put someplace.
You can always use search and search for
variables.txt to see where it ended up.
On rare occasions I've seen files get created off of the visible desktop, so it may just be off screen.
The first COMSPEC value is the correct one:
C:\WINDOWS\system32\cmd.exe
so that part is OK. (I'm guessing the period at the end in the 2nd post was added when you typed the reply).
I'm not sure how the path ended up this way. Haven't heard of malware doing this but I'm no malware expert.
I
have seen glitches where a program doesn't add itself to the path correctly and ends up deleting the current value.
You end up with just the new program in the path, plus anything added after that point.
It is definitely missing the Windows folders which is the reason cmd doesn't work from the run box.
Two other oddities: 1 item without a drive letter, and it and another item are duplicated.
I've broken it down to the separate folders so it's easier to see:
GL
C:\Program Files\Java\jdk1.6.0_14\bin
C:\Program Files\TortoiseSVN\bin
c:\Program Files\Microsoft SQL Server\100\Tools\Binn
c:\Program Files\Microsoft SQL Server\100\DTS\Binn
GL
C:\Program Files\Java\jdk1.6.0_14\bin
The
GL doesn't have a drive letter, meaning it will be seen as a relative path, which can cause odd behavior, especially in a Command Prompt.
The items in blue are duplicates.
I'd check and see if you have a
C:\GL folder, and if so, make sure you know what it is.
Next we can fix the path variable and see if it resolves the issue. If it gets changed after we fix it and reboot, then it's likely malware at work.
Right click My Computer, click
Properties
Click the
Advanced tab
Click the
Environment Variables button at the bottom
Check under the
User variables for username section. There should not be a
PATH entry. If there is, copy the value and post back
(Double click on path, press CTRL+C to copy the contents. Then press CTRL+V in the reply window (or notepad))
Under
System variables, find the
PATH entry and double click it.
The
Variable value: box should be selected with it's contents highlighted; Press
Delete
Copy and paste the following into the box:
Code:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Java\jdk1.6.0_14\bin;C:\Program Files\TortoiseSVN\bin;c:\Program Files\Microsoft SQL Server\100\Tools\Binn;c:\Program Files\Microsoft SQL Server\100\DTS\Binn;GL
OK your way back to the Desktop, and try
Start | Run | CMD and see if it now works.
Now, reboot and see if it still works.
If not, then something is changing that path value; it should only be changed when a program is installed that needs to use the path variable, not that many do.
In that case, time to let the malware experts take over.
Note:
%Systemroot% will be expanded to the correct value, usually
C:\Windows, and will display that way in the
System variables window and the Command Prompt, but will appear as
%Systemroot% in the Edit box.
I've left the
GL as the last item just in case a program needs it for some odd reason.
You can search your hard drive for a folder named exactly
GL, and if none exist, just remove
;GL from the end of the line.
Only other thing that comes to mind is it's the tail end of something that got deleted when the glitch happened,
say something ending with
OpenGL, perhaps part of a Video Driver.
I don't have that in the path on any of my systems, but I only have Built in or ATI cards.