Start menu -> Command prompt -> right click -> run as admin = error

I have a problem that seems (to me at least) to be quite common as well as annoying when it happens because you don't know when it started occurring and have no way to fix it, which is why I am finally asking after all these years.

The problem is, when typing Command prompt into the start search box, then right clicking it and choosing run as admin, there's an error. I know I can use Win+X+A to run command prompt as admin, I can also right click a shortcut and run as admin, I can even type cmd into the start search box and run as admin. But when right clicking Command Prompt in the start menu and running as admin, it doesn't work.

This happened even on Windows 7. Actually, I'm using StartIsBack on Windows 10 right now. I just tried using the default Windows 10 start menu and there's no such problem, but that's because the Windows 10 start menu operates differently. (Am I posting this in the right place? Should it actually belong in SevenForums then?)

I can even invoke the error by searching for Task Manager, or On-Screen Keyboard, and various other Windows system tools. It seems that if I right click, and "Run as Administrator" does not have a shield icon, it will error if I click it. Refer to screenshots below:



So, how can I finally fix this?

(btw, I think the error message is different on Windows 7 but basically it's the same problem nonetheless)

You don't say what the error is but it's simpler to right click start then choose CMD prompt admin. You say you type command that is MS-DOS command.com not CMD.exe

The error is clearly there in the screenshot.

Typing "command" is to search for "Command Prompt" in the start menu. In fact, command.com has not existed in Windows since XP (or Vista, I don't remember).

The reason I brought up the issue was because I was trying to run PowerShell as admin. Typing powershell in the start menu, right clicking it and choosing run as administrator, gives me the same error. And don't tell me to enable the option to replace Command Prompt with PowerShell in the Win+X menu, because that's not a solution (and because I use cmd a lot more often than PowerShell).

yogalD said:

This happened even on Windows 7. Actually, I'm using StartIsBack on Windows 10 right now. I just tried using the default Windows 10 start menu and there's no such problem, but that's because the Windows 10 start menu operates differently. (Am I posting this in the right place? Should it actually belong in SevenForums then?)

That would tend to indicate to me that StartIsBack is the problem, not Windows 10.

NavyLCDR said:

That would tend to indicate to me that StartIsBack is the problem, not Windows 10.

Perhaps, but Windows 7 has the same issue. If I can get a solution to the the Windows 7 problem it will probably work for StartIsBack on Windows 8 and 10, considering StartIsBack really just uses the unused start menu code that is hidden in those versions of Windows.

Hi YogaID, I saw your post here (and the Win 7 forum) and came to say I've started to have the same issue. I've been using StartIsBack for many years, and have only just started experiencing this issue. I assume it's a coincidence but I also happened to notice this when trying to run Powershell as admin, although the fault occurs for other programs too.

I haven't yet tried uninstalling StartIsBack yet (not sure where my license key is!), but will try that when I get a sec. There is a comment I've seen which we should track: Run As Administrator | Startisback

Good luck!

Retne said:

Hi YogaID, I saw your post here (and the Win 7 forum) and came to say I've started to have the same issue. I've been using StartIsBack for many years, and have only just started experiencing this issue. I assume it's a coincidence but I also happened to notice this when trying to run Powershell as admin, although the fault occurs for other programs too.

I haven't yet tried uninstalling StartIsBack yet (not sure where my license key is!), but will try that when I get a sec. There is a comment I've seen which we should track: Run As Administrator | Startisback

Good luck!

I just tried reinstalling StartIsBack but that doesn't solve it. Seeing as the problem occurs in Windows 7 as well, it has to be due to the start menu (what's left of it in Win10) rather than StartIsBack - thus it's a problem with Windows and not with any third party application like SIB.