Iis – The great Vanishing Act of INetMgr.exe on the Windows 7 x64 system

iisiis-7.5windows 7

I'm facing an odd issue with the IIS Manager on Windows 7 (x64).

At home, I have Win7 Professional, and when I check my IIS manager icon in the start menu, I see it links to 

%windir%\system32\inetsrv\InetMgr.exe

When I launch this from the command line, it works like a charm.

At work, however, I have Windows 7 Enterprise (x64), and when I check my link in the start menu, the entry is exactly the same. If I click on it – it works like a charm.

Now if I'd like to launch it from the command line (cmd.exe or TakeCommand), however – the file just isn't there – a 

DIR %windir%\system32\inetsrv\*.exe

shows a number of files, including a "inetmgr6.exe" – but no "inetmgr.exe" – and of course, I can't launch it either 🙁

Strangely enough, when I look at the directory %windir%\system32\INetSrv in Windows Explorer or Windows Powershell, I SEE the INetMgr.exe file and I can launch it – no problem.

What the **** is going on here? How can I find the INetMgr.exe from my classic command line and launch it from there??

UPDATE: ok, some updates. On my work laptop, the INetMgr.exe file appears to really be located in a directory called c:\windows\syswow64\inetsrv (I'm recalling from memory, so don't quote me on the directory name – something like that). I can see this if I search for it in e.g. Powershell or Windows 7 Explorer.

However, from a "classic" command line like cmd.exe, it appears to be in c:\windows\system32\inetsrv ….. hmmm…. trouble is – even though I now know where the file really is, I cannot access that directory from my classic command line – not even if I'm running cmd.exe as admin with elevated privileges……. so I know where the file is, but that still doesn't solve my problem 🙁

Best Answer

That's an interesting one. Try launching your command prompt with elevated privileges in case UAC is fighting with you. My only other guess is that %windir% is set differently in your path for the command prompt somehow. Try navigating to it with the explicit path. Also, try creating a test file like 'test.txt' from your command prompt and make sure that it shows up in Windows Explorer, to make sure that the paths between the two apps aren't messing with you.

Related Topic