System Path variables not passed to NEW CMD prompt.


  1. bds2006
    Posts : 2
    Windows 7 Professional 64 bit
       New #1

    System Path variables not passed to NEW CMD prompt.


    Random problem or when I install new program or uninstall a program:
    As I use my pc throughout the day, any new CMD prompts will have a path=(null) and as such I can't use standard windows commands. If I try to go to 'My Computer', 'Properties',... to check on the value of the 'PATH' environment, I get an error indicating that it can't find the program. %windir% value is also not set.
    However, when I go to REGEDIT and drill down to the 'session manager' I see that the PATH and WINDIR variables are there AND have the correct values.
    At this point the only way I know how to get my PC working correctly again is to reboot, then all is good until it happens again.
    I thought that by putting procmon on and running it to monitor PATH and WINDIR variable via registry change, I would somehow see what was causing my system to lose those variables. Well, those variables are not getting changed. duh.
    Something is blocking my system from accessing THOSE registry variables when creating a new COMMAND or CMD prompt and without the WINDIR some of apps/windows programs are not found type of errors.
    I do have SP1 installed.
    I really don't know when it started happening so backing out updates is not something I want to do. My system doesn't indicate any type of warnings/errors in the event logs. If I install/uninstall an application (simple or big apps) then it messes up. Throughout the day as I use apps and close down apps, it will randomly happen. I tested specific apps by opening, running and closing but the issue didn't happen. I tried testing by opening, running and closing multiple applications at the same time. Still everything fine.
    Just randomly when I open a CMD prompt that it is messed up and then I know to reboot to get it working correctly again.
      My Computer
    Quote Quote

  3. Callender
    Posts : 4,776
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
       New #2

    System Variables


    Here's a suggestion but it's really a shot in the dark.

    Perhaps check file paths in "system variables" to see if the correct ones exist.

    Start> Run then type sysdm.cpl and press enter. On the advanced tab check that these entries still exist and create them if they don't.

    Variable = windir Value = %SystemRoot%

    Variable = ComSpec Value = %SystemRoot%\system32\cmd.exe

    Like I said - it's just a guess from me!
      My Computer
    Quote Quote

  4. bds2006
    Posts : 2
    Windows 7 Professional 64 bit
    Thread Starter
       New #3

    Just randomly hit again...


    PATH and COMSPEC are both there and in place but when i open a new cmd/command the PATH is empty and windir is not set as well.
    after i ran the sysdm.cpl clicked ok just to see if it would reset everything. no luck still not set under new cmd/command.
      My Computer
    Quote Quote

 

  Related Discussions
Hi. Is it safe to delete the entry shown? I don't see a folder anywhere on C: (windows partition) named BVTBin even with super-hidden files shown. I'm asking because I don't understand why the entry exists.
Whenever I launch the Command Prompt, It says "The system cannot find the path specified" under the Copyright Label on the Command Line. 220584 Can someone please tell me how to fix this?
i was editing the path in environment variables after installing jdk-6.0 when i accidentally deleted it...is there a way to recover it? or if not , can somebody tell me what was the default variable path was that? i'm using windows 7 starter...and a toshiba laptop.....please i really need help...
I was editing the command prompt path and my command prompt stopped working. Here's what the path is: %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShel l\v1.0\ I tried a dozen different paths after I accidentally deleted it when editing...
Subject says it all really. If I use an environment variable on the commandline in a path it apppears to stop path completion from working correctly. In the example below on the last line I hit TAB after typing "dir %userprofile%\do" and instead of the path completion acting on the expanded...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 14:42.
Find Us