Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.os.windows-10 > #183961 > unrolled thread

No CMD

Back to article view | Back to alt.comp.os.windows-10

Contents

  No CMD Ed Cryer <ed@somewhere.in.the.uk> - 2025-04-25 10:36 +0100
    Re: No CMD Paul <nospam@needed.invalid> - 2025-04-25 06:31 -0400
    Re: No CMD VanguardLH <V@nguard.LH> - 2025-04-25 06:05 -0500
      Re: No CMD Ed Cryer <ed@somewhere.in.the.uk> - 2025-04-25 14:42 +0100
        Re: No CMD MikeS <MikeS@fred.com> - 2025-04-25 15:47 +0100
        Re: No CMD Ed Cryer <ed@somewhere.in.the.uk> - 2025-04-25 16:16 +0100
          Re: No CMD VanguardLH <V@nguard.LH> - 2025-04-25 12:53 -0500
            Re: No CMD Ed Cryer <ed@somewhere.in.the.uk> - 2025-04-25 20:05 +0100
              Re: No CMD VanguardLH <V@nguard.LH> - 2025-04-25 20:53 -0500
                Re: No CMD Ed Cryer <ed@somewhere.in.the.uk> - 2025-04-26 12:00 +0100
                  Re: No CMD Frank Slootweg <this@ddress.is.invalid> - 2025-04-26 15:01 +0000
                    Change of Subject (was: No CMD) VanguardLH <V@nguard.LH> - 2025-04-26 18:50 -0500
                      Re: Change of Subject Hank Rogers <Hank@nospam.invalid> - 2025-04-26 19:13 -0500
                        Re: Change of Subject VanguardLH <V@nguard.LH> - 2025-04-26 19:40 -0500
                      Re: Change of Subject Daniel70 <daniel47@eternal-september.org> - 2025-05-03 22:58 +1000
                        Re: Change of Subject VanguardLH <V@nguard.LH> - 2025-05-03 09:47 -0500
                  Re: No CMD Stan Brown <the_stan_brown@fastmail.fm> - 2025-04-26 15:48 -0700
      Re: No CMD "...winston" <winstonmvp@gmail.com> - 2025-04-25 11:12 -0400
        Re: No CMD Ed Cryer <ed@somewhere.in.the.uk> - 2025-04-25 17:19 +0100
    SOLVED Ed Cryer <ed@somewhere.in.the.uk> - 2025-04-25 17:40 +0100
      Re: SOLVED Paul <nospam@needed.invalid> - 2025-04-25 16:19 -0400
      Re: SOLVED VanguardLH <V@nguard.LH> - 2025-04-25 22:19 -0500
      Re: SOLVED Ed Cryer <ed@somewhere.in.the.uk> - 2025-05-13 18:47 +0100
    Re: No CMD Stan Brown <the_stan_brown@fastmail.fm> - 2025-04-25 13:14 -0700
      Re: No CMD Char Jackson <none@none.invalid> - 2025-04-26 00:14 -0500
        Re: No CMD "R.Wieser" <address@is.invalid> - 2025-04-26 11:02 +0200
          Re: No CMD Char Jackson <none@none.invalid> - 2025-04-26 20:48 -0500
            Re: No CMD "R.Wieser" <address@is.invalid> - 2025-04-27 08:45 +0200
        Re: No CMD Stan Brown <the_stan_brown@fastmail.fm> - 2025-04-26 15:52 -0700
        Re: No CMD VanguardLH <V@nguard.LH> - 2025-04-26 19:36 -0500
          Re: No CMD "R.Wieser" <address@is.invalid> - 2025-04-27 13:12 +0200
            Re: No CMD John <Man@the.keyboard> - 2025-04-28 20:11 +0100
              Re: No CMD "R.Wieser" <address@is.invalid> - 2025-04-28 23:15 +0200

Page 1 of 2  [1] 2  Next page →

#183961 — No CMD

On two of my Win10 systems, I can swap between Powershell and command 
prompt. But on the third there's a most peculiar problem.
Settings/Personalisation/Taskbar has the option to switch between the 
two. When I set it to CMD, CMD appears for a second in a tiny window and 
then disappears. I can't get it to stay put.

I've run DISM and sfc, have the latest 22H2 19045.5796 build.

Ed

[toc] | [next] | [standalone]

#183963

On Fri, 4/25/2025 5:36 AM, Ed Cryer wrote:
> On two of my Win10 systems, I can swap between Powershell and command prompt. But on the third there's a most peculiar problem.
> Settings/Personalisation/Taskbar has the option to switch between the two. When I set it to CMD, CMD appears for a second in a tiny window and then disappears. I can't get it to stay put.
> 
> I've run DISM and sfc, have the latest 22H2 19045.5796 build.
> 
> Ed

Okay, open the Settings, type "Relia" in the search box
and locate the Reliability Monitor. Check the events of
today, and see if anything is recorded for your disappearing
shells. If the entry for the cmd.exe croaking has an error
number, run it through Google and see what the error indicates.
(As long as it is not "Something Happened" of course.)

Another way to look at an error number, is with the
command line error number lookup tool (which you would
have to run on another computer at the moment).

https://www.microsoft.com/en-us/download/details.aspx?id=100432

     Err_6.4.5.exe    File Size: 2.2 MB

There are lots of errors that aren't in there,
like the newly created error numbers.

   Paul

[toc] | [prev] | [next] | [standalone]

#183964

Ed Cryer <ed@somewhere.in.the.uk> wrote:

> On two of my Win10 systems, I can swap between Powershell and command 
> prompt. But on the third there's a most peculiar problem.
> Settings/Personalisation/Taskbar has the option to switch between the 
> two. When I set it to CMD, CMD appears for a second in a tiny window and 
> then disappears. I can't get it to stay put.
> 
> I've run DISM and sfc, have the latest 22H2 19045.5796 build.

Not sure what config wizard setting to which you refer.  When I
right-click on a blank area of the Taskbar, click on Taskbar Settings in
the context menu, I don't see a toggle choosing between Command or
Powershell.  I see:

  Replace Command Prompt with Windows PowerShell in the menu 
  when I right-click the start button or press Windows key+X.

The only times I start cmd.exe this way is when reading some online help
file on starting cmd.exe.  I use a shortcut to cmd.exe, and the shortcut
is in a toolbar in the Taskbar configured to run with admin privs (so
the UAC prompt appears).  I can also click on the Start menu button, and
enter "cmd" which shows Command Prompt as a match.  The first match
opens in non-admin mode.  Another match let me click on its rightward
chevron to get more choices, like Open or Run as administrator.

How are you starting cmd.exe?  If using a shortcut, make sure to add the
/k command-line argument to keep open the console window, like:

cmd.exe /k

Normally, when cmd is done running whatever your told it to run, the
console window closes, because the cmd shell unloads after running
whatever you told cmd.exe to run.  You want to keep the shell loaded, so
add /k switch.  Also check which cmd.exe the shortcut specifies.  Have
it point at the one under the system32 folder.

In Task Manager, check if any instances of cmd.exe are running.  If so,
kill them.  You don't say how you run cmd.  Try the following:

- Bring up the Task Manager (Ctrl+Shift+Esc).  
    o Select the Details tab.
    o Click on the Name column header to sort by process name.
    o Scroll down to where the C's would start.
    o Check there are no running instances of cmd.exe
- Run cmd.exe:
    o Bring up the Run dialog (Win+R).
    o Or, use the File -> Run new task menu in Task Manager.
- Enter: cmd.exe.  Include the .exe extension.  Click OK.

See a console window now?  
Did the console window stay open?
In Task Manager, did you see cmd.exe show up?

If you saw cmd.exe show up in Task Manager, but only temporarily, and
its console window did not stay open, do the above again; however,
instead of relying on pathing to find the cmd.exe executable file, enter
the full path to the executable: c:\windows\system32\cmd.exe.

Look in Event Viewer to see if an error got reported when trying to load
cmd.exe.

cmd.exe is one of the programs often attacked by malware to prevent the
user from have a low-level tool to undo the malware.  Run a full scan
using your anti-virus software.  If using Windows Defender, see:

https://learn.microsoft.com/en-us/defender-endpoint/command-line-arguments-microsoft-defender-antivirus

and run:

mpcmdrun.exe -scan -scantype 2

Defender's manual scan is slow, so it will take a long time to complete.
If its console window disappears after it completes, so you don't get to
see its output, pipe stdout into a file to open in Notepad, like:

mpcmdrun.exe -scan -scantype 2 > %temp%\mpscan.txt & notepad %temp%\mpscan.txt

[toc] | [prev] | [next] | [standalone]

#183971

VanguardLH wrote:
> mpcmdrun.exe -scan -scantype 2 > %temp%\mpscan.txt & notepad %temp%\mpscan.txt

Thanks for jumping to help.

No sign of CMD in Task Manager, nor in Reliability Monitor.
The shortcut points to the version in system32, which I tried by 
clicking on it in situ; same brief flash.
Cmd.exe and cmd.exe/k produce the same phenomenon.
I've run DISM and sfc /scannow again, plus done a full chkdsk c: /f /r.
I'm now running a full Windows Defender scan; fingers crossed.

Ed

[toc] | [prev] | [next] | [standalone]

#183975

On 25/04/2025 14:42, Ed Cryer wrote:
> VanguardLH wrote:
>> mpcmdrun.exe -scan -scantype 2 > %temp%\mpscan.txt & notepad 
>> %temp%\mpscan.txt
> 
> Thanks for jumping to help.
> 
> No sign of CMD in Task Manager, nor in Reliability Monitor.
> The shortcut points to the version in system32, which I tried by 
> clicking on it in situ; same brief flash.
> Cmd.exe and cmd.exe/k produce the same phenomenon.
> I've run DISM and sfc /scannow again, plus done a full chkdsk c: /f /r.
> I'm now running a full Windows Defender scan; fingers crossed.
> 
> Ed
> 
There are often multiple copies of cmd.exe in the Windows folder. Try 
another one, eg C:\Windows\SysWOW64\cmd.exe

[toc] | [prev] | [next] | [standalone]

#183977

Ed Cryer wrote:
> VanguardLH wrote:
>> mpcmdrun.exe -scan -scantype 2 > %temp%\mpscan.txt & notepad %temp% 
>> \mpscan.txt
> 
> Thanks for jumping to help.
> 
> No sign of CMD in Task Manager, nor in Reliability Monitor.
> The shortcut points to the version in system32, which I tried by 
> clicking on it in situ; same brief flash.
> Cmd.exe and cmd.exe/k produce the same phenomenon.
> I've run DISM and sfc /scannow again, plus done a full chkdsk c: /f /r.
> I'm now running a full Windows Defender scan; fingers crossed.
> 
> Ed
> 

Full scan ok. 57 mins. Zero threats found.
No mention of CMD in Event Viewer.
The version of CMD in SysWOW64 has the same disappearing behaviour.

However, I installed Administrator account and it works just fine from 
there. And the file location is the same as my user.

I'm pondering whether to run a full system repair - download Win10 
latest. But there's no sign of any other problem, and this one seems too 
minor to warrant such extensive attention. I can use Powershell, and, in 
case of necessity, CMD in Administrator account.

Ed

[toc] | [prev] | [next] | [standalone]

#183992

Ed Cryer <ed@somewhere.in.the.uk> wrote:

> Ed Cryer wrote:
>> VanguardLH wrote:
>>> mpcmdrun.exe -scan -scantype 2 > %temp%\mpscan.txt & notepad %temp% 
>>> \mpscan.txt
>> 
>> Thanks for jumping to help.
>> 
>> No sign of CMD in Task Manager, nor in Reliability Monitor.
>> The shortcut points to the version in system32, which I tried by 
>> clicking on it in situ; same brief flash.
>> Cmd.exe and cmd.exe/k produce the same phenomenon.
>> I've run DISM and sfc /scannow again, plus done a full chkdsk c: /f /r.
>> I'm now running a full Windows Defender scan; fingers crossed.
>> 
>> Ed
>> 
> 
> Full scan ok. 57 mins. Zero threats found.
> No mention of CMD in Event Viewer.
> The version of CMD in SysWOW64 has the same disappearing behaviour.
> 
> However, I installed Administrator account and it works just fine from 
> there. And the file location is the same as my user.
> 
> I'm pondering whether to run a full system repair - download Win10 
> latest. But there's no sign of any other problem, and this one seems too 
> minor to warrant such extensive attention. I can use Powershell, and, in 
> case of necessity, CMD in Administrator account.
> 
> Ed

winston mentions there might be a window sizing problem.  Possibly the
console window is minimized leaving only its Taskbar button.

In addition, after you run cmd.exe, and the window opens and disappears,
is cmd.exe still listed as a running process in Task Manager?  

Is there still a Taskbar button for cmd.exe?  Or is it the Taskbar
button you see appear and quickly disappear (and never do see the
console window)?

If there is a Taskbar button for cmd.exe's console window, but you don't
see the window, could be it is minimized, or it is offscreen.  Click the
Taskbar button for cmd.exe to make it the active window, hit
Alt+Spacebar to activate its Control Menu, hit M (to select the Move
menu entry), and use the arrow keys to move the window around.  Most
windows still have the Control Menu, but often the "-" at the left end
of the titlebar is not shown.  Alternatively, you can Shift+rightclick
on the Taskbar button to see the Control Menu for that window.

You could also try using Win+arrowkey to move around a window.  Click
the Taskbar button for the program, and use: Win+left to snap the window
to the upper left side of the screen, Win+right to snap to the upper
right side, Win+up to maximize to full screen height, and Win+down to
normalize.  

https://www.howtogeek.com/310/bring-misplaced-off-screen-windows-back-to-your-desktop-keyboard-trick/

Besides the other methods mentioned, it notes using WinLister.  I forgot
I had this tool.  I have most of Nirsoft's tools, and this one, too.
The "Centered Selected Windows" context menu item would snap and resize
those windows to the center of your monitor.

Do you have dual monitors?  For multiple monitors, Win+Shift+left/right
moves the window between monitors.  Win+P gives a menu of where you want
to project the screen.

You say cmd.exe loads okay in a new Windows account.  There is always an
Administrator account.  It is created when you install Windows.  It
prompts you to create another account.  So, I'm not sure what you mean
by you installed an Administrator account when it should've already
existed.  When booting Windows, does it automatically log into your
Windows account (i.e., never ask you which account to use)?  Automatic
login won't show accounts you can log into.

Run netplwiz to see a list of accounts.  For the one called
Administrator, you just created that account, or you just logged into it
for the first time?  For the "User must enter a username ..." option, is
it selected, or not?

Are you using Applocker?

https://learn.microsoft.com/en-us/windows/security/application-security/application-control/app-control-for-business/applocker/applocker-overview
https://www.youtube.com/watch?v=xVVgXnorpvA

Or Software Restriction Policies (SRPs)?

https://learn.microsoft.com/en-us/windows-server/identity/software-restriction-policies/software-restriction-policies
https://www.youtube.com/watch?v=L--wgJJrosY
https://www.tenforums.com/tutorials/124008-use-applocker-allow-block-executable-files-windows-10-a.html

You didn't say which edition of Windows 10 you have.  Home editions
don't have either the gpedit.msc or secpol.msc policy editors.  When I
had a Pro edition, I played with Applocker for a short time, but decided
it was too complicated to bother with, and I didn't need to lockdown my
computer that hard, anyway.  However, if you log into a domain account
it is possible security policies get pushed to your workstation.  You
probably are logging into a local account, but something or someone
could still add registry entries for policies.  According to:

https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/ee844171(v=ws.11)

Applocker settings are stored under:

\HKEY_LOCAL_Machine\Software\Policies\Microsoft\Windows\SrpV2

The key name hints Applocker is the 2nd version of SRP (Software
Restriction Policy).

I've used SRPs in the past to block a program from loading.  I added a
Path rule to specify which .exe I did not want to allow to load.  These
were locally defined by me, not pushed by a domain login.  All policies
are defined in the registry, but SRPs are hash protected.

Local group policies are stored under C:\Windows\System32\GroupPolicy to
get merged into the registry during startup for computer policies or
during logon for user policies.  When using gpedit.msc, you are viewing
what is under C:\Windows\System32\GroupPolicy, not what is currently
loaded in the registry.

SRPs are not applied when booting into Windows safe mode.  Try that and
logging into your account to retest cmd.exe.

https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh994620(v=ws.11)?redirectedfrom=MSDN#if-you-experience-problems-with-applied-policy-settings-restart-windows-in-safe-mode

Microsoft tried to neuter SRPs, but there are hacks to keep it working.
They want you to use Applocker.  But if you used SRPs before, and
upgraded Windows instead of a fresh install, possibly some SRPs survived
into the upgrade.

https://borncity.com/win/2023/02/24/software-restriction-policies-safer-still-possible-under-windows-11-22h2/

3rd-party security software could also effect the same disable/block on
starting programs.

[toc] | [prev] | [next] | [standalone]

#184003

VanguardLH wrote:
> Ed Cryer <ed@somewhere.in.the.uk> wrote:
> 
>> Ed Cryer wrote:
>>> VanguardLH wrote:
>>>> mpcmdrun.exe -scan -scantype 2 > %temp%\mpscan.txt & notepad %temp%
>>>> \mpscan.txt
>>>
>>> Thanks for jumping to help.
>>>
>>> No sign of CMD in Task Manager, nor in Reliability Monitor.
>>> The shortcut points to the version in system32, which I tried by
>>> clicking on it in situ; same brief flash.
>>> Cmd.exe and cmd.exe/k produce the same phenomenon.
>>> I've run DISM and sfc /scannow again, plus done a full chkdsk c: /f /r.
>>> I'm now running a full Windows Defender scan; fingers crossed.
>>>
>>> Ed
>>>
>>
>> Full scan ok. 57 mins. Zero threats found.
>> No mention of CMD in Event Viewer.
>> The version of CMD in SysWOW64 has the same disappearing behaviour.
>>
>> However, I installed Administrator account and it works just fine from
>> there. And the file location is the same as my user.
>>
>> I'm pondering whether to run a full system repair - download Win10
>> latest. But there's no sign of any other problem, and this one seems too
>> minor to warrant such extensive attention. I can use Powershell, and, in
>> case of necessity, CMD in Administrator account.
>>
>> Ed
> 
> winston mentions there might be a window sizing problem.  Possibly the
> console window is minimized leaving only its Taskbar button.
> 
> In addition, after you run cmd.exe, and the window opens and disappears,
> is cmd.exe still listed as a running process in Task Manager?
> 
> Is there still a Taskbar button for cmd.exe?  Or is it the Taskbar
> button you see appear and quickly disappear (and never do see the
> console window)?
> 
> If there is a Taskbar button for cmd.exe's console window, but you don't
> see the window, could be it is minimized, or it is offscreen.  Click the
> Taskbar button for cmd.exe to make it the active window, hit
> Alt+Spacebar to activate its Control Menu, hit M (to select the Move
> menu entry), and use the arrow keys to move the window around.  Most
> windows still have the Control Menu, but often the "-" at the left end
> of the titlebar is not shown.  Alternatively, you can Shift+rightclick
> on the Taskbar button to see the Control Menu for that window.
> 
> You could also try using Win+arrowkey to move around a window.  Click
> the Taskbar button for the program, and use: Win+left to snap the window
> to the upper left side of the screen, Win+right to snap to the upper
> right side, Win+up to maximize to full screen height, and Win+down to
> normalize.
> 
> https://www.howtogeek.com/310/bring-misplaced-off-screen-windows-back-to-your-desktop-keyboard-trick/
> 
> Besides the other methods mentioned, it notes using WinLister.  I forgot
> I had this tool.  I have most of Nirsoft's tools, and this one, too.
> The "Centered Selected Windows" context menu item would snap and resize
> those windows to the center of your monitor.
> 
> Do you have dual monitors?  For multiple monitors, Win+Shift+left/right
> moves the window between monitors.  Win+P gives a menu of where you want
> to project the screen.
> 
> You say cmd.exe loads okay in a new Windows account.  There is always an
> Administrator account.  It is created when you install Windows.  It
> prompts you to create another account.  So, I'm not sure what you mean
> by you installed an Administrator account when it should've already
> existed.  When booting Windows, does it automatically log into your
> Windows account (i.e., never ask you which account to use)?  Automatic
> login won't show accounts you can log into.
> 
> Run netplwiz to see a list of accounts.  For the one called
> Administrator, you just created that account, or you just logged into it
> for the first time?  For the "User must enter a username ..." option, is
> it selected, or not?
> 
> Are you using Applocker?
> 
> https://learn.microsoft.com/en-us/windows/security/application-security/application-control/app-control-for-business/applocker/applocker-overview
> https://www.youtube.com/watch?v=xVVgXnorpvA
> 
> Or Software Restriction Policies (SRPs)?
> 
> https://learn.microsoft.com/en-us/windows-server/identity/software-restriction-policies/software-restriction-policies
> https://www.youtube.com/watch?v=L--wgJJrosY
> https://www.tenforums.com/tutorials/124008-use-applocker-allow-block-executable-files-windows-10-a.html
> 
> You didn't say which edition of Windows 10 you have.  Home editions
> don't have either the gpedit.msc or secpol.msc policy editors.  When I
> had a Pro edition, I played with Applocker for a short time, but decided
> it was too complicated to bother with, and I didn't need to lockdown my
> computer that hard, anyway.  However, if you log into a domain account
> it is possible security policies get pushed to your workstation.  You
> probably are logging into a local account, but something or someone
> could still add registry entries for policies.  According to:
> 
> https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/ee844171(v=ws.11)
> 
> Applocker settings are stored under:
> 
> \HKEY_LOCAL_Machine\Software\Policies\Microsoft\Windows\SrpV2
> 
> The key name hints Applocker is the 2nd version of SRP (Software
> Restriction Policy).
> 
> I've used SRPs in the past to block a program from loading.  I added a
> Path rule to specify which .exe I did not want to allow to load.  These
> were locally defined by me, not pushed by a domain login.  All policies
> are defined in the registry, but SRPs are hash protected.
> 
> Local group policies are stored under C:\Windows\System32\GroupPolicy to
> get merged into the registry during startup for computer policies or
> during logon for user policies.  When using gpedit.msc, you are viewing
> what is under C:\Windows\System32\GroupPolicy, not what is currently
> loaded in the registry.
> 
> SRPs are not applied when booting into Windows safe mode.  Try that and
> logging into your account to retest cmd.exe.
> 
> https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh994620(v=ws.11)?redirectedfrom=MSDN#if-you-experience-problems-with-applied-policy-settings-restart-windows-in-safe-mode
> 
> Microsoft tried to neuter SRPs, but there are hacks to keep it working.
> They want you to use Applocker.  But if you used SRPs before, and
> upgraded Windows instead of a fresh install, possibly some SRPs survived
> into the upgrade.
> 
> https://borncity.com/win/2023/02/24/software-restriction-policies-safer-still-possible-under-windows-11-22h2/
> 
> 3rd-party security software could also effect the same disable/block on
> starting programs.

Have you seen my SOLVED posting in this thread?
It worked for me. I found it in a Google search for this problem.
I'm no expert on Win10, but I should think that the things done therein 
should reveal the underlying cause to someone who is.

Ed

[toc] | [prev] | [next] | [standalone]

#184036

Ed Cryer <ed@somewhere.in.the.uk> wrote:

> Have you seen my SOLVED posting in this thread?
> It worked for me. I found it in a Google search for this problem.
> I'm no expert on Win10, but I should think that the things done therein 
> should reveal the underlying cause to someone who is.
> 
> Ed

Yep, saw it.  First response was you have a corrupted Windows account.
But I'm not sure that explains why an executable won't run other than
SRPs, Applocker, or something else you run under your Windows account
that blocks execution of some programs.  You said you created the
Administrator account, but it should exist when you install Windows.  It
is a default account.  In fact, it is the only account that has the same
SID (Security Identifier) across all Windows installations.

https://learn.microsoft.com/en-us/windows/security/identity-protection/access-control/local-accounts
"Every computer has an Administrator account (SID S-1-5-domain-500,
display name Administrator)."

When you said you "created" the Administrator account, maybe what you
meant was you got it added to the login screen, so you could pick it
from a list, like you ran "net user administrator /active:yes" in either
a cmd or Powershell shell (with admin privs).  Or, it was the first time
you logged into the Administrator account which then created a profile
folder, and did the initial setup for the account.  Unlikely you created
an account that already existed.  You cannot delete Administrator, but
you can rename it.

The Administrator account should not be used as an everyday account.
You should create another user account to play with.  Because Windows
profiles can get corrupted, and beyond the Administrator account the
setup creates at the start, I create a backup admin-level account.  So,
I end up with Administrator, BkupAdmin, and 1 or more user accounts.

Update:

I have filters that will flag posts to hide them.  I did not see your
"SOLVED" subthread, because one of my filters flags posts that have all
uppercase in the Subject.  One, that is YELLING.  Two, spammers and
trolls are desparate to get attention.  When I switched to a view that
showed ignore-flagged posts, I saw yours.  I'll reply under that
subthread.

[toc] | [prev] | [next] | [standalone]

#184054

VanguardLH wrote:
> Ed Cryer <ed@somewhere.in.the.uk> wrote:
> 
>> Have you seen my SOLVED posting in this thread?
>> It worked for me. I found it in a Google search for this problem.
>> I'm no expert on Win10, but I should think that the things done therein
>> should reveal the underlying cause to someone who is.
>>
>> Ed
> 
> Yep, saw it.  First response was you have a corrupted Windows account.
> But I'm not sure that explains why an executable won't run other than
> SRPs, Applocker, or something else you run under your Windows account
> that blocks execution of some programs.  You said you created the
> Administrator account, but it should exist when you install Windows.  It
> is a default account.  In fact, it is the only account that has the same
> SID (Security Identifier) across all Windows installations.
> 
> https://learn.microsoft.com/en-us/windows/security/identity-protection/access-control/local-accounts
> "Every computer has an Administrator account (SID S-1-5-domain-500,
> display name Administrator)."
> 
> When you said you "created" the Administrator account, maybe what you
> meant was you got it added to the login screen, so you could pick it
> from a list, like you ran "net user administrator /active:yes" in either
> a cmd or Powershell shell (with admin privs).  Or, it was the first time
> you logged into the Administrator account which then created a profile
> folder, and did the initial setup for the account.  Unlikely you created
> an account that already existed.  You cannot delete Administrator, but
> you can rename it.
> 
> The Administrator account should not be used as an everyday account.
> You should create another user account to play with.  Because Windows
> profiles can get corrupted, and beyond the Administrator account the
> setup creates at the start, I create a backup admin-level account.  So,
> I end up with Administrator, BkupAdmin, and 1 or more user accounts.
> 
> Update:
> 
> I have filters that will flag posts to hide them.  I did not see your
> "SOLVED" subthread, because one of my filters flags posts that have all
> uppercase in the Subject.  One, that is YELLING.  Two, spammers and
> trolls are desparate to get attention.  When I switched to a view that
> showed ignore-flagged posts, I saw yours.  I'll reply under that
> subthread.

Hiya man.
It used be standard good netiquette to put "solved" in upper case; in 
Web and Usenet threads. I'm not going to apologise for having done it 
here. Your filtering out of them is your personal affair. I have no 
battle with upper-case abusers because I don't get any.

The Administrator account.
Yes, I think your second theory is correct; it had never been fully set 
up. It took time to initiate it all, with lots of questions to answer.

BTW, rather than create another account as safety backup, I'll stick 
with my regular Macrium images and Windows restore points. They've 
always served me well enough.

See you,  Ed

[toc] | [prev] | [next] | [standalone]

#184062

Ed Cryer <ed@somewhere.in.the.uk> wrote:
> VanguardLH wrote:
[...]

> > Update:
> > 
> > I have filters that will flag posts to hide them.  I did not see your
> > "SOLVED" subthread, because one of my filters flags posts that have all
> > uppercase in the Subject.  One, that is YELLING.  Two, spammers and
> > trolls are desparate to get attention.  When I switched to a view that
> > showed ignore-flagged posts, I saw yours.  I'll reply under that
> > subthread.
> 
> Hiya man.
> It used be standard good netiquette to put "solved" in upper case; in 
> Web and Usenet threads. I'm not going to apologise for having done it 
> here.

  Well, the "standard good netiquette" was/is to *add* 'SOLVED' in the
subject line, not to replace the subject. But you're forgiven! :-)

>       Your filtering out of them is your personal affair. I have no 
> battle with upper-case abusers because I don't get any.

  I have a similar filter, but once a day, I check the actions of the
filter(s), so your 'indiscretion' was easily spotted and undone! :-)

  Anyway, you've gotten us an excuse to nitpick, so thanks for that!

  All the best.

[...]

[toc] | [prev] | [next] | [standalone]

#184089 — Change of Subject (was: No CMD)

Frank Slootweg <this@ddress.is.invalid> wrote:

> Ed Cryer <ed@somewhere.in.the.uk> wrote:
>
>> VanguardLH wrote:
> 
>>> Update:
>>> 
>>> I did not see your "SOLVED" subthread, because one of my filters
>>> flags posts that have all uppercase in the Subject.  
>> 
>> It used be standard good netiquette to put "solved" in upper case; in 
>> Web and Usenet threads. I'm not going to apologise for having done it 
>> here.
> 
> Well, the "standard good netiquette" was/is to *add* 'SOLVED' in the
> subject line, not to replace the subject. But you're forgiven! :-)

Netiquette when modifying the Subject header (which adding SOLVED or
changing to just SOLVED would do) is to show the new Subject header and
append "(was: <originalSubject>)", so here it looked like:

Solved (was: No CMD)

I have also seen:

Solved - No CMD

I don't recall "Solved" was to be all uppercased, but I don't visit all
newsgroups.  Been in Usenet since around 92.  At the height of where I
visited, I used to inhabit 52 newsgroups, but that's waned to 19 now.

If the original Subject was still there, and "SOLVED" had been added,
the Subject would not have been all uppercase: the "o" was lowercase.
Prepending "Solved" would also not have the Subject as all uppercase.
I'll look into my all-uppercase filter to see if I can add an exception
for just "SOLVED"; i.e., Subject starts with "solved" whether upper- or
lowercase, or mix of both; however, that would permit starter posts that
aren't replies, like "SOLVE YOUR DEBT".

[toc] | [prev] | [next] | [standalone]

#184090 — Re: Change of Subject

VanguardLH wrote on 4/26/2025 6:50 PM:
> Frank Slootweg <this@ddress.is.invalid> wrote:
> 
>> Ed Cryer <ed@somewhere.in.the.uk> wrote:
>>
>>> VanguardLH wrote:
>>
>>>> Update:
>>>>
>>>> I did not see your "SOLVED" subthread, because one of my filters
>>>> flags posts that have all uppercase in the Subject.
>>>
>>> It used be standard good netiquette to put "solved" in upper case; in
>>> Web and Usenet threads. I'm not going to apologise for having done it
>>> here.
>>
>> Well, the "standard good netiquette" was/is to *add* 'SOLVED' in the
>> subject line, not to replace the subject. But you're forgiven! :-)
> 
> Netiquette when modifying the Subject header (which adding SOLVED or
> changing to just SOLVED would do) is to show the new Subject header and
> append "(was: <originalSubject>)", so here it looked like:
> 
> Solved (was: No CMD)
> 
> I have also seen:
> 
> Solved - No CMD
> 
> I don't recall "Solved" was to be all uppercased, but I don't visit all
> newsgroups.  Been in Usenet since around 92.  At the height of where I
> visited, I used to inhabit 52 newsgroups, but that's waned to 19 now.
> 
> If the original Subject was still there, and "SOLVED" had been added,
> the Subject would not have been all uppercase: the "o" was lowercase.
> Prepending "Solved" would also not have the Subject as all uppercase.
> I'll look into my all-uppercase filter to see if I can add an exception
> for just "SOLVED"; i.e., Subject starts with "solved" whether upper- or
> lowercase, or mix of both; however, that would permit starter posts that
> aren't replies, like "SOLVE YOUR DEBT".
> 

Here is a forum that might help you and ed.

https://able2know.org/forum/english_grammar/

Many experts there that can nitpick the tiniest of grammar mistakes.

[toc] | [prev] | [next] | [standalone]

#184092 — Re: Change of Subject

Hank Rogers <Hank@nospam.invalid> wrote:

> VanguardLH wrote on 4/26/2025 6:50 PM:
>> Frank Slootweg <this@ddress.is.invalid> wrote:
>> 
>>> Ed Cryer <ed@somewhere.in.the.uk> wrote:
>>>
>>>> VanguardLH wrote:
>>>
>>>>> Update:
>>>>>
>>>>> I did not see your "SOLVED" subthread, because one of my filters
>>>>> flags posts that have all uppercase in the Subject.
>>>>
>>>> It used be standard good netiquette to put "solved" in upper case; in
>>>> Web and Usenet threads. I'm not going to apologise for having done it
>>>> here.
>>>
>>> Well, the "standard good netiquette" was/is to *add* 'SOLVED' in the
>>> subject line, not to replace the subject. But you're forgiven! :-)
>> 
>> Netiquette when modifying the Subject header (which adding SOLVED or
>> changing to just SOLVED would do) is to show the new Subject header and
>> append "(was: <originalSubject>)", so here it looked like:
>> 
>> Solved (was: No CMD)
>> 
>> I have also seen:
>> 
>> Solved - No CMD
>> 
>> I don't recall "Solved" was to be all uppercased, but I don't visit all
>> newsgroups.  Been in Usenet since around 92.  At the height of where I
>> visited, I used to inhabit 52 newsgroups, but that's waned to 19 now.
>> 
>> If the original Subject was still there, and "SOLVED" had been added,
>> the Subject would not have been all uppercase: the "o" was lowercase.
>> Prepending "Solved" would also not have the Subject as all uppercase.
>> I'll look into my all-uppercase filter to see if I can add an exception
>> for just "SOLVED"; i.e., Subject starts with "solved" whether upper- or
>> lowercase, or mix of both; however, that would permit starter posts that
>> aren't replies, like "SOLVE YOUR DEBT".
>> 
> 
> Here is a forum that might help you and ed.
> 
> h**ps:// able2know. org/ forum/ english_grammar/
> 
> Many experts there that can nitpick the tiniest of grammar mistakes.

The issue is not about grammar.  We are discusssing etiquette, not
grammar.

[toc] | [prev] | [next] | [standalone]

#184263 — Re: Change of Subject

On 27/04/2025 9:50 am, VanguardLH wrote:
> Frank Slootweg <this@ddress.is.invalid> wrote:
>> Ed Cryer <ed@somewhere.in.the.uk> wrote:
>>> VanguardLH wrote:
>>
>>>> Update:
>>>>
>>>> I did not see your "SOLVED" subthread, because one of my filters
>>>> flags posts that have all uppercase in the Subject.
>>>
>>> It used be standard good netiquette to put "solved" in upper case; in
>>> Web and Usenet threads. I'm not going to apologise for having done it
>>> here.
>>
>> Well, the "standard good netiquette" was/is to *add* 'SOLVED' in the
>> subject line, not to replace the subject. But you're forgiven! :-)
> 
> Netiquette when modifying the Subject header (which adding SOLVED or
> changing to just SOLVED would do) is to show the new Subject header and
> append "(was: <originalSubject>)", so here it looked like:
> 
> Solved (was: No CMD)

Did you notice how the Subject: changed from your 'Change of Subject 
(was: No CMD)' to my 'Re: Change of Subject' ??

My SeaMonkey Suite (and, I think, Thunderbird) does that auto-magically 
... getting rid of the bracketed stuff!
-- 
Daniel70

[toc] | [prev] | [next] | [standalone]

#184266 — Re: Change of Subject

Daniel70 <daniel47@eternal-september.org> wrote:

> VanguardLH wrote:
>                  
>> Netiquette when modifying the Subject header (which adding SOLVED or
>> changing to just SOLVED would do) is to show the new Subject header and
>> append "(was: <originalSubject>)", so here it looked like:
>> 
>> Solved (was: No CMD)
> 
> Did you notice how the Subject: changed from your 'Change of Subject 
> (was: No CMD)' to my 'Re: Change of Subject' ??

When modifying the Subject, the "(was:...)" postfix should get added
automatically by a proper NNTP client to show the original Subject.  

When replying to an article with the "(was:...)" postfix, the client
/should/ remove the postfix.  It is not necessary nor desirable to keep
carrying forward that Subject changed at some point indicating a change
in topic, or discuss a side topic.

Notice how "(was:...)" did not get appended when your client added the
"Re:" prefix.  Technically that is a change in Subject, but it used as a
qualifier to denote a reply to the same Subject.

> My SeaMonkey Suite (and, I think, Thunderbird) does that auto-
> magically ... getting rid of the bracketed stuff!

So does mine (40tude Dialog).  Proper NNTP clients should.

[toc] | [prev] | [next] | [standalone]

#184085

On Sat, 26 Apr 2025 12:00:47 +0100, Ed Cryer wrote:
> It used be standard good netiquette to put "solved" in upper case; in 
> Web and Usenet threads. I'm not going to apologise for having done it 
> here. 

But you left one thing out of that standard good practice: Append 
SOLVED to the original subject line.

Replacing the subject line entirely is not a good idea, because it 
breaks the human-eyeballs connection with the thread describing the 
problem. Yes, technically it's in the same thread, but it doesn't 
look that way to a human.

-- 
Stan Brown, Tehachapi, California, USA         https://BrownMath.com/
Shikata ga nai...

[toc] | [prev] | [next] | [standalone]

#183976

VanguardLH wrote:
> Ed Cryer <ed@somewhere.in.the.uk> wrote:
> 
>> On two of my Win10 systems, I can swap between Powershell and command
>> prompt. But on the third there's a most peculiar problem.
>> Settings/Personalisation/Taskbar has the option to switch between the
>> two. When I set it to CMD, CMD appears for a second in a tiny window and
>> then disappears. I can't get it to stay put.
>>
>> I've run DISM and sfc, have the latest 22H2 19045.5796 build.
> 
> Not sure what config wizard setting to which you refer.  When I
> right-click on a blank area of the Taskbar, click on Taskbar Settings in
> the context menu, I don't see a toggle choosing between Command or
> Powershell.  I see:
> 
>    Replace Command Prompt with Windows PowerShell in the menu
>    when I right-click the start button or press Windows key+X.
> 
> The only times I start cmd.exe this way is when reading some online help
> file on starting cmd.exe.  I use a shortcut to cmd.exe, and the shortcut
> is in a toolbar in the Taskbar configured to run with admin privs (so
> the UAC prompt appears).  I can also click on the Start menu button, and
> enter "cmd" which shows Command Prompt as a match.  The first match
> opens in non-admin mode.  Another match let me click on its rightward
> chevron to get more choices, like Open or Run as administrator.
> 
> How are you starting cmd.exe?  If using a shortcut, make sure to add the
> /k command-line argument to keep open the console window, like:
> 
> cmd.exe /k
> 
> Normally, when cmd is done running whatever your told it to run, the
> console window closes, because the cmd shell unloads after running
> whatever you told cmd.exe to run.  You want to keep the shell loaded, so
> add /k switch.  Also check which cmd.exe the shortcut specifies.  Have
> it point at the one under the system32 folder.
> 
> In Task Manager, check if any instances of cmd.exe are running.  If so,
> kill them.  You don't say how you run cmd.  Try the following:
> 
> - Bring up the Task Manager (Ctrl+Shift+Esc).
>      o Select the Details tab.
>      o Click on the Name column header to sort by process name.
>      o Scroll down to where the C's would start.
>      o Check there are no running instances of cmd.exe
> - Run cmd.exe:
>      o Bring up the Run dialog (Win+R).
>      o Or, use the File -> Run new task menu in Task Manager.
> - Enter: cmd.exe.  Include the .exe extension.  Click OK.
> 
> See a console window now?
> Did the console window stay open?
> In Task Manager, did you see cmd.exe show up?
> 
> If you saw cmd.exe show up in Task Manager, but only temporarily, and
> its console window did not stay open, do the above again; however,
> instead of relying on pathing to find the cmd.exe executable file, enter
> the full path to the executable: c:\windows\system32\cmd.exe.
> 
> Look in Event Viewer to see if an error got reported when trying to load
> cmd.exe.
> 
> cmd.exe is one of the programs often attacked by malware to prevent the
> user from have a low-level tool to undo the malware.  Run a full scan
> using your anti-virus software.  If using Windows Defender, see:
> 
> https://learn.microsoft.com/en-us/defender-endpoint/command-line-arguments-microsoft-defender-antivirus
> 
> and run:
> 
> mpcmdrun.exe -scan -scantype 2
> 
> Defender's manual scan is slow, so it will take a long time to complete.
> If its console window disappears after it completes, so you don't get to
> see its output, pipe stdout into a file to open in Notepad, like:
> 
> mpcmdrun.exe -scan -scantype 2 > %temp%\mpscan.txt & notepad %temp%\mpscan.txt
> 

Settings/Personalization/Taskbar/ yields the same settings options as 
Rt.Click Taskbar/Taskbar Settings

The only purpose of this settings is to change what is shown(Command.com 
or Powershell) in the window for the Start Menu button(right click) or 
the Quick Menu(Windows key + X).
  i.e. it doesn't run Command.com or Powershell


The symptom of running Command.com from the above menu options and 
resulting in it disappearing(brief window) was a known issue quite some 
time ago(circa 20H2)
  - the fix was to access the command.com shortcut and ensure it was 
configured to run in a normal window but not run in a 
minimized/maximized window. If set to 'normal' temporarily toggle it to 
minimized or maximum, restart, then reset back to normal.
  - Note: Even when changing the shortcut properties to use the 
command.com /k option, it was still necessary to reset/toggle/toggle 
back the properties window setting. Since multiple access points(to 
command.com) in Windows or user configured/created shortcuts exist, all 
command.com shortcuts should be configured/reset to run in the same 
window(e.g. Normal). Finally, configuring the shortcut to run-as Admin 
or not is not related to the disappearing issue(it can be admin or not).

-- 
...w¡ñ§±¤ñ

[toc] | [prev] | [next] | [standalone]

#183985

...winston wrote:
> VanguardLH wrote:
>> Ed Cryer <ed@somewhere.in.the.uk> wrote:
>>
>>> On two of my Win10 systems, I can swap between Powershell and command
>>> prompt. But on the third there's a most peculiar problem.
>>> Settings/Personalisation/Taskbar has the option to switch between the
>>> two. When I set it to CMD, CMD appears for a second in a tiny window and
>>> then disappears. I can't get it to stay put.
>>>
>>> I've run DISM and sfc, have the latest 22H2 19045.5796 build.
>>
>> Not sure what config wizard setting to which you refer.  When I
>> right-click on a blank area of the Taskbar, click on Taskbar Settings in
>> the context menu, I don't see a toggle choosing between Command or
>> Powershell.  I see:
>>
>>    Replace Command Prompt with Windows PowerShell in the menu
>>    when I right-click the start button or press Windows key+X.
>>
>> The only times I start cmd.exe this way is when reading some online help
>> file on starting cmd.exe.  I use a shortcut to cmd.exe, and the shortcut
>> is in a toolbar in the Taskbar configured to run with admin privs (so
>> the UAC prompt appears).  I can also click on the Start menu button, and
>> enter "cmd" which shows Command Prompt as a match.  The first match
>> opens in non-admin mode.  Another match let me click on its rightward
>> chevron to get more choices, like Open or Run as administrator.
>>
>> How are you starting cmd.exe?  If using a shortcut, make sure to add the
>> /k command-line argument to keep open the console window, like:
>>
>> cmd.exe /k
>>
>> Normally, when cmd is done running whatever your told it to run, the
>> console window closes, because the cmd shell unloads after running
>> whatever you told cmd.exe to run.  You want to keep the shell loaded, so
>> add /k switch.  Also check which cmd.exe the shortcut specifies.  Have
>> it point at the one under the system32 folder.
>>
>> In Task Manager, check if any instances of cmd.exe are running.  If so,
>> kill them.  You don't say how you run cmd.  Try the following:
>>
>> - Bring up the Task Manager (Ctrl+Shift+Esc).
>>      o Select the Details tab.
>>      o Click on the Name column header to sort by process name.
>>      o Scroll down to where the C's would start.
>>      o Check there are no running instances of cmd.exe
>> - Run cmd.exe:
>>      o Bring up the Run dialog (Win+R).
>>      o Or, use the File -> Run new task menu in Task Manager.
>> - Enter: cmd.exe.  Include the .exe extension.  Click OK.
>>
>> See a console window now?
>> Did the console window stay open?
>> In Task Manager, did you see cmd.exe show up?
>>
>> If you saw cmd.exe show up in Task Manager, but only temporarily, and
>> its console window did not stay open, do the above again; however,
>> instead of relying on pathing to find the cmd.exe executable file, enter
>> the full path to the executable: c:\windows\system32\cmd.exe.
>>
>> Look in Event Viewer to see if an error got reported when trying to load
>> cmd.exe.
>>
>> cmd.exe is one of the programs often attacked by malware to prevent the
>> user from have a low-level tool to undo the malware.  Run a full scan
>> using your anti-virus software.  If using Windows Defender, see:
>>
>> https://learn.microsoft.com/en-us/defender-endpoint/command-line- 
>> arguments-microsoft-defender-antivirus
>>
>> and run:
>>
>> mpcmdrun.exe -scan -scantype 2
>>
>> Defender's manual scan is slow, so it will take a long time to complete.
>> If its console window disappears after it completes, so you don't get to
>> see its output, pipe stdout into a file to open in Notepad, like:
>>
>> mpcmdrun.exe -scan -scantype 2 > %temp%\mpscan.txt & notepad %temp% 
>> \mpscan.txt
>>
> 
> Settings/Personalization/Taskbar/ yields the same settings options as 
> Rt.Click Taskbar/Taskbar Settings
> 
> The only purpose of this settings is to change what is shown(Command.com 
> or Powershell) in the window for the Start Menu button(right click) or 
> the Quick Menu(Windows key + X).
>   i.e. it doesn't run Command.com or Powershell
> 
> 
> The symptom of running Command.com from the above menu options and 
> resulting in it disappearing(brief window) was a known issue quite some 
> time ago(circa 20H2)
>   - the fix was to access the command.com shortcut and ensure it was 
> configured to run in a normal window but not run in a minimized/ 
> maximized window. If set to 'normal' temporarily toggle it to minimized 
> or maximum, restart, then reset back to normal.
>   - Note: Even when changing the shortcut properties to use the 
> command.com /k option, it was still necessary to reset/toggle/toggle 
> back the properties window setting. Since multiple access points(to 
> command.com) in Windows or user configured/created shortcuts exist, all 
> command.com shortcuts should be configured/reset to run in the same 
> window(e.g. Normal). Finally, configuring the shortcut to run-as Admin 
> or not is not related to the disappearing issue(it can be admin or not).
> 

I tried this, but it didn't work.
I even created a shortcut on the Desktop, and performed your recommended 
actions through that.

Ed

[toc] | [prev] | [next] | [standalone]

#183986 — SOLVED

Ed Cryer wrote:

I ran this on Powershell.

echo off
reg delete "HKCU\Console" /f
reg delete "HKCU\Software\Microsoft\Command Processor" /v "AutoRun" /f
reg delete "HKLM\Software\Microsoft\Command Processor" /v "AutoRun" /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File
Execution Options\cmd.exe" /f
echo done

Ed

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | alt.comp.os.windows-10

csiph-web