Help. CD/DVD drive not found after using most recent Windows Update

Slimer wrote:


Is it possible that the device was simply disabled for some reason?
If the BIOS sees it, there's truly no reason for Windows to ignore
its existence unless the user decided that it should be inactive. I
truly doubt that a CD-ROM would have any kind of issue with drivers
since these tend not to be updated all too often anyway.

That's what I don't know and what I now believe is at the heart of my
problem. Device Manager event log says the device was configured. The
very next entry says that it did not start, but I don't see anything in
the entry that says why it did not start other than "problem: 9x13"
which I take to mean error code 13.

A Google search yielded about 14 hits for "what is error code 13".
AFAICT, error code 13 covers a multitude of sins. If I understood the
various hits, there's a problem (corrupted) in the system files, but no
clear fix unless I wish to trust an unknown app designed to fix error
13 problems. No thanks on that option.

I think I've already tried the suggestion in another of the hits from
Google - use Device Manager to remove the problematic device and then
do a find new hardware. I'll have to re-try that because I may have
done the sequence out of order.

On Thu, 11 Jun 2015 09:56:59 -0700, Stormin' Norman wrote:

Is it an IDE or SATA drive. The cable may just need to be reseated. Bios
may see it, but if the data contacts aren't connecting, Windows may not
see it.
That would be my first thing troubleshooting.

Good to see us old timers focusing on the basics. Next thing to try
would be connecting a different drive if one is readily available.

Can it boot from the device? Something like Memtest86+.

--
Faster, cheaper, quieter than HS2
and built in 5 years;
UKUltraspeed http://www.500kmh.com/

Char Jackson wrote:

On Thu, 11 Jun 2015 15:31:17 +0000 (UTC), "Yes"

-- snipped --

The CD-ROM is listed in BIOS. In fact, I changed it to be the first
bootable device in hopes that that would force Windows to recognize
it when the Windows OS kicks in. That didn't work out, however.
Windows booted up but the drive was not recognized.

I have gone back to the event logs for this device. As a practical
matter, it seems that there are only two entries of note.

The first entry has the description "device configured (cdrom.inf)".
Its content:

Device
IDE\CdRomASUS_DRW-24B1ST___i_____________________1.00____\5&15956494
&0&1 .0.0 was configured.

Driver Name: cdrom.inf
Class Guid: {4D36E965-E325-11CE-BFC1-08002BE10318}
Driver Date: 06/21/2006
Driver Version: 6.3.9600.16384
Driver Provider: Microsoft
Driver Section: cdrom_install
Driver Rank: 0xFF0004
Matching Device Id: GenCdRom
Outranked Drivers: cdrom.inf:GenCdRom:00FF2000
Device Updated: false


The second entry has the description "Device not started (cdrom)".

Device
IDE\CdRomASUS_DRW-24B1ST___i_____________________1.00____\5&15956494
&0&1 .0.0 had a problem starting.

Driver Name: cdrom.inf
Class Guid: {4D36E965-E325-11CE-BFC1-08002BE10318}
Service: cdrom
Lower Filters:
Upper Filters:
Problem: 0x13
Status: 0x0


If I understand correctly, the drive is recognized by the BIOS but not
displayed in Windows Explorer. There are two intermediate locations,
midway between those two: Device Manager and Disk Management. What do
both of those locations show? The drive has to be visible in both of
those locations, and it should have some clues there, as well.

Also, where are you seeing the "outranked drivers" message? That
sounds like a clue.

Lastly, in Device Manager, do you see phantom CD drives when you
choose to display hidden devices?

Yes - the drive is recognized in BIOS but not displayed in Windows
Explorer.

wrt Device Manager, the device shows up. Right clicking on the icon
and selecting Properties then IIRC details is the source of the
material I posted about the events for the drive.

wrt Disk Management, the drive does not show up there even after
selecting for hidden devices.

Neil wrote:

On 6/11/2015 11:31 AM, Yes wrote:
I have gone back to the event logs for this device. As a practical
matter, it seems that there are only two entries of note.

[...]


The second entry has the description "Device not started (cdrom)".

Device
IDE\CdRomASUS_DRW-24B1ST___i_____________________1.00____\5&15956494
&0&1 .0.0 had a problem starting.

Driver Name: cdrom.inf
Class Guid: {4D36E965-E325-11CE-BFC1-08002BE10318}
Service: cdrom
Lower Filters:
Upper Filters:
Problem: 0x13
Status: 0x0

This is the entry that gets me to raise my eyebrows...

* When you look at your CD drive in Device Manager, what do you see?

* If you start Task Manager, do you see a running service for the CD
ROM?

* Have you looked in your System Services to see if the CD drive is
set to start automatically (depending on the drive, there may not be
an option)?

wrt Device Manager, it appears as an entry underneath the line
"DVD/CD-ROM drives"

wrt Task Manager, I do not see a running service for the CD ROM. This
is consistent with Device Manager's statement that the device had a
problem starting

wrt System Services (via Control Panel), I did not find any entry that
said it was for the CD-ROM. I visually scanned the entries after
sorting them on the startup type column (automatic, disabled, manual)
and by name. That was the extent of what I could understand. Nor did
I notice any service by way of Task Manager identified as CD-Rom.

On 6/11/2015 3:47 PM, Yes wrote:
[...]
wrt Device Manager, the device shows up. Right clicking on the icon
and selecting Properties then IIRC details is the source of the
material I posted about the events for the drive.

I ran a search for the error "0x13" for your particular drive and found
someone that had the same problem and fixed it. Since your listing has
the same categories without data values, it might be worth a try.

http://answers.microsoft.com/en-us/w...4-f35f9f28ee3e

--
Best regards,

Neil

On Thu, 11 Jun 2015 19:47:17 +0000 (UTC), "Yes"
wrote:

Char Jackson wrote:

On Thu, 11 Jun 2015 15:31:17 +0000 (UTC), "Yes"

-- snipped --

The CD-ROM is listed in BIOS. In fact, I changed it to be the first
bootable device in hopes that that would force Windows to recognize
it when the Windows OS kicks in. That didn't work out, however.
Windows booted up but the drive was not recognized.

I have gone back to the event logs for this device. As a practical
matter, it seems that there are only two entries of note.

The first entry has the description "device configured (cdrom.inf)".
Its content:

Device
IDE\CdRomASUS_DRW-24B1ST___i_____________________1.00____\5&15956494
&0&1 .0.0 was configured.

Driver Name: cdrom.inf
Class Guid: {4D36E965-E325-11CE-BFC1-08002BE10318}
Driver Date: 06/21/2006
Driver Version: 6.3.9600.16384
Driver Provider: Microsoft
Driver Section: cdrom_install
Driver Rank: 0xFF0004
Matching Device Id: GenCdRom
Outranked Drivers: cdrom.inf:GenCdRom:00FF2000
Device Updated: false


The second entry has the description "Device not started (cdrom)".

Device
IDE\CdRomASUS_DRW-24B1ST___i_____________________1.00____\5&15956494
&0&1 .0.0 had a problem starting.

Driver Name: cdrom.inf
Class Guid: {4D36E965-E325-11CE-BFC1-08002BE10318}
Service: cdrom
Lower Filters:
Upper Filters:
Problem: 0x13
Status: 0x0


If I understand correctly, the drive is recognized by the BIOS but not
displayed in Windows Explorer. There are two intermediate locations,
midway between those two: Device Manager and Disk Management. What do
both of those locations show? The drive has to be visible in both of
those locations, and it should have some clues there, as well.

Also, where are you seeing the "outranked drivers" message? That
sounds like a clue.

Lastly, in Device Manager, do you see phantom CD drives when you
choose to display hidden devices?

Yes - the drive is recognized in BIOS but not displayed in Windows
Explorer.

wrt Device Manager, the device shows up. Right clicking on the icon
and selecting Properties then IIRC details is the source of the
material I posted about the events for the drive.

wrt Disk Management, the drive does not show up there even after
selecting for hidden devices.

I assume you meant to swap Device Manager and Disk Management, above. Hidden
devices applies to Device Manager.

I was really expecting the drive to show up in Device Manager with a yellow
exclamation mark and a note about how it couldn't start. I'm somewhat
surprised that it's visible in Disk Management but not in Device Manager.
Usually, it's the other way around.

I just saw the link in another post about removing any entries for upper and
lower filters, so that's where I'd go next.

On 6/11/2015 4:04 PM, Yes wrote:
Neil wrote:

On 6/11/2015 11:31 AM, Yes wrote:
I have gone back to the event logs for this device. As a practical
matter, it seems that there are only two entries of note.

[...]


The second entry has the description "Device not started (cdrom)".

Device
IDE\CdRomASUS_DRW-24B1ST___i_____________________1.00____\5&15956494
&0&1 .0.0 had a problem starting.

Driver Name: cdrom.inf
Class Guid: {4D36E965-E325-11CE-BFC1-08002BE10318}
Service: cdrom
Lower Filters:
Upper Filters:
Problem: 0x13
Status: 0x0

This is the entry that gets me to raise my eyebrows...

* When you look at your CD drive in Device Manager, what do you see?

* If you start Task Manager, do you see a running service for the CD
ROM?

* Have you looked in your System Services to see if the CD drive is
set to start automatically (depending on the drive, there may not be
an option)?

wrt Device Manager, it appears as an entry underneath the line
"DVD/CD-ROM drives"

wrt Task Manager, I do not see a running service for the CD ROM. This
is consistent with Device Manager's statement that the device had a
problem starting

wrt System Services (via Control Panel), I did not find any entry that
said it was for the CD-ROM. I visually scanned the entries after
sorting them on the startup type column (automatic, disabled, manual)
and by name. That was the extent of what I could understand. Nor did
I notice any service by way of Task Manager identified as CD-Rom.

See the link in my other post. If the registry has entries that the
driver doesn't understand (or expects some values to be assigned), it
may not load properly, resulting in what you're going through.

--
Best regards,

Neil

Neil wrote:

On 6/11/2015 3:47 PM, Yes wrote:
[...]
wrt Device Manager, the device shows up. Right clicking on the icon
and selecting Properties then IIRC details is the source of the
material I posted about the events for the drive.

I ran a search for the error "0x13" for your particular drive and
found someone that had the same problem and fixed it. Since your
listing has the same categories without data values, it might be
worth a try.


http://answers.microsoft.com/en-us/w...4-f35f9f28ee3e

Thanks. I've discovered I've muddied the waters. I've been thinking
decimal. What I thought was "error code 13" is probably actually
"error code 19" - I'm now assuming that 0x13 is hexadecimal. Revising
my Google search with error code number 19 produced hits much more in
line with the device (CD-ROM). The problem still deals with corruption
in the registry files, and it's still tedious to fix but the answers to
resolve the problem fit more than the ones for an "error code 13". I
only realized this when I reviewed a hardware diagnostic I ran a few
minutes ago.

In fact, the 3rd or 4th paragraph in the link you provide references
error code 19. Perhaps back to remedial math for me :-)

Char Jackson wrote:

On Thu, 11 Jun 2015 19:47:17 +0000 (UTC), "Yes"
wrote:

Char Jackson wrote:

On Thu, 11 Jun 2015 15:31:17 +0000 (UTC), "Yes"

-- snipped --

The CD-ROM is listed in BIOS. In fact, I changed it to be the
first bootable device in hopes that that would force Windows to
recognize it when the Windows OS kicks in. That didn't work
out, however. Windows booted up but the drive was not
recognized.
I have gone back to the event logs for this device. As a
practical matter, it seems that there are only two entries of
note.
The first entry has the description "device configured
(cdrom.inf)". Its content:

Device

IDE\CdRomASUS_DRW-24B1ST___i_____________________1.00____\5&15956494
&0&1 .0.0 was configured.
Driver Name: cdrom.inf
Class Guid: {4D36E965-E325-11CE-BFC1-08002BE10318}
Driver Date: 06/21/2006
Driver Version: 6.3.9600.16384
Driver Provider: Microsoft
Driver Section: cdrom_install
Driver Rank: 0xFF0004
Matching Device Id: GenCdRom
Outranked Drivers: cdrom.inf:GenCdRom:00FF2000
Device Updated: false


The second entry has the description "Device not started
(cdrom)".
Device

IDE\CdRomASUS_DRW-24B1ST___i_____________________1.00____\5&15956494
&0&1 .0.0 had a problem starting.
Driver Name: cdrom.inf
Class Guid: {4D36E965-E325-11CE-BFC1-08002BE10318}
Service: cdrom
Lower Filters:
Upper Filters:
Problem: 0x13
Status: 0x0


If I understand correctly, the drive is recognized by the BIOS but
not displayed in Windows Explorer. There are two intermediate
locations, midway between those two: Device Manager and Disk
Management. What do both of those locations show? The drive has to
be visible in both of those locations, and it should have some
clues there, as well.
Also, where are you seeing the "outranked drivers" message? That
sounds like a clue.

Lastly, in Device Manager, do you see phantom CD drives when you
choose to display hidden devices?

Yes - the drive is recognized in BIOS but not displayed in Windows
Explorer.

wrt Device Manager, the device shows up. Right clicking on the icon
and selecting Properties then IIRC details is the source of the
material I posted about the events for the drive.

wrt Disk Management, the drive does not show up there even after
selecting for hidden devices.

I assume you meant to swap Device Manager and Disk Management, above.
Hidden devices applies to Device Manager.

I was really expecting the drive to show up in Device Manager with a
yellow exclamation mark and a note about how it couldn't start. I'm
somewhat surprised that it's visible in Disk Management but not in
Device Manager. Usually, it's the other way around.

I just saw the link in another post about removing any entries for
upper and lower filters, so that's where I'd go next.

No, the drive is not visible in the Disk Management pane and of course
not in Windows Explorer either. The device is visible in Device
Manager under the category CD-ROM drive IIRC. That entry is the source
for the info I posted. Like you, I would have expected ti to have that
yellow exclamation point, but it didn't.

I've discovered that I made a big mistake wrt to the error code. I
finally found and ran diagnostic software that prints info about my
hardware. In the printout, it notes the problem is "error code 19" not
"error code 13" as I had originally thought. I treated "0x13" as
decimal rather than hexidecimal. That mistake sent me down the wrong
path. The problem still involves corrupt registry values but of a
different sort if that makes sense. The link provided by Neil
references it as error code 19 even.

Rodney Pont wrote:

On Thu, 11 Jun 2015 09:56:59 -0700, Stormin' Norman wrote:

Is it an IDE or SATA drive. The cable may just need to be
reseated. Bios may see it, but if the data contacts aren't
connecting, Windows may not see it.
That would be my first thing troubleshooting.

Good to see us old timers focusing on the basics. Next thing to try
would be connecting a different drive if one is readily available.

Can it boot from the device? Something like Memtest86+.

Haven't gotten that far. It's beginning to look more and more that for
whatever reason the registry files for the device are corrupted. Also,
the error code for the problem is number 19. I treated "0x13" as a
decimal number. It took looking at a diagnostic printout to realize
that I forgot to treat it as hexadecimal and convert "0x13" to 19
decimal. The link in Neil's post is clear about that. As a
cross-confirmation, the diagnostic sw I used stated the error code
number was 19. And my revised Google search using that number gave
hits that are specifically reference CD-ROM drives. So I have more
rabbit holes to go down, but there does look to be light at the end of
the tunnel.

Yes wrote:


The next possibility on my checklist regards Microsoft's Windows 10
Update offer.

Removing that is addressed here.

http://www.howtogeek.com/218856/how-...fication-tray/

Paul

Paul wrote:

Yes wrote:


The next possibility on my checklist regards Microsoft's Windows 10
Update offer.

Removing that is addressed here.


http://www.howtogeek.com/218856/how-...fication-tray/

Paul

Thanks. I had noticed the GWX thing in Task Manager and did a quick
look about it. For the moment, because in and of itself it does not
appear to be related to my current problem I've put dealing with it on
the backburner. FWIW, I only installed the Win 10 update because the
literature suggested that I'm keeping my options open without 100%
committing to actually installing it. That's fine by me.

The MS Win 10 forum has yet to answer a question I asked there about
the licensing, which is what I really want to find out. Namely, in my
case I chose to buy the Retail edition of Windows 64-bit Pro 8.1
because I did not want to be hassled moving the OS to a new machine (or
perhaps upgrading pieces of my pc). My question in Microsoft's forum
was about whether I would still have the same licensing provisions of
my retail edition if I were to upgrade.

An upgrade is 'nice', but IMO it's useless to me if I do it and then
get told oh, by the way, this upgrade only upgrades your OS and you
have to buy a new license if you want to move your OS to a new machine.
I further asked if it will be available on DVD or at least can be
burned to DVD for whenever I do move to a new pc. The only answer I've
gotten was - we don't know! That was about two or three weeks ago.

Yes wrote:
Paul wrote:

Yes wrote:

The next possibility on my checklist regards Microsoft's Windows 10
Update offer.
Removing that is addressed here.


http://www.howtogeek.com/218856/how-...fication-tray/
Paul

Thanks. I had noticed the GWX thing in Task Manager and did a quick
look about it. For the moment, because in and of itself it does not
appear to be related to my current problem I've put dealing with it on
the backburner. FWIW, I only installed the Win 10 update because the
literature suggested that I'm keeping my options open without 100%
committing to actually installing it. That's fine by me.

The MS Win 10 forum has yet to answer a question I asked there about
the licensing, which is what I really want to find out. Namely, in my
case I chose to buy the Retail edition of Windows 64-bit Pro 8.1
because I did not want to be hassled moving the OS to a new machine (or
perhaps upgrading pieces of my pc). My question in Microsoft's forum
was about whether I would still have the same licensing provisions of
my retail edition if I were to upgrade.

An upgrade is 'nice', but IMO it's useless to me if I do it and then
get told oh, by the way, this upgrade only upgrades your OS and you
have to buy a new license if you want to move your OS to a new machine.
I further asked if it will be available on DVD or at least can be
burned to DVD for whenever I do move to a new pc. The only answer I've
gotten was - we don't know! That was about two or three weeks ago.

"I chose to buy the Retail edition of Windows 64-bit Pro 8.1"

1) The terms for Retail (a higher price version of the OS), allow
moving the installation to another machine.

2) Once the OS is moved, you can upgrade to Win10 64-bit Pro

3) The Pro edition will have some slight control over Windows Update
(defer update), but I haven't seen details of how it'll work.

Media will be available in the fullness of time. Media was
available for the older OSes (Win7 images from Digital River,
Win8 images via Microsoft media creator, and so on). There will
be some solution for Win10, but we'll have to wait to find
out. That applies only to desktops. If you buy a tablet
with TPM/secure boot, don't expect media. The old "installation"
model, only exists for desktops/laptops/traditional computers.

http://www.newegg.com/Product/Produc...82E16832588491

There is also supposed to be some provision for clean installing
Win10, using the free upgrade path. But I don't know the details,
and how that will be enforced. Ideally, the Win10 installer
would just accept a Win7 SP1 key or a Win8.1 key, but we don't
know that yet. The thing is, existence of media, is no "proof
of purchase" at all. Only the license key has value, and
provides trace-ability.

The sad part, is most of the good info is coming from a
single MVP in the Answers forum. As if he has been
couched by Microsoft employees with the answers. I would
prefer if a Microsoft.com page would state these tidbits
as "facts". I don't want to say in an answer, "well,
I heard in the bar, that we won't have to pay taxes
any more". This stuff should really be traceable to
a Microsoft web page, as "policy". Not as "hints"
and "whiffs". I would have to go running all over,
to get the latest "he said she said hint", to answer
all your questions. And that's a damn poor way to run
a business.

Paul

Yes wrote:
Neil wrote:

On 6/11/2015 3:47 PM, Yes wrote:
[...]
wrt Device Manager, the device shows up. Right clicking on the icon
and selecting Properties then IIRC details is the source of the
material I posted about the events for the drive.

I ran a search for the error "0x13" for your particular drive and
found someone that had the same problem and fixed it. Since your
listing has the same categories without data values, it might be
worth a try.


http://answers.microsoft.com/en-us/w...4-f35f9f28ee3e

Thanks. I've discovered I've muddied the waters. I've been thinking
decimal. What I thought was "error code 13" is probably actually
"error code 19" - I'm now assuming that 0x13 is hexadecimal. Revising
my Google search with error code number 19 produced hits much more in
line with the device (CD-ROM). The problem still deals with corruption
in the registry files, and it's still tedious to fix but the answers to
resolve the problem fit more than the ones for an "error code 13". I
only realized this when I reviewed a hardware diagnostic I ran a few
minutes ago.

In fact, the 3rd or 4th paragraph in the link you provide references
error code 19. Perhaps back to remedial math for me :-)

But you already showed us, in your pasted info, you
have no UpperFilter. Which is why I didn't need to
give an UpperFilter recipe or recommend the
Microsoft Fixit for optical drives (as it does the
UpperFilter cleanup for you).

You posted...

Lower Filters:
Upper Filters:

so there doesn't appear to be a third-party UpperFilter
in place.

Paul

Paul wrote:

Yes wrote:
Paul wrote:

Yes wrote:

The next possibility on my checklist regards Microsoft's
Windows 10 Update offer.
Removing that is addressed here.



http://www.howtogeek.com/218856/how-...fication-tray/
Paul

Thanks. I had noticed the GWX thing in Task Manager and did a quick
look about it. For the moment, because in and of itself it does not
appear to be related to my current problem I've put dealing with it
on the backburner. FWIW, I only installed the Win 10 update
because the literature suggested that I'm keeping my options open
without 100% committing to actually installing it. That's fine by
me.

The MS Win 10 forum has yet to answer a question I asked there about
the licensing, which is what I really want to find out. Namely, in
my case I chose to buy the Retail edition of Windows 64-bit Pro 8.1
because I did not want to be hassled moving the OS to a new machine
(or perhaps upgrading pieces of my pc). My question in Microsoft's
forum was about whether I would still have the same licensing
provisions of my retail edition if I were to upgrade.

An upgrade is 'nice', but IMO it's useless to me if I do it and then
get told oh, by the way, this upgrade only upgrades your OS and you
have to buy a new license if you want to move your OS to a new
machine. I further asked if it will be available on DVD or at
least can be burned to DVD for whenever I do move to a new pc. The
only answer I've gotten was - we don't know! That was about two or
three weeks ago.

"I chose to buy the Retail edition of Windows 64-bit Pro 8.1"

1) The terms for Retail (a higher price version of the OS), allow
moving the installation to another machine.

2) Once the OS is moved, you can upgrade to Win10 64-bit Pro

3) The Pro edition will have some slight control over Windows Update
(defer update), but I haven't seen details of how it'll work.

Media will be available in the fullness of time. Media was
available for the older OSes (Win7 images from Digital River,
Win8 images via Microsoft media creator, and so on). There will
be some solution for Win10, but we'll have to wait to find
out. That applies only to desktops. If you buy a tablet
with TPM/secure boot, don't expect media. The old "installation"
model, only exists for desktops/laptops/traditional computers.

http://www.newegg.com/Product/Produc...82E16832588491

There is also supposed to be some provision for clean installing
Win10, using the free upgrade path. But I don't know the details,
and how that will be enforced. Ideally, the Win10 installer
would just accept a Win7 SP1 key or a Win8.1 key, but we don't
know that yet. The thing is, existence of media, is no "proof
of purchase" at all. Only the license key has value, and
provides trace-ability.

The sad part, is most of the good info is coming from a
single MVP in the Answers forum. As if he has been
couched by Microsoft employees with the answers. I would
prefer if a Microsoft.com page would state these tidbits
as "facts". I don't want to say in an answer, "well,
I heard in the bar, that we won't have to pay taxes
any more". This stuff should really be traceable to
a Microsoft web page, as "policy". Not as "hints"
and "whiffs". I would have to go running all over,
to get the latest "he said she said hint", to answer
all your questions. And that's a damn poor way to run
a business.

Paul

I hadn't thought about moving the 8.1 version and then upgrading. The
question mark is simply when I happen to do so. I seem to keep my OS
longer than I keep my existing pc :-), so I could very well upgrade my
pc three years down the road. Would I be able to move the 'free'
Windows 10 upgrade that had been provided for my retail edition Windows
8.1. The upgrade is supposed to be like to like, which theoretically
my upgrade should be to the Windows 10 Pro with the 'retail' license
provision to move it to new machine without having to purchase a new
license. I just would like Microsoft to come clean on that detail.

Currently I plan to stay with a desktop.