9

Set non-default browser in Windows 8 RTM (Chrome, Firefox) and try to run code like this:

ShellExecute(NULL, "open", "http://stackoverflow.com", NULL, NULL, SW_SHOWNORMAL);

It's ok. But then change manifest to require Administrative priveleges or just "run as administrator".

Code won't work.

Ok, then try to run any application using "run as administrator".

You will see the same result, links are not working.

Change default browser back to IE -> all works fine.

In Windows 8 previous builds there is no such behavour.

What is going on?

PS. It seems Microsoft experienced the same problems in their own software :) Visual Studio 2012 Web Publish on Windows 8 RTM Fails Browser Launch

Community
  • 1
  • 1
Brun
  • 388
  • 3
  • 11
  • What's the return value of ShellExecute? – Luke Aug 21 '12 at 15:08
  • Hmmm. I just tried this on Windows 8 RP and ShellExecute returns 31 when run as admin. 31 = SE_ERR_NOASSOC = "There is no application associated with the given file name extension." – Luke Aug 21 '12 at 15:27
  • 1
    Looking at procmon logs of the two scenarios, the only difference I can see is that the "run as admin" scenario fails to open one of the registry keys. The odd thing is that it fails with "NAME NOT FOUND", but obviously the key exists. Don't really know how to diagnose it further. – Luke Aug 21 '12 at 16:24
  • Expert said it is probably not a Windows bug, but security patch. They deny ShellExecute from elevated processes to close security breach. – Brun Aug 22 '12 at 06:07
  • That doesn't make sense because it still works if Internet Explorer is set as the default browser (and it works with other arbitrary programs, just not other browsers). – Luke Aug 22 '12 at 14:19

2 Answers2

3

I've been seeing the same behavior with Chrome until today. Spent some time trying to figure out what was going on and couldn't for the longest time make Chrome come up with ShellExecute() under elevated rights either. Failed for elevated rights (ie. UAC dialog, or Run As Administrator) or even when turning off UAC altogether.

I ended up uninstalling and re-installing Chrome and that actually fixed it.

Also saw the behavior with other browsers, however after a few tries with FireFox I went into the Set Default Programs settings from FireFox and EXPLICITLY (ie. in Windows) set the associations for .htm file and the HTTP protocol. That worked as well.

So it looks like this is some sort of registration issue, rather than an actual problem in Windows. First thing I would try is to explicitly set the associations in Windows (rather than Set Default Browser in the browser). If that fails try reinstalling the browser...

Rick Strahl
  • 17,302
  • 14
  • 89
  • 134
0

@ Rick Strahl

You're incorrect. It's not just registration. I tested with Photoshop CC and Windows 8. I created a launcher for Photoshop to make it portable: - with Administrative Rights, shell integration does not work. - when run as normal user, shell integration works as expected.

Tested on Windows 7. - works with or without Administrative Rights.

I can confirm O.P. is correct.

user2513957
  • 1