A shortcut to the Run dialog

Date:November 24, 2003 / year-entry #139
Tags:code;tipssupport
Orig Link:https://blogs.msdn.microsoft.com/oldnewthing/20031124-00/?p=41723
Comments:    6
Summary:Here's a little script that opens the Run dialog. You can save it as "Run.js" and double-click it. (new ActiveXObject("Shell.Application")).FileRun(); The advantage of this approach over various others people have come up with is that this one is actually documented. (And therefore is less likely to break in the next version of the operating system.)

Here's a little script that opens the Run dialog. You can save it as "Run.js" and double-click it.

(new ActiveXObject("Shell.Application")).FileRun();

The advantage of this approach over various others people have come up with is that this one is actually documented. (And therefore is less likely to break in the next version of the operating system.)


Comments (6)
  1. Phil Rodgers says:

    Hitting Windows+R is documented too, at Q126449.

  2. Adina Adler says:

    Hitting Windows+R is also documented in the Help system, and I think it has been since Windows 98. (I think that’s when I found it, as well as all of the other things you can do with the Windows key.)

  3. Bill Wert says:

    Except you can’t use WScript’s sendkeys method to send the windows key. That’s what makes the script chunk above useful.

  4. Corey Gouker says:

    You can also just create a regular shortcut to " &Run… ". not sure if it’s documented anywhere though :-).

  5. Girish says:

    You can just drag and drop "Run" from the start menu onto desktop. That will start the "Run" when you double-click.

  6. Alec Soroudi says:

    That only works with XP’s new start menu, not the old, "classic" start menus.

Comments are closed.


*DISCLAIMER: I DO NOT OWN THIS CONTENT. If you are the owner and would like it removed, please contact me. The content herein is an archived reproduction of entries from Raymond Chen's "Old New Thing" Blog (most recent link is here). It may have slight formatting modifications for consistency and to improve readability.

WHY DID I DUPLICATE THIS CONTENT HERE? Let me first say this site has never had anything to sell and has never shown ads of any kind. I have nothing monetarily to gain by duplicating content here. Because I had made my own local copy of this content throughout the years, for ease of using tools like grep, I decided to put it online after I discovered some of the original content previously and publicly available, had disappeared approximately early to mid 2019. At the same time, I present the content in an easily accessible theme-agnostic way.

The information provided by Raymond's blog is, for all practical purposes, more authoritative on Windows Development than Microsoft's own MSDN documentation and should be considered supplemental reading to that documentation. The wealth of missing details provided by this blog that Microsoft could not or did not document about Windows over the years is vital enough, many would agree an online "backup" of these details is a necessary endeavor. Specifics include:

<-- Back to Old New Thing Archive Index