I've always wondered why Windows has an Eject option but doesn't include a corresponding Close / Close Tray option in the context menu of optical drives.

Is there a way of closing the optical drive tray without the use of any third party software in Windows?

  • 1
    Did you want this option in the case you are remotely accessing a computer? – Christopher Chipps Dec 6 '12 at 5:58
  • 4
    @ChristopherChipps Is he going to remotely put the CD in the tray as well? – cutrightjm Dec 6 '12 at 6:02
  • 1
    Touche @ekaj. Sure, seriously in the case the user needs the tray opened and is unable to themself. In which case this is needed, I am unsure. – Christopher Chipps Dec 6 '12 at 6:07
  • 2
    Remember that (most, if not all) laptop optical drives have to be pushed to be closed, since the tray cannot retract automatically. I suppose they could have somehow made the drive advertise whether it supports automatic tray retraction or not, and the OS could have displayed or hidden the Close option based on this, but really, that would just be way too much time and resources spent on something so trivial and mostly useless. – Karan Dec 8 '12 at 2:43
  • 2
    +1 for the question. @ekaj, while it is unusual to need to remotely close a disc tray, there are times when such functionality is a convenience. I remotely authored a CD for a client and wanted to check that the burn was successful, however the authoring software auto-ejected the disk. At home, if I'm not satisfied with the encoding of video rip on a linux server, I can type eject -t from my laptop and re-encode without having to walk to the server closet to close the tray manually. A rather small convenience, but perhaps not as absurd as the down votes suggest. – jthetzel Dec 8 '13 at 14:08

The only way to do this IMO without the use of 3rd party utils (such as NirCmd and Wizmo) would be via VBScript or PowerShell. All the VBScript solutions I've seen so far use an outdated Windows Media Player OCX. I don't know whether the latest versions of WMP include an OCX with similar functionality or not, plus disabling/uninstalling it via Windows Features might interfere with the functioning of the script in any case.

A common way to implement this functionality via code is by using the Media Control Interface (MCI) APIs (specifically, the set command). However, since VBScript does not support calling normal Windows API functions or even functions from arbitrary DLLs, that leaves us with PowerShell. Thus the following should work out of the box in Windows 7+ that comes with PS pre-installed, and on XP/Vista after PS is installed. The MCI DLL i.e. Windows\System32\WinMM.dll should be available as part of the default installation in XP+.

1) Save the following as CD_Open.ps1:

$cd = Add-Type -memberDefinition @"
[DllImport("winmm.dll", CharSet = CharSet.Ansi)] public static extern int mciSendStringA(string lpstrCommand, string lpstrReturnString, int uReturnLength, IntPtr hwndCallback);
"@ -passthru -name mciSendString
$cd::mciSendStringA('set cdaudio door open', $null, 0, 0);

2) Save the following as CD_Close.ps1:

$cd = Add-Type -memberDefinition @"
[DllImport("winmm.dll", CharSet = CharSet.Ansi)] public static extern int mciSendStringA(string lpstrCommand, string lpstrReturnString, int uReturnLength, IntPtr hwndCallback);
"@ -passthru -name mciSendString
$cd::mciSendStringA("set cdaudio door closed", $null, 0, 0);

Now comes the problem. By default, unsigned PS scripts cannot be executed in Windows for security reasons. Type get-help about_signing at the PS prompt to know more about this, including how to self sign your scripts and so on.

Luckily there's a workaround as the get-help command above states:

   When you start Windows PowerShell on a computer for the first time, the
   Restricted execution policy (the default) is likely to be in effect.

   The Restricted policy does not permit any scripts to run.

   To find the effective execution policy on your computer, type:


   To run unsigned scripts that you write on your local computer and signed
   scripts from other users, use the following command to change the execution
   policy on the computer to RemoteSigned:

       set-executionpolicy remotesigned

   For more information, see Set-ExecutionPolicy.

3) So from an elevated Command Prompt, run the following command:

powershell set-executionpolicy remotesigned

(You can run powershell set-executionpolicy restricted to revert to the default setting.)

This command needs to be run only once and remains in effect until you change the execution policy again.

4) Now you can use the following commands (even from a non-elevated Command Prompt) to open/close the optical drive tray:

powershell -file CD_Open.ps1
powershell -file CD_Close.ps1

Of course, you can create shortcuts as well so that you can open/close the tray with a click or a key combo:

CD Tray Shortcuts

You can also add the Close command to the context menu of your optical drive using the following .REG file:

Windows Registry Editor Version 5.00



@="C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\Powershell.exe -windowstyle hidden -file I:\\CD_Close.ps1"

(Edit the paths as required. Also, the -WindowStyle parameter is only available with PS 2.0+.)

  • 2
    I would +1 you for the PowerShell script, and then +1 again for the Registry idea. – palswim Sep 15 '17 at 19:37
  • With one of the updates, Windows 10 removed my Drive.CDROM key from the registry. I re-added it to the SystemFileAssociations key and this solution still works. – palswim Sep 26 '18 at 0:28

Here is an example. Here is an implementation in C#.. (may require a DLL or two).

There are lots of them, so if one doesn't work for you try another.

  • Well, I did search. But couldn't find other than downloading something . The command ling thing is useful, thanks. – Reza M. Dec 6 '12 at 5:35

I haven't tried these myself, but may be this will help Link
But you have to download a dll
Here is the C source code to do it if you want to compile it yourself, but you need to look for a way to integrate the compiled program in the Windows Explorer right click menu for the CD drive C code

  • The CDR program you link to includes an executable in addition to the C source code. From the command line, CDR close D: solved the problem of needing to remotely close a disc tray. – jthetzel Dec 8 '13 at 14:28

It could be that the Eject button was originally designed for cases of hardware failure where the hardware button did not respond any more.

Close on the other hand can typically be done by just pushing the drive in. This maybe the reason for not adding a close.

Also eject works well on virtual/mounted drives(mac dmgs, any mounted drives), usb drives (as safely remove) etc, where there is no version of close.

  • Huh, good point for the hardware failure part. Wouldn't of thought about that. I could see that being true as a lot of cases where the original design/goal doesn't apply any more but they still kept it. – Reza M. Dec 6 '12 at 5:31

In Linux (and therefore, probably in OSX and BSD and UNIXes etc etc), "there's an app for that":

eject -t

You did not specify which version of Windows you are running. I just noticed on my Windows 2000 system, the CD Player program (under Start > Accessories > Entertainment) has an eject button. Clicking on that Eject button will open the tray if the tray is closed, and it will close the tray if the tray is open.


there is another way. in Windows Media Player (at least in 12), you can click, at the top, Play, then Eject, and choose your drive. if it is already ejected, nothing will happen. then do it again, and it should CLOSE the drive :)


This is a small app that adds a button to the task bar for opening and closing the optical drive. http://digola.com/doorcontrol.html

  • 2
    The question said ‘‘without the use of any third party software’’. – Scott Jul 27 at 15:44

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.