up vote 0 down vote favorite
share [g+] share [fb]

Every once in a while when I launch powershell on my Windows 7 SP1 x64 machine I get this error.

powershell error "There is no disk in the drive"

None of the buttons will get rid of the error, it just comes back, I have to close the broken powershell window to dismiss the error. A reboot will fix it for a while until it decides to come back (not a real solution). Any ideas on why powershell would intermittently look for a disk?

link|improve this question
are there any errors or warnings in your systemlog? – wullxz Apr 21 '11 at 7:27
- System - Provider [ Name] Application Popup - EventID 26 [ Qualifiers] 16384 Level 4 Task 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2011-04-19T20:15:55.000000000Z EventRecordID 41303 Channel System – Peter Apr 21 '11 at 20:04
What is drive D:? Is it a optical drive? An SATA or SAS disk? USB? Firewire? iSCSI? Is there actually a disk there? – Bacon Bits Apr 22 '11 at 13:03
It's an optical drive, there are rarely disks in it. And powershell will launch fine 99% of the time with no disk in D: – Peter Apr 26 '11 at 22:41
feedback

migrated from serverfault.com Apr 20 '11 at 10:44

This question came from our site for system administrators and desktop support professionals.

1 Answer

up vote 0 down vote

I noticed this happens if there is a disk in the drive at the time it is booted. If the disk is removed prior to shutting the PC down, this error will occur. The only fix I have come up with is to eject the disk when shutting down the PC, at the point when it displays the message "Shutting Down". The next time the PC is booted, there is no disk in the drive to be referenced. The other way is to manually force eject the cd/dvd tray, if the PC has no power to it, using a paper clip as a pointer in the small hole.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

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