Environment variables missing and can't open advanced system settings
Hi all, I'm using a windows 7 32 bit system and have had this problem for several weeks. The problem started after I installed a GTK+ 2.6 file (gtk-win32-2.6.10-rc1) that messed up my environment variables (I was trying to get this calculator emulator program to work http://lpg.ticalc.org/prj_tiemu/win32.html). I have since uninstalled and deleted that file but it didn't help. Now I have many problems. First, I am unable to install any new programs. This includes updating firefox, adobe, and microsoft update, etc. Also, certain windows accessories programs such as calculator, command prompt, notepad, paint, etc don't have the normal icon anymore and don't do anything when I click on them. Also system restore and backup don't run either, when I click on the icon under the program list nothing happens. I also cannot access the advanced system settings after opening system properties, I get the error saying "Windows cannot find '%windir%\system32\systempropertiesadvanced.exe'. Make sure you typed the name correctly, and then try again." Also, after using the computer for a while ~1hr, on my desktop it says in the bottom right hand corner that my copy of windows might not be authentic (which is wrong since I bought the os from my school). When I go to check the windows activation settings under system properties it says "status not available" and "Product ID: Not Available". I think it is definitely a environment problem and when I run cmd and type echo %PATH% I just get a single semicolon with nothing else. After searching for answers I found many people with the same problem but no solutions. How do you add the default environments back in (C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;) when you can't access the edit function under advanced settings? In trying to find a way to do this through a command prompt I discovered that typing regedit only runs when I'm in safe mode and not under normal startup. I get the error: "C:\Windows\regedit.exe The system could not find the environment option that was entered." I tried to run system file checker but it always had errors. And as I mentioned earlier system restore and backup will not run since they can't find the environment. I really think a solution would be to add back in the default environment variables, but I don't know how without using the advanced settings. I would really like to find a solution to this so I won't have to reinstall windows. Right now, the computer runs fine, but at some point I'm going to want to install a new program or at least update my current ones (esp windows). Thanks for the help.
March 22nd, 2011 5:30am

Update -- I was able to enter the default environments back in to the system variable path while running under safe mode. However this only solved a few of my problems. While in safe mode I was able to update firefox, thunderbird, and adobe, but I still can't install new programs or update windows and I still have the same errors when trying to access windows applications (such as calculator) and advanced system properties. Now when I type echo %path% I get the default environments, but I still have the same errors about being unable to run things.
Free Windows Admin Tool Kit Click here and download it now
March 22nd, 2011 8:42pm

Hi, please try to perform an in-place upgrade: http://support.microsoft.com/kb/2255099 Seven
March 24th, 2011 6:27am

So I was looking for a more elegant solution, but I guess a repair install is my only option. Unfortunately when I put in the installation dvd and clicked on setup.exe, I was greeted with the following: "D:\setup.exe The system could not find the environment option that was entered." Foiled again. What is strange is that I can browse through all the files and folders of the installation disc, but whenever I try to run an executable it doesn't work. Also, if I load in safe mode, the installation runs fine. However, you can't do a in-place upgrade from safe mode so again I'm stuck.
Free Windows Admin Tool Kit Click here and download it now
March 27th, 2011 11:03pm

I made a bootable usb key with the installation and also tried mounting an iso of the win7 installation dvd. Same results when I tried to run setup.exe, "The system could not find the environment option that was entered." Anyone know what is going on?
March 28th, 2011 12:30am

In case it is helpful, I tried running sfc several more times from a command prompt at boot through the win7 dvd. I kept getting the same result, "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log." I'm not really sure what the log file says, but it always stopped almost immediately after finishing the verify portion of the program. It seems to have a problem with a file called encdec.dll. Here's what it says at the end of the file when it begins the repair part: CSI 00000668 [SR] Repairing 1 components CSI 00000669 [SR] Beginning Verify and Repair transaction CSI 0000066a Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-tvencdec_31bf3856ad364e35_6.1.7600.16385_none_e04e6c93efba3643\EncDec.dll do not match actual file [l:20{10}]"EncDec.dll" : Found: {l:32 b:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=} Expected: {l:32 b:SBvRwpCATs3ooB52rDP3Lg1RjkSzJL9/yb61m7wtDvc=} CSI 0000066b [SR] Cannot repair member file [l:20{10}]"EncDec.dll" of Microsoft-Windows-TVEncDec, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch CSI 0000066c Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-tvencdec_31bf3856ad364e35_6.1.7600.16385_none_e04e6c93efba3643\EncDec.dll do not match actual file [l:20{10}]"EncDec.dll" : Found: {l:32 b:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=} Expected: {l:32 b:SBvRwpCATs3ooB52rDP3Lg1RjkSzJL9/yb61m7wtDvc=} 0000066d [SR] Cannot repair member file [l:20{10}]"EncDec.dll" of Microsoft-Windows-TVEncDec, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch CSI 0000066e [SR] This component was referenced by [l:238{119}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~x86~~6.1.7600.16385.Microsoft-Windows-Client-Features-Update" CSI 0000066f Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-tvencdec_31bf3856ad364e35_6.1.7600.16385_none_e04e6c93efba3643\EncDec.dll do not match actual file [l:20{10}]"EncDec.dll" : Found: {l:32 b:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=} Expected: {l:32 b:SBvRwpCATs3ooB52rDP3Lg1RjkSzJL9/yb61m7wtDvc=} CSI 00000670 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"EncDec.dll"; source file in store is also corrupted CSI 00000671 Repair results created: CSI 00000672 [SR] Repair complete Not sure what all of this means. Maybe someone does. If you want the rest of the log file just let me know and I can email it or post it somewhere online. Thanks
Free Windows Admin Tool Kit Click here and download it now
March 28th, 2011 4:26am

Not sure what all of this means. Maybe someone does. It has been my overwhelming experience that they don't. Knowledge about Windows settings and the default exploitabilities and vulnerabilities that come courtesy of every installation (guaranteed if your installation was an "unattended" one - not that you'd ever know, of course, until those guarantees arrive)...appears basically limited to non-technical users who have been subjected to the unpleasantness. Everything I have learned in 9 weeks from illiteracy to this point has been courtesy of non-'expert' users like yourself, who learn the very difficult way. The experts know very little, at least this has been my experience. Especially the paid ones. FWIW and surely not much, I'm having a semi-related issue. I had some system environment variables which are not default by any means, but I cannot delete them even with BUILTIN Adminstrator login. Just earlier, I deleted an unknown .dll with access to my kernel, which BUILTIN Administrator could not delete, but for which I found a nifty workaround involving adding a registry key allowing Administrators to remote delete registry settings that console administrators could not. The sheer ludicrous nature of that reality, sums up everything about Microsoft's approach to security. The endpoint users are dirt and must be controlled by the remote powers, with their Actively signed but not quite as actively verified (to ensure endpoint security) silent deployed code. It's almost criminal, that home users don't realise how their Default Windows settings are packaged by Microsoft almost disturbingly conveniently, for remote access. I know if I reboot, I'm facing a reinstall. I would have saved time, had I done that immediately, rather than look for answers from the 'experts'. Oh when oh when will I ever learn. gl
April 21st, 2011 2:17am

Update -- I was able to enter the default environments back in to the system variable path while running under safe mode. However this only solved a few of my problems. While in safe mode I was able to update firefox, thunderbird, and adobe, but I still can't install new programs or update windows and I still have the same errors when trying to access windows applications (such as calculator) and advanced system properties. Now when I type echo %path% I get the default environments, but I still have the same errors about being unable to run things. See if fixing the %windir% path helps. In the Environment Variables window, double-click "windir" and set its value data as follows: %SystemRoot% Ramesh Srinivasan | The Winhelponline Blog Microsoft MVP, Windows Desktop Experience
Free Windows Admin Tool Kit Click here and download it now
April 21st, 2011 10:26am

I was able to enter the default environments back in to the system variable path while running under safe mode. I still can't install new programs or update windows. See if fixing the %windir% path helps. In the Environment Variables window, double-click "windir" and set its value data as follows: %SystemRoot% I appreciate that your suggestion may help (or give the illusion of), but how you could POSSIBLY think your suggestion could be the Answer? You know more than the coders who coded in the Default settings? You know something they don't? You're pretending to. Please read what the OP wrote. How could adjusting the default environment variables ever be the answer? It might help, of course it probably wouldn't help at all, if a user shrugs now that "things are working again". Default environment settings are not working. That...is a problem. Change them, the Windows coders who set Default settings for a reason, they don't have a clue, not compared to you. That's your Answer? %SystemRoot% - who's system? Yours? Perhaps you'd explain why you'd suggest a change in system environment settings from their Defaults, without bothering to explain why his Default system environment settings require changing in the first place.
May 8th, 2011 10:58am

I was able to enter the default environments back in to the system variable path while running under safe mode. I still can't install new programs or update windows. See if fixing the %windir% path helps. In the Environment Variables window, double-click "windir" and set its value data as follows: %SystemRoot% I appreciate that your suggestion may help (or give the illusion of), but how you could POSSIBLY think your suggestion could be the Answer? You know more than the coders who coded in the Default settings? You know something they don't? You're pretending to. Please read what the OP wrote. How could adjusting the default environment variables ever be the answer? It might help, of course it probably wouldn't help at all, if a user shrugs now that "things are working again". Default environment settings are not working. That...is a problem. Change them, the Windows coders who set Default settings for a reason, they don't have a clue, not compared to you. That's your Answer? %SystemRoot% - who's system? Yours? Perhaps you'd explain why you'd suggest a change in system environment settings from their Defaults, without bothering to explain why his Default system environment settings require changing in the first place. Who asked to modify the defaults? Are you saying that %SystemRoot% is not the default value for WinDir variable? Regardless of your rants, the above *is* my proposed solution.Ramesh Srinivasan | The Winhelponline Blog Microsoft MVP, Windows Desktop Experience
Free Windows Admin Tool Kit Click here and download it now
May 8th, 2011 12:33pm

I was able to enter the default environments back in to the system variable path while running under safe mode. I still can't install new programs or update windows. See if fixing the %windir% path helps. In the Environment Variables window, double-click "windir" and set its value data as follows: %SystemRoot% Please read what the OP wrote. How could adjusting the default environment variables ever be the Answer? Who asked to modify the defaults? Are you saying that %SystemRoot% is not the default value for WinDir variable? Regardless of your rants, the above *is* my proposed solution. No. You're the one who claims %SystemRoot% is what the OP's Default system environment variable should be. The OP seems fairly bright, and quite clearly stated re-entered the Default values. You claim he's wrong, but provide no supporting evidence. So, although I'm capable of ranting, warranted questions pointing out what appear to be glaring pecularities and stunning oversight (at best), and some pretty unpleasant stuff (at worse)...is never ranting. My questions are valid, politely presented, and you are compelled to provide answers to them. If I'm wrong, I will apologise. But we shouldn't even be needing to discuss this. You should have provided supporting evidence for your claim that the OP's default values are incorrect. And I know nothing, except that this industry's experts don't like to answer warranted, direct, polite if somewhat uncomfortable, questions. And that finding the answers to those questions is like pulling teeth. The onus of proof is on you. You have claimed a the OP's value is incorrect, and stated a correct value. For a pretty important environment variable. You either know this for a fact, which means you're too lazy to provide the requisite URL....or you don't really know at all, but you're acting as as if you do. And that's a bit fraudulent. Am I missing a third alternative? I cannot see one. Either way, it's my personal opinion that you should provide some basic supporting evidence - so I ask again, can you please provide the requisite link, in support of your claim? Or...are you saying you cannot? Or can't be bothered? But that we should trust you, regardless?
May 8th, 2011 3:13pm

Who asked to modify the defaults? Are you saying that %SystemRoot% is not the default value for WinDir variable? Regardless of your rants, the above *is* my proposed solution. No. You're the one who claims %SystemRoot% is what the OP's Default system environment variable should be. The OP seems fairly bright, and quite clearly stated re-entered the Default values. You claim he's wrong, but provide no supporting evidence. So, although I'm capable of ranting, warranted questions pointing out what appear to be glaring pecularities and stunning oversight (at best), and some pretty unpleasant stuff (at worse)...is never ranting. My questions are valid, politely presented, and you are compelled to provide answers to them. If I'm wrong, I will apologise. But we shouldn't even be needing to discuss this. You should have provided supporting evidence for your claim that the OP's default values are incorrect. And I know nothing, except that this industry's experts don't like to answer warranted, direct, polite if somewhat uncomfortable, questions. And that finding the answers to those questions is like pulling teeth. The onus of proof is on you. You have claimed a the OP's value is incorrect, and stated a correct value. For a pretty important environment variable. You either know this for a fact, which means you're too lazy to provide the requisite URL....or you don't really know at all, but you're acting as as if you do. And that's a bit fraudulent. Am I missing a third alternative? I cannot see one. Either way, it's my personal opinion that you should provide some basic supporting evidence - so I ask again, can you please provide the requisite link, in support of your claim? Or...are you saying you cannot? Or can't be bothered? But that we should trust you, regardless? >> And that's a bit fraudulent. Pls mind your words. You seem to have no knowledge on things, and I'd advise any such person to wait and watch. I haven't said "OP's value is incorrect," i said "OP's value could be incorrect" so resetting to defaults could help. Ramesh Srinivasan | The Winhelponline Blog Microsoft MVP, Windows Desktop Experience
Free Windows Admin Tool Kit Click here and download it now
May 8th, 2011 4:34pm

Who asked to modify the defaults? Are you saying that %SystemRoot% is not the default value for WinDir variable? Regardless of your rants, the above *is* my proposed solution. You have claimed a the OP's value is incorrect, and stated a correct value. For a pretty important environment variable. You either know this for a fact, which means you're too lazy to provide the requisite URL....or you don't really know at all, but you're acting as as if you do. And that's a bit fraudulent. Am I missing a third alternative? >> And that's a bit fraudulent. Pls mind your words. You seem to have no knowledge on things, and I'd advise any such person to wait and watch. I haven't said "OP's value is incorrect," i said "OP's value could be incorrect" so resetting to defaults could help. That's the whole point though, isn't it? No one knows the correct defaults, because Microsoft doesn't supply them (I am a professional researcher, and Microsoft...doesn't supply what is impossibly standard and generic information which thousands of users are asking on forums). Why? Because Microsoft doesn't supply that information. Why? One would have to speculate, because Microsoft doesn't supply that information either. One theory - a rather concerning one - is that Microsoft is very happy for confusion to reign. That way, everyone can speak with Authority on answers they cannot have possible authority to claim. Because Microsoft doesn't supply that information. I was being facetious when I asked if %SystemRoot% was your system, but I've read for another 4 hours (to go with multiple hours of frustration a month ago on this very unique topic); and - unbelievably - I'm even more confused than 7 hours of reading ago. What I'm not confused about, is that there is a BIG problem. %SystemRoot% is indeed, a value that will get the Home User's computer working again. Who's system? = an incredibly more poignant question than I realised when I asked it. And if you don't know who's system, and I have to assume you don't, or you would have clarified it when I asked...then to present it as THE ANSWER is a little bit fraudulent, and I'll kindly thank you to watch your words, please. Because I'm trying to make incredibly value points, incredibly politely. And whilst some people would seek to score cheap points by focusing on your very correct reversing of history, I thank you instead. It was the right thing to do. Rewriting history, I don't mind so much. As long as we're moving in the direction of what is Right and Correct. It's better than the normal abuse my polite points invoke, from people who are out and out frauds, rather than merely guilty of nothing more than trying to help, in a situation where not knowing what the values actually mean, could hurt a lot more than help. Of course, that's not your fault, not knowing... MICROSOFT DOESN'T SUPPLY THAT INFORMATION. With any luck, they'll "recognise" both, and many more values, as acceptable. Their choice of term, RECOGNISE their own values, on the only inadequately ridiculous confusing-rather-than-clarifying official page I could find.
May 11th, 2011 4:10am

Who asked to modify the defaults? Are you saying that %SystemRoot% is not the default value for WinDir variable? You have claimed a the OP's value is incorrect, and stated a correct value. For a pretty important environment variable. You either know this for a fact, which means you're too lazy to provide the requisite URL....or you don't really know at all, but you're acting as as if you do. And that's a bit fraudulent. Am I missing a third alternative? Pls mind your words. You seem to have no knowledge on things, and I'd advise any such person to wait and watch. I haven't said "OP's value is incorrect," i said "OP's value could be incorrect" so resetting to defaults could help. That's the whole point though, isn't it? No one knows the correct defaults, because Microsoft doesn't supply them (I am a professional researcher, and Microsoft...doesn't supply what is impossibly standard and generic information which thousands of users are asking on forums). Why? Because Microsoft doesn't supply that information. Why? One would have to speculate, because Microsoft doesn't supply that information either. One theory - a rather concerning one - is that Microsoft is very happy for confusion to reign. That way, everyone can speak with Authority on answers they cannot have possible authority to claim. Because Microsoft doesn't supply that information. %SystemRoot% is indeed, a value that will get the Home User's computer working again. Who's system? = an incredibly more poignant question than I realised when I asked it. There can only ever be one Default value. If the system legitimately is turned into an Endpoint, then the Default value CHANGES. It does not get added to a list of correct - multiple - defaults. And therein lies the dirty reason for all the secrecy and ambiguity and confusion. There is only ever one reason for secrecy, ambiguity and confusion = it serves someone's interests. Who's? You tell me. I'm not Sherlock Holmes, but I fail to see how he wouldn't look at the entity responsible for creating that secrecy, ambiguity and confusion, with raised eyebrows. This is my system, as it stands presently. 3 months after I asked these questions and was dismissed with scorn by 'experts' who are IGNORANT, and yet speak with AUTHORITY. http://i.imgur.com/MIfA2.png Look at the command lines. My default system environment variable is %windir% - at least, it should be. But that wouldn't allow %systemroot% command lines; or would it? Heck if I know. AND it's abundantly clear, NEITHER DO YOU. Our ignorance is neither our 'fault', though it's fraudulent to pretend otherwise. Only one of us is pretending, otherwise. But I didn't need this thread to know that you cannot possibly know what you're claiming to be an authority on. How did I know this, when I know almost NOTHING? Well, it's really simple, actually.... MICROSOFT DO NOT SUPPLY THAT INFORMATION.
Free Windows Admin Tool Kit Click here and download it now
May 12th, 2011 10:02am

um..i went to safe mode then i jus restore to an earlier point...worked for me..i had the same problem
May 19th, 2011 1:22pm

Possible new answer for this problem! Somebody else has proposed that this is related to the PATH environment variable being excessively long... I checked mine, and there was a bunch of duplicated information in it, and I'm now crossing my fingers and getting ready to reboot. We still need to reboot, I guess... I haven't had to play with environment variables since Windows NT! Would have thought that the reboot wouldn't be neccessary, but the fix isn't working, yet... will check back in and let you know how it works out! --UPDATE! Reboot not required! I can now launch SystemPropertiesAdvanced.exe and other similar system utilities without the error message about windir. I will propose this as the solution to this thread!
Free Windows Admin Tool Kit Click here and download it now
August 4th, 2011 5:53pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics