N
none
While trying to ping an NTP server (it was nist1-dc.WiTime.net or
nist1-ny.WiTime.net), I accidentally typed "cmd ping %NTPServerURL% in
the command line. This resulted in an error message scrolling across
the command line window non-stop. I killed the command line window by
pressing the X symbol at the top right of the window, and did not
receive any message about killing a running process. Now this happens:
I go to "Start > Run" and type in "cmd," I get an "Open with" prompt
window that asks me to
"Choose the program you want to use to open this file:
File: cmd"
I've used the "Browse" button to locate the Windows Command Processor,
but I have to select it from the list of "Program." The "Always use the
selected program to open this kind of file" check box is grayed out. I
don't even know why Windows has decided cmd is a file to be opened by an
external application.
This problem only occurs on one user account. On another user account,
"Start > Run > cmd" still opens up a command line window. Is this a
file association problem? Can I fix it via the Registry? Thanks.
nist1-ny.WiTime.net), I accidentally typed "cmd ping %NTPServerURL% in
the command line. This resulted in an error message scrolling across
the command line window non-stop. I killed the command line window by
pressing the X symbol at the top right of the window, and did not
receive any message about killing a running process. Now this happens:
I go to "Start > Run" and type in "cmd," I get an "Open with" prompt
window that asks me to
"Choose the program you want to use to open this file:
File: cmd"
I've used the "Browse" button to locate the Windows Command Processor,
but I have to select it from the list of "Program." The "Always use the
selected program to open this kind of file" check box is grayed out. I
don't even know why Windows has decided cmd is a file to be opened by an
external application.
This problem only occurs on one user account. On another user account,
"Start > Run > cmd" still opens up a command line window. Is this a
file association problem? Can I fix it via the Registry? Thanks.