Classic Shell: Forum

while new to classicshell I am not new to windows installer which is why the post.

I am trying to silently install the start menu and explorer options only like this;
ClassicShellSetup_4_2_1.exe /quiet /norestart ADDLOCAL=ClassicExplorer,ClassicStartMenu /l*v C:\temp\cshellall.log

when I do msiexec pops it help window.

When I do it like this it works fine;
ClassicShellSetup_4_2_1.exe /quiet /norestart ADDLOCAL=All /l*v C:\temp\cshellall.log

Will I have to do it like this?
ClassicShellSetup_4_2_1.exe /quiet /norestart ADDLOCAL=ClassicStartMenu /l*v C:\temp\cshellmenulog
and then
ClassicShellSetup_4_2_1.exe /quiet /norestart ADDLOCAL=ClassicExplorer /l*v C:\temp\cshellexp.log

no biggie as it works just counter productive and quite frankly strange.

I should mention I do not want to do the All option if it includes the IE9 shell app.

What version of Windows do you have?

Windows 7 enterprise x64 and WIN8 Enterprise x64

Hm, your exact command line worked for me on Windows 7 Ultimate.
Make sure you run the command from an admin prompt.

this one worked?

ClassicShellSetup_4_2_1.exe /quiet /norestart ADDLOCAL=ClassicExplorer,ClassicStartMenu /l*v C:\temp\cshellall.log

I know about the admin window, this is what I do here. Will try again though. Thanks for checking.

Yes, that exact command worked for me too. The C:\temp folder exists right and is writable?

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

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

same issue when not using log files but yes. We decided to only use the Start Menu portion so issue is now moot.

thanks to all who have taken a look though.

Strange really. If you are able to reproduce it later, please report how.

Btw you are putting the path to the installer in double quotes, right? e.g.
"C:\Downloads\ClassicShellSetup_4_2_1RTM.exe" /norestart ADDLOCAL=ClassicExplorer,ClassicStartMenu

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

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

no, that makes no difference either way. now the big question to all of you is this. Are you using a CMD window (old school) or a powershell admin window? we use powershell via sccm 2012 to do this type of work.

I am using an admin cmd window, not powershell. Maybe powershell gets tripped by the comma or something. You can use a tool like Process Explorer to examine the command line actually passed to the installer EXE and verify if it has been altered.