• Remote Desktop Mts
• Mstsc Ip
• Technet Mstsc

And then provide full authorization to mstscax.dll and mstsc.exe files respectively. Step-2: Uninstall the update that is causing this issue which is probably KB4284835. Step-3: Processing forward, restore original Windows 10 files (mstsc.exe and mstscax.dll) to the following folder. Process rdcProcess = new Process; rdcProcess.StartInfo.FileName = Environment.ExpandEnvironmentVariables(@'%SystemRoot% system32 cmdkey.exe');. Wanted to access Remote desktop in Windows using Run Command? Press Windows+R to open Run and type mstsc and press enter. There are other several ways to launch Remote desktop connection using command line and by creating shortcuts.

Reference list of Windows Icons contained in DLL and EXE icon libraries

The num­bers below each icon refer to the icon num­ber of the file, and the num­ber in brack­ets indic­ates how many vari­ants of the icon there are.

%windir%system32compstui.dll (Com­mon Prop­erty Sheet User Inter­face)

%windir%system32ddores.dll (Device Cat­egory Inform­a­tion and Resources)

%windir%system32ieframe.dll (Inter­net Explorer)

%windir%system32imageres.dll (Win­dows Image Resource)

%windir%system32mmcndmgr.dll (Microsoft Man­age­ment Con­sole Node Man­ager)

%windir%system32moricons.dll (Win­dows NT Setup Icon Resources)

%windir%system32netshell.dll (Net­work Con­nec­tions Shell)

%windir%system32pnidui.dll (Net­work Sys­tem Icons)

%windir%system32shell32.dll (Win­dows Shell Com­mon)

%windir%system32wmploc.dll (Win­dows Media Play­er Resources)

%windir%system32pifmgr.dll (Win­dows NT PIF Man­ager Icon Resource Lib­rary)

%windir%system32wpdshext.dll (Port­able Devices Shell Exten­sion)

%windir%system32comres.dll (COM+ Resources)

%windir%system32dmdskres.dll (Disk Man­age­ment Sup­port Snap-In)

%windir%system32dsuiext.dll (Dir­ect­ory Ser­vice Com­mon UI)

%windir%system32inetcplc.dll (Inter­net Con­trol Pan­el)

%windir%system32mstsc.exe (Remote Desktop Con­nec­tion Cli­ent)

%windir%system32mstscax.dll (Remote Desktop Ser­vices Act­iveX Cli­ent)

%windir%system32setupapi.dll (Win­dows Setup API)

%windir%system32shdocvw.dll (Shell Doc Object and Con­trol Lib­rary)

%windir%system32urlmon.dll (OLE32 Exten­sion for Win32)

%windir%system32wiashext.dll (Ima­ging Devices Shell Folder UI)

%windir%system32mmres.dll (Gen­er­al Audio Resources)

See Updates 3 and 4 below for how the issue has evolved

My computer (Windows 7 x64, Lenovo Thinkpad T530) is having an issue resolving %windir%. After boot-up, everything works fine. At some point a while later, the computer is suddenly unable to resolve %windir%.

Checking the environment variables window shows that it is defined.

Checking the registry also shows that it is defined as well. I've actually deleted the key and re-entered it to no avail.

After a reboot, everything works fine for a while. Does anyone have any thoughts on anything else I can check?

Update 1:After thinking about it some, I have uninstalled the Konica Minolta Pagebox driver/program that was installed about the time this problem started happening (see comments below). The problem seems to take about 4-24 hours (I've never timed it) to manifest, so I'll update again after that.

Update 2:Issue is still occurring. I came back from lunch and %windir% cannot be found. I did a test after a reboot this morning and put the computer to sleep, then woke it up. %windir% was still defined after waking up.

Update 3:Per Daniel in the comments, I ran set before and after error and compared the outputs. The first thing I noticed is that on a fresh boot my %path% is 2000+ characters long. I pruned it down to ~375 characters and verified it in a new cmd window. I rebooted, checked the path again, and it was back to over 2000+ characters (it matched what I originally saw). I truncated it again and rebooted once more and the same thing happened. I deleted the path variable and created a new one; same thing happened. At this point all I can conclude is either I cannot permanently change my path OR the path is being reset by some process on boot. Any thoughts?

Update 4:I edited my path via the registry method suggested below. I checked my path today after running for a while and it has grown from what I entered into the registry; it now has a few new entries and a lot of duplicates. The only new entries are from SQL Server 2012. I went to change this in the registry and I noticed that the registry does NOT match the output of echo %path%. Checking the Environment Variables from the Advanced Properties Tab shows a third version of my path.

It looks as though the command line path = registry path + environment variables path. I attempted to set the registry path and the environment variables path to the same thing and reboot. After reboot, my path is now doubled, basically two back-to-back copies of the registry path above.

Once again, any thoughts?

Update 5: After talking with the IT Manager, he says he is fighting a similar issue on another computer. Both computers have SSDs (seems to be the only common factor). This may or may not be pertinent.

10 Answers

I had the same issue and found this question first. However, the real cause/solution is not mentioned yet in this question, but it is mentioned here: Windows 7's PATH and environment variables are corrupted

Summary of the solution: make sure your path is < 2048 characters. Check in both the user variables and the system variables.

With the GUI, set your %windir% variable content to %SystemRoot%.

As for your %path%, you may solve this with Registry Editor:

• Start Regedit.exe
• Go to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerEnvironment
• In the right pane, double-click on the value Path (REG_EXPAND_SZ)
• Change the value however you like and reboot

I did have the same problem in my Lenovo TS530. It started to occur after installing new programs that caused my path to be even much longer than before and so that the installers added the new stuff into the beginning of path definition. I edited the path in regedt by moving %SystemRoot% into the beginning of the path definition.

In addition, I edited enviromental variable windir from

to

That seems to have fixed the problem. (It is possible that I did the mistake with backslash earlier while trying to fix the problem. Or alternatively the installer has changed it.)

I had the same issue. It was resolved when I deleted the PATH Environment variable (after making a backup of its contents) in the following dialog.

I reconstructed the PATH variable later one by one. I moved part of the PATH contents which did not fit in the System variables into the User variables PATH.

suspectus

I have found (consistently) that this will also occur if SQL Server 2012 or later versions are installed on the Windows 7 machine (not sure if the issue also occurs on Win8.x or Win10), but the solution I've found is to also create the windir Environment variable under the current user context to be set to %SystemRoot%. The only time we would see this is when RDP'ing (remote session) into the workstation(s). If we logged into the console we would not encounter this at all. I don't know SQL 2012 (or later) components happened to be installed on yours just prior to this happening or not, but you could try this resolution.

Our help desk gave me this response:

1. Open User Account Control Settings by clicking the Start button , and then clicking Control Panel. In the search box, type uac, and then click Change User Account Control settings.
2. Do the following:•To turn off UAC, move the slider to the Never notify position, and then click OK. If you're prompted for an administrator password or confirmation, type the password or provide confirmation. You will need to restart your computer for UAC to be turned off.

It works given two different things:

1.) This problem doesn't actually exist because this program requires %windir to be correctly working. Instead run C:WindowsSystem32UserAccountControlSettings in command prompt.

2.) You prefer not having the windows security warnings.

I had the same problem after upgrading to an SSD on my Lenovo X230. The software I used for the migration (Acronis TrueImage) had added a path value, which must have pushed me over the limit. I solved it as follows:

Open Regedit

Go to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerEnvironment

Modify the Path value (see the answer from user184745 above).

Cut the current value and pasted into Notepad.

Edited out several duplicate values as well as paths that seemed of little benefit. I reduced the length of the path from 2,283 chars to 1,517.

Pasted the new path string into the Path key.

(Saved the contents of my Notepad just in case.)

Rebooted. All is well.

Excellll

As already mentioned by @Pieter-Jan Busschaert it's most likely because of a corrupt or too long PATH environment variable.

Remote Desktop Mts

The easiest way how to fix this is by downloading the Rapid Environment Editor. It shows you what's wrong with your PATH settings and lets you fix it right away.

DunkenDunken

Please check out the limitation of the path-variable:https://support.microsoft.com/en-us/kb/2685893

Mstsc Ip

I had the same issues as above. %windir%. icons not showing for some items. Any application that used windir... Went through all the fixes including cold boot, path shortening, etc.
Finally recreated my windows profile... problem gone.

protected by bwDracoApr 25 '16 at 20:26

Technet Mstsc

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged windows-7environment-variables or ask your own question.