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

Paul wrote:

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

That's where thing go wonky. I followed up on the link Neil posted.
When I went to the registry entry for the cd-rom device
(4D36E965-E325-11CE-BFC1-08002BE10318), the registry enty had a value
for lower filters. Following the instructions in the link, I deleted
that one entry, closed the registry and restarted windows. My pc now
recognizes the CD-ROM device and it shows up in Windows Explorer.
Thank God.

I have no idea why there was the discrepancy, but there was. At least
for the near term I have my CD-ROM/DVD drive back. Later on I might
buy a replacement, maybe upgrade to one of the blu-ray drives. That's
a choice for a later day ;-)

Yes wrote:


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.

Now, see, that's the problem with the freaking upgrade matrix.

See how many combinations you can throw at it ?

Theoretically, the free upgrade only lasts for a year.

And a hint was, that you would be able to use media
to do a clean install (somehow that copy of free Win10 knows
which Win 8.1 license key "qualified it").

Now when we combine those two, what is the answer ?

Don't know. In three years time, it'll either work...
or it won't work. Or it'll cost you $150.00. Now what
do you think would happen ? Would it cost you $0 ?
Or would it cost you $150.00 ? And how much support
do you think you'd get from Microsoft, to make the
$0 option work ?

When you download a free copy of Win10, to a qualifying
Win 8.1 Pro Retail machine, does the new copy become "retail" ?
It is an "upgrade" (must drag around qualifying OS with it) ?
Presumably all these things matter to "The Matrix", but
even the Matrix is a bit fuzzy right now. And I have to
wait for that guy in the bar, to make up a "suitable story".

Paul

Yes wrote:
Paul wrote:

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

That's where thing go wonky. I followed up on the link Neil posted.
When I went to the registry entry for the cd-rom device
(4D36E965-E325-11CE-BFC1-08002BE10318), the registry enty had a value
for lower filters. Following the instructions in the link, I deleted
that one entry, closed the registry and restarted windows. My pc now
recognizes the CD-ROM device and it shows up in Windows Explorer.
Thank God.

I have no idea why there was the discrepancy, but there was. At least
for the near term I have my CD-ROM/DVD drive back. Later on I might
buy a replacement, maybe upgrade to one of the blu-ray drives. That's
a choice for a later day ;-)

So the thing that produced that information, lied to you.

I must keep this in mind the next time.

You can get filter info from the Registry. You can get
filter info from devcon64.

This is what the output of devcon looks like. You use
devcon64 on a 64 bit OS (a hard to get tool). You use
devcon on a 32 bit OS. Notice how, in theory, the filters
will get listed for you.

devcon stack gencdrom

IDE\CDROMname_____CDRW121032______1.08\5&60546BC &0&0.0.0
Name: name CDRW121032
Setup Class: {4D36E965-E325-11CE-BFC1-08002BE10318} CDROM
Upper filters:
driver name
Controlling service:
cdrom
Lower filters:
driver name
1 matching device(s) found.

So where ever that info came from in this case, don't
use it next time :-)

Also, if you ever run into that Filter again,
take note of what software is using it. In case
something is re-installing that on you. For UpperFilters,
there is GearAspi and Roxio, as examples of
sources of breakage. I don't know what would be
using a lowerfilter.

You can see more examples of filter usage, here.

https://forum.slysoft.com/showthread...-original-disc

Paul

Paul wrote:

Yes wrote:
Paul wrote:

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

That's where thing go wonky. I followed up on the link Neil posted.
When I went to the registry entry for the cd-rom device
(4D36E965-E325-11CE-BFC1-08002BE10318), the registry enty had a
value for lower filters. Following the instructions in the link, I
deleted that one entry, closed the registry and restarted windows.
My pc now recognizes the CD-ROM device and it shows up in Windows
Explorer. Thank God.

I have no idea why there was the discrepancy, but there was. At
least for the near term I have my CD-ROM/DVD drive back. Later on
I might buy a replacement, maybe upgrade to one of the blu-ray
drives. That's a choice for a later day ;-)

So the thing that produced that information, lied to you.

I must keep this in mind the next time.

You can get filter info from the Registry. You can get
filter info from devcon64.

This is what the output of devcon looks like. You use
devcon64 on a 64 bit OS (a hard to get tool). You use
devcon on a 32 bit OS. Notice how, in theory, the filters
will get listed for you.

devcon stack gencdrom

IDE\CDROMname_____CDRW121032______1.08\5&60546BC &0&0.0.0
Name: name CDRW121032
Setup Class: {4D36E965-E325-11CE-BFC1-08002BE10318} CDROM
Upper filters:
driver name
Controlling service:
cdrom
Lower filters:
driver name
1 matching device(s) found.

So where ever that info came from in this case, don't
use it next time :-)

Also, if you ever run into that Filter again,
take note of what software is using it. In case
something is re-installing that on you. For UpperFilters,
there is GearAspi and Roxio, as examples of
sources of breakage. I don't know what would be
using a lowerfilter.

You can see more examples of filter usage, here.


https://forum.slysoft.com/showthread...-original-disc

Paul

I wish I could give you better insight because you help out when you
can so often here and in other newsgroups; it's very much appreciated.
Suffice it to say that I believed the output from Device
ManagerPropertiesEvents. Fortunately I noticed that the registry
entry itself did have a "lower filter" field with a value in it. So it
does pay to confirm things if one knows how to do so. The registry is
an area that I try to avoid like the plague because from what I've read
of others' experiences, one mistake and you may as well re-install your
entire OS.

And given my lack of knowledge about the registry, I'm at a loss as to
the procedure to even find what app may have installed the value in a
registry field. ISTM that the value was something like afc. All that
comes to mind with that is American Football Conference :-)

A discouraging note is that just now, when I drilled down in Device
Manager to recreate what I did so that I could post them for you, I
notice that the events tab has not updated its contents to reflect what
I did today 6/11. The events in it still show 6/10 yesterday. That
strikes me as abnormal.

Paul wrote:
Yes wrote:


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.

Now, see, that's the problem with the freaking upgrade matrix.

See how many combinations you can throw at it ?

Theoretically, the free upgrade only lasts for a year.

And a hint was, that you would be able to use media
to do a clean install (somehow that copy of free Win10 knows
which Win 8.1 license key "qualified it").

Now when we combine those two, what is the answer ?

Don't know. In three years time, it'll either work...
or it won't work. Or it'll cost you $150.00. Now what
do you think would happen ? Would it cost you $0 ?
Or would it cost you $150.00 ? And how much support
do you think you'd get from Microsoft, to make the
$0 option work ?

When you download a free copy of Win10, to a qualifying
Win 8.1 Pro Retail machine, does the new copy become "retail" ?
It is an "upgrade" (must drag around qualifying OS with it) ?
Presumably all these things matter to "The Matrix", but
even the Matrix is a bit fuzzy right now. And I have to
wait for that guy in the bar, to make up a "suitable story".

Paul

It is another scenario but most likely destined for failure.

If the Win10 license provided by the upgrade is tied to the device and
stored in the MSFT Windows Store then media created from the Win10 Media
Creation Tool (iso/usb/dvd) would be the source media for later use
- use of a full package product Win10 retail media with its own
provided Win10 key is already a given available route for a new device
and wouldn't be applicable to 'moving' the Win10 license (to do so would
seem insane especially if attempting to use it in 'move' process somehow
accidentally wasted the license and tied to that earlier device).

Since the license is tied to the upgraded device it would seem unlikely
that use of any media available for Win10 would be successful on a
different device without the need to enter an entirely different and
unique product key (again only available on full version purchased product).

Imo, the above makes sense because the upgrade scenario - free for the
life of device remains intact and only for that specific upgraded device
not another device.

It's my understanding that the upgrade will retain the same inherent
type of license (retail license of Win7Sp1/8.1 become retail Win10, OEM
license of 7Sp1/8.1 become OEM Win10)
- note this would be unlike the earlier Media Center
add-Windows-feature which resulted in a retail Window 8/8.1 Pro with
Media Center but like the Pro upgrade from Core where a retail or OEM
Core became a Pro retail.
- The upgraded device and corresponding license's record in the Store
could include a product key (possibly even accessible via a MSFT
account) but would it not make sense for MSFT to tie that product key by
design and protection of their interest to the same device.

I'm not sure how the upgrade tag (prior o/s) is significant after
upgrading but it would seem to be more applicable and could come into
play if returning the device to the prior upgradeable o/s via a restore,
reinstall etc. i.e. give up one (Win10) to get the other (earlier
licensed o/s)- activation then unless key firmware stored (or even with
firmware stored) could require phone activation or human MSFT support.

Lol..nothing precludes some hair-brained 'do-this, do that, voila'
technically feasible not necessary compliant method to use a free
upgrade free meda for a different device new or old without the
necessity of a Win10 product key.

--
...winston
msft mvp consumer apps

Yes wrote:


I wish I could give you better insight because you help out when you
can so often here and in other newsgroups; it's very much appreciated.
Suffice it to say that I believed the output from Device
ManagerPropertiesEvents. Fortunately I noticed that the registry
entry itself did have a "lower filter" field with a value in it. So it
does pay to confirm things if one knows how to do so. The registry is
an area that I try to avoid like the plague because from what I've read
of others' experiences, one mistake and you may as well re-install your
entire OS.

And given my lack of knowledge about the registry, I'm at a loss as to
the procedure to even find what app may have installed the value in a
registry field. ISTM that the value was something like afc. All that
comes to mind with that is American Football Conference :-)

A discouraging note is that just now, when I drilled down in Device
Manager to recreate what I did so that I could post them for you, I
notice that the events tab has not updated its contents to reflect what
I did today 6/11. The events in it still show 6/10 yesterday. That
strikes me as abnormal.

It says here, your LowerFilter is "Arcsoft". Arcsoft is a company,
making many products. Sometimes, the software performs another
function (DVD authoring) and just happens to include a DVD burner
program in the package, and the DVD program busts the optical drive
operation.

http://answers.microsoft.com/en-us/w...e-3b9deabf5e9c

I would prefer these products to just generate an ISO file, and
leave it to the users imagination to find another program. For
some reason, these companies have really bad taste in burner packages,
where ever they are finding them. In the case of Apple iTunes
for Windows, several years ago Apple was including a third-party
burner program, and that needed to be removed from UpperFilters.
The current iTunes has fewer packages, so they're gradually
cleaning up their act.

Paul

Paul wrote:

Yes wrote:


I wish I could give you better insight because you help out when you
can so often here and in other newsgroups; it's very much
appreciated. Suffice it to say that I believed the output from
Device ManagerPropertiesEvents. Fortunately I noticed that the
registry entry itself did have a "lower filter" field with a value
in it. So it does pay to confirm things if one knows how to do so.
The registry is an area that I try to avoid like the plague because
from what I've read of others' experiences, one mistake and you may
as well re-install your entire OS.

And given my lack of knowledge about the registry, I'm at a loss as
to the procedure to even find what app may have installed the value
in a registry field. ISTM that the value was something like afc.
All that comes to mind with that is American Football Conference :-)

A discouraging note is that just now, when I drilled down in Device
Manager to recreate what I did so that I could post them for you, I
notice that the events tab has not updated its contents to reflect
what I did today 6/11. The events in it still show 6/10 yesterday.
That strikes me as abnormal.

It says here, your LowerFilter is "Arcsoft". Arcsoft is a company,
making many products. Sometimes, the software performs another
function (DVD authoring) and just happens to include a DVD burner
program in the package, and the DVD program busts the optical drive
operation.


http://answers.microsoft.com/en-us/w...e-3b9deabf5e9c

I would prefer these products to just generate an ISO file, and
leave it to the users imagination to find another program. For
some reason, these companies have really bad taste in burner packages,
where ever they are finding them. In the case of Apple iTunes
for Windows, several years ago Apple was including a third-party
burner program, and that needed to be removed from UpperFilters.
The current iTunes has fewer packages, so they're gradually
cleaning up their act.

Paul

So that was the one that was causing the problem, LOL. In May I bought
a KWorld TV tuner on a USB stick and installed it. ArcSoft wrote the
software titled TotalMedia for the manufacturer KWorld. I installed it
on both my pc and my laptop.

** - OT/Rant - **
I was very disappointed with the performance of the TV tuner and of the
software that came with it. Had I known the limitations - I'm talking
about in general, not what happened here specifically - of the
software, I would have absolutely ignored it to begin with and never
installed it.

IMO that software package is a piece of crap; it has limited
functionality, is a resource hog, always wants to phone home and is a
nightmare to navigate around its TV menu options, which is the reason
I'm using it in the first place. The hardware (USB TV tuner) works,
but I had to connect a more robust external TV antenna to it to pull in
stations. And most perplexingly it failed to pull in two stations that
I could watch by way of my old TV setup at the same physical location,
and I have yet to find a way to force it to scan specifically for those
two individual stations. You have to do a new scan AFAICT, but that
still hasn't pulled in those two stations.

I used Windows Uninstall Programs to uninstall TotalMedia on my pc.
Obviously, it was not absolutely successful as events have
demonstrated. I have not yet uninstalled it on my laptop.

I'll have to keep this fiasco - about the missing drive - in mind
because I've been looking for alternative software to use on my laptop
to replace ArcSoft's TotalMedia. VLC is reported to have been
successfully used with the tuner, and I just came across another
program SmartDVB that is in beta testing.

Unfortunately, no one in the VLC forum has responded to my question -
posted about a month ago now, and I haven't found documentation about
how to configure VLC to find and display streams. It can be done; I
just haven't found the documentation yet to actually do it.

I just ran across SmartDVB a few days ago and haven't done much
research yet. It appears to offer many options, but setting it up is
quite complex when you don't know the terminology and navigating within
the program. At present its web site seems to have very little
documentation such as manuals or user instructions. The installed
program has a help file, but I'd rather study it without having to run
the program.

P.S.: I contacted both ArcSoft and Kworld directly in May. ArcSoft
answered within a day or so recommending that I contact KWorld because
ArcSoft wrote TotalMedia at the direction of KWorld. KWorld has yet to
respond to my inquiry, so that's been about 30 days now (as of 6/12).