Classic Shell: Forum

Up to build 10074 (I think - I could be off a few builds), I could run an application with a parameter
from the Search box or Run option in Classic Shell.

Now the addition of a parameter causes an Explorer window to open with a failed search.

As an example, I have a small application that pops up a message box. If I enter the following:



I get no run of the application, but instead this failed search:



Running the same command from a CMD window, the application is run successfully:




Note that when I do the same thing from Classic Shell 4.2.2 in Win 8.1 the "See more results"
submenu item does NOT pop up and when I hit return I DO see the application run properly with the parameters. This is the more preferable result.




A secondary problem:

On Win 10 any attempt to bring up the Run box from Classic Shell yields nothing at all.



-Noel

OK, on the first item, I now realize the "See more results" entry comes from the [ ] Search files box being checked. It's also checked on my Win 8.1 system, but I keep the search indexer disabled, so it was non-functional (and showing a red mark).

However, the Run box is still non-functional.

-Noel

Well the 1st bug you reported is also correct. For example, in the Windows 7 Start Menu or at command prompt, or Run dialog, if we type:
regedit -M
It opens multiple instances of Regedit (because the -m switch is being sent correctly)
In Classic Start Menu, regedit -M doesn't open another instance of Regedit because the parameter is being ignored.

Thanks for reporting the bug

Btw I checked previous versions and this bug/regression is new for Classic Shell 4.2.2 beta. Earlier versions are not affected.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and did Classic Shell's testing and usability/UX feedback.

Hm, the Run command works for me on build 10130, with both Classic and Windows 7 styles.
What build do you have? is it 32 or 64 bit?

Run command works for me too.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and did Classic Shell's testing and usability/UX feedback.

Well, I *had* 10159 (x64), but Microsoft has seen fit to send out another one. Seems like all my time any more doing is in reworking the config settings I like after new builds reset most of it.

I'll let you know if 10162 (or whatever this new one is going in now) allows the run prompt to come up.

Assuming the problem continues, do you have a log or something that I can look in to see why it's just ignoring the request for Run?

-Noel

Please try the Run command before you do any customizations to 10162 to make sure it is broken from the start.
There are no logs that can help diagnose it. If you still have problems after the upgrade I will have to make a small test program for you to try.

Since 10162 went in as an upgrade, most of the customizations were already there. Unfortunately it didn't start working.

I plan to do a clean install of the GA version when it comes out. I'll track whether Run works on a virgin system and assuming it does, then what I tweak that causes it to fail.

I am seeing some error events in the Windows Application log. This is probably part of what's wrong...

Faulting application name: ShellExperienceHost.exe, version: 10.0.10162.0, time stamp: 0x5592109c
Faulting module name: StartUI.dll, version: 10.0.10162.0, time stamp: 0x5592080b
Exception code: 0xc0000005
Fault offset: 0x000000000003c1c3
Faulting process id: 0x1710
Faulting application start time: 0x01d0b7ad0302aebe
Faulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Faulting module path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\StartUI.dll
Report Id: a7caeed1-e1ee-4c8a-9527-08a8886c96d0
Faulting package full name: Microsoft.Windows.ShellExperienceHost_1000.10162.0.0_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: App

-Noel

Command line switches for programs should work in the search box again in Classic Shell 4.2.3 release candidate.

However, neither Ivo nor I could reproduce the issue where the "Run" item doesn't work on Windows 10.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and did Classic Shell's testing and usability/UX feedback.